Platform WhatsApp
Use the centrally managed EventHex route for supported transactional purposes when that setup applies.
Platform-managedChoose the configured sending route, use approved templates for the messages your event needs, and keep marketing sends on an organization-owned official account.
The available route depends on organization and event configuration; one option is not presented as universally best.
Use the centrally managed EventHex route for supported transactional purposes when that setup applies.
Platform-managed
✓ Platform routeView platform route
✓ Organization routeReview organization routeReuse the organization's configured WhatsApp account across eligible events.
Portfolio-levelUse event-specific provider credentials and template overrides when the event owns its setup.
Event-level
✓ Event routeReview event routeEventHex resolves the selected event or organization account before dispatch. Provider fields vary, and saved access tokens remain a credential—not customer-facing copy.
Choose the supported provider used by the account.
Identify the sending account or device according to that provider.
Store the provider token or API key used for delivery.
Use only where the configured provider path supports it and the organizer has enabled it.
Separate operational event delivery from the organization-owned identity required for campaign sends.
Use the event's configured route for supported OTP, registration, ticket, certificate, exhibitor, and system messages.
✓ Transactional routeEvent messages
✓ Organization-ownedCampaigns onlyUse a tenant-owned official Meta Cloud API account with complete credentials before campaign sending is considered ready.
Unofficial provider routes are deliberately blocked for marketing campaigns; the platform number is not used for a tenant's marketing send.
The organizer workspace groups templates by purpose and lets teams preview the default message and variables before use.
OTP and checkout verification templates help the configured account support an intentional event journey.
Authentication purpose Preview template Use the registry's success, pending, approval, rejection, and related status message purposes for attendee updates.
Registration status Preview template Represent text, image, document, and certificate delivery purposes in the connected template registry.
Delivery purpose Preview template Keep exhibitor, booth-member, InstaSnap, InstaRecap, campaign, and system purposes visible in one template library.
Workflow purpose Preview template Review the purpose, approved name, numbered variables, and supported EventHex fields before saving an override.
Book a DemoOpen the template used for that registration, ticket, exhibitor, or campaign moment.
✓ Purpose selected Choose purpose Use the exact Meta-approved name for the connected account.
✓ Approved name Enter template name Create the numbered placeholders expected by the template.
✓ Variables ordered Add variables Connect each position to the supported EventHex field, then save the override.
✓ Override saved Save override Use the preview to confirm the purpose, approved template name, variables, and media requirement before a WhatsApp message is sent. For a custom account, review the mapped fields as a separate setup step.
Separate client-owned accounts and approved templates where the event requires them.
Explore More
Reuse organization-level routing for a repeat event programme and its connected message purposes.
Explore More
Coordinate exhibitor and booth-member message purposes alongside attendee delivery.
Explore More
Connect verification, registration status, ticket, and reminder journeys to the chosen account.
Explore More
Platform contextAccount routes Sending boundary Keep account routing, provider credentials, approved templates, variable mapping, and sending-readiness boundaries in this integration page.
Use the configured WhatsApp route for the supported event message purposes without repeating the full attendee product experience here.
Link people to the feature page that owns the attendee or organizer task instead of duplicating its capability grid here.
Connected pages cover concierge conversations, campaigns, notifications, registration, ticket delivery, and photo or recap experiences.
Feature linkedEvent experience Attendee journey Give attendees event-aware answers, forms, tickets, reminders, networking, and human help.
Build and schedule campaigns from EventHex audience data.
Orchestrate operational messages and delivery status across channels.
Create the attendee journey that triggers verification and outcome messages.
Yes. EventHex supports organization-level or event-specific account configuration where the required provider credentials are available.
No. Campaigns require a tenant-owned official Meta Cloud API account so one organization's marketing does not use the shared platform identity.
Custom-account events can enter their Meta-approved template names and map numbered variables to supported EventHex fields.
The current registry covers authentication, registration, tickets, certificates, exhibitors, media products, campaigns, and system purposes.
Delivery depends on the connected account, approved template, recipient eligibility and consent, provider availability, and the destination device or network.
No. This page explains the account and template connection. The concierge page owns attendee conversations and event-aware assistance.