Campaigns
Call a list of people automatically — pick contacts from your CRM, press start, and let the queue work through them.
On this page
A campaign is a batch of outbound calls: choose who, press start, and the system works through them inside your calling hours and line limits.
CRM → CampaignsWhat it's good for
- Re-engaging leads who went quiet.
- Following up on a promotion.
- Confirming appointments for next week.
- Chasing renewals.
- Any list where the conversation is roughly the same for everyone.
If the list is one person, use the Dialer. If it's "ring them back on Thursday", use Follow-ups.
Creating one
- 1
Name it and pick a caller ID
The name is for you. If you have more than one number, choose which one the whole batch dials from — local numbers get answered more often.
- 2
Filter your contacts
Narrow down by stage, tags, a text search over name and phone, and a created-date range. Leave a filter empty to ignore that dimension.
This is where your CRM setup pays off — good stages and tags make targeting a ten-second job.
- 3
Select who to call
Tick contacts individually, or select everyone in the current filtered view. A running count shows how many are selected out of how many are shown.
- 4
Start
The campaign is created and begins immediately.
What happens when it runs
- Do-not-call is scrubbed first. Any selected contact on your DNC list is marked skipped before anything dials.
- The rest join the call queue — the same queue that handles follow-ups and callbacks.
- The dispatcher works through them, respecting your calling hours, your concurrent-line limit, your balance and your retry settings.
- Results are written back as each call completes, so the progress counter is live.
Note
Campaigns are the lowest priority in the queue, deliberately. Auto-callbacks and follow-ups jump ahead of them, because someone is waiting on those. On a busy day your campaign dials slowly — that's the design working, not a fault.
Controlling a running campaign
The list shows each campaign's status, a progress counter and the created date, refreshing every few seconds.
| Action | What it does |
|---|---|
| Run | Starts a draft campaign. |
| Pause | Stops further dialling. Calls already in progress finish. |
| Resume | Picks up where it left off — the contacts not yet called are re-queued. |
Pausing is safe and loses nothing.
Retries
By default a campaign contact is tried once. A busy signal or no answer means that contact is marked failed and the campaign moves on.
That's usually the right behaviour for bulk outreach — repeatedly ringing people who didn't pick up is how you end up marked as spam. If you want retries, raise the campaign attempt count in Call queue settings. Your plan enforces a minimum gap between attempts whatever you set.
Reading the progress counter
completed / total counts contacts that have been processed, not contacts that answered. Skipped
(do-not-call) and failed contacts count as processed.
To see what actually happened, look at the call log or the individual contacts.
Limits and gotchas
- Campaigns need Professional or above. On Trial and Starter the module is locked.
- Your plan limits campaigns per month. See Plans & limits; more can be bought as an add-on.
- Contacts without a phone number are silently skipped and stay pending — which means a campaign where everyone left lacks a number will never show as finished.
- You can't edit a campaign after creating it. No adding contacts, no changing the name, no deleting it. Make a new one.
- Your email must be verified to start or resume a campaign.
Running campaigns responsibly
Bulk outbound is the part of this product most likely to cause you problems if used carelessly.
- Only call people who expect to hear from you. Existing customers and enquiries, not a purchased list.
- Set calling hours and respect them. See Call queue.
- Honour opt-outs immediately — put them on the DNC list rather than remembering not to include them next time.
- Keep AI disclosure on for outbound. People are much more forgiving of an AI that says so.
- Start small. Run 20 contacts, read the transcripts, fix the agent, then run 500.