Overview
Route by region/price/quality and auto-failover on error spikes.
Prerequisites
None.
Permissions required
Steps (3)
-
1
Define primary & secondary routes
Routing → Rules → **New**. Select channel (SMS/WhatsApp), region (e.g., US/EU/IN), primary provider and fallback.
Tips
—
Validation
—
Success criteria
—
-
2
Set health & SLO thresholds
Choose error-rate and latency p95 thresholds. Enable **automatic failover** and **auto-rollback** when metrics recover.
Tips
—
Validation
—
Success criteria
—
-
3
Dry-run with canary
Send 5–10% traffic through the new route. Monitor dashboards for 15 minutes; then lift gradually.
Tips
—
Validation
—
Success criteria
- No SLO breach during canary; automatic rollback verified in simulation.
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.