Skip to main content
A Campaign is a scheduled group of outbound calls. Ringg AI uses one assistant, one or more caller numbers, and a contact list to call many people without manual dialing.

​
What a Campaign Needs

​
Campaign Settings

When creating a campaign, you fill in two main sections.

​
Campaign Settings

​
Calling List

The calling list is usually a CSV file. It should include:
  • A phone number column.
  • Any custom variables used in the assistant prompt.
  • Clean headers with no extra spaces.
Example: if the assistant says @{{callee_name}}, the CSV needs a callee_name column.

​
Campaign Status

​
Campaign Concurrency

Concurrency controls how many calls can happen at the same time. Use Manage Concurrency when:
  • Multiple campaigns are running at once.
  • API-triggered calls and dashboard campaigns share the same workspace capacity.
  • You want to control how call slots are split across campaigns.
If campaign concurrency is not set manually, Ringg AI distributes available campaign call slots across running campaigns.

​
Developer Handoff

Developers need campaign IDs to start, monitor, and reconcile calls outside the dashboard. For the standard API flow, developers should use POST /campaign/save and then POST /campaign/start. For 5,000 or more rows, developers should use the beta large-campaign flow:
  1. POST /campaign/upload-csv
  2. GET /campaign/upload-status/{bulk_list_id}
  3. POST /campaign/make-call-async
  4. POST /campaign/check-balance/{bulk_list_id}