Dedicated Broadcast IVR: mass voice campaigns with your own API

A dedicated engine to call thousands of contacts with a voice message and a menu of options, without anyone dialing one by one. Run it on its own or wire it into your system through the API.

What the Dedicated Broadcast IVR is

It is an engine for mass voice campaigns: you upload a contact list, pick a voice tree -- the message and the menu of options whoever answers will hear -- and the system calls everyone, plays the message and records how each person responded. No agents dialing or waiting on the line.

It handles what today eats call center hours and does not need a person: payment reminders, cutoff notices, appointment confirmations, short surveys, first-contact campaigns. The person listens, presses a key, and that answer lands in the report.

It is dedicated: it runs on its own instance, with its capacity reserved for your campaigns. It does not compete for resources with another operation.

How a campaign works

The flow is always the same, and it is documented step by step in the API:

1. You pick a voice tree. It is the script: what is said and which options whoever answers can press. You build it once and reuse it across as many campaigns as you want.

2. You create the campaign and upload contacts. You can upload them with data -- name, amount, date -- so each call goes out personalized instead of generic.

3. You review and start. The system dials, plays the tree and saves each contact's response.

4. You read the result. Who answered, which option they pressed, who did not pick up. All through the API or on screen, ready to act on those answers.

The API: to connect it with what you already use

The Broadcast IVR ships with a full REST API, publicly documented at docs.neervox.com. From your CRM, your ERP or whatever system you have, you fire a campaign, upload contacts and read results with plain HTTP calls.

That means you do not have to open another screen or export files: when something happens in your system -- a quota comes due, an appointment gets booked -- your system launches the voice call on its own. Authentication is token-based, with two permission levels, and there are endpoints for campaigns, contacts, lists, reports, audios and trees.

Compliance and protecting your numbers

Calling en masse without care burns your caller IDs and annoys people who did not want the contact. The engine brings two defenses out of the box.

Do-Not-Call: a contact who asked not to be called does not enter the campaign, with no one having to remember it.

Carrier health: the system watches how the outbound lines respond and spreads the load, so a number does not burn out from overuse. It is the same logic that protects contact rate in the dialer.