Outbound calling campaigns
Outbound AI calling burns lists and breaks quiet hours. Zumu dials inside the window, every time.
Zumu’s outbound AI calling checks the callee’s own quiet hours before a single number dials, catches a voicemail box before an agent wastes a turn on it, and stops itself the moment a campaign hits its daily budget cap.
- Quiet hours computed from the callee’s area code
- Voicemail handling the campaign enforces itself
- A daily budget cap the queue cannot cross
- A consent gate before barge-in in two-party states
- default quiet-hours window, in the callee’s resolved local timeProduct default. Adjustable per organization
- 9a–8p
- outcome recorded on every dial attemptConnected, voicemail, no answer, or capped. Never a blank row
- Typed
- budget cap enforced on the campaign itselfYou set the ceiling. The dialer stops there
- Daily
- consent states get a gate before a supervisor can barge inRequires an organization-level acknowledgement first
- Two-party
These are configuration defaults you can change per agent or per organization, not fixed limits of the platform.
Quiet hours, computed per number
Every number gets its own clock
A campaign contact carries an area code, and Zumu resolves that to a real local time zone before it ever reaches the dialer. The window is checked again the moment a number is about to dial, not only when the list was imported.
(212) •••-••18
(312) •••-••63
(602) •••-••91
(415) •••-••42
(206) •••-••05
What outbound costs you today
The list you already burned
Outbound calling breaks in the same few places on almost every list. None of it shows up until the complaint, the fine, or the afternoon nobody wants to talk about.
Today
The bill you are already paying
- A list dialed at the wrong hour turns into a complaint instead of a lead
- Agents spend the afternoon dialing voicemail boxes one at a time
- A budget nobody was watching becomes a surprise on the invoice
- Nobody can show which calls happened inside the window and which did not
With Zumu
What changes on the first campaign
- Every number dials inside its own quiet hours, checked at the moment it dials
- A voicemail outcome marks the job and releases the line
- The campaign halts itself at the budget you set, not the one you meant to set
- Every outbound call sits on the same record as an inbound one
Which hour a call lands in stops being a habit somebody has to remember and starts being a setting the dialer checks.
The controls
Five things a campaign checks before it dials
Each one traces to a real setting in the outbound dispatcher, not a marketing gloss over a spreadsheet of phone numbers.
- 01The default control
Quiet hours, computed per number
Every contact carries a phone number, and every phone number resolves to a real area code and a real local time zone. The window defaults to nine in the morning to eight at night in that time zone, and it is not read once from your organization’s own clock.
- Default window: 9 AM to 8 PM, callee’s local time
- Set at the organization level, not hardcoded in the dialer
- Checked again the moment a number is about to dial, not only at import
- 02
A machine answer ends the job cleanly
Campaign policy decides what happens when a voicemail box picks up. The job is marked with a voicemail outcome and the line is released, so the queue moves on instead of reading a script to a beep.
- Voicemail is a typed outcome on the job record
- The line is released, not left open on a machine
- Handling is set by campaign rules, not agent habit
- 03
The queue stops itself
A daily budget cap sits on the campaign, not on a dashboard alert somebody has to notice. Once the cap is reached, dialing halts for the day instead of continuing on momentum.
- Enforced per campaign, per day
- The dialer halts. Nobody has to catch it after the fact.
- Resumes on the next scheduled day, at the cap you chose
- 04
Two-party states get an extra gate
States with two-party consent wiretap law get a control most outbound tools skip: a supervisor cannot barge into the live audio of a call in those states until the organization has acknowledged the consent requirement.
- Applies in states like California, Illinois, and Washington
- The acknowledgement sits at the organization level, once
- Listening in and coaching notes still work; barging into live audio is what is gated
- 05
When someone answers and wants a person, one exists
A campaign call that turns into a real conversation does not have to end at the agent. The same warm-handoff path used on inbound calls is available here, bringing your specialist into the room instead of promising a callback.
- The same warm-transfer mechanics as an inbound call
- Recording and the session report continue through the handoff
- A declined or missed handoff falls back the same way an inbound one does
The list does not know what time it is on the other end.
Part of the same platform
Campaigns do not run alone
The same agents, the same reporting, and the same handoff rules that work on inbound calls carry straight into outbound.
AI voice agents
The same agent that answers your inbound line places the outbound call. One prompt, one voice, one revision history, in either direction.
See how agents are configuredAnalytics and QA
A campaign call produces the same session report as an inbound one: cost, outcome, and a transcript, not a shorter dial log with less in it.
See what a session report holds
Questions
What operators ask before they run a campaign
Still have questions?
Bring a list you are nervous about. We will show you where it would and would not have dialed.
Book a demo
Bring us a list you are afraid to dial
Show us the state mix and the hours you are worried about. We will set up a campaign against your own quiet-hours defaults and your own budget cap, live, so you can see where it would and would not have dialed.
- No credit card for the demo
- Your own area codes, your own hours