Skip to main content

Campaign launch

Open Campaigns and select Create campaign. A campaign is not assembled in a dialog box but on a page of its own — a wizard with five steps: Campaign → Schedule → Dialing → Contacts → Review and launch Any user of the organization can create and launch a campaign. There is one restriction: only administrators and developers can pick a hidden agent. Next is inactive while the fields of the step have errors: the error is shown under the field, and the line next to the button reads “Fix the errors in the fields above”. On the Contacts step the button is called Review, on the Review and launch step — Launch. Leaving the page warns about unsaved changes. Visited steps stay open for going back, steps ahead are locked.
The campaign record is created when you move on to the Contacts step: before that there is nowhere to upload contacts or to compute the effective calling window. An existing campaign is edited in the dialog box on the campaign card, not in the wizard — the fields there are the same, except the Attempt counting and Frequency settings groups.

Step 1. Campaign

The Basics group — name and agent:
  • Campaign name — 1 to 80 characters.
  • Agent — published agents only. The field is a searchable list: start typing to filter by name instead of scrolling. Members are offered only agents visible to them; for administrators and developers a hidden agent carries a · hidden from members suffix.
  • Classification — the call purpose: Marketing, Servicing, or Debt collection. A new campaign starts with the organization’s default campaign classification; if the organization has none, the field is empty and must be filled in. It sets the consent tier required from the subscriber and the exact legal wording the operator signs at launch. The required tier is shown on the Review and launch step above the attestation: “Classification · requires PEWC” (or PEC).
Classification cannot be changed after launch — otherwise the attestation signature would no longer match what it was signed under. The platform does not check the classification against the agent’s flow: the campaign gets exactly the one selected. If the conversation has any marketing content at all, choose Marketing — the required consent and the call frequency rules depend on the classification.
The Campaign step: name, agent and the mandatory classification The agent field opened: a search box filters the list by name

Step 2. Schedule

The Date range & time group:
  • Time zone — the organization’s zone, shown as text: the zone and the organization name. Contacts are called and working hours apply in this zone. For an organization with the US market profile this zone only displays dates, while calls and working hours follow each contact’s local time; without working hours calls go only within the contact’s legal window. The zone is changed in the organization settings — the Organization settings link is next to it.
  • Start and End — the dates the campaign is allowed to dial. They are entered in your computer’s time zone; if it differs from the campaign zone, the field is marked “this computer, …”, and under the date the same moment is shown in the campaign zone (”= … (organization)”, with a previous or next day mark). The start is no earlier than today, the end is strictly after the start.
  • Open the campaign to call additions — set only at creation. Such a campaign requires an end date; it may launch without contacts, and a drained queue does not complete it — new calls arrive through the API. See Adding calls.
  • Call in the contact’s local time — calling windows are computed in each contact’s zone. This affects dialing, not the displayed campaign dates. Organizations on the US market profile do not see this checkbox: their calling windows are always computed in the contact’s zone from the ZIP code or state (US campaigns).
The Calling windows group:
  • Restrict to a schedule (optional) — a toggle. Turn it on to set weekdays and time intervals, for example 09:00–18:00.
  • If no schedule is set, the platform states what applies instead: “No schedules set — the organization’s calling window 08:00—21:00 applies”. Round-the-clock dialing does not exist — see The organization calling window.
  • Effective calling window — what the restrictions actually add up to. It appears once the campaign record exists (that is, when you come back to this step). If the calling window was narrowed after the schedule was saved, the platform says so: “Narrowed to the organization’s calling window … — the saved value is kept” (or “Narrowed to the platform calling window …”). Your saved schedule is not rewritten.
The Schedule step with the restriction off: the organization calling window applies

The organization calling window

An organization on the Kazakhstan market profile has a calling window — an interval that applies every day of the week in the dialing time zone. The platform default is 08:00–21:00. Under the US profile the lower bound is the legal window of the contact’s jurisdiction, see US campaigns.
  • A campaign schedule may only narrow the window. A schedule wider than the window is not saved: the platform names the interval and the window it goes beyond.
  • An empty campaign schedule equals the organization window on all seven days.
  • A contact outside the window is not dropped but deferred until the window next opens.
  • If the window changes and the campaign schedule no longer intersects it, contacts are refused with “No legal calling window (empty intersection)”.
  • The window itself is set only by the platform administrator; the change is audited.
The organization’s calling rules — the window, frequency and voicemail (Organization → Settings tab → Edit settings → Calling rules section) — also apply to a running campaign, starting from the next call. Organization settings: the calling market profile and the calling window set to the 08:00—21:00 platform default

Step 3. Dialing

