Before You Start
Make sure you have:An outbound assistant that has been tested
At least one phone number in your workspace
A CSV file with phone numbers and any fields used by the assistant
Enough call credits for the campaign
Step 1 - Open Campaigns
- Click Campaigns in the left sidebar.
- Click + Create Campaign.
Step 2 - Fill in Campaign Settings
On the Campaign Settings tab, fill in:| Field | What to Choose |
|---|---|
| Campaign Name | A clear name such as March Admissions Follow-up |
| Assistant | The assistant that should make the calls |
| Numbers | One or more caller numbers |
| Campaign Start Date/Time | When calling should begin |
| Campaign End Date/Time | When calling must stop |
| Timezone | The timezone for the schedule |
| Email Notifications | People who should receive updates |
Step 3 - Upload the Calling List
Click Next to open the Calling List tab. Upload a CSV file with one row per contact. Include:- A phone number column.
- One column for each custom variable used in the assistant prompt.
- Clear column names with no extra spaces.
@{{callee_name}}, the CSV must include a callee_name column.
Step 4 - Save and Start
- Review the campaign settings.
- Click Save CSV.
- Click Make Call to activate the campaign.
| Schedule | Campaign State |
|---|---|
| Start time is in the future | Scheduled |
| Start time is now or already passed | Ongoing |
Monitor a Campaign
From the Campaigns page, use the Actions column to:- View campaign call history.
- View campaign analytics.
- Terminate a running campaign if needed.
Set Campaign Concurrency
Concurrency controls how many calls can happen at the same time.- Click Manage Concurrency on the Campaigns page.
- Use Workspace Concurrency to split capacity between API calls and campaign calls.
- Use Campaigns Concurrency to allocate capacity across running campaigns.
- Click Save.
If you do not set campaign concurrency, Ringg AI distributes available call slots across running campaigns.
Developer Handoff
If engineers are starting campaigns by API or pulling campaign results into another system, send them:| Item | Why They Need It |
|---|---|
| Campaign name | Lets them confirm they are working with the right campaign |
agent_id | Identifies the assistant that should make the calls |
Caller number or from_number_id | Identifies which number should dial contacts |
| CSV column names | Must match assistant custom variables |
bulk_list_id or list ID | Identifies the uploaded calling list for start, status, history, and analytics |
| Webhook requirement | Tells them whether to send call results to CRM, sheets, data warehouse, or support tools |
POST /campaign/save, then start it with POST /campaign/start.
For large campaigns with 5,000 or more rows, use the beta large-campaign flow:
POST /campaign/upload-csvGET /campaign/upload-status/{bulk_list_id}POST /campaign/make-call-asyncPOST /campaign/check-balance/{bulk_list_id}
bulk_list_id because it is needed to check upload status, start calls, filter history, and reconcile results.