Communications Overview
The Communications section lets you reach players through several channels using reusable, templated messages. Build personalized notifications for marketing, transactional, and engagement purposes, then deliver them on their own or as part of an automated flow.
Key Features
- Multi-channel delivery — Email, Short Message Service (SMS), Push, In-App, and Popup messages
- Template builder — a visual editor with a live preview
- Personalization — insert player and brand details into the message body
- Artificial Intelligence (AI) assistant — draft template content with AI help
- Version history — track changes made to a template over time
Accessing Communications
The Communications menu contains:
| Section | Description |
|---|---|
| Notification Templates | Create and manage message templates |
| System Notifications | Assign templates to automatic transactional triggers, such as welcome, account verification, and password reset |
| Registration Forms | Configure the player registration form |
Communication Channels
Email
- Rich, formatted content
- Supports attachments
- Best for: detailed communications, receipts, and newsletters
SMS
A One-Time Password (OTP) is a single-use code used to confirm an action.
- Plain-text messages, subject to per-message character limits
- Typically read quickly after delivery
- Best for: urgent alerts and OTP messages
Push notifications
- A title and body, with optional action buttons
- Require the player to allow notifications in their app or browser
- Best for: real-time alerts and promotions
In-App messages
- Shown to the player inside the app or website
- Support rich formatting and an action link
- Best for: feature announcements and guided tours
Popup
Popups are on-site messages shown to logged-in players. For each popup you can set:
- A title, body, primary and secondary actions (each a web address plus button text), and an optional image
- A style (modal, top banner, bottom banner, or corner) and a priority
- A delay before it appears, an optional auto-dismiss, and whether a close button is shown
- Per-theme appearance (solid or gradient background, in dark and light) and an expiry (a value plus a unit of minutes, hours, or days)
Best for: on-site promotions, welcome-back messages, and timed offers.
Purpose and Category
Each template carries two independent labels that control how it behaves and how you organize it:
| Label | Values | What it does |
|---|---|---|
| Purpose | Transactional or Promotional (shown for Email and SMS) | Promotional adds the required unsubscribe option to the message and shows a compliance reminder in the editor when that unsubscribe affordance is missing. |
| Category | Operator-defined, free-form labels you create, edit, and delete per brand | Used for organizing and filtering templates. |
Marking a template as Promotional ensures it carries an unsubscribe option, which anti-spam regulations require for marketing messages.
The automatic transactional flows (welcome, verification, password reset, and similar) are configured separately on the System Notifications page.
Workflow Integration
Attach a template to an automated flow so messages send in response to player events — this runs timely lifecycle campaigns without anyone sending each message by hand.
- Define triggers in a workflow
- Select a notification template
- Configure recipient targeting
- Messages send automatically
See Workflows for details.
Personalization
Templates support dynamic variables written as double-brace, dotted paths — for example {{player.firstName}}. Only this {{ namespace.field }} form is recognized; a single-brace name such as {firstName} appears in the message as literal text.
| Variable | Description |
|---|---|
{{player.firstName}} | Player's first name |
{{player.lastName}} | Player's last name |
{{player.email}} | Player's email |
{{player.currencyCode}} | Player's currency code |
{{brand.name}} | Brand name |
Trigger-scoped variables (for example {{deposit.amount}} or {{bonus.amount}}) are available only when the template is used by that trigger. Money fields accept an optional | currency pipe that formats the value with the player's currency symbol — for example {{deposit.amount | currency}}. See Notification Templates for the full variable list.
Best Practices
- Keep SMS messages concise
- Use compelling subject lines for email
- Test a template before sending
- Include an unsubscribe option on promotional messages
- Follow anti-spam regulations
- Personalize when possible
- Monitor delivery rates
Delivery Providers
Messages are sent through the providers you configure, so they route through your own vendor accounts and sender identities:
| Channel | Supported providers |
|---|---|
| Resend, SendGrid | |
| SMS | Twilio, Infobip, Sinch, Wirepick, Blackbox, BSG, ESMS, Fortytwo, Nexmo (Vonage), Scarpel, Termii |
| Push | Firebase, OneSignal, VAPID / Web Push |
| In-App | Delivered by the platform itself |
Nexmo (Vonage) delivery receipts arrive on a per-send callback, so no receipt URL needs configuring in the Vonage dashboard. Two account settings do matter: the Default SMS Setting must be SMS API (not Messages API), or receipts arrive in a shape the platform ignores; and the delivery-receipt method should be POST JSON rather than the default GET, because a GET receipt carries the player's phone number in its URL.
Provider configuration is set on the Notifications settings tab at the System, Operator, or Brand level — a lower scope inherits from the one above unless it sets its own. See Operators.