Objective
Run the reminder campaign under a call limit, then read connectivity, promises to pay and the exported report.The scenario
The October run goes to every customer with an EMI due on 15 October, under two rules from compliance: nobody is called more than three times in a day, retries included, and the collections lead gets a report. You run it over the part 4 list.Hands-on
Creating a campaign in the dashboard
1
Checkpoint 5: set the call limit
Open Settings → Call limits and switch on Limit how often one person is called. Set Maximum calls to one person to
3 and Rolling window to 24 hours; Projected impact shows what those values would have held back. Click Save, then Save limit in the This affects calls already queued dialog.The limit counts every agent’s calls to the same person, retries included, never test or inbound calls. A campaign call over it waits as Waiting for limit in Logs; if no slot opens before the campaign’s end time, it is cancelled instead and shows Cancelled by limit.2
Upload details
Open Monitor → Campaigns → Create campaign. Name it
October EMI reminders, pick EMI reminder - Hindi under Select assistant, upload the part 4 CSV, check the mapping for due_amount, due_date and loan_account, and click Next: “CSV verified successfully”.3
Configure campaign
Under Select number, pick the part 4 pool under Number pool. Keep the default Start date & time, 10 minutes from now, and set End date & time to later today. Calling windows default to 08:00–20:00 in the campaign’s Timezone; click Edit if you are outside them now.Set Retry count to 2 Retries: with the first attempt, that is three dials per row, which fits the limit; with the default 3 Retries, the limit would hold back or cancel a fourth. Set Cooldown Period to 5 Minutes. The read-only Call limits card confirms the limit applies. Click Create campaign: “Campaign created successfully!”. Every attempt is a real call.
4
Watch it run
Answer when Ananya calls, and let one row ring out to see its retry 5 minutes later. Click the campaign’s row, then History: Logs opens filtered to this campaign, whatever the date range.
5
Checkpoint 6: read the report
In the detail panel click Analytics; the page is scoped to the campaign. Read Calls connected and Connectivity rate; Goal achieved, the share of analysed calls where
payment_promised was true; and the Connectivity chart by attempt, which decides next month’s retry count.Once the status is Completed, the panel shows Export report. Click Download (“Download a ZIP of the call report”). The dashboard offers it for 60 days after the campaign’s end time.Checkpoint
Call limits shows the switch on with 3 calls in 24 hours.
October EMI reminders is Completed, History lists every row’s calls, Analytics shows Goal achieved as a percentage rather than “Pick an agent to see goal metrics”, and the ZIP is in your downloads.Exercise
In Analytics for the campaign, click the Calls connected value. Expected result: Logs opens filtered to status Completed and this campaign: only the calls you answered.What you learned
- The call limit is a workspace rule counted across agents and retries; a campaign’s retry count has to fit inside it, or the extra attempts wait or are cancelled.
- Results live in Logs per call (History), Analytics for the rates, and the ZIP (Export report), offered for 60 days after the campaign ends.
- Goal achieved says whether the reminder worked; it exists because part 3 marked a Boolean as the goal.
Where to go next
API quick start
Place calls, run campaigns and read results from your backend.
MCP server
Let an AI assistant work in your workspace from a chat.
Workflows
Chain the call, a wait and a WhatsApp nudge per contact.