7.1 Overview

The AI Agents section is where users create and manage the virtual representatives that conduct inbound and outbound telephone conversations.

An AI Agent determines:

AIUNIFY Assistant separates the Agent’s conversation behavior from the telephone and Campaign resources that use it.

The basic relationship is:

An Agent can also be assigned to a connected Phone Number to handle inbound calls. The reviewed Agent record stores the Agent’s name, System Prompt, opening message, voice information, outbound number, Knowledge Base, Knowledge Base section settings, language, appointment capability, appointment description, owner, and creation and update dates.

Understanding AI Agents

7.2 Agent Versus Campaign

An Agent and a Campaign perform different functions.

AI Agent

Controls the conversation.

It determines:

Campaign

Controls the calling operation.

It determines:

Editing an Agent can affect every future call made by Campaigns that use that Agent.

7.3 Agent Versus Phone Number

The Agent’s Outbound Phone Number determines the Caller ID used when that Agent places calls.

The Phone Number’s Inbound Agent determines which Agent answers when someone calls that number.

These assignments are separate:

An Agent can be configured without an outbound number, but it cannot place a normal outbound Campaign call until an appropriate number has been assigned.

7.4 Agent Versus Knowledge Base

The System Prompt tells the Agent how to behave.

The Knowledge Base supplies business information.

Example:

The System Prompt should contain operational rules. The Knowledge Base should contain facts the Agent may need during conversations.

7.5 Inbound Versus Outbound Agent Design

The same Agent can technically be used for inbound and outbound calls, but its instructions and opening message must make sense for both directions.

Outbound opening

Inbound opening

An outbound-specific Agent should not be assigned to an inbound number unless its opening message and instructions have been revised for callers who initiated the conversation.

Opening the AI Agents Page

7.6 Accessing AI Agents

After signing in:

1. Locate AI Agents in the Sidebar.
2. Select it once.
3. Wait for the loading indicator to disappear.
4. Confirm that the page displays AI Agents.
5. Review the existing Agents before creating another one.

The page describes its purpose as:

7.7 Cards View

On desktop, the page can display Agents as Cards.

Each Card can show:

The voice provider is identified as either:

Card view is also used automatically on smaller or mobile screens.

7.8 List View

Desktop users can switch to List view.

List view includes columns such as:

The Voice column can also display the Agent’s outbound number.

7.9 Remembered View Preference

The system remembers whether the desktop user selected Card or List view in the current browser.

Another browser or device may use a different display preference.

7.10 Empty Agent Account

When no Agents exist, the page displays:

and explains that the first Agent must be created before intelligent calling can begin.

Select Create Agent to start.

The page supports Card and List views and provides Edit and Delete actions for each Agent. It does not show a separate Duplicate button or Agent activation switch.

Creating an Agent

7.11 Create Agent Menu

Select Create Agent to open two choices:

From Template

Starts with prewritten settings for a particular business purpose.

From Scratch

Opens a blank Agent form.

7.12 Choosing the Right Creation Method

Use From Template when:

Use From Scratch when:

A template is a starting point, not a finished production configuration.

Creating an Agent from a Template

7.13 Opening the Template Library

Select:

The Template drawer displays:

and explains that the selected template will prefill recommended Agent settings.

7.14 Template Filters

The Template library provides:

Search examines:

The Appointments switch limits results to templates with appointment capability enabled.

7.15 Template Categories

The reviewed library contains categories for:

7.16 Core English Templates

Examples include:

The reviewed template library contains 37 templates, including English templates and localized versions for several supported languages.

7.17 Localized Templates

The library also includes templates written for languages such as:

A localized template can prefill both the selected language and the appropriate translated instructions.

7.18 Template Information

Each template card can display:

Review all of this information before selecting the template.

7.19 What a Template Prefills

Selecting a template can prefill:

7.20 What a Template Does Not Assign

A template does not automatically assign:

The Agent form deliberately begins with:

even when a template has been selected.

7.21 Reviewing a Template

After selecting a template:

1. Read the entire System Prompt.
2. Replace generic business language.
3. Review every required question.
4. Remove instructions that do not apply.
5. Review the First Message.
6. Select the correct Phone Number.
7. Select a suitable voice.
8. Assign the correct Knowledge Base.
9. Confirm appointment settings.
10. Test the Agent before production use.

Do not assume a template complies with every industry, state, country, or organizational requirement.

Creating an Agent from Scratch

7.22 Opening a Blank Agent

Select:

