Skip to main content
Creating a campaign means putting a bot to work on a list of cases. The wizard walks you through: pick the bot, upload the file, and confirm. It opens with the Create campaign button, at the top right of a bot’s Campaigns section, next to Campaign list. It’s also in the filter bar of Campaign monitoring, for when you aren’t coming from one bot in particular. Either way the wizard opens in a window over the screen, so you don’t lose what you were looking at.
Creating a campaign triggers real calls from the chosen bot, within its configured schedule. It isn’t a test action: if you want to experiment, do it with a test bot and a test file.

The short way

1

Go into the bot

Module menu (⊞) → Operations → Bots, and press the bot’s card. It opens on its Campaigns section.
2

Open Create campaign

The button sits at the top right. If you don’t see it, your user doesn’t have permission to create campaigns.
3

Pick the bot

Type the name or the alias. Only outbound bots show up.
4

Upload the file

Name the campaign and upload the list of cases. Every other field already comes filled in.
5

Check the validation and confirm

The system checks the file before creating anything. If the result is what you expected, press Create campaign.
Each step, in detail:

Step 1: pick the bot

The wizard opens with a bot search. Type the name or alias and pick the right one. Only outbound bots appear: the ones that just receive incoming calls don’t run campaigns, so they aren’t on the list.

Step 2: name, description and file

With the bot chosen, you fill in: The file has to follow the structure you configured in Campaign Input for that bot: which column carries the phone number, which one the case identifier, which ones the data the bot uses during the conversation.

The rest of the fields come pre-filled

The remaining configuration —start date, schedule, dial mode, retries and phone priority— arrives with sensible defaults, so you can create the campaign without touching them:
If you’re not sure what any of those fields mean, they’re explained one by one in Campaigns. It’s worth reviewing them before a large campaign: Retries set to 1 means a single call per phone number.

Step 3: file validation

When you continue, the system checks the file before creating anything: that the expected columns are there, that the phone numbers are valid, that there are no duplicates. It takes a few seconds and ends in one of three ways:
The file was uploaded successfully. You’ll see the breakdown of how many cases were loaded, how many were filtered out or had errors, how many were discarded due to rest and how many were validated and ready to handle.
The file was uploaded, but no case is left to handle. Every case fell out through filtering or rest. The campaign would have nobody to call.
The file contains errors. You’ll get the detail of what failed so you can fix it and upload it again.
Only if the validation succeeds does the button to continue become available.
This step hasn’t created anything yet. If the result isn’t what you expected, fix the file and upload it again without having left a half-made campaign behind.

Phone validation (ENACOM)

In Argentina, phone numbers are checked against the regulator’s public numbering assignment registry before any call is placed. Numbers that don’t exist, and those in a range not assigned to any carrier, are dropped. If the bot has this validation active, uploading the file shows a notice that it’s on and that processing may take a bit longer. The result shows up in the validation step, under Phone validation (ENACOM), with three figures: If the file brings no phone number to validate, the block doesn’t appear at all.

Why a number gets dropped

The validation also classifies each number as mobile or landline by its format.
If you’re uploading numbers you know exist and they still get filtered, check the format first: the 0 and the 15 explain almost every case.

When it applies

It isn’t a campaign setting: it’s configured per bot and Inceptia turns it on. Ask Customer Success if you want it switched on or off. And being switched on isn’t enough. The filter only runs if the bot meets all four conditions at once:
  • Argentina time zone,
  • outbound bot,
  • voice bot,
  • campaign input on version 2.
If any one is missing, the filter has no effect even though it shows as active.
The quick way to tell whether a bot has it running is to upload a file: if the notice doesn’t show up in step 2, the filter isn’t being applied to that bot.
Once the campaign is created, the filtered phone numbers stay in its detail, in Campaigns.

Step 4: confirm

Create campaign opens a confirmation before doing anything. Once you accept, the campaign is created and the file finishes processing, which can take a few more seconds. When it’s done, you get a direct link to the detail of the campaign you just created. From there you can also start another one without closing the wizard.

After creating it

The campaign already shows up in the list with the number of cases that passed validation. It starts out ongoing and begins working right away — unless you gave it a future date or created it outside its time window: in those two cases it starts out scheduled and kicks off on its own when the time comes. To follow it, pause it or finish it, see Campaigns.
If you need to create campaigns from your own system instead of doing it by hand, the API covers the same flow: Create campaign and Upload cases.