How is this different from email marketing?

The recipient can reply, and the platform can cut you off. Consent, timing, and frequency carry real consequences, and a campaign only works if replies land somewhere a person is watching.

Can we upload a list and send to it?

You can import contacts, and a contact with no opt-in basis is excluded from a marketing audience with the reason shown. That refusal protects the number the campaign depends on.

How current are the segments?

They are worked out at the moment the send starts, so the audience is who qualifies then, not who qualified when you drafted it.

Can we run A and B tests?

Yes. A campaign can carry variants, and results are reported split by variant.

What stops us messaging the same person too often?

A per-contact frequency cap over a rolling window, applied across campaigns and sequences, plus quiet hours in the contact's own timezone.

Where do replies to a campaign go?

Into the shared inbox as normal conversations, with a draft already written and the campaign attributed to the contact.

Can we see what a campaign will cost before sending?

Yes. A cost estimate and a send forecast are shown before you approve, and the price Meta reports for each delivered message is recorded afterwards.

Do you support click-to-WhatsApp ads?

Yes. The ad that produced the chat is captured on the first message, usable in a segment, and reportable back to Meta as a conversion.

Can marketing and support share the same contact records?

That is the point. A segment built for a campaign is the same record the person answering the reply is looking at.

Campaigns you can answer, not just send.

A broadcast that produces replies is worth more than one that produces opens, as long as somebody is there to answer them.

Messaging campaigns are marketing sends delivered over WhatsApp, Instagram, Messenger, or Telegram. They read differently because the recipient can reply, which makes consent, timing, and frequency far more consequential than in email, and makes a campaign useless unless the replies land somewhere a person will see them.

What usually goes wrong.

The blast has no return path: Most messaging tools send well and receive badly. Replies arrive in a place nobody is watching, so a campaign that worked looks like a campaign that failed.
Segments live in a different tool from sending: The audience is defined in one system, exported, reshaped, and uploaded into another. By the time it sends, it is describing customers as they were last week.
Consent is treated as paperwork: On email a bad list costs deliverability. On WhatsApp it costs the number. Marketers who have only run email tend to find this out the expensive way.
Nobody can say which spend produced which conversation: Ad reporting stops at the click. What happened in the conversation afterwards, and whether it turned into anything, usually lives nowhere.

What Otobiz does about it.

Segments built where the data already is

Audiences are defined over the same records support works in: channel, tags, lifecycle stage, custom attributes, order behaviour, engagement recency, conversation state, and stored customer facts. Conditions combine with and, or, and not, and the live count updates as you build.

Around thirty condition types across profile, behaviour, and events
And, or, and not nesting, so conditions can be grouped
A live audience count using the same query the send will use

Campaigns with a review step

A campaign moves from draft to review to approval before anything sends. You get a per-recipient render preview, a readiness check, a cost estimate, and a send forecast before you commit, and per-recipient reporting afterwards.

Draft, review, approve, schedule, pause, resume, cancel
Per-recipient preview and readiness report before sending
A and B variants with results split by variant

Consent, pacing, and suppression as defaults

Every recipient is screened for consent and suppression before the send, quiet hours are respected in the contact's own timezone, and per-contact frequency caps stop the same person being messaged repeatedly across campaigns.

Consent recorded per purpose, with the exact wording you showed
Quiet hours, batch size, and interval per channel
Opt-out keywords handled automatically with a confirmation

Replies land where somebody is looking

A campaign reply arrives in the shared inbox as a normal conversation, with a draft already written and the campaign attributed to the contact. Responders and clickers can be saved straight back as a new segment.

Replies threaded into the shared inbox
Responders and clickers savable as a segment
Follow-up campaigns targeted at either group

Multi-step sequences instead of one-off sends

A sequence enrols contacts on a tag, a lifecycle change, or a named event and walks them through timed steps, re-screening each contact at each step for suppression, replies, and frequency.

Started by a tag, a stage change, an event, or by hand
Consent, suppression, and frequency re-checked at every step
Contacts exit on reply or on opt-out

Ad spend tied to the conversations it produced

Create click-to-WhatsApp campaigns, build custom audiences from your segments, and see spend against the conversations and outcomes that followed. Campaigns created here always land paused, so launching spend is a separate decision by a person.

Click-to-WhatsApp campaign creation, always paused on creation
A saved segment pushed to Meta as a custom audience
Daily spend, impressions, clicks, and conversation counts

Search and site performance in the same place

Search Console and analytics connected read-only, so the traffic that produces conversations and the conversations themselves are reported side by side.

Clicks, impressions, position, and top queries
Sessions, engagement, and key events
On-page checks against your own pages

What matters most here.

Common questions

How is this different from email marketing?: The recipient can reply, and the platform can cut you off. Consent, timing, and frequency carry real consequences, and a campaign only works if replies land somewhere a person is watching.
Can we upload a list and send to it?: You can import contacts, and a contact with no opt-in basis is excluded from a marketing audience with the reason shown. That refusal protects the number the campaign depends on.
How current are the segments?: They are worked out at the moment the send starts, so the audience is who qualifies then, not who qualified when you drafted it.
Can we run A and B tests?: Yes. A campaign can carry variants, and results are reported split by variant.
What stops us messaging the same person too often?: A per-contact frequency cap over a rolling window, applied across campaigns and sequences, plus quiet hours in the contact's own timezone.
Where do replies to a campaign go?: Into the shared inbox as normal conversations, with a draft already written and the campaign attributed to the contact.
Can we see what a campaign will cost before sending?: Yes. A cost estimate and a send forecast are shown before you approve, and the price Meta reports for each delivered message is recorded afterwards.
Do you support click-to-WhatsApp ads?: Yes. The ad that produced the chat is captured on the first message, usable in a segment, and reportable back to Meta as a conversion.
Can marketing and support share the same contact records?: That is the point. A segment built for a campaign is the same record the person answering the reply is looking at.