Outbound campaigns
Reach your customer list, on your schedule.
Load a list, map its columns, pick a channel and a time window. On the phone, your outbound agent holds the conversation and can book a callback.
- Channel
- Phone
- Audience
- appointments.csv · name, phone, consent
- Window
- Mon–Sat · 09:00–18:00
- Reach
- 5 at once · 3 tries
- Load list
- Map columns
- Call
- Callback
- Timeline
How it works
How a campaign runs
A campaign belongs to a project and pins the agent workflow that handles the conversation.
Audience
Choose a file from a project data source and link its columns to fields: name, contact, language, timezone, consent, policy number.
Channel
Phone, e-mail, chat, WhatsApp or Telegram, each with its own contact field.
Window
Days of the week, start and end time, and the campaign timezone.
Reach
How many people at once, and how many tries per person.
Follow
Statistics, a calendar of callbacks and a timeline for each person.
Built in
What comes with it.
Audience from your files
Pick a file from a project data source, check the rows and link columns to fields. Columns with matching names are linked for you.
Five channels
Phone attempts go to the dialer queue; e-mail, chat, WhatsApp and Telegram messages go through your connected channel.
Time windows
Days, hours and timezone for each campaign. People are only reached inside the window.
Attempts and retries
Set how many people are reached at once and how many tries each person gets.
Callbacks during the call
When someone asks to be called later, the agent books a slot inside the callback window, with a slot cap and a rule for full slots.
Campaign statistics
Audience progress, consent, call results (completed, no answer, failed) and the reach queue.
Timeline per person
Calls, callbacks and reach attempts for each person, with filters and CSV export.
The agent holds the conversation
Phone campaigns pin an agent workflow. It follows its instructions and knowledge, and its analysis records the outcome of each call.
Example scenario
Appointment confirmation calls
Illustrative example, not a customer case. A clinic starts from the Appointment confirmation calls template.
- 01Load tomorrow’s appointment list
- 02Link name, phone and consent
- 03Calls run Monday to Saturday, 9:00 to 18:00
- 04A patient asks to be called back at 10:00 and the agent books it
- 05The team follows confirmed, rescheduled and unreachable patients
Control
Rules before every attempt
The campaign checks each person before reaching out.
- People with consent “no” are skipped
- Nothing goes out outside the window
- A maximum number of tries per person
- No new attempt while one is still open
- People already contacted keep their result when a new file is loaded
Campaign questions
Outbound campaigns with AI agents, answered.
Which channels can an outbound campaign use?
Phone, e-mail, chat, WhatsApp and Telegram. Phone attempts go to the dialer queue and are handled by the agent workflow pinned to the campaign; the other channels send a message through the channel connected to your workspace.
How do we import the customer list?
Choose a file from a data source linked to the project, check the rows, then link its columns to the campaign fields: name and the contact for the channel, plus optional language, timezone, consent and a policy number passed to the agent.
Can we control when people are contacted?
Yes. Each campaign has its days, hours and timezone, a number of people reached at once and a maximum number of tries. Callbacks booked during a call follow their own window, minimum lead time and slot cap.
How is consent handled?
Each person can carry a consent value. People marked “no” are skipped, and the campaign statistics show how many consented, declined or have no value yet.
How do we follow a campaign’s results?
Campaign statistics show audience progress, call results and the reach queue. Each person has a timeline of calls, callbacks and attempts, and both the history and the audience can be exported as CSV.