The full-screen Agent drawer opens with blank conversation fields and default configuration choices.

7.23 Required Fields

The following fields are required when creating an Agent:

The backend also accepts settings for voice, outbound number, Knowledge Base, language, and appointment capability. Creating a new Agent requires an active Plan or applicable trial and is subject to the account’s Agent limit.

Agent Name

7.24 Purpose of the Agent Name

The Agent Name identifies the Agent inside:

Use a clear operational name.

Recommended:

Avoid:

7.25 Agent Name Versus Spoken Name

The Agent Name is primarily an internal record name.

A caller hears whatever name is written into the First Message or conversation instructions.

Example:

Changing the Agent Name does not automatically change the spoken introduction.

System Prompt

7.26 What the System Prompt Does

The System Prompt is the Agent’s main behavioral instruction.

It tells the Agent:

The form provides an example such as:

7.27 Recommended Prompt Structure

A strong System Prompt should contain:

7.28 Role

Define the Agent’s identity and responsibility.

Example:

7.29 Conversation Objective

State the result the Agent should work toward.

Example:

7.30 Required Questions

Tell the Agent what information must be gathered.

Example:

Avoid requiring every question when it would make the conversation unnatural.

7.31 Conversation Style

Telephone responses should be short and natural.

Recommended instruction:

The live custom-voice processing also adds internal telephone-response rules instructing the model to keep replies brief, generally no more than two sentences or approximately 12 seconds of speech at a time.

7.32 Accuracy Rules

Add instructions such as:

7.33 Sensitive Information

Tell the Agent not to collect unnecessary sensitive information.

Example:

7.34 Handling Uncertainty

Recommended:

7.35 Ending the Call

Recommended:

7.36 Outbound Prompt Example

7.37 Inbound Prompt Example

7.38 Avoid Overloading the Prompt

A prompt that tries to cover every department can become inconsistent.

Avoid combining all of these into one Agent unless carefully designed:

Separate Agents are easier to test, control, and assign to the correct numbers and Campaigns.

First Message

7.39 Purpose of the First Message

The First Message is the opening statement the Agent says when the call connects.

It should immediately establish:

The form describes it as:

7.40 Outbound First Message

Example:

7.41 Inbound First Message

Example:

7.42 Avoid Long Openings

A lengthy opening can cause the Lead to interrupt, hang up, or miss the purpose of the call.

Recommended opening length:

Do not begin by reading the full company history, legal policy, service list, or qualification questionnaire.

Personalization Variables

7.43 Supported Variables

The form advertises variables such as:

The Twilio greeting process also supports Lead custom fields using their exact field names.

Examples:

The Agent’s opening message is personalized when the call begins.

7.44 Name Variable

Example Lead:

Message template:

Spoken result:

In the Twilio call flow, a missing name can fall back to a general term such as “there.” The SIP custom-voice flow can replace it with a blank value when the Lead has no usable name.

For this reason, every production Lead should have a valid Name.

7.45 Company Variable

The {{company}} value is taken from the Lead’s Company custom field.

Example:

When Company is blank, the replacement can also be blank.

Avoid using {{company}} in a sentence that becomes confusing when some Leads have no Company value.

7.46 Custom-Field Variables

Suppose a Lead contains:

The First Message can use:

Custom-field names should match the placeholder exactly.

7.47 Variables in the System Prompt

The interface also mentions variables beside the System Prompt.

However, the reviewed live-call source clearly confirms variable replacement for the opening greeting. It does not show the same consistent replacement process for the complete System Prompt.

For dependable production behavior:

Test any System Prompt variable before relying on it.

7.48 No Conditional Variables

The interface does not show conditional template syntax such as:

Design First Messages that still sound correct when optional custom fields are missing.

Outbound Phone Number

7.49 Selecting the Number

The Outbound Phone Number control displays numbers owned by the current account.

Each option shows:

Example:

7.50 No Outbound Number

The selection includes:

An Agent can be saved without an outbound number, but normal outbound Campaign calling will fail until one is assigned.

The form explains:

7.51 No Numbers Found

When no Phone Numbers exist, the form displays a link to:

This opens the Phone Numbers section.

Configure and test the number before returning to the Agent.

7.52 Number Ownership

The backend confirms that the selected Phone Number belongs to the current account.

When it does not, the operation can return:

This prevents a user from assigning another account’s telephone resource.

7.53 Twilio Number

Selecting a Twilio number permits use of:

when the required services are configured.