Telephony — a collapsible group with a summary line:
  • SIP trunk — the trunk used for outbound calls. If the organization has exactly one, the field opens already filled in: a choice with no alternatives is not a choice, it is an extra step. With two or more the platform does not guess.
  • Subgroup — automatic by trunk and agent pair, or another available option. Once the trunk is filled in, the label names the subgroup that will be used right away. If the agent is not attached to any outbound subgroup of the selected trunk, a warning appears under the field — “Agent ”…” is not attached to any outbound subgroup of this trunk — launch will be blocked.” — with a Configure in Telephony link.
  • Caller ID — the number the subscriber sees. The By subgroup policy option leaves the choice of number to the subgroup, and the label names the actual number whenever the pool holds only one.
The autofill only applies when a campaign is created. On a saved campaign an empty trunk is a deliberate state, and the platform writes nothing into it. Anything filled in for you can be changed by hand or set back to empty.
The Speed & duplicates group:
  • Dialing speed — calls per minute, any whole number from 1 to 200. The list offers ready-made values: 1, 2, 5, 10, 20, 30, 60, 100, 200. For any other value tick Set a custom speed: the list is locked and a Calls per minute field appears. A value outside the range shows “Enter a whole number from 1 to 200” under the field, and Next stays unavailable until it is fixed.
  • Auto-speed mode — a checkbox under Set a custom speed: the platform picks the speed, see Auto speed below. While it is ticked, the speed list and Set a custom speed are locked.
  • Duplicate numbers — how repeated contacts are handled, for example reject them and report them.
The speed is an upper bound of the campaign’s pace. Deferred dials (a contact outside the window, a frequency cap) do not consume it. There is no platform ceiling that would cut the value you chose; the trunk subgroup may have its own calls-per-minute limit.

Auto speed

With Auto-speed mode you don’t work out the speed yourself: the platform picks it so that the whole base is dialed before the campaign ends.
  • How it is computed. The platform estimates how many dials are still needed — counting callbacks and how many retries fit by the interval — and picks the lowest steady pace at which every attempt still fits before the campaign end, given the retry interval. Only working minutes count — the campaign working hours inside the calling window. That is why the speed at the start is a little higher than plain dials divided by minutes: the last attempts need time left for their interval. For example, 10,000 contacts with 15 attempts every 10 minutes over 6 hours need 128 dials a minute, not 115. Towards the end of the window the speed goes down by itself.
  • Below target because of the interval. If the campaign dials slower than its target while the limits are not reached, the contacts are usually waiting out the retry interval — there is no one to dial yet.
  • Callbacks. For the first 50 attempts the callback share is a default; after that it is measured on the campaign itself, over the last 30 minutes. Late in the day the base is left with people who don’t pick up, and each contact needs more dials — the speed takes this into account.
  • Recomputed every 10 minutes, with one computation for the whole campaign. When another auto-speed campaign starts or stops, the speed is recomputed at once, but no more often than once a minute. Between recomputations the speed holds. In one recomputation it goes down by at most 20 % and, when catching up, goes up by at most 50 %.
  • Ceilings. The speed never goes above the calls-per-minute limit of the trunk’s outbound subgroup, the platform ceiling of 200 per minute, or what the organization’s concurrent call limit can carry. When several campaigns run on auto speed, the shared limits are split between them in proportion to their need; campaigns with a manual speed take their share first.
  • What it needs. The End date is required. If the campaign runs over several days (its window crosses midnight in the campaign time zone), it also needs working hours on the Schedule step — otherwise the dials would spread into the night. Without them an error appears under the checkbox and the launch is blocked.
  • The manual speed is kept. Untick the box and the campaign goes back to the speed chosen in the list.
Auto speed is an estimate, not a guarantee. It does not account for the capacity of the number pool, the trunk refusing dials over its limit or the time zones of individual contacts. What limits the campaign is shown on the Review and launch step in the Speed group.
The Attempt counting group — Count attempts to a phone number across: all campaigns of the organization or this campaign only. This scale drives attempt numbers only; the voicemail pauses and caps, legal caps and the organization’s frequency policy always count every campaign. The Retries & strategy group:
  • Retries — how many times to call back on top of the first dial, 0 to 29. The first dial is not included in that number: both figures always stand under the field, for example “9 retries · 10 dials”.
  • Redial intervals — two modes:
    • Same interval — one identical pause between all dials of the same number.
    • Per-retry intervals — an interval per retry, set on the Retry 1, Retry 2, … pills. This is how a “often first, rarely later” ladder is built, for example 2 min → 5 min → 1 d → 3 d. At the retry limit the + add retry button gives way to the caption “Maximum 29 retries · 30 dials” — the same 30 attempts the Web API accepts.
  • Intervals come from a fixed list of values — from 1 minute to 7 days.
  • Dialing logic — Standard (a dial budget and an interval) or Expert logic (rules of the form “if reason → action”). Expert logic adds the preset selector and the rule editor below.
