Overview
Use normalized codes, apply fixes, requeue with backoff, and replay from DLQ.
Prerequisites
None.
Permissions required
Downloads & Templates
Steps (3)
-
1
Open Error Console
Monitoring → Errors. Filter by channel, provider, or reason (e.g., template_not_approved, missing_opt_in).
Tips
—
Validation
—
Success criteria
—
-
2
Apply the suggested fix
Follow guidance per error. When fixed, click **Retry** → PulseGate requeues with exponential backoff.
Tips
—
Validation
—
Success criteria
—
-
3
Replay from DLQ (if needed)
For persistent failures moved to DLQ, use **Replay** after remediation; verify rate limits per provider.
Tips
—
Validation
—
Success criteria
- Replayed messages achieve delivery or surface actionable errors only.
About this guide
PulseGate centralizes business messaging for SMS and popular OTT channels including WhatsApp, Facebook Messenger, Instagram DM, and Telegram. Connect providers like Twilio or Meta Cloud API once, then send and receive through a single, normalized interface. PulseGate tracks delivery receipts, applies rate-limit aware retries, and surfaces errors with one-click safe requeue.
Admins manage connectors, numbers/senders, WhatsApp templates, and compliance (opt-in/opt-out, quiet hours). Apps such as LiveConnect and Agent Desk consume clean events and message states without worrying about vendor quirks.
Built for reliability and scale with queues, backoff, DLQs, and health dashboards.