Overview
Create communication requests from engagement activity, queue channel work, dispatch through the configured routing provider, and ingest outcomes.
Prerequisites
- Notification-routing provider configured
- Content/campaign or event activity ready to create communication work
Permissions required
Steps (6)
-
1
Configure the Notification routing & customer preferences provider
Configure the Notification routing & customer preferences provider.
Tips
Validation
Success criteria
-
2
Create campaign asset notification policy or another communication-producing action
Create campaign asset notification policy or another communication-producing action.
Tips
Validation
Success criteria
-
3
Allow EngagementHub to create communication request and request-channel records
Allow EngagementHub to create communication request and request-channel records.
Tips
Validation
Success criteria
-
4
Allow the communication outbox worker to claim due work
Allow the communication outbox worker to claim due work.
Tips
Validation
Success criteria
-
5
Dispatch through notification
Dispatch through notification.dispatch and record provider references/attempts.
Tips
Validation
Success criteria
-
6
Ingest delivery outcomes and review communication/channel status
Ingest delivery outcomes and review communication/channel status.
Tips
Validation
Success criteria
- Communication requests, attempts and delivery outcomes are correlated and visible in operations data.
About this guide
EngagementHub gives workspace teams one governed system for news, announcements, events, promotions and coordinated campaigns. Content shares a common publishing model for titles, summaries, bodies, categories, tags, calls to action, media references, attachments, visibility, placements, related records, versions and publication state.
Editorial work moves through configurable review and approval steps before immediate or scheduled publication. The publication engine maintains schedules, expiry, feed indexing and per-viewer feed state. Events add occurrences, registration windows, capacity, waitlists, attendance, reminders and feedback. Promotions add codes, claims and claim lifecycle records. Campaigns add goals, channels, assets, stages, runs and measurable outcomes.
Audience targeting is provider-driven. EngagementHub discovers applications that advertise the audience-provider contract, loads catalogues and categories, establishes least-privilege provider access, and freezes returned members into reproducible snapshots. Secure media is delegated to the configured file-storage provider, while queued communication requests are handed to the configured notification-routing provider.
For application interoperability, EngagementHub exposes a canonical capability runtime across Handler, RCP and Bridge v2, implements the eight-operation ContextResolver contract, publishes domain events through the platform EventBus, consumes trusted project-reference and email-delivery events, and supports signed outbound webhooks with retries and delivery logs.