Broadcast Campaigns

Schedule one-time or recurring SMS campaigns to targeted customer segments, configure recurrence rules, and track dispatch status.

Schedule customer messages

To schedule automated customer messages, navigate to Communication → Campaigns in your Nukta dashboard.

Broadcast campaigns allow your ISP to plan and automate time-sensitive customer outreach—such as planned upstream maintenance alerts, holiday promotional discounts, and automated monthly renewal reminders—via SMS. (For visual placements on your captive login screens, see Captive Promo Banners).

The campaign dashboard

The campaign overview displays four real-time summary KPI cards:

• Total: All campaigns ever configured in your workspace.
• Scheduled: Upcoming dispatches waiting for their target dispatch window.
• Completed: Successfully delivered campaign runs.
• Failed: Campaigns that encountered execution errors.

Status tabs allow you to filter records by All, Scheduled, Processing, Completed, and Failed. Each table row summarizes the transmission channel, target audience, next scheduled send date, recurrence rule, status, and total count delivered.

Required campaign fields

When creating a new broadcast campaign, specify the following parameters:

• Campaign Name: Required internal reporting label (maximum 120 characters). Use a descriptive name.
• Channel: SMS (mobile text messaging).
• Message Body: Required text content (1 to 1,600 characters). Supports standard personalization tags.
• Audience Type: Choose between Everyone, Segments, Mikrotiks, or Specific Customers.
• Audience Selection: Required whenever the audience type is not Everyone (e.g., selecting specific customer groups or MikroTik routers).
• Scheduled Start Time: The exact date and time the campaign should dispatch.
• End Recurrence (Optional): If recurrence is configured, the end date must occur after the scheduled start time.

Recurrence rules

Nukta supports flexible recurrence rules for ongoing customer communication:

• One-time: Dispatches once at the scheduled date and time.
• Daily: Dispatches every day at the designated time.
• Weekly: Dispatches once per week on the designated day.
• Monthly: Dispatches once per month on the corresponding date.
• Yearly: Dispatches annually on the specified calendar date.
• Holiday (Annually): Repeats on the same annual holiday date (similar to yearly).

NOTE

Recurring Failures and Gateway Errors

If a recurring campaign encounters an execution failure (such as temporary handset unreachability), it automatically schedules its next upcoming run according to the calendar rule. The only exception is a missing or unconfigured SMS gateway, which halts future executions. Once you restore gateway credentials in Settings → Communications, edit the campaign and re-save it to resume the schedule.

Saving a failed or completed campaign with a future execution date automatically re-schedules it for dispatch.

How and when campaigns send

Nukta's background scheduler scans for due campaigns every 5 minutes:

• An active campaign typically begins dispatching within 1 to 5 minutes of its scheduled trigger time.
• During each sweep, Nukta processes up to 25 due campaigns per ISP.
• Dispatches are not retried automatically if rejected by carriers.

Why a campaign run may fail

A campaign run reports an immediate failure if:

1. Unconfigured Gateway: The SMS gateway lacks active credentials under Settings → Communications → SMS → Gateways.
2. Empty Audience: No customers currently match the selected segment or router filter.
3. Delivery Rejection: The gateway rejected the batch payload (e.g. zero valid phone numbers or depleted SMS balance).

Open any campaign detail drawer to review total dispatched count, delivered messages, and failure logs.

Best practices for safe campaign creation

1. Use Specific Internal Names: Avoid generic titles like "Promo 1"; use names that reflect site, date, and audience.
2. Configure Providers First: Ensure your SMS gateway is active and verified before scheduling.
3. Target Carefully: Restrict maintenance notices to specific affected MikroTik routers rather than messaging your entire customer base.
4. Preview Variable Tags: Test variable tags (e.g., {{first_name}}) to ensure fallback text renders cleanly for records lacking optional values.
5. Account for Timezones: Double-check that the scheduled dispatch time corresponds to your ISP's local operational timezone.
6. Prevent Accidental Duplicates: If a campaign status appears pending around its dispatch window, do not create a duplicate campaign. Inspect the 5-minute queue cycle and provider dashboard first.

Editing and deleting campaigns

• Editing: Modifying an upcoming recurring campaign updates all future dispatches according to the revised schedule. If an earlier run already completed, verify what changed before adjusting the audience.
• Deleting: Permanently cancels future scheduled dispatches. Delete only when ongoing history retention is not required (campaigns cannot be temporarily paused).

For immediate single or bulk texting, see SMS. For captive portal marketing banners, see Captive Promo Banners. For gateway configurations and credentials, see Messaging Providers and Sender IDs. For automated trigger notifications, see Notifications and Templates.