What standard logic redials. The number is dialed again after the campaign interval, while dials are left and the campaign has not ended:
  • not reached — Busy, No answer and other failed dials;
  • answered, but not by a person — voicemail (whether or not the agent left a message), a call screener that ran out of its timeout, a voice menu with buttons.
A conversation with a person closes the number. A call screener that declined the call counts as User declined: under the US profile the number is not dialed again, under other profiles it is redialed. How many messages to leave on voicemail is decided by the voicemail message policy. The full table of outcomes is in Call outcomes.
A campaign can carry a stored dial budget larger than the current limit — for example, one created through the Web API. The real number is shown as is, with no silent clamping, and is labelled “Stored budget shown as is — it cannot be increased”.
Two more groups follow:
  • Frequency settings — attempt limits per number. A campaign inherits the organization settings or makes them stricter: lowers the limits or increases the waiting time. They can be changed only in a draft.
  • Voicemail message policy — when the agent leaves a message on voicemail. A campaign inherits the organization policy or overrides it with Override for this campaign; Reset to organization policy removes the override.
See Call frequency. The Dialing step: telephony, speed and duplicates, retries as a pair of figures Per-retry intervals mode with the retry pills

Rule actions

An expert logic rule is a pair: If a condition → Then an action. There are three actions: Conditions: Busy, Dial failed, No answer, Voicemail reached, Hung up before threshold and Goal not achieved. Dial failed means the dial gave no connection and telephony reported no precise reason; the dial attempt is spent. A rule’s Times field limits how many times it can fire for one contact. Expert logic is standard logic plus rules. An outcome with no rule, or whose rule has used up its Times, is handled as in standard logic. For example, voicemail without a rule of its own is redialed after the campaign interval while dials are left. To stop redialing voicemail, add the rule Voicemail reached → Stop calling this number — the Conservative preset does exactly that. Redial after a delay gives each outcome its own interval: for example, redial Busy in 10 minutes and No answer and Voicemail reached in 2 hours.
  • For that contact, the rule interval replaces the campaign interval.
  • The calling window, the do-not-call registry and the caps apply as to any retry.
  • The action is available for every condition that allows a retry, including Hung up before threshold and Goal not achieved.
  • The campaign card shows the interval next to the rule, for example ” · 1 h 30 min”.
  • If the interval is not shorter than the time left until the campaign ends, the launch shows the warning “The rule interval (…) is not shorter than the remaining campaign window (…) — this retry will not happen”.

Dialing strategy presets

Inside expert logic, a Strategy preset selector appears above the rule editor — a ready-made rule set instead of assembling one from scratch. Three are built in: How it behaves:
  • Editing any rule of a preset switches the selector to Own rules (from ”…”) — a preset is never detached silently.
  • Save as preset is available only for own rules; your own preset can be updated, renamed, and deleted, a built-in one cannot. The limit is 20 presets per organization.
  • Editing your preset does not change the rules of campaigns already configured: a preset is a template, not a live reference.
  • A preset carries rules only. The retry count and the intervals stay campaign fields and are untouched by the selector.
  • Rule order is visible in the list and affects the outcome — rules are evaluated top to bottom.
The selector lives inside expert mode: it does not switch the dialing logic from standard to expert, it only fills the rules of the expert logic you already chose.
The Strategy preset selector and the rule editor inside expert logic

Step 4. Contacts

Upload a contacts file in CSV or XLSX. The phone column is recognized by its header, and the remaining columns become call variables. The import report lists accepted rows, warnings, rejected rows with their row numbers and reasons, duplicates, and column fill rates; it exports to CSV or XLSX. Above the report sits the Matches against the do-not-call registry panel — numbers from your organization’s do-not-call registry. If there are matches, choose a decision:
  • Block the launch — I will remove the matches from the file;
  • Skip them and launch the campaign without them.
The decision is written to the campaign audit: who, when, how many contacts and for which file. Until a decision is made, the launch is blocked. For more on uploads and the import report, see Campaign contacts.

Step 5. Review and launch

The final step shows a summary of the settings, the check findings and the attestation signature. The findings fall into three blocks:
  • Launch is not possible — blockers: while any remain, the campaign will not launch.
  • Warnings — do not block the launch but are worth reading.
  • How the dialing will go — notes: the platform describes the dialing plan without suggesting a fix.
