Overview
Queue communication requests and channel work, dispatch through a configured routing provider, and reconcile outcomes.
Problem
Campaign and content workflows need reliable queued delivery handoff outside normal browser request execution.
Solution
EngagementHub uses communication request, channel, outbox, attempt and delivery-outcome records around provider handoff.
How it works
A campaign or publishing action creates communication work, the outbox worker claims due records, notification.dispatch hands work to the configured routing provider, and outcomes update request/channel state for operational and analytics use.
Who is this for
Expected outcomes
- Queued delivery handoff outside request processing
- Attempt and outcome history
- Provider routing remains configurable per workspace
Key metrics
Communication outbox rows linked to requests/channels
0 %
100 %
Provider attempts recorded with correlation identifiers
0 %
100 %
Delivery outcomes linked to communication state
0 %
100 %
Gallery
Security impact
- Communication requests, channel records, outbox records, provider references, attempts and outcomes · PII: Recipient identifiers and channel addresses can be included in authorized communication payloads
Compliance
- Workspace-scoped application permissions and trusted execution context
- Operation/resource authorization for application calls
- Auditable workflow, queue, event or interaction records for this use case