Overview
Create and manage the sender identities, registrations, pools, and members used by channel routing.
Prerequisites
Permissions required
Steps (4)
-
1
Create the sender identity
Add the channel-specific sender identity and its operational metadata.
Tips
Validation
Success criteria
-
2
Configure number or registration state
Maintain number registrations and sender verification/registration details where applicable.
Tips
Validation
Success criteria
-
3
Build sender pools when required
Group eligible senders and configure sender-pool members for routing.
Tips
Validation
Success criteria
-
4
Attach routing policy
Use routing rules and destinations to select the appropriate sender for the message context.
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.