PRODUCT GUIDE

Run reliable voice broadcasts and interactive surveys.

Set up your contacts, voice prompts, caller ID, and survey flow—then track every call and customer response in one place.

START HERE

Getting started

Before launching a campaign, make sure your wallet has funds, an active caller ID is available, and the survey has a Voice Library audio file on its opening node.

Create or import a contact list.
Upload or generate the audio prompts in Audio Library.
Create a survey, then select it when creating a campaign.
Choose an active caller ID and start the campaign.

VIDEO GUIDE

Video tutorial

Follow this short walkthrough to set up your account and start using NextGenBroadcast.

BROADCASTING

Campaigns

A campaign connects a contact list, caller ID, and survey. The worker dials contacts in the background and keeps the configured concurrency, retry, and balance limits.

Concurrency

Limits how many calls this campaign can place simultaneously.

Retries

Busy and unanswered contacts can be scheduled again using your retry settings.

Pause and stop

Pause prevents new calls; active calls can complete. Stop ends future dispatching.

INTERACTIVE VOICE

Surveys and DTMF

Use a Voice Library file for each prompt. Add DTMF options to let recipients choose an action by pressing a key.

Action	What happens after the key press
Play audio	Plays the selected Voice Library file.
Next node	Continues to another node in the same survey.
Dial number	Transfers the active call to the configured number.
Redirect survey	Starts the opening flow of the selected survey.
End call	Ends the call cleanly.

Every valid DTMF selection is saved in Survey Records with its key, label, chosen action, and webhook delivery result.

VOICE PROMPTS

Audio Library

Upload ready-to-use audio files or generate speech with text-to-speech. Generated audio is stored as a playable WAV file and can be selected in a survey node or DTMF option.

Campaigns use the survey’s opening audio; a campaign-level message is not required.

OBSERVABILITY

Call History and Survey Records

Call History contains every dial attempt, including the called number, caller ID, provider call ID, status, timings, billable duration, cost, retries, and hangup reason.

Survey Records lists every key press separately, including the number called, campaign, survey, DTMF key, label, action, and webhook result. Open a call detail to see its responses in sequence.

API AUTOMATION

Voice API for orders and deliveries

Use the Voice API to place a single voice call whenever an event happens in your store, CRM, or delivery system. Common uses include order confirmation, payment reminders, out-for-delivery updates, delivery verification, appointment reminders, and customer feedback calls.

1. Create a voice flow

Create and activate a survey with the message or DTMF choices your customer should hear.

2. Create an API key

Open API Keys in the customer panel and save the new key securely on your server.

3. Trigger from your backend

Call the endpoint when the order event occurs. Never expose an API key in browser or mobile-app code.

Queue an order-confirmation call

Send a POST request to /api/v1/customer/survey-calls. The API Key page automatically generates an example using your live domain and selected survey.

POST /api/v1/customer/survey-calls
Authorization: Bearer cb_live_your_api_key
Content-Type: application/json

{
  "surveyId": "YOUR_ACTIVE_SURVEY_ID",
  "to": "8801712345678",
  "callerId": "8801XXXXXXXXX",
  "reference": "order-12345",
  "metadata": {
    "orderId": "12345",
    "event": "order.confirmed"
  }
}

For delivery events, keep the same request and change the reference, idempotency key, and event value—for example delivery.out_for_delivery or delivery.delivered. The reference and metadata are returned with the call request, making it easy to match calls with your order records.

Prevent duplicate calls and check results

Use an Idempotency-Key that is unique to the order and event. Retrying the same request after a timeout returns the original request instead of placing another call. The response contains a requestId; use GET /api/v1/customer/survey-calls/{requestId} to check its queue and call status. Calls also appear in Call History and use the normal wallet, billing, caller-ID, and survey-response handling.

Only call customers who have provided the required consent, and ensure the selected caller ID and survey are active before sending live traffic.

INTEGRATIONS

DTMF webhooks

Open Surveys, then create or edit a survey. Enter your endpoint in Survey webhook URL, above the DTMF Actions section. One URL applies to every valid key selection in that survey; it is not configured separately for each DTMF action.

NextGenBroadcast sends an HTTP POST request with a JSON body each time a recipient selects a configured key:

{
  "dtmf": "1",
  "label": "Sales",
  "callAttemptId": "5f7d8e34-1bf5-4c28-8ad0-3e3a688ef6e2",
  "campaignId": "fbe11b52-52d0-4977-9eca-ec67276ef383",
  "customerId": "0d5dbdf5-e21f-4794-91fd-26fd4ffcc0d0",
  "mobileNumber": "8801XXXXXXXXX",
  "requestId": "e25dd3d5-f8a9-41bb-9c6e-1fd9b3628eaa",
  "reference": "order-12345",
  "metadata": { "orderId": "12345" }
}

dtmf is the key pressed, label is the action label you entered, and mobileNumber is the number called. requestId, reference, and metadata are null for normal campaigns unless the call was created through the Voice API with those values.

Your endpoint should be publicly reachable and return promptly (within five seconds). The webhook is recorded as delivered or failed in Survey Records; a delivery failure is logged but does not interrupt the caller’s selected action.

ACCOUNT

Billing and wallet

Your wallet must have sufficient balance to begin chargeable activity. Call charges are calculated from your tariff’s rate and billing pulse. TTS generation can also use a per-character tariff rate.