​

MENA channels onboarding: WhatsApp and SMS

​

Pick the right channel per market

​

1. Sender and KYC readiness

1. Complete Organization KYC onboarding — the organization profile, legal entity, and the documents a carrier-facing sender will ask you for. Saudi Arabia and the UAE are the strictest sender-identity regimes in the region; KYC holds there stall both SMS sender-id registration and WhatsApp Business Account review.
2. Check Country capabilities for the exact markets you send into — it tells you whether two-way SMS, voice, and WhatsApp are open per country before you buy numbers or register sender-ids.
3. Register your alphanumeric SMS sender-id per market where you intend to use one. In the GCC this is usually pre-registered with the carrier through your organization documents — budget days to weeks, not hours. In most North African markets sender-id is dynamic or numeric — receivers see a phone number, not a brand. Test sender-id behavior in each market before you bulk-send.
4. For WhatsApp, connect your Business Account in WhatsApp getting started — the WABA review is where KYC and brand pages get re-checked; a mismatch there is the single most common MENA stall.

​

2. WhatsApp — template approval for Arabic-first markets

1. Open the WhatsApp template creation walkthrough — name the template, set the category (MARKETING, UTILITY, AUTHENTICATION), and write the body. Arabic or bilingual Arabic-English templates usually pass review faster than English-only in Gulf markets, because Meta’s reviewers validate against local-language normativity — keep the body human, not transliterated.
2. Use the right script. Meta accepts the Arabic alphabet (plus digits and common punctuation). Avoid mixing scripts inside a single body — right-to-left and left-to-right text re-order unpredictably in variable placeholders. If you must include a Latin product name, put it in a fixed literal, not a {{variable}}.
3. Keep the variable count low. Each added {{n}} is another rejection-review vector; template variable count limits covers the failure shape.
4. Wait for approval before you send — no send path works until the template is APPROVED. Rejection reasons are most often a MISLEADING sample or a variable that does not match the sample — read WhatsApp template troubleshooting before you re-submit.

​

3. SMS — the send path and the errors you will actually see

curl -X POST https://api.orbit.devotel.io/api/v1/messages \
  -H "X-API-Key: dv_live_sk_..." \
  -H "Content-Type: application/json" \
  -d '{
    "to": "+971501234567",
    "body": "Your order has shipped.",
    "channel": "sms"
  }'

​

4. Quiet hours and local compliance pointers

• Quiet hours — define a recipient-local sending window (for example, no marketing SMS 21:00–08:00) per market in Campaign limits and quiet hours. Because quiet hours fail open, an unset window never blocks a send — set the window only for the markets where you want one.
• Country-level requirements — Country requirements lists per-market legal duties (sender registration duties in Saudi, opt-in requirements in Egypt, voice marketing bans in North Africa). These are your obligations to fill in; Orbit’s compliance checklists make the country rules visible without hard-gating them.
• Frequency caps — use Frequency caps to avoid over-sending in markets with low SMS tolerance; caps are tenant-side and default off.
• Consent and DNC — wire opt-out handling through Consent management and DNC scrub where local law requires it.

​

5. Troubleshooting accordions

​

See also

• APAC channels onboarding — the same playbook shape in APAC (LINE / WeChat).
• WhatsApp getting started — the WABA connect path.
• Send and receive messages — the cross-channel send pattern.
• Country capabilities — per-market channel coverage.