Your customer doesn't care
which channel it was.
Email, WhatsApp and SMS against the same contact record, with consent recorded separately for each. Right-to-left languages render properly. You connect WhatsApp and Twilio with your own accounts, so your provider bills you at their rates.
In much of the world, email is the second choice.
If your customers are in Pakistan, India, the Gulf, Latin America or Southeast Asia, WhatsApp is often where business actually happens — and an email-only platform quietly loses those conversations. Western tools treat WhatsApp as an add-on. Regional WhatsApp providers can't do email or deliverability. You end up running both and reconciling by hand.
All three, properly.
Your own authenticated domain, managed DKIM and DMARC, suppression, and one-click unsubscribe.
- Authentication managed for you
- Do-not-send list honoured on every send
- One-click unsubscribe in the header
The official Meta Cloud API on your own account. Author a template, submit it for Meta's review, and track its status from here; approved templates are pickable when you send. Broadcasts to a segment work today.
- Your own Meta account
- Template authoring and submission
- Approval status tracked here
- Broadcast to a segment
Twilio on your own account, with signature-validated inbound and STOP handled automatically.
- Your own Twilio account
- Signature-validated inbound
- STOP handled automatically
Everything arrives in one place.
A WhatsApp message, an SMS reply and an email reply land in the same inbox against the same contact, each classified the same way and ranked by the same priority score.
Inbound WhatsApp or SMS from someone you've never met creates a contact keyed on their phone number and records that they messaged you first — so someone who only ever WhatsApps you still becomes a real customer record.
Consent per channel, because it isn't transferable.
Email consent is not WhatsApp consent, and we don't treat it as if it were. Each channel carries its own consent state with a timestamped, append-only trail. Reachability is tracked separately again — whether we hold an identifier for that channel, and whether it's bounced or suppressed.
Opt-out keywords are honoured on every channel — and not only in English. A recipient replying with an Arabic or Urdu stop word is opted out, which is the difference between compliance and a recipient who believes they opted out while messages keep arriving. STOP and STARTare idempotent, so a repeat doesn't produce contradictory state.
Arabic and RTL, built in.
Arabic, Urdu, Persian and Hebrew render right-aligned in an appropriate font — in the inbox, in previews, and in generated email. One Latin brand name inside an Arabic sentence doesn't flip the whole block.
Where automation stands today.
Automations send email today, triggered by segments, tags, replies, dates or events from your own code. Broadcasts can go out on WhatsApp, and all three channels share the inbox and the contact record.
Automation nodes that send WhatsApp or SMS are not built Roadmap. When one appears in a flow, the run log records it as skipped rather than done, because a silent no-op is how you find out three weeks later.
Multi-channel, mechanically.
Do I need a Meta Business account?
Yes, for WhatsApp Business, and your own Twilio account for SMS. We'll walk you through both.
Can I send WhatsApp marketing messages?
Only within Meta's template rules, which we help you author and submit. Meta approves or rejects — not us.
How is WhatsApp priced?
Your provider bills you directly, per message, at rates that vary by destination country. Email volume is what you buy from us.
What if a provider goes down?
Messages hold and drain as the provider recovers, rather than failing one by one.
Meet people
where they already are.
Email, WhatsApp and SMS against the same contact record, with consent recorded separately for each.