Overview
Route messages by channel, country, category, sender, provider, priority, rate limits, and failover rules.
Prerequisites
- At least one eligible provider connection or workspace-app provider is configured
Permissions required
Steps (4)
-
1
Create the routing profile
Define the workspace routing profile used by message orchestration.
Tips
Validation
Success criteria
-
2
Add destinations and rules
Configure channel/provider destinations and ordered rules for message context.
Tips
Validation
Success criteria
-
3
Configure failover and rate limits
Add failover policy and provider/routing rate-limit controls for eligible traffic.
Tips
Validation
Success criteria
-
4
Verify route decisions
Send representative messages and inspect route decisions, provider attempts, and final delivery state.
Tips
Validation
Success criteria
About this guide
PulseGate is the communications control plane for Velaxe workspaces. Applications send business communication through trusted contracts while PulseGate resolves recipients and templates, applies authorization and policy, routes delivery, records message state, and publishes clean events.
Operations teams get a dedicated Messenger workspace for conversations, contacts, campaigns, approvals, failed messages, and media, plus administration for provider connections, sender identities, routing, templates, consent, suppression, quiet hours, cost rules, audit, and reports.
Durable workers handle dispatch, schedules, reminders, campaigns, provider webhooks, retries, reconciliation, metrics, retention, exports, media processing, and operational recovery. Handler, RCP, Bridge v2, EventBus, and ContextResolver contracts keep workspace integrations governed and source-aware.