Skip to main content
IA ELOHelp center
Outbound calls

Create an outbound campaign

Import contacts, map data, test and launch a campaign with controlled pacing.

A campaign calls a contact list while giving the bot shared context and row-specific data.

Prepare the file

Use an Excel or CSV file with a header row. One column must contain the telephone number. Other columns can provide a name, reference, amount or any data useful to the scenario.

Include only information required for the call.

Create the campaign

  1. Name the campaign and choose the bot.
  2. Describe the shared objective.
  3. Import the file, then select the telephone number column.
  4. Map the other columns to labels the bot can understand.
  5. Select the required campaign type: direct marketing, marketing with explicit consent, or transactional.
  6. Set the date, pacing and maximum number of concurrent calls.
  7. If an external system must be notified, enter its HTTPS URL under Completion notification.
  8. Save as draft or schedule it.

Receive the completion notification

The webhook is optional. BeAI calls it asynchronously once all campaign contacts have reached a final state. A temporary failure triggers several retries.

The notification is deliberately minimal: it contains the outbound_campaign.completed event, the campaign identifier, the completed status, a delivery identifier and the GET /api/v1/outbound-campaigns/{id} route. It contains no contact details, transcript or detailed result. The receiving system can use its own BeAI API key to retrieve only the information it is authorised to access.

Make a test call

Use Test call to enter your number and representative values for each column. The test checks the prompt and behaviour without launching the full list.

Control pacing

The selected number remains subject to the global server limit and your SIP operator's limits. A campaign configured for three concurrent calls may progress more slowly if other calls already use the available capacity.

DNCM control

For direct marketing, BeAI checks the number against the DNCM list. A recent cached decision is used first, then the official API when required. If the API is unavailable and no local decision exists, the call may proceed in degraded mode and the decision is logged.

Monitor and reuse

Open the pre-filtered conversations from the campaign. You can remove or edit eligible contacts, duplicate a campaign to reuse its context with a new file, and restart a campaign using the available actions.

Documentation updated with the application