A campaign with auto speed also has a Speed group above them: “Auto · needed N/min · achievable M/min”. Below it is either “The window fits — the plan will reach every contact in time.” or what limits the campaign: the outbound subgroup of the trunk, the concurrent call limit of the organization or the platform ceiling. In the second case part of the base will not be reached before the campaign end — next to it are the Go to the schedule and Go to the speed links. This is not a blocker. Frequent blockers:
  • “No contacts ready to dial — upload a contacts file”;
  • “Contacts in the file are in the do-not-call registry — remove them or confirm the launch without them”;
  • “Dialing binding is incomplete: trunk, subgroup or Caller ID unavailable”;
  • “Expert logic has no rules — add a rule or switch back to standard”;
  • “Start date is in the past” and “The campaign end has already passed”;
  • “The campaign agent has no published version”;
  • “The agent is not configured correctly — contact support” — this is how a member and a manager see errors in the agent’s published version: in the recognition, synthesis or model settings, a knowledge base or audio file not found, an unpublished transfer target agent. They cannot fix them themselves. An administrator or developer sees the errors themselves in place of this line;
  • “The campaign agent is hidden from members” — the person launching is a member and the agent is hidden from them. An administrator or developer launches the same campaign without the blocker;
  • “N contacts in file ”…” have no usable location and cannot be dialed — fix the file and upload it again”. There is no way around it: a partial launch is not possible;
  • “Contact file is missing a required column: … The agent … needs it for every contact — add the column and upload the file again”. Which variables form the signature is set on the agent — see Agent variables;
  • “All campaign contacts are in the do-not-call registry — there is nobody to call”;
  • “The rule ”…” retries a permanent reason — remove it or change the action”;
  • “Auto speed needs the campaign end — set the end date or switch to a manual speed” and “Auto speed over several days needs the working hours — set the campaign schedule or switch to a manual speed”.
Warnings — for example: “The retry schedule is longer than the campaign window — N retries will not happen” — the interval ladder does not fit into the campaign dates. A manual speed gets a warning when it is above the limit of the trunk subgroup (“the dials above it will be refused and retried”) or needs more concurrent calls than the organization has. A voice setting outside the synthesis provider’s range is also a warning: the agent will speak with the nearest allowed value — see Voice. Warnings about provider settings are shown only to an administrator and a developer — a member and a manager see them neither at launch, nor at resume, nor when adding contacts. Notes — for example: “A frequency policy is active: at most N attempts per 7 days and N per day per number” or “Working hours are not set — dialing is limited by the organization’s calling window 08:00–21:00”.

How to read the findings list

  • A blocker names the field it belongs to next to its text. Findings carry a Go to … link — to the contacts, the schedule, the retry rules and so on: it jumps to the wizard step where that field lives. Findings about the market profile and the attestation have no link, and neither do notes: there is nothing to fix on the wizard steps.
  • Findings of the same kind collapse. Four or more warnings about the same variables fold into one expandable row; up to three they are listed one by one.
  • Technical findings carry two halves of text: a sentence for a human on top, and the technical part under a collapsible “More for the administrator”.
  • Finding texts arrive in the cabinet’s language. The server returns a code with parameters and the cabinet renders the text, so the numbers inside a phrase — filled out of how many, which cap, which condition — are substituted as separate values.
Only the agent’s signature is checked against the file columns — the variables ticked In signature on the agent, see Agent variables. A signature variable with no column is a blocker: the campaign cannot be launched or resumed, and a batch of contacts without that column cannot be added to a running campaign. Warnings about a partly filled column or a header spelled differently from the variable also concern signature variables only. Any other variable is a working variable of the flow and yields neither a blocker nor a warning. The check runs against the agent’s current published version; an agent with an empty signature is not checked against the file columns at all.
Permission attestation — the signature stating that consent to call has been obtained. Above it stand the classification and the required consent tier; the wording comes from the server and depends on the classification from step 1. It is a legal statement, not a formality: the record captures who signed and when. The attestation is not in the blockers list: until its checkbox is ticked, Launch is inactive with the hint “Sign the permission attestation to launch”. Replacing the contacts file clears the checkbox — a new version of the file has to be attested again. The Review and launch step: blockers, warnings and the permission attestation After Launch the campaign card opens. If the start is still ahead, the campaign waits for it in the Scheduled status; if the start time has already come, dialing begins immediately.
After launch the dialing configuration is frozen: changing the retries, the rules or other settings requires a new campaign. The exception is the dialing speed and auto-speed mode: they can be changed on a scheduled, running or paused campaign, see Campaign details. That is why a first launch is done on 20–30 contacts rather than the whole base.