The auto-dialer: outbound campaigns
The lead queue, operators, number rotation, disposition codes and the schedule — how to set up automated calling without breaking the team’s work.
The auto-dialer removes the most expensive part of an operator’s work — dialling the number and waiting through the ringing. The system takes the next customer from the queue itself, dials them and connects a free operator at “hello”. In exchange the operator commits to staying in the “Ready” state and setting a result code after every conversation. This page covers everything: from creating a campaign to working out why the dialer has stopped.
#How the calling cycle works
- The operator joins a campaign and switches to Ready.
- The system takes the next lead from the queue — by priority, then by the time it was added — and reserves it for that operator.
- The CRM dials the customer. If they answer, the conversation goes straight into the operator’s headset and the lead card opens by itself.
- After the call the operator gets wrap-up time to finish filling the lead in, and sets a result code.
- The operator returns to “Ready” and the system takes the next lead. The cycle repeats while the queue holds numbers and the campaign is active.
#Step 1. Create a campaign
- 01
Open the “Campaigns” section
The Campaigns item in the side menu. It lists every campaign with filters by project and status and a short progress bar for each.
- 02
Click “New campaign”
The minimum to start is a name and a project. Write the name so that it still makes sense in a month:
Uncollected May,Cold base Kyiv— not “Campaign 3”. - 03
Choose the dial mode and check the basics
Then the call timeout and the maximum number of attempts. Everything else lives under Advanced settings.
| Setting | Default | What it does |
|---|---|---|
| Dial mode | Power | The system dials a customer as soon as an operator becomes “Ready” — one call per operator |
| Call timeout | 30 s | How long to wait for the customer to answer before the attempt counts as failed |
| Maximum attempts | 3 | How many times to come back to one number before it is marked as failed |
| Retry intervals | — | The pause between attempts in minutes, for example 30, 120, 1440 — in half an hour, in two hours, the next day |
| Who ends the wrap-up | The operator, with the “Ready” button | The alternative is automatically, on a timer |
| Time to fill the lead in | 180 s | How long is given to complete the lead after the call |
| Open the card automatically | On | The operator sees the customer’s name and history before the first word |
| Auto-answer in the softphone | Off | The call is answered without picking up |
| Schedule | Mon–Fri 9:00–18:00 | The days and the window in which the campaign may call |
#Step 2. Fill the queue
A campaign with no queue does nothing. There are two ways to fill it, and in 90% of cases the first one is used.
- From the dashboard, as a bulk action. Filter leads the way you need them (status, source, date, manager), select them and pick the Add to a calling campaign action — then choose the campaign from the list of active ones. It is the same mechanism as the other bulk actions.
- From the campaign itself. The Queue tab → search by phone or name → add individually. Handy when a few specific customers need topping up.
| Rule | Detail |
|---|---|
| Duplicates | A lead already in this campaign’s queue is not added twice |
| No phone number | Leads without a number are simply skipped |
| Limit per operation | Up to 5,000 leads in one addition |
| A completed campaign | Nothing can be added — start it again first, or create a new one |
Queue item states
| State | What it means |
|---|---|
| Waiting | Ready to be dialled. After a failed attempt it waits for its retry interval |
| Dialling | A call is in progress right now |
| Answered | The customer picked up |
| Completed | The operator set a result code — work on this number is closed |
| Failed | The maximum attempts are used up and the customer could not be reached |
| Skipped | Taken out of processing |
| Blocked | The number is on the blacklist — the dialer will not call it |
#Step 3. Operators
On the Operators tab the manager decides who works the campaign: adds people by searching for a name or login, sees each person’s current state and, if needed, forces a break or removes them from the campaign.
The operator joins from the side menu: the status button opens a Join a campaign window listing the active campaigns. The current state is always visible in the menu.
| Operator state | What is happening |
|---|---|
| Offline | Not taking part — no calls arrive |
| Ready | Waiting to be connected; the system may hand over a call at any moment |
| Ringing operator / Dialling | The customer is being dialled, the connection has not happened yet |
| On call | A conversation |
| Wrap-up | The call has ended; time to fill the lead in |
| Break | Temporarily receiving no calls — see “Operators, breaks and limits” |
#Wrap-up: what the operator sees after the call
Filling a lead in — the address, the branch, the cart — takes one to three minutes. That is why by default the operator leaves wrap-up themselves with the Ready button, and the timer stays as a safeguard against getting stuck.
- When the call ends, a “Post-call work” bar appears at the top with a countdown and the hint “Fill the lead in and press Ready”.
- A Call result window opens: the result codes, a notes field and, for call-back codes, a time picker.
- The Ready button returns the operator to the queue for the next customer.
#Result (disposition) codes
The result code is the whole reason outbound reporting exists. It is configured per campaign on the Settings tab under “Result codes”.
Result code fields
CodetextrequiredThe technical identifier, for example
confirmed,callback,refused.NametextrequiredWhat the operator sees in the result window.
ColourHEXSo the eye finds the right code in the list within a second.
Successful resultyes / noCodes marked as successful form the campaign conversion.
Requires a call-backyes / noThe operator picks a time straight away and a reminder is created.
Lead statuschoiceThe lead moves into this status automatically after the code is set.
#The DID pool and number rotation
Which number the customer sees is handled on the DID pool tab. Numbers from the telephony are added there, and a rotation strategy is chosen.
| Strategy | Logic |
|---|---|
| Round robin | Numbers are used in turn — an even load |
| Least used | The number that has been called from least today |
| Random | An arbitrary number from the pool |
| The operator’s personal DID | Each operator calls from their own number — the customer calls back to the same manager |
| Regional match | The number is matched to the customer’s prefix — a local call is answered more willingly |
- The cooldown before reuse (60 minutes by default) prevents calling the same customer from the same number twice in a row.
- The system keeps statistics for every number: how many calls and how many answers. A number whose answer rate suddenly drops is the first candidate to check with the carrier.
#Starting, scheduling and campaign states
| State | What it means |
|---|---|
| Draft | Created but not calling. The only state in which settings can be edited freely |
| Scheduled | Starts by itself inside the schedule window |
| Active | Calling right now |
| Paused | Stopped; calls in progress finish, no new ones start |
| Completed | The work is finished. It can be started again if something is left in the queue |
| Archived | Removed from the list of working campaigns |
- The Start · Pause · Stop · Archive buttons are in the campaign header.
- The schedule sets the days of the week and the time window. A campaign in the “Scheduled” state starts and stops on its own — that is the mechanism which stops you calling customers at 9 pm.
- Restart failed returns everything that ended as “Failed” to the queue — handy the next day after a wave of missed calls.
#The number blacklist
The blacklist holds numbers that must not be called: people who asked not to be disturbed, complaints, wrong contacts. It can be global (for every campaign) or limited to one. The dialer does not call a blacklisted number — in the queue it is immediately marked as “Blocked” and skipped.
#Oversight while the campaign runs
| Tab | What it gives a manager |
|---|---|
| Overview | Leads in the queue, calls made, answers, conversion, how many operators are on the line right now |
| Queue | The state of every number with filters by status and result, and the time of the next attempt |
| Operators | Who is in which state and for how long, plus forced breaks |
| DID pool | The numbers and the answer statistics for each |
| Log | A journal of attempts: when, whom, from which number, with what result |
The data updates in real time — no need to reload the page. Listening to a live call, whispering to the operator and barging into a conversation are described separately in “Supervisor work”.
#Permissions
| Permission | What it grants |
|---|---|
dialer.view | Seeing your own campaigns |
dialer.view_all | Seeing campaigns across all projects |
dialer.manage | Creating, editing and starting campaigns, filling the queue |
dialer.operator | Working a campaign as an operator: readiness, breaks, result codes |
dialer.monitor | Real-time campaign monitoring |
dialer.listen / dialer.whisper / dialer.barge | Listening to a call, whispering to the operator, joining the conversation |
dialer.pause_operator | Forcing an operator onto a break |
dialer.blacklist | Managing the blacklist |
#The dialer is not calling: what to check
| Symptom | Most likely cause |
|---|---|
| The campaign is active but there are no calls | Not a single operator is in the “Ready” state — everyone is offline, on a break or in wrap-up |
| The queue is not moving | Every item already has its next attempt scheduled in the future — the retry intervals kicked in |
| An operator keeps being knocked offline | The softphone is not receiving calls: microphone access was not granted, the CRM tab is closed, or there are network problems |
| Leads cannot be added from the dashboard | The campaign is completed, or the dialer.manage permission is missing |
| The campaign starts and immediately goes quiet | The current time is outside the schedule window |
| Customers complain about calls from different numbers | The rotation strategy is random or round robin; for recognisability switch to the operator’s personal DID |
#Campaign launch checklist
- Telephony works: a test outbound call from the browser goes through
- The campaign has operators, and each of them has tested the softphone at their own desk
- The queue holds a targeted selection, not “all leads”
- Result codes are configured, and each one leads to a lead status
- The maximum attempts and retry intervals match your cycle rather than being set to the maximum
- The schedule closes evenings and weekends if you do not call then
- The DID pool is filled and the rotation strategy is a deliberate choice
- The time allowed to fill a lead in matches how long the paperwork really takes
- The manager knows where to look at conversion per campaign and per operator