Overview
Attach channel instructions to published content or campaign stages while leaving actual delivery to the dedicated messaging apps.
Prerequisites
- At least one delivery app connected
- Message templates and consent rules configured
Permissions required
Steps (6)
-
1
Choose the trigger
Configure communication for content published, event registration confirmed, event reminder due, event rescheduled, promotion launched, promotion expiring, or campaign stage reached.
Tips
Validation
Success criteria
-
2
Choose channels
Select in-app, email, SMS, WhatsApp, or voice. Each selection becomes an instruction or event for the responsible delivery app.
Tips
Validation
Success criteria
-
3
Choose audience snapshot
Use the content or campaign snapshot, or create a stage-specific snapshot from a provider segment.
Tips
Validation
Success criteria
-
4
Map template variables
Map title, summary, CTA URL, event time, venue, promotion expiry, project name, campaign name, and recipient merge variables expected by the delivery template.
Tips
Validation
Success criteria
-
5
Run a test delivery
Send to a controlled test audience and verify template rendering, links, tracking, sender configuration, and channel consent behaviour.
Tips
Validation
Success criteria
-
6
Launch and reconcile
Publish the instruction events, retain correlation IDs, and ingest delivery outcomes for campaign reporting without making EngagementHub the message transport.
Tips
Validation
Success criteria
- Delivery status can be traced from campaign asset to snapshot, instruction, provider message, and outcome.
About this guide
EngagementHub gives organizations one governed backend for news, announcements, events, promotions, and coordinated campaigns. A shared content engine keeps titles, summaries, bodies, media, categories, tags, calls to action, related records, placements, visibility, and publication status consistent across every content type.
Teams can plan campaigns around a business objective, connect news, announcements, events, promotions, and communication instructions, then move content through draft, review, approval, scheduling, publication, expiry, and archive states. Events support registration, capacity, waitlists, approvals, reminders, check-in, attendance, feedback, and follow-up. Promotions support eligibility, claims, redemption, limits, terms, and automatic expiry.
Audience targeting uses the platform pattern already shared by PeopleGraph and ProspectLayer. EngagementHub discovers installed apps that declare audience-provider capability, requests each app’s segment catalog, collects any required segment parameters, previews the match, and asks the selected source app to create a frozen snapshot. AccessGuard can expose account segments, HomeBridge can expose parameterized property audiences, PeopleGraph can expose tags, and ProspectLayer can expose lists. EngagementHub never needs direct knowledge of another app’s database.
ProjectBoard supplies project truth, FileVault supplies secure files, HomeBridge exposes the customer experience, AccessGuard handles identity and in-app notification records, EmailHub sends email, and PulseGate sends SMS, WhatsApp, and voice. EngagementHub owns the content, campaign plan, audience reference, schedule, publication lifecycle, and performance record.