Overview
Use routing profiles, rules, destinations, sender identities, pools, failover policy, provider connections, country rules, and rate limits to choose delivery paths.
Problem
Applications should express communication intent without embedding provider or sender selection rules.
Solution
Centralize delivery routing in PulseGate and evaluate the message context against workspace routing configuration.
How it works
Routing can use channel, category, country, sender policy, provider destinations, priority, failover and rate-limit configuration while retaining route-decision history.
Who is this for
Communications Administrator
Platform Operator
Expected outcomes
- Provider and sender selection managed centrally
- Reusable routing policy across trusted application traffic
Key metrics
Security impact
- Routing profiles/rules, provider destinations, sender identities, country policy, rate limits and route decisions · PII: yes where recipients, messaging identities, message content, consent, media, or external identity mappings contain personal data
Compliance
- Routing changes require workspace permissions and remain subject to message authorization and policy
Availability & next steps
Team
Enterprise