7.54 SIP Number

Selecting a SIP number uses the ElevenLabs custom-voice path.

A SIP Agent also requires:

The Agent form marks the voice section with a SIP indicator when a SIP number is selected.

Language

7.55 Supported Language Choices

The Agent form provides:

The default language is English.

7.56 Selecting One Language

When a specific language is selected, the live custom-voice process adds an internal instruction requiring the Agent to respond in that language.

Example:

7.57 Auto-Detect Multilingual

Selecting:

instructs the Agent to respond in the same language used by the caller.

The interface explains:

7.58 Language and Voice Are Separate

Changing the language does not automatically select the most appropriate voice.

The user should confirm:

A voice designed for English may pronounce names or terms poorly in another language.

7.59 Knowledge Base Language

The selected Agent language does not automatically translate a Knowledge Base.

For best results, provide Knowledge Base content in the language the Agent is expected to use or test the model’s translation carefully.

Voice Configuration

7.60 Voice Requirements

AIUNIFY Assistant supports two voice paths:

Deepgram supports speech recognition, while OpenRouter supplies the language-model response.

7.61 Missing Voice Configuration

When neither Twilio nor ElevenLabs is configured, the Agent form displays:

and directs the user to Settings.

An Agent record may still be saved, but it will not be ready for a complete calling operation.

7.62 Missing Deepgram or OpenRouter

The form can display:

or a separate message identifying which service is missing.

Deepgram

Used for speech-to-text processing.

OpenRouter

Used for the AI model and conversation response.

Select Configure to open Settings.

Standard Twilio Voice

7.63 When Standard Voice Is Available

Standard Twilio voices are available when:

7.64 Standard Voice Choices

The current Agent form provides:

The internal values use Amazon Polly voice names through Twilio, such as:

7.65 Standard Voice Advantages

Standard Twilio voice can be appropriate when:

7.66 Standard Voice Limitations

The Agent form does not provide the same preview control for standard Twilio voices that it provides for ElevenLabs voices.

Test the Agent through a controlled call before choosing a production voice.

Custom ElevenLabs Voice

7.67 Enabling Custom Voice

When Twilio is available, use the switch:

The interface describes this as:

7.68 When Custom Voice Is Required

The custom voice path is forced when:

SIP calls cannot use the standard Twilio voice selection in the current Agent form.

7.69 Available Voices

The voice list is retrieved from the ElevenLabs account associated with the saved API key.

Each entry can include:

This means the available voices can differ between accounts and may change when the ElevenLabs account changes.

7.70 Previewing a Voice

To preview:

1. Select a voice.
2. Select the speaker button.
3. Listen to the sample.
4. Select the button again to pause where necessary.
5. Compare pronunciation and tone.
6. Save only after testing.

The preview uses the preview_url returned by ElevenLabs.

7.71 Selecting a Custom Voice

When a voice is selected, AIUNIFY Assistant stores:

The Voice ID controls the generated voice. The Voice Name is used for display inside the application.

7.72 Rachel Fallback

The data model and live voice services include a Rachel voice fallback when no usable Voice ID is supplied.

Production users should still select and preview the intended voice rather than relying on a fallback.

7.73 ElevenLabs Voice Error

When the voice list cannot be retrieved, the form can display:

or:

The backend can also return:

The voices endpoint retrieves the current voice list directly from ElevenLabs using the account’s saved key.

7.74 Voice Selection Considerations

Review:

A promotional voice may be inappropriate for healthcare, collections, technical support, or sensitive customer calls.

Knowledge Base

7.75 Selecting a Knowledge Base

The Agent form includes:

Available Knowledge Bases owned by the current account appear in the list.

Select:

when the Agent should operate only from its System Prompt.

7.76 No Knowledge Bases Available

When none exist, the form displays a link to:

This opens the Knowledge Base section.

7.77 Knowledge Base Ownership

The backend confirms that the selected Knowledge Base belongs to the current account.

An invalid selection can return:

7.78 Knowledge Base Sections

After selecting a Knowledge Base, the Agent form displays three controls:

Each switch determines whether that section is added to the Agent’s working information.

7.79 Basic Info

Use Basic Info for content such as:

7.80 FAQs

Use FAQs for structured questions and answers.

Example:

7.81 Other Info

Use Other Info for additional approved material that does not fit the first two sections.

Examples:

The live voice system appends only the enabled Knowledge Base sections to the Agent’s instructions.

7.82 Disabling Knowledge Sections

A section can be switched off without deleting it from the Knowledge Base.

Example:

The same Knowledge Base can therefore be used by different Agents with different section selections.

7.83 Knowledge Base Does Not Override Poor Instructions

A Knowledge Base contains facts, but the Agent still needs instructions explaining:

Appointment Booking

7.84 Enabling Appointment Booking

The Agent form contains:

The description states:

Use the switch to enable or disable the capability.

7.85 Available Appointment Actions

When enabled, the live calling process gives the Agent internal commands to:

The commands are processed by the backend and are not intended to be spoken to the caller.

The system also supplies the Agent with the account’s current time zone and date so that words such as “today” and “tomorrow” can be interpreted.

7.86 Appointment Description

When Appointment Booking is enabled, the form displays:

Example:

Template examples include descriptions for:

7.87 Important Appointment Description Note

The reviewed Agent form saves the Appointment Description with the Agent.

However, the live voice-processing source clearly adds generic appointment commands and does not clearly show the Appointment Description being automatically inserted into the Agent’s live instructions.

For dependable behavior, also explain the booking purpose inside the System Prompt.

Example:

7.88 Availability Must Be Configured

Enabling Appointment Booking does not create available time slots.

Before production use, configure:

Appointment configuration is covered fully in Chapter 12.

7.89 Appointment Testing

Test that the Agent can:

Call Transfer and Human Handoff

7.90 No Dedicated Transfer Setting in the Current Agent Form

The reviewed Agent form and Agent data model do not contain a visible field for:

The current user interface therefore does not confirm a user-configurable Agent call-transfer feature.

Do not write instructions such as:

and assume that the telephone transfer will occur automatically.

A System Prompt can tell the Agent to explain the next human-support step, but a real telephone transfer requires separately implemented and tested call-routing functionality.

7.91 Safe Handoff Language

Where transfer is not configured, use wording such as:

Saving the Agent

7.92 Creating the Agent

After reviewing all fields:

1. Confirm Agent Name.
2. Confirm System Prompt.
3. Confirm First Message.
4. Confirm outbound number.
5. Confirm language.
6. Confirm voice.
7. Confirm Knowledge Base.
8. Confirm appointment capability.
9. Select Create Agent once.
10. Wait while the button displays Creating...

A successful operation displays:

7.93 Active Plan Requirement

Creating an Agent requires an active Plan or applicable trial.

The creation route uses:

7.94 Agent Limit

The account’s Plan or trial controls the number of Agents that can be created.

When the limit is reached, the system responds:

Super Administrators bypass normal user limits.

7.95 Agent Ownership

The new Agent is assigned to the user who created it.

Normal users generally see Agents they own, while a Super Administrator can retrieve a broader Agent list.

7.96 Saving Without a Number

An Agent can be created with:

This can be appropriate when:

It must receive an outbound number before normal outbound Campaign use.

7.97 Saving with Missing AI Keys

The Agent form can save the Agent’s configuration even when some AI services are missing.

However, Campaigns require:

and the applicable telephony provider before calls can operate.

Treat missing-key warnings as production blockers even when the Agent record saves successfully.

Editing an Agent

7.98 Opening Edit Agent

From Card view:

1. Find the Agent.
2. Select Edit Agent.
3. Review the full form.
4. Make the approved changes.
5. Select Update Agent.

From List view:

1. Find the row.
2. Select Edit.
3. Complete the changes.
4. Select Update Agent.

A successful operation displays:

7.99 Editable Settings

The user can edit:

7.100 Editing an Agent Used by a Campaign

Changes to an Agent affect future calls that load the updated Agent record.

Before editing an Agent used by an active or scheduled Campaign:

1. Identify the Campaigns using it.
2. Stop or postpone calling where necessary.
3. Wait for active calls to end.
4. Save the Agent change.
5. Test the updated Agent.
6. Resume the Campaign only after approval.

Do not change the prompt, voice, language, or caller ID in the middle of an important production Campaign without review.

7.101 Editing an Inbound Agent

When the Agent is assigned to an inbound number, changes can affect the next caller immediately.

Test after changing:

7.102 Removing the Outbound Number

Select:

and update the Agent.

Campaigns using that Agent will no longer have a valid outbound caller ID and can fail when started.

7.103 Removing the Knowledge Base

Select:

The Agent will continue using its System Prompt but will no longer receive the selected business information.

7.104 Changing the Voice Provider

Switching between Twilio standard voice and ElevenLabs custom voice changes the live calling architecture.

Retest:

Duplicating an Agent

7.105 No Duplicate Agent Action

The current AI Agents page provides:

but does not provide a dedicated:

action.

7.106 Safely Recreating a Similar Agent

To create a similar Agent:

1. Open the original Agent in Edit.
2. Preserve the approved System Prompt externally.
3. Preserve the First Message.
4. Create a new Agent From Scratch.
5. Paste and revise the content.
6. Select the correct number and Knowledge Base.
7. Give the new Agent a distinct name.
8. Test it separately.

Where an available template matches the purpose, starting From Template may be easier.

Testing an Agent

7.107 No Dedicated Full Agent-Test Button

The AI Agents page does not show a direct button that conducts a complete live Agent conversation.

It provides an ElevenLabs voice preview, but that tests only the voice sample.

A complete test should use:

7.108 Voice Preview Test

Voice preview confirms:

It does not confirm:

7.109 Controlled Outbound Agent Test

Use this procedure:

1. Create an internal test Lead.
2. Use an approved telephone number.
3. Assign a connected outbound number to the Agent.
4. Confirm all AI keys.
5. Create a one-Lead test Campaign.
6. Start the Campaign.
7. Answer the test call.
8. Ask several expected questions.
9. Ask one unexpected question.
10. Test interruption and silence.
11. Test an Appointment where enabled.
12. End the call.
13. Review Call Logs.
14. Review the recording and transcript.
15. Correct the Agent.

7.110 Controlled Inbound Agent Test

1. Assign the Agent to a Phone Number as the inbound Agent.
2. Call from an outside telephone.
3. Confirm the opening message.
4. Confirm caller information is recognized.
5. Ask Knowledge Base questions.
6. Test the selected language.
7. Test appointment behavior.
8. End the call.
9. Review the inbound Lead.
10. Review the Call Log.

7.111 Prompt Test Questions

Test:

7.112 Production Approval

An Agent should not be approved based on one successful call.

Test:

Using Agents in Outbound Campaigns

7.113 Campaign Assignment

A Campaign selects one Agent.

That Agent supplies:

7.114 Campaign Readiness

Before selecting an Agent for a Campaign, confirm:

7.115 Changing the Campaign Agent

Changing a Campaign to another Agent can change:

Review the entire Campaign before starting it.

Using Agents for Inbound Calls

7.116 Inbound Assignment

Inbound Agents are assigned from the Phone Number record.

To assign:

1. Open Phone Numbers.
2. Edit the intended number.
3. Select the Agent under Inbound Call Handling Agent.
4. Save.
5. Test the number from an outside telephone.

7.117 One Agent per Inbound Number

A connected Phone Number stores one inbound Agent assignment.

The current Phone Number form does not provide a multi-Agent inbound queue.

Deleting an Agent

7.118 Opening Delete

To delete:

1. Find the Agent.
2. Select Delete Agent or Delete.
3. Review the confirmation:

1. Confirm only after checking dependencies.

A successful deletion displays:

7.119 No Agent Archive or Disable Switch

The current Agent model and page do not show:

Deletion should therefore be treated as permanent unless an independent database backup exists.

7.120 Dependency Warning

The reviewed Agent-delete route removes the Agent directly and does not show dependency validation for:

As an operational inference, deleting an assigned Agent can leave related records pointing to an Agent that no longer exists.

7.121 Safe Deletion Procedure

Before deleting:

1. Open Campaigns.
2. Identify Campaigns using the Agent.
3. Stop active Campaigns.
4. Reassign or remove scheduled Campaigns.
5. Open Phone Numbers.
6. Remove the Agent from inbound-number assignments.
7. Review required historical records.
8. Preserve the System Prompt where required.
9. Confirm the deletion is approved.
10. Delete the Agent.

7.122 Historical Call Logs

Deleting an Agent does not show an automatic process that removes historical Call Logs.

Historical records may remain, but the deleted Agent’s populated name or details may become unavailable.

Do not delete Agents needed for reporting, auditing, or legal retention without approval.

Troubleshooting AI Agents

7.123 “Failed to Load Agents”

Possible causes include:

Try:

1. Refreshing once.
2. Opening Dashboard.
3. Signing out and back in.
4. Trying another browser.
5. Contacting Support with the time of the error.

7.124 Create Agent Does Not Open

Check:

Try a private browser window.

7.125 Agent Will Not Save

Confirm:

7.126 Agent Limit Reached

The system displays:

Review:

