Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Campaigns

Campaigns let your voicebot call a list of contacts automatically - with business hours, retries and per-contact personalisation.

A campaign is a list of phone numbers that your voicebot calls on its own. You upload the contacts (optionally with extra data such as name or contract number), define when and how often the bot may call, and launch it. The platform then dials every contact, runs your conversation flow and records the result of each call.

Campaigns are available in projects with outbound calling enabled. You find them in the left menu under Campaigns.

Campaign types

Type
When to use it
How it ends

Batch

You have a fixed list of contacts known in advance (e.g. a daily list of 200 leads). Upload all numbers, launch, get a complete report.

Automatically, once every contact has been attempted - or when you stop it. A finished batch campaign cannot be launched again (copy it instead).

Continuous

Contacts arrive over time - from a CRM, a web form or another integration. New numbers are called as soon as they are added.

Never on its own - it runs until you stop it.

The type is chosen when the campaign is created and cannot be changed later.

How a campaign works

  1. Create the campaign and configure the calling line, business hours and retry rules. A new campaign is always inactive.

  2. Upload contacts - an Excel file with a phone number column and any number of extra columns (metadata).

  3. Launch - all contacts are put into the call queue.

  4. Dialling - the platform picks the next contact whenever all of the following allow it:

    • the current time is within the campaign's business hours (in the campaign timezone),

    • today is not a public holiday (unless Call on holidays is on),

    • the max. parallel calls limit of the campaign and of your organisation is not reached,

    • the retry delay of the contact has passed.

  5. The call is answered - your conversation flow runs. The flow can load the contact's metadata with get_campaign_call_metadata and store the outcome with update_campaign_call_result.

  6. The call is not answered (busy, no answer, disconnected) - the contact is scheduled for another attempt according to the retry rules. The flow can additionally react in the Start node - see Unsuccessful calls.

  7. Result - each contact ends up as Processed (successful) or Failed (all attempts used up).

Pages in this section

Last updated

Was this helpful?