The Campaigns section organizes outbound calling operations. A Campaign connects:
The selected AI Agent supplies the conversation instructions, voice, language, Knowledge Base, appointment tools, and outbound Phone Number. The selected Leads determine who will receive calls.
The relationship is:
Creating a Campaign does not automatically mean that calls begin immediately. A Campaign created without a future schedule starts with an idle status and must be launched by the user. A Campaign created with a valid future date and time receives a scheduled status and is started by the Campaign scheduler when it becomes due.
A Campaign controls:
A Campaign does not directly store:
Those items come from the selected Agent.
Determines:
Determines:
Changing an Agent after testing can affect every Campaign that uses that Agent.
A Lead is one contact record.
A Campaign is a group of Lead records assigned to one calling operation.
Example:
The Campaign can contain all three Leads.
The Campaign is the calling plan.
A Call Log is the record of one individual call attempt.
Example:
Repeated Campaign launches or multiple attempts can produce more than one Call Log for the same Lead.
After signing in:
The page heading is:
The description states:
The page contains:
The page does not currently show a general Campaign search box or status filter.
When no Campaigns exist, the page displays:
with the explanation:
Select Create Campaign to begin.
When the page cannot retrieve Campaigns, it displays:
Possible causes include:
Refresh once and confirm that another protected page opens before creating replacement Campaigns.
Cards view displays each Campaign as a separate Card.
A Card can show:
Selecting the Card opens its Campaign Details page.
List view displays Campaigns in a table.
The columns are:
The Actions area provides:
The selected Card or List preference is stored in the current browser.
Returning to Campaigns on the same browser restores the saved preference.
On smaller screens, the interface uses Cards automatically.
The Campaign list is sorted by creation date with the newest Campaigns first.
This means a newly created or duplicated Campaign generally appears near the top of the page.
The Campaign record supports:
An idle Campaign exists but has not started.
An unscheduled Campaign is created as idle.
Idle Campaigns display a Start action.
A scheduled Campaign has a valid future start date and time.
The Campaign page displays the scheduled date and time instead of a Start button.
The scheduler checks for due Campaigns approximately once every minute.
A running Campaign has entered its execution sequence.
The system is initiating calls, processing active calls, or waiting for Call Logs to reach final statuses.
The Campaign page displays:
and uses an animated running status indicator.
A completed Campaign has reached the system’s completion condition.
The Start action is disabled and can display:
Completion does not mean that every Lead answered successfully. A Campaign can complete with:
A stopped Campaign was manually ended before ordinary completion.
A stopped Campaign can be started again through the current interface.
Restarting a stopped Campaign can create new calls for the entire Campaign Lead list, including Leads who were previously called. Review every Lead before restarting.
Campaign creation requires:
The current backend requires the user’s Plan status to be active. A trial account marked only as trialing may be blocked unless the platform has configured it differently.
Each Plan can limit how many Campaign records the account may create.
The Campaign limit counts existing Campaign records regardless of whether they are:
When the limit is reached, the user must delete approved non-running Campaigns or upgrade the Plan before creating or duplicating another one.
At least one owned AI Agent must exist.
Before using the Agent, confirm:
Campaign creation can succeed before the Agent’s calling configuration is complete. The more detailed readiness checks occur when the Campaign starts.
At least one Lead must be selected through the customer interface.
The form displays:
when the user attempts to submit without a selected Lead.
Every selected Lead must belong to the signed-in account.
The backend rejects the operation when one or more selected Lead IDs are not owned by the user:
The selected Agent is validated in the same way.
Before selection, review:
Creating a Campaign does not validate every telephone number for deliverability.
To begin:
The form description states:
The form contains:
The Date & time field appears only when Schedule for later is selected.
Campaign Name is required.
The interface provides an example:
The backend does not require Campaign names to be unique.
Use a name that identifies:
Examples:
Avoid:
Unclear names make reporting and Campaign selection difficult.
Clearly distinguish tests from production operations.
Examples:
Delete test Campaigns when they are no longer required and Campaign history has been reviewed.
Open:
and choose the intended AI Agent.
The placeholder is:
Only Agents returned for the signed-in account appear.
The Campaign form does not contain a separate Phone Number field.
The selected Agent supplies its outbound Phone Number.
Before creating the Campaign, confirm the Agent is assigned to:
The selected Agent also supplies:
The Campaign does not store independent copies of these settings.
Selecting the wrong Agent can cause:
Review the Agent Name carefully before submitting.
When an Agent associated with a Campaign is later removed, the Campaign list can display:
Do not launch or duplicate such a Campaign without assigning or recreating an appropriate Agent through an approved process.
The current Campaign list does not provide a visible Agent-edit control.
The form displays:
Each Lead entry shows:
The selected count updates as Leads are added or removed.
To select one Lead:
Selecting the checkbox again removes that Lead.
The search field displays:
Search checks:
Name search is case-insensitive. Telephone search matches the stored digit string.
The Campaign Lead search does not search Lead Tags.
Use Add by Tag to select a Tag group.
When the current search matches no records, the selection area displays:
Clear or revise the search text.
The Campaign dialog contains:
Selecting a Tag adds every Lead containing that Tag to the Campaign selection.
Example:
Selecting several Tags adds the matching groups together.
Example:
A Lead matching both Tags is added only once.
This differs from the Leads-page Tag filter, which can require a Lead to contain all selected Tags.
Tag selection uses the complete loaded Lead list rather than only the currently visible search results.
A Tag can therefore add Leads that are not visible under the current search.
Always review the total selected count after using Add by Tag.
When no Lead Tags exist, the menu displays:
Add or import Tags in the Leads section before reopening the Campaign dialog.
The visible Tag control adds matching Leads.
It does not provide a direct Remove by Tag action.
Remove incorrect Leads individually or clear the entire selection.
The Select All checkbox selects all Leads currently matching the search.
Example:
Selecting Select All sets the Campaign selection to the currently filtered Lead list.
It does not merely add the visible Leads to a previous selection.
Example:
This behavior is important when building a Campaign from several search groups.
Clearing Select All removes the entire Campaign Lead selection, not only the current search results.
Review the selected count before continuing.
To safely select multiple groups:
Select:
to display:
The field uses the browser’s date-and-time selector.
When Schedule for later is not selected, the Campaign is created with:
The user must start it manually.
Checking Schedule for later without selecting a Date & time does not create a valid schedule.
The form sends a scheduled time only when both:
When no value is present, the Campaign can be created as idle instead.
The scheduled date and time must be in the future.
The backend compares the submitted time with the current server time.
A future value creates:
A value that is missing, invalid, current, or in the past is stored without an active schedule and the Campaign remains or becomes idle.
The date-and-time field is entered in the browser’s local time and converted into an ISO timestamp before submission.
Therefore, verify:
The Campaign record stores an absolute timestamp rather than a separate Campaign time-zone field.
The Campaign creation dialog does not show a separate time-zone selector.
The selected time is primarily interpreted from the device and browser environment.
The account’s time-zone setting may be important elsewhere in the system, but the Campaign scheduling form itself sends the selected browser-local date and time converted to an absolute timestamp.
When Leads are located in another time zone:
The Campaign scheduler checks approximately every:
It searches for Campaigns where:
A Campaign may therefore begin shortly after the exact selected minute rather than at the exact second.
A scheduled Campaign can start late when:
Because due Campaigns remain scheduled until successfully started, a delayed service can attempt to start them after normal operation resumes.
Review overdue scheduled Campaigns before restoring a production calling service.
The Campaign page displays the scheduled date and time using the browser’s local formatting.
A scheduled Campaign does not display the ordinary Start button on the Campaign list.
The current user interface does not display a dedicated:
action.
When the schedule is incorrect:
The current Campaign page and Details page display the schedule rather than an early-start control.
To run it earlier, create an approved unscheduled replacement rather than waiting for the incorrect scheduled record.
Avoid leaving both Campaigns active because both could call the same Leads.
Before selecting Create Campaign, confirm:
Select:
once.
During processing, it displays:
The Cancel and form controls are disabled while the request is being submitted.
When no scheduled timestamp is submitted, the interface displays:
The Campaign receives idle status.
When a scheduled timestamp is submitted, the interface displays:
The backend still confirms whether the timestamp is actually in the future before assigning scheduled status.
After successful creation, AIUNIFY Assistant redirects the browser to the new Campaign Details page.
Use that page to verify:
Select:
to close the form without creating the Campaign.
Unsaved selections are cleared when a successful Campaign is created. Closing and reopening the dialog can require the user to review the form again.
An idle Campaign displays:
or:
Select it only after completing the readiness review.
From Card or List view:
The list-page success message is:
From the Campaign Details page:
The Details page also provides the Stop Campaign action when status is running.
A start-success message means the Campaign execution sequence was initiated.
It does not mean:
The call process continues after the start request returns.
Before initiating calls, the backend changes Campaign status to:
If the Campaign was scheduled, its scheduled timestamp is cleared when execution starts.
Starting requires an active Plan.
When the Plan is not active, the system can display:
The start route checks the account’s monthly Call Log usage.
When the limit has already been reached, the system can display:
The current limit check counts Call Logs created since the first day of the current month.
The start check determines whether the account has already reached its call limit.
It does not visibly reserve one call allowance for every Lead before the Campaign begins.
For a Campaign near the remaining limit:
Every Campaign start requires:
When one or more are missing, the backend identifies them:
The current Campaign runner checks for an ElevenLabs key even when a Twilio Agent may use a standard Twilio voice.
Therefore, configure all three AI services before launching any Campaign.
When the Agent’s outbound Phone Number uses Twilio, starting requires:
A missing credential produces:
The Twilio Agent must have a connected outbound Phone Number.
A missing number produces:
The Campaign list performs a Twilio configuration check before sending its start request.
It can display:
It can also warn:
The current Campaign list’s precheck can block the Start action when Twilio is not configured, even when the Agent uses a SIP Phone Number.
The Campaign Details page sends the start request directly, and the backend then evaluates the actual Phone Number provider.
For a SIP-only account affected by the list-page warning:
When the Agent’s outbound number uses SIP, the Voice Engine must be connected.
A failure produces:
Confirm:
For each selected Lead, the Campaign engine attempts to:
When Twilio rejects an individual call request, the system creates a failed Call Log for that Lead.
For each selected Lead, the Campaign engine attempts to:
When a SIP call cannot be initiated, the system creates a failed SIP Call Log.
The Campaign engine can finish submitting or initiating all Lead calls before those calls reach final results.
Do not interpret:
as:
Review Campaign Details and Call Logs.
When at least one Campaign is:
the Campaign page refreshes Campaign data approximately every three seconds.
This allows the page to detect:
When no Campaign is running or scheduled, automatic three-second Campaign-page polling stops.
Refresh or reopen the page when reviewing an older Campaign whose data appears stale.
Select:
to open:
Campaign Details provides the fuller operational view and is covered in Chapter 10.
The stop action is available from Campaign Details when status is running.
Select:
The confirmation explains that active calls will be terminated.
The interface asks:
Do not confirm unless ending active conversations is authorized.
The backend first changes the Campaign status to:
This prevents additional calls from being initiated.
It then attempts to terminate active calls whose Call Logs are:
For Twilio, the system attempts to complete or terminate each active provider call and changes the associated Call Log to:
For SIP, the system instructs the SIP manager to stop active calls associated with the Campaign.
When Twilio credentials are unavailable, the Campaign status can still become stopped, but the backend may report:
In that situation, verify active calls directly with the provider.
A normal stop result displays:
or:
Review Call Logs to confirm final call statuses.
Closing the browser does not stop a running Campaign.
The Campaign engine operates on the backend.
Use Stop Campaign when the operation must end.
A stopped Campaign can display the Start action again.
Starting it causes the Campaign engine to process the Campaign’s Lead list again.
The Campaign runner does not show a rule that skips Leads based on earlier Campaign Call Logs.
Restarting can therefore redial:
Review and obtain approval before restarting.
For selective retries:
Example:
Campaigns can be duplicated from Card or List view.
The duplicate operation copies:
and creates the new Name:
The duplicate receives:
and does not retain the original schedule.
Duplicating requires:
A duplicate counts as another Campaign under the Plan limit.
The duplicate operation does not reopen the creation form.
It does not ask the user to reconfirm:
The copy is created immediately.
After duplication:
(Copy).The current duplicate route can copy a running Campaign.
The new copy is idle and can contain the same Leads.
Do not start the copy while the original is still calling.
A scheduled Campaign’s copy becomes idle.
The scheduled timestamp is not copied.
The copy will not start automatically unless a new visible schedule is created through a replacement Campaign.
When the original Agent or Leads were deleted, the copy can retain stale record references.
Review the Campaign before starting it.
To delete:
A successful operation displays:
A running Campaign cannot be deleted.
The backend responds:
The Campaign-page Delete control is also disabled while status is running.
A scheduled Campaign can be deleted before it starts.
Deleting it prevents that Campaign record from being found by the scheduler.
Confirm that no replacement Campaign will call the same Leads unexpectedly.
Completed and stopped Campaigns can be deleted through the current route.
Before deletion, review:
The Campaign deletion route removes the Campaign record.
It does not show an automatic deletion of related Call Logs.
Historical Call Logs can remain, but their Campaign relationship may no longer populate correctly.
Preserve Campaign records required for reporting.
Bulk selection is available in List view.
Use:
The List-view header checkbox selects every Campaign currently loaded on the page.
The Campaign page does not presently provide a search or status filter, so Select All can include:
Review the selected records carefully.
After selection, a floating action bar displays:
The interface asks:
When any selected Campaign is running, the complete bulk deletion is rejected:
No selected Campaigns should be assumed deleted until a success message appears.
Campaign completion depends on Call Logs reaching terminal statuses such as:
When Campaign Details is opened, the backend can reconcile nonterminal Twilio Call Logs with Twilio when a status callback was missed.
When the number of finished Call Logs is at least the number of Campaign Leads, the Campaign can be changed to:
A completed Campaign can have:
Use Call Logs, transcripts, Lead qualification, and Appointments to measure business results.
Normal users generally see Campaigns created by their own accounts.
Campaign creation also requires ownership of the selected Agent and every selected Lead.
A Super Administrator can retrieve a broader Campaign list and bypass some ownership and Plan-limit checks.
Normal-user documentation should not assume that global administrative access is available.
A resource visible through another sharing mechanism may still fail Campaign ownership validation when it is not owned by the current account.
When the interface displays a resource but Campaign creation reports an ownership error:
Each Campaign should have one primary objective.
Examples:
Avoid combining unrelated objectives into one Agent and Campaign.
Identify:
Use Lead Tags to organize the group.
Before launch, document the desired result.
Examples:
The Dashboard’s technical Success Rate is not the same as Campaign conversion.
Begin with a controlled test group.
Recommended progression:
Do not begin with the entire database.
A Lead appearing in AIUNIFY Assistant does not prove calling consent.
Verify the lawful basis for every outbound Campaign.
Exclude Leads who:
A do-not-call Tag does not automatically guarantee technical exclusion.
The Campaign scheduler starts at the selected timestamp but does not separately calculate each Lead’s local calling time.
For multi-time-zone Campaigns:
Review applicable requirements for:
Include approved disclosure language in the Agent’s opening message where required.
Use this order:
A test Campaign should contain:
Test:
The Campaign dialog could not retrieve Agents or Leads.
Check:
Close and reopen the dialog after the issue is corrected.
Confirm:
Close and reopen Create Campaign after creating an Agent.
Confirm:
Select one or more Lead checkboxes.
Confirm the selected count is greater than zero.
Possible causes include:
Refresh and select an Agent returned by the current dialog.
Possible causes include:
Close the form, refresh Leads, and create the Campaign again.
The system can report:
Review completed, stopped, and test Campaigns before deleting any record.
When the Plan is not active:
Review the account Plan status in Settings or the applicable purchase area.
Check whether:
Checking the schedule box without entering the date and time creates an unscheduled Campaign.
Check:
Delete and recreate the non-running Campaign with the corrected time.
The Campaign is already active.
Do not select Active or Start repeatedly.
Open Campaign Details and monitor progress.
Open Settings and configure every listed service.
The Campaign requires:
Confirm:
Open AI Agents and assign a connected Phone Number to the Campaign’s Agent.
Creating a Phone Number does not automatically assign it to the Agent.
Open SIP Trunks and confirm:
Contact Support when ARI remains offline.
Review:
Do not delete Call Logs merely to attempt to bypass an account limit.
Check:
Wait briefly because the start request returns before all call requests are processed.
Likely causes include:
Stop the Campaign before correcting the configuration.
Review each failed Call Log.
Do not restart the entire Campaign merely to retry a small number of failed Leads.
Create a selective retry group.
Check:
A scheduled Campaign can fail its start validation and remain scheduled.
The scheduler checks once per minute, and service interruptions can add delay.
A small delay can be normal. A long delay requires server review.
The schedule was stored as an absolute timestamp based on the browser-selected local time.
Review the device time zone used when the Campaign was created.
When two scheduled Campaigns contain the same Leads:
Check whether:
Verify directly in Twilio when necessary.
Check:
Contact Support when channels remain active.
A running Campaign must be stopped first.
Wait for status to become stopped before deleting.
Check whether any selected Campaign is running.
Deselect or stop the running Campaign, then retry.
Refresh the page.
When deletion succeeded but the browser list remains stale, reopening Campaigns retrieves the current records.
Campaign Details can reveal:
Do not leave the page visible on an unattended device.
Never include:
in a Campaign Name.
Before sharing a Campaign screenshot:
Confirm:
Confirm:
Confirm:
Confirm:
Confirm:
Confirm:
Confirm:
Confirm:
Confirm:
At the end of this chapter, the user should understand how to create, schedule, launch, monitor, stop, duplicate, restart, and delete outbound Campaigns in AIUNIFY Assistant.
The user should now understand that a Campaign combines an AI Agent with a selected group of Leads, while the Agent supplies the voice, System Prompt, First Message, language, Knowledge Base, Appointment capability, and outbound Phone Number used during the calls.
The user should also understand the five primary Campaign statuses:
and how each status determines the actions available to the user.
The user should be able to:
The user should understand that scheduled Campaigns are handled by a backend scheduler that checks for due Campaigns and starts those whose scheduled time has arrived. Campaign Call Logs are also reconciled so that Campaigns can eventually move to completed after their calls reach terminal statuses.
The user should know that successful Campaign creation does not guarantee calling readiness. Before launch, the account must have the required Plan capacity, AI service credentials, telephony configuration, Agent outbound number, valid Leads, and working provider infrastructure.
The user should also understand that Campaign completion represents the completion of the calling process, not necessarily a successful business result. Final Campaign performance should be evaluated using:
The user should recognize the operational risks of:
Before any full production Campaign, the recommended process is:
With Chapter 9 complete, the user has covered the full process of preparing and launching AI-powered outbound calling operations.