Messaging Campaign Manager
The EnableX Messaging Campaign Manager lets you run outbound messaging campaigns across SMS, WhatsApp, and RCS from the EnableX Portal — with no code required. What makes it a unified campaign tool is its intelligent fallback routing: you designate one channel as the primary delivery path and optionally configure one or two fallback channels. If a message is not delivered on the primary channel within a defined window, EnableX automatically attempts delivery on the next channel in the sequence.
A single campaign can reach contacts over their most reachable channel — not just the one you prefer. The campaign wizard is dynamic: the number of steps and their titles adapt based on which channels you select and how many fallbacks you configure.
EnableX does not charge anything to use the Messaging Campaign tool. You pay only for the messages delivered — billed as per your existing subscription for each channel (SMS, WhatsApp, RCS).
Prerequisites
Before creating a Messaging Campaign, the following must be in place in your EnableX project:
- At least one messaging channel (SMS, WhatsApp, or RCS) must be configured and active in the project
- Pre-approved message templates must exist for each channel you intend to use — WhatsApp and RCS require templates approved through the respective platform; SMS requires DLT-registered templates for India
- Contacts must be prepared as a CSV file or previously uploaded to the Portal
The campaign tool uses pre-approved templates for each channel. You cannot compose free-form messages for WhatsApp or RCS during campaign creation — templates must be approved before the campaign wizard is used. For SMS, DLT-registered templates are required for promotional and transactional delivery in India.
How Fallback Routing Works
Fallback routing is the core feature that makes this a unified campaign rather than a single-channel blast. The system attempts delivery on the primary channel first. If the message is not delivered — either because the recipient is unreachable on that channel, or because delivery fails outright — EnableX moves to the next channel after a configurable wait window.
Each fallback channel has its own trigger conditions:
- Not delivered within: A time threshold (in minutes). If the primary channel has not confirmed delivery within that window, the fallback attempt begins.
- Delivery Failed: A toggle that also triggers fallback when the carrier or platform reports an explicit delivery failure, independent of the timeout.
You configure up to two fallback channels — Fallback 1 and Fallback 2. Each is optional. The overall delivery sequence for any one contact looks like this:
- Attempt delivery on the Primary Channel
- If trigger condition met → attempt delivery on Fallback 1 (if configured)
- If trigger condition met → attempt delivery on Fallback 2 (if configured)
Once a message is delivered successfully at any stage, the sequence stops for that contact. Fallback attempts are not made for contacts who already received the message.
Campaign Wizard — Step Overview
The campaign wizard adapts its step count and step titles based on the channels you select in Step 1. The minimum is four steps (one primary channel, no fallbacks). Each fallback channel you add inserts one additional step for its content configuration. The Review step is always last.
| Step | Title | Condition |
|---|---|---|
| 1 | Campaign Info | Always present |
| 2 | Contacts & Schedule | Always present |
| 3 | [Primary Channel] Content | Always present; title reflects selected primary channel (e.g. SMS Content) |
| 4 | [Fallback 1 Channel] Content | Only if Fallback 1 channel is selected |
| 5 | [Fallback 2 Channel] Content | Only if Fallback 2 channel is selected |
| Last | Review & Send | Always present; position shifts based on how many content steps exist |
Step 1 — Campaign Info
This step defines the campaign identity and channel strategy. Everything configured here drives the structure of the remaining steps.
Campaign Name and Project
Enter a name for the campaign — this appears in the campaign list and in the Review step summary. Then select the Project from the dropdown. The project list only shows projects that have at least one messaging channel (SMS, WhatsApp, or RCS) configured and active. Projects without any messaging channel do not appear.
Primary Channel Selection
The channels available for selection as the primary delivery channel depend entirely on which channels are configured in the selected project:
- 1 channel in project: That channel is automatically pre-selected as the Primary Channel. No selection is needed. The Step 3 title updates to reflect it (e.g. "SMS Content").
- 2 channels in project: Both channels appear under Primary Channel — you select one. Step 3 updates its title to match your selection. The other channel appears under Fallback 1 as an optional choice.
- 3 channels in project: All three appear under Primary Channel — you select one. Step 3 updates its title. The remaining two channels appear as Fallback 1 options and Fallback 2 options respectively. Both fallbacks are optional.
Fallback Channel Selection
After selecting the Primary Channel, the remaining eligible channels appear under Fallback 1 and Fallback 2. Selecting a fallback channel dynamically adds a content step to the wizard for that channel and pushes the Review step further back. You may choose neither, one, or both fallback channels.
The channel strategy panel at the bottom of the screen shows the full delivery sequence as you make selections — Primary → Fallback 1 → Fallback 2 — so the routing logic is visible before you proceed.
Step 2 — Contacts & Schedule
This step defines who receives the campaign and when this batch of messages is sent.
Audience — Contact Upload
Contacts are supplied as a CSV file. You can either:
- Upload a new CSV: Drag and drop the file into the upload zone or click to browse and select it. Give the contact list a name — this name appears in the campaign record and can be reused for future batches.
- Select a previously uploaded list: If you have uploaded contacts in an earlier campaign or batch, they appear in the Contact List dropdown and can be reused without re-uploading.
The CSV must include a column for the recipient phone number in international format. Any additional columns in the CSV become available as contact data fields for mapping to template variables in subsequent steps.
The contacts uploaded at this step form the first batch for this campaign. After the initial batch is sent, you can return to the campaign and add additional batches — uploading a new contact file each time — without creating a new campaign. This allows you to build a campaign progressively over time or in waves.
Schedule
Choose when this batch should be delivered:
- Send Immediately: Delivery begins as soon as you launch the campaign from the Review step.
- Specific Date & Time: Select a future date and time. The batch is queued and delivery begins at the scheduled moment.
Delivery Notifications
A delivery notification toggle is available to receive a summary report when the batch completes. This is sent to the account's registered contact.
Step 3 — Primary Channel Content
The title of this step reflects the channel you selected as Primary in Step 1 — for example, SMS Content, WhatsApp Content, or RCS Content. The configuration options vary slightly by channel.
SMS Content
When SMS is the selected channel, configure the following:
- SMS Type: Select the message category — Promotional, Transactional, or Service Implicit. This determines the DLT classification and the regulatory rules that apply to delivery.
- State / DLT Entity: Select the DLT-registered state or entity. Required for India SMS delivery under TRAI regulations.
- Target Country: The country to which messages will be sent.
- Sender ID: The alphanumeric or numeric sender ID registered with the DLT. Only registered sender IDs are selectable.
- Select Template: Choose from the DLT-approved templates available in your project. The selected template body is previewed, with variable placeholders shown.
WhatsApp Content
When WhatsApp is the selected channel, configure the following:
- Select Template: Choose from your approved WhatsApp Business message templates. The template body and any header or footer are previewed.
- User Actions: If the selected template includes interactive elements — such as call-to-action buttons or quick reply options — this section confirms they are active for the campaign. Link-type actions (e.g. "link") display their activation status.
RCS Content
When RCS is the selected channel, configure the following:
- Select Template: Choose from your approved RCS templates. Card-based templates (C-card format) are supported alongside plain text templates.
- DLT Agent: The RCS agent identifier registered with the operator. Select from the agents linked to the project.
- Message Expiry: A date after which undelivered RCS messages should not be attempted. Set this to limit delivery attempts to a relevant window.
- Enable Bot Number: Toggle to route the campaign through a registered RCS bot number rather than a standard long code.
- Business Data: An optional free-text field to attach metadata to the RCS message for tracking or analytics purposes.
Mapping Template Variables
Most message templates include variable placeholders — for example, {{1}} (WhatsApp /
RCS numbering) or {#var#} (DLT pattern). These placeholders are replaced
with actual recipient-specific data at send time.
The Map Template Variables section appears below the template preview for every channel. For each variable in the template, a dropdown lets you select which column from the uploaded contact CSV should supply the value.
For example, if your SMS template reads:
Dear {#var#}, your service {#var#} is now active. Call 1800-XXX-XX for support.
You map the first variable to the name column and the second variable to the
service column from your CSV. At delivery time, each recipient receives a personalised
message with their actual name and service plan substituted in.
The CSV column names you use when uploading contacts become the options in the variable mapping dropdown. If a column name is missing or mistyped, the mapping will not work correctly. Ensure your CSV headers are clean, consistent, and free of special characters before uploading.
Steps 4 & 5 — Fallback Channel Content
If you selected one or two fallback channels in Step 1, those channels each get a dedicated content step. These steps are titled with the channel name and its position — for example, WhatsApp — Fallback 1 or RCS — Fallback 2.
The content configuration for each fallback step is identical to the primary channel step for that channel type (SMS, WhatsApp, or RCS) — you select a template and map its variables to contact CSV columns.
What is unique to fallback steps is the Trigger Conditions section at the top of each step:
Trigger Conditions
- Trigger On — Not delivered within: A dropdown to set the wait time (in minutes) after the preceding channel's delivery attempt. If the message from the prior channel is not confirmed as delivered within this window, the fallback attempt for this contact is initiated.
- Delivery Failed: A toggle. When enabled, if the prior channel returns an explicit delivery failure (rather than just a timeout), the fallback is triggered immediately — without waiting for the timeout window to expire.
The two conditions work independently. You can enable either or both. If both are enabled, whichever condition is met first triggers the fallback.
These trigger conditions apply per contact. A contact whose primary message is delivered successfully will never see a fallback attempt, regardless of what the trigger window is set to.
Review & Send
The final step presents a complete summary of the campaign before launch. Review all settings carefully here — once the campaign is launched, scheduled batches proceed automatically.
Campaign Summary
The summary panel shows:
- Project: The project selected in Step 1
- Campaign Name: As entered
- Messaging to: The number of contacts in this batch
- Send: Immediately or the scheduled date and time
- Channel delivery sequence: Each channel is shown as a card — Primary, Fallback 1, Fallback 2 — with the channel name, its template, and its position in the delivery sequence. Fallback trigger conditions are visible here for confirmation.
Test Before Launch
Before launching to the full contact list, you can send a test message to verify that templates render correctly and delivery works end-to-end. Enter a mobile number in the test field and click the channel button (SMS, WhatsApp, or RCS) to send a live test message to that number for the corresponding channel.
Test messages use the same template and variable mappings configured in the campaign — the test recipient receives the message exactly as a campaign recipient would. Run a test on each channel before proceeding if fallback channels are configured.
Variable mapping errors only become visible when a message is actually composed and sent. The test feature catches mapping mismatches — missing values, incorrect column references, or formatting issues in the template — before they affect thousands of recipients.
Launching the Campaign
Click Launch Campaign to confirm. If scheduled for immediate delivery, the first batch begins processing. If scheduled for a future time, the campaign enters a scheduled state and delivery begins at the configured moment.
After launch, the campaign appears in the Messaging Campaigns list in the Portal. You can return at any time to add further batches of contacts, view delivery progress, or access per-contact delivery logs.
Related Documentation
Messaging Campaign Manager is built on the EnableX Messaging service. The following pages provide deeper context on channel setup, API access, and number management: