Channel Dispatch (A5)

The layer that actually sends: SMS, WhatsApp, RCS, app push, in-app. A dispatcher, deliberately not an agent.

Vertical: BTL · Status: ⬜ Planned Back to BTL · workflows index

---

Trigger

Called by every Program workflow. Nothing in BTL or Program works without it.

Flow

message + audience from a Program workflow
        |
suppression: DND - opt-out - frequency cap - quiet hours
        |
channel selection by reachability + cost
        |
rate-limited dispatch      (Clevertap | Netcore | direct)
        |
delivery receipts -> retry or fall back to next channel
        |
per-message audit record

Why this is not an agent

Routing rules, rate limits, retries and suppression are entirely deterministic - and in a regulated context each message needs to be auditable and reproducible.

Putting an LLM in this path adds cost and removes reproducibility. The roadmap draws it as A5; it should be built as a dispatcher.

Agents involved

None. Copy arrives already generated and already compliance-reviewed.

Blocked on

A channel provider (Clevertap, Netcore or direct), plus a consent and suppression store.

Consent, DND and quiet hours are absent from the roadmap entirely and are regulatory requirements for Indian outbound, not features.

Roadmap source

Page 2 - A5 -> Rollout -> SMS / WA / RCS / App push / In-App | Clevertap - Netcore - Humanoid — see roadmap_ref_extracted.md.