Overview
Hand queued EngagementHub communications to the configured workspace provider that resolves customer preferences and dispatches supported channels.
Capabilities
-
Requires notification.dispatch from the selected provider
-
Uses Platform RCP for trusted same-workspace handoff
-
Queues communication requests and channel records before dispatch
-
Records attempts, provider references and delivery outcomes
-
Maintains correlation and idempotency metadata across retries
Setup Steps (6)
-
1
-
2
-
3
-
4
-
5
-
6
Limitations
-
The configured provider controls channel support and customer preference resolution.
-
EngagementHub hands off queued communication work after its own publication and campaign rules are satisfied.
-
Provider calls remain workspace-scoped through trusted platform transport.
FAQs
What does the Notification Routing Provider integration use?
Hand queued EngagementHub communications to the configured workspace provider that resolves customer preferences and dispatches supported channels.
How is access controlled?
EngagementHub uses workspace-scoped platform identity, configured application/provider grants, operation scopes, and resource authorization appropriate to the integration transport.
Where can administrators inspect activity?
EngagementHub exposes integration, connection, EventBus, webhook, communication and operational records through its Studio and generated operations views.
Pricing
Starter
USD 219.07 / annual
Growth
USD 730.42 / annual
Business
USD 1,460.91 / annual
Enterprise
USD 2,921.89 / annual