Delete only approved unused Agents after checking Campaign and Phone Number assignments.

7.127 “You Do Not Own This Phone Number”

The selected number is not owned by the current account.

Possible causes include:

Refresh the Agent form and select a current number.

7.128 “You Do Not Own This Knowledge Base”

The selected Knowledge Base is not owned by the current account.

Refresh the form and select one shown in the current list.

7.129 Agent Saves but Campaign Will Not Start

Check:

Creating an Agent does not validate the complete calling environment.

7.130 No Outbound Number Appears

Open Phone Numbers and confirm:

7.131 Wrong Caller ID Appears

Check:

1. Campaign’s selected Agent.
2. Agent’s Outbound Phone Number.
3. Phone Number provider.
4. Provider-level Caller ID settings.
5. Whether the Campaign uses an older Agent.

7.132 ElevenLabs Voices Do Not Load

Check:

Open Settings and save the correct key.

7.133 Voice Preview Does Not Play

Possible causes include:

Try another voice and run a real controlled call.

7.134 Wrong Voice Is Heard

Confirm:

A SIP Agent uses the custom ElevenLabs voice path even when an old Twilio standard voice value remains stored.

7.135 Agent Uses the Wrong Language

Check:

Selecting a language does not automatically translate every stored field.

7.136 Multilingual Agent Stays in One Language

Possible causes include:

7.137 Personalization Is Blank

Check whether the Lead contains:

Example:

These may not match as expected.

7.138 Agent Says the Placeholder Aloud

A value such as:

may be spoken literally when:

Use only tested variables.

7.139 Knowledge Base Is Not Used

Confirm:

7.140 Agent Gives Incorrect Knowledge Base Answers

Review:

Correct the Knowledge Base and retest.

7.141 Appointment Booking Does Not Work

Check:

Repeat the booking purpose in the System Prompt.

7.142 Appointment Time Is Incorrect

Review:

7.143 Agent Promises a Transfer but No Transfer Happens

The current Agent editor does not include a dedicated transfer control.

Remove unsupported transfer promises from:

Provide an approved alternate human-support method.

7.144 “Agent Not Found”

Possible causes include:

Refresh the relevant page and assign an existing Agent.

7.145 Deleted Agent Still Appears in a Campaign

The Campaign can retain the historical Agent reference after the Agent record is removed.

Do not start the Campaign.

Create or select a replacement Agent and revise the Campaign.

Agent Security

7.146 Do Not Store Credentials in the Prompt

Never enter:

inside:

The Agent can potentially expose information included in its instructions.

7.147 Protect Business Information

Review the Knowledge Base and prompt for:

Only include information the Agent is authorized to discuss.

7.148 Prompt Injection and Caller Requests

A caller may attempt to instruct the Agent to ignore its rules.

Include instructions such as:

7.149 Legal and Compliance Instructions

Where required, include approved language for:

AIUNIFY Assistant supplies calling technology, but the organization remains responsible for lawful Agent use.

Recommended Agent Development Workflow

7.150 Complete Setup Sequence

Use this sequence:

7.151 Narrow-Purpose Agent Workflow

A focused Agent should have:

Example:

7.152 Testing Workflow

After every meaningful change:

Do not assume that a minor prompt change has only a minor effect.

Agent Checklists

7.153 New Agent Checklist

Confirm:

7.154 System Prompt Checklist

Confirm:

7.155 First Message Checklist

Confirm:

7.156 Voice Checklist

Confirm:

7.157 Knowledge Base Checklist

Confirm:

7.158 Appointment Checklist

Confirm:

7.159 Outbound Readiness Checklist

Confirm:

7.160 Inbound Readiness Checklist

Confirm:

7.161 Pre-Deletion Checklist

Confirm:

Chapter Completion

At the end of this chapter, the user should understand how to create an AI Agent From Scratch or From Template; how to use the template search, category, language, and Appointment filters; how Agent Names, System Prompts, First Messages, personalization variables, outbound Phone Numbers, languages, Twilio voices, ElevenLabs voices, Knowledge Bases, and Appointment settings work; why templates must be customized; why SIP requires the custom-voice path; how to test an Agent through controlled inbound and outbound calls; why the current interface does not confirm a dedicated call-transfer or Agent-duplication function; how Plan limits affect Agent creation; how edits affect Campaigns and inbound numbers; how to delete an Agent safely; and how to troubleshoot voice, language, Knowledge Base, personalization, Appointment, and telephone-assignment problems.