Send across every channel your customers actually use. Replies land in the same unified inbox, threaded against the same contact, classified by the same engine. RTL and Arabic / Urdu / Hindi rendering, native — not bolted on.
Every send is ed.send() with a channel argument. Identical templates, identical webhook surface, identical analytics. Choose the channel — or let the cascade choose for you.
Transactional + marketing on one platform. AWS SES is our sending pool today; the abstraction supports multiple backends so we can add Resend / Postmark fallbacks later.
Direct Meta Cloud API integration — no BSP middleman taking margin. The connection plumbing is live; the template editor + bidirectional inbox view land alongside the unified-inbox UI in the next release.
SMS via Twilio, available as a primary channel or — more commonly — as the cascade fallback when email bounces or a WhatsApp template gets rejected.
Most Western ESPs treat WhatsApp as a $19/month add-on through a partner. We treat it like email — same template editor, same automation engine, same inbox, same analytics. Because in Karachi, São Paulo, Riyadh, and Mumbai it is primary.
Define a cascade per automation: try WhatsApp first, fall back to email if the template is rejected, fall back to SMS if email bounces. Cascade engine is Q4 2026.
order_confirm sent to +92 333····. Quality rating high; immediate delivery; no further channels needed.Arabic, Urdu, Hindi, Hebrew — rendered correctly at every layer (editor, template preview, sent message, unified inbox). Pair messaging with Easypaisa, JazzCash, UPI, or PIX checkout links.
If you already have one with Meta, we connect to it. If you don't, you'll need to provision one — typically Meta verification takes 1–3 business days. We handle the BSP-level setup with Meta directly; you don't need a Wati or Gallabox account.
Today: you write the template, submit to Meta directly via the API. Most approvals come back within an hour. Built-in template editor with policy guardrails is Q3 2026.
Meta charges per conversation (not per message), by destination country, by category. Our pricing passes Meta's cost through with an 8% margin. A US conversation is ~$0.027, a Pakistani conversation is ~$0.005, a Brazilian conversation is ~$0.063. See add-ons for the full rate card.
No — and we won't let you. WhatsApp opt-in is a Meta requirement, not just our policy. We log the opt-in event per contact with timestamp and source; you can export the audit log on demand. Cold WhatsApp outbound gets your number banned by Meta within hours.
The template editor detects language and applies RTL automatically. Mixed-direction content (English brand name in an Arabic message) follows Unicode bidirectional algorithm with explicit isolation marks. WhatsApp itself handles RTL on the device side; we make sure the body we send is well-formed.
Beyond Stripe for global card payments: Easypaisa, JazzCash (Pakistan), UPI, Razorpay (India), PIX (Brazil), bKash, Nagad (Bangladesh), DANA, OVO (Indonesia). We don't process payments — we generate the deep-link or QR code that the rail expects and surface a webhook when payment lands. Most are Q4 2026.
Email Digit stops being three tools the moment you stop using three tools. The cascade, the inbox, the analytics — all unified.