Create an outbound calling campaign
Four decisions: the line, who answers, the audience and the sequence. Everything a campaign could duplicate from elsewhere has been left where it already lives.
A campaign form is short and that is deliberate. Everything it could plausibly duplicate has been left where it already lives: the bot owns its instruction, voice and model; the channel owns concurrency and calling hours; the contact schema owns what a person is.
What remains is genuinely campaign-shaped — which line, who answers, who we are calling, and how we follow up. Four decisions.
The one piece of advice that matters more than the rest: run it against twenty contacts first and listen to two of the recordings. A campaign is the one thing in this product that can annoy four thousand people before lunch.
Before you start
- A calling channel with outgoing enabled.
- A call bot you have tested, or a call flow.
- An audience — a filter, a list or a file.
- Confirmation that you are permitted to call these people.
Steps
Open Campaigns and create one
Campaigns are a rail item beside AI bots and Workflows, because building them is regular work rather than a settings pane.
Pick the line
An existing calling channel with outgoing enabled. A campaign never defines a line of its own — which means it inherits the hours and the concurrency that line already has.
Pick who answers
An AI bot or a call flow, with inline create if you need one. The list shows this as a BOT or FLOW chip and the name, because it is the only thing about a campaign you cannot infer.
Build the audience
A dynamic filter, a static list, or an import. The choice matters more than people expect — a dynamic filter keeps picking up new matches while the campaign runs.
Write the follow-up sequence in sentences
Calling hours and the follow-up, written in plain English. Six lines ship as the default and you edit them rather than starting from nothing.
Check the inherited calling hours
The campaign shows the pattern and timezone it inherited from the channel. Override only if this campaign genuinely differs, and remember an override can only narrow.
Start it against twenty contacts
Then stop, listen to two recordings, and read three contacts' activity feeds. Ten minutes here prevents the campaign you have to apologise for.
Check it worked
Watch the four numbers at the top of Campaigns after your first small run: dial attempts, connect rate, meetings booked and active campaigns. If the connect rate is very low, the problem is your list or your number, not your script — and you should fix that before scaling.
The parts people get wrong
- You cannot set the model, the instruction or the voice on a campaign. The bot owns those, which means changing them changes every campaign and channel using that bot.
- Concurrency lives on the channel. Two campaigns on one line share the same allowed calls count, along with every inbound call.
- A campaign is always outbound. There is no direction control, because a campaign that waits for the phone to ring is just a channel.