19.1 Overview
AI Voice Agent is the AIUNIFY PROS SUITE workspace for placing AI-powered telephone calls and managing the conversational agent that speaks during those calls.
The current interface is titled:
AI Voice Calling Agent
with the description:
“Low-latency, conversational calling pipelines powered by Twilio.”
The workspace provides subscriber-facing controls for:
The current workspace contains two main tabs:
Interactive Dialer
and:
Agent Configuration.
19.2 Where AI Voice Agent Is Located
Navigate to:
Sidebar → Core Tools → AI Voice Agent
The current route is:
/voice-agent.
19.3 Authentication Is Required
AI Voice Agent requires an authenticated PROS SUITE account.
If you are not signed in, the Voice Agent route redirects toward:
Login.
Normal Plan and feature-access rules can also determine whether the Tool is available to your account.
19.4 Understanding the Voice Agent Workspace
The current interface has three primary operating areas:
Interactive Dialer
Used to start an outbound AI telephone call.
Agent Configuration
Used to define how the AI Voice Agent should behave.
Call Log Console
Used to review recent calls and their transcripts.
The Call Log Console remains on the right side of the workspace while the Dialer or Agent Configuration occupies the main left side on larger screens.
19.5 Active Sessions
At the top of the workspace, AI Voice Agent displays:
[number] Active Sessions.
This indicates the number of active calls returned by the current Call Log service.
When one or more active sessions exist, the status indicator changes visually.
19.6 Refresh
Beside Active Sessions is a Refresh control.
Its tooltip is:
Refresh Logs & Transcript.
Use it when you want to manually update:
19.7 Interactive Dialer
Select:
Interactive Dialer
to access the outbound calling workspace.
The primary card is titled:
Outbound Calling Console
with:
“Test the AI agent voice pipeline instantly by entering your mobile number.”
19.8 Agent Ready vs. Agent Offline
The Outbound Calling Console shows one of two states:
Agent Ready
or:
Agent Offline.
This status reflects the current Voice Agent configuration's Active Status.
19.9 Voice Pipeline Dormant
When no local call session is active, the visual call area displays:
VOICE PIPELINE DORMANT.
This means the Dialer is currently idle.
19.10 Active Call Stream
When the current Dialer enters its calling state, the waveform display changes and shows:
Active Call Stream.
The waveform itself is a visual status indicator.
It should not be interpreted as a diagnostic recording of actual audio amplitude; the current interface generates the displayed waveform animation for visual feedback.
19.11 Recipient Phone Number
To place a call, locate:
Recipient Phone Number.
The field displays:
Enter phone number
and uses an international phone-number input.
19.12 Selecting the Country
The current phone control includes a Country selector.
The interface tells users:
“Select the country flag from the dropdown and type your phone number. The input will format your number automatically!”
Recommended sequence:
19.13 Current Default Country
The current Dialer source initializes the phone input with:
India (IN)
as the default country.
Therefore, users calling another country should select the correct Country flag before dialing rather than assuming the initial country is correct.
19.14 International Option
The Country selector also contains:
International.
Use the Country selector to ensure the telephone number is interpreted with the correct international dialing information.
19.15 Phone Number Is Required
If you try to initiate a call without a number, PROS SUITE displays:
Phone Number Required
with:
“Please specify a valid phone number.”
Enter the intended recipient's number before continuing.
19.16 Customize Persona for This Call
The Interactive Dialer includes a switch labeled:
Customize Persona for This Call
with:
“Override the default agent settings for this call session.”
This lets you temporarily change the Voice Agent's Greeting and core instructions for one outbound call without redefining the persistent Agent configuration.
19.17 When to Use a Call-Specific Override
Use Customize Persona for This Call when the Agent normally performs one role but you need a different objective for one particular call.
For example:
Default Agent
General customer-support assistant
One Call
Billing follow-up
or:
Default Agent
Sales qualification
One Call
Appointment confirmation
This avoids unnecessarily rewriting your main Agent instructions.
19.18 Initial Greeting Override
When call customization is enabled, the first additional field is:
Initial Greeting Override.
The current placeholder is:
“Hello! This is a custom greeting for this session.”
Use this to change the first statement spoken when that specific call connects.
19.19 Example Greeting Override
For a sales follow-up:
Hello, this is the AIUNIFY assistant calling on behalf of ABC Company. I'm following up regarding your software consultation request.
For an appointment:
Hello, I'm calling on behalf of Smith Financial to confirm your consultation scheduled for tomorrow.
Keep spoken greetings concise and clear.
19.20 System Prompt / Core Objective Override
The second temporary field is:
System Prompt / Core Objective Override.
Its example placeholder is:
“You are an outbound support agent assisting with a billing ticket...”
Use this field to define what the Agent should accomplish during this individual call.
19.21 Example Call-Specific Objective
A useful one-call Prompt might be:
You are an outbound appointment-confirmation assistant. Confirm the customer's appointment date and time, answer basic scheduling questions, and ask whether they need to reschedule. Keep every response conversational and brief. Do not discuss unrelated services.
19.22 Overrides Are Optional
If Customize Persona for This Call remains off, the outbound call uses the Agent's normal configuration.
If it is on:
The current outbound request only adds those values when the respective override field contains content.
19.23 Initiate Call Session
When the Dialer is ready, select:
Initiate Call Session.
The call request includes:
19.24 Telephony Readiness Is Required
The Initiate Call Session button is disabled unless the Voice Agent reports that Twilio is configured.
For ordinary subscribers:
If the calling infrastructure is unavailable, you cannot enable it from the Dialer itself.
Contact the appropriate AIUNIFY account/support contact rather than attempting to modify server configuration.
19.25 Call Initiated
When the outbound request succeeds, PROS SUITE displays:
Call Initiated
with:
“Dialing [phone number] via Twilio.”
The current call identifier is then retained by the interface and the Call Logs are refreshed.
19.26 Calling Failed
If initiation fails, PROS SUITE displays:
Calling Failed
with either the specific returned error or:
“Could not connect call via Twilio.”
Read the specific message before retrying.
19.27 Dialer Changes During a Call
Once the interface enters its active calling state:
19.28 Force Terminate Session
During an active Dialer state, the available stop control is:
Force Terminate Session.
Select it when you want the current Dialer session to end.
19.29 Current Force-Terminate Implementation Limitation
There is an important current-version limitation.
The user-facing control says:
Force Terminate Session
and displays:
Ending call
“Disconnect signal dispatched.”
However, the current client source for that button does not show a network request to Twilio or a call-termination API. It clears the local Dialer calling state and schedules a Call Log refresh.
Therefore:
The supplied source does not verify that selecting Force Terminate Session actually disconnects the live telephone call at the provider level.
After using it, check the Call Log status or the actual phone connection rather than treating the button message alone as confirmation that Twilio disconnected the call.
19.30 Call Status Is the Better Verification
After a call:
The call record provides a stronger indication of what the calling system recorded than the local waveform alone.
19.31 Twilio Infrastructure Guard
Below the Dialer is:
Twilio Infrastructure Guard.
It reports either:
Twilio Configured & Ready
or:
Twilio Configuration Missing.
19.32 Twilio Configured & Ready
When telephony infrastructure is available, the interface states:
Twilio Configured & Ready
and identifies the Twilio phone number through which outbound dialing is mapped.
This means the Dialer can expose Initiate Call Session as an available action.
19.33 Twilio Configuration Missing
When the infrastructure is unavailable, the Dialer reports:
Twilio Configuration Missing.
The current UI contains a technical message referring to server environment variables.
Those are infrastructure settings, not ordinary subscriber controls.
For this User Operations Manual:
Subscribers should not edit server environment variables.
If this status appears unexpectedly, contact AIUNIFY support or the appropriate account administrator.
19.34 Account Reference
When Twilio is configured, the Infrastructure Guard can display:
Account Reference
with the current Twilio Account SID/reference.
Ordinary users do not need to modify this value through the Voice Agent workspace.
19.35 Agent Configuration
Select:
Agent Configuration
to control the Voice Agent's persistent behavior.
The configuration card is titled:
AI Voice Agent Parameters.
19.36 Understanding the Scope of Agent Configuration
The screen's description uses wording about modifying Agent parameters “globally.”
For this User Operations Manual, this refers only to the Voice Agent configuration presented to the signed-in subscriber. The underlying Voice Agent configuration model includes a user association, and this chapter does not document platform-wide administrator configuration.
19.37 Agent Alias
The first field is:
Agent Alias.
This identifies the Voice Agent.
The current default configuration uses:
Nova.
19.38 Choosing an Agent Alias
Use a short, natural Name that fits the call.
Examples:
Ava
Morgan
AIUNIFY Assistant
Customer Care Assistant
Appointment Assistant
If the Agent introduces itself by Name, make sure the Greeting and System Prompt use consistent wording.
19.39 Language
Agent Configuration includes:
Language.
The current source-defined supported options are:
19.40 Default Voice-Agent Language
The source-defined default Agent configuration uses:
English (US) — en-US.
Choose another supported Language when appropriate for the intended callers.
19.41 Language and Voice Should Be Compatible
Language selection and TTS Voice are separate settings.
For the best caller experience, select a voice that reasonably matches:
Do not assume merely changing the Language will automatically select another Voice.
19.42 TTS Voice Provider
The second selector is labeled:
TTS Voice Provider.
The menu actually presents individual available voice choices.
19.43 Current Amazon Polly Neural Voices
The current source defines:
19.44 Current Google TTS Voices
The current source also defines:
19.45 Current Classic Twilio Voices
The current options also include:
19.46 Default Voice
The current default Voice Agent configuration uses:
Joanna (US Female)
with the underlying voice ID:
Polly.Joanna-Neural.
19.47 Core Objective
The next field is:
Core Objective.
This describes the Agent's high-level purpose.
The current default is:
General purpose AI phone assistant.
19.48 Core Objective Examples
Possible objectives include:
Qualify inbound sales prospects and determine whether they should be scheduled for a product demonstration.
Confirm appointments and identify whether the customer needs to reschedule.
Answer basic customer service questions and gather information for escalation.
Follow up with leads who requested information about our services.
Keep the objective focused on what the Agent should accomplish.
19.49 Max Duration (seconds)
Agent Configuration provides:
Max Duration (seconds).
The current default configuration is:
600 seconds
or:
10 minutes.
19.50 Setting Maximum Call Duration
Use the maximum duration to define the intended upper boundary of the call.
For example:
300
= 5 minutes
600
= 10 minutes
A shorter value may make sense for:
A longer duration may be appropriate for more involved support conversations.
19.51 Silence Timeout (seconds)
The next field is:
Silence Timeout (seconds).
The current default configuration is:
5 seconds.
The type definition describes this as the number of seconds before a re-prompt.
19.52 Choosing a Silence Timeout
A very short timeout can cause the Agent to respond before a caller has finished thinking.
A very long timeout can create awkward dead air.
Test the setting with real calls and adjust according to the conversation style you want.
19.53 Call Terminating Keywords
Agent Configuration provides:
Call Terminating Keywords
with:
(comma-separated).
These are phrases intended to signal that the conversation should end.
19.54 Current Default Terminating Phrases
The current default list is:
19.55 Editing Terminating Keywords
Enter phrases separated by commas.
For example:
goodbye, bye, thank you goodbye, end call, hang up, that's all
Website Builder—not applicable here. In Voice Agent, the field splits the value at commas and stores each non-empty phrase separately.
19.56 Be Careful with Broad Terminating Phrases
Avoid words that can appear naturally in the middle of a conversation if you do not want them interpreted as call-ending instructions.
Prefer explicit expressions such as:
goodbye
or:
that's all
rather than extremely common words.
19.57 Greeting Message
The Voice Agent configuration includes:
Greeting Message (Spoken first on connection).
This is the standard Greeting spoken when the call begins unless a call-specific Greeting Override is used.
19.58 Default Greeting
The current default is:
“Hello! I'm Nova, your AI assistant. How can I help you today?”
19.59 Writing a Good Greeting
A good Greeting should quickly establish:
Keep it natural enough to work as spoken conversation.
19.60 Example Sales Greeting
Hello, I'm the AIUNIFY assistant calling on behalf of ABC Solutions. You recently requested information about our business software, and I'd like to ask a few questions to help determine the best solution for your team.
19.61 Example Appointment Greeting
Hello, I'm calling on behalf of Smith Financial to confirm your consultation scheduled for tomorrow. Is now a good time for a quick confirmation?
19.62 System Prompt / Agent Instructions
The primary behavioral field is:
System Prompt / Agent Instructions.
Use it to tell the Voice Agent:
19.63 Default System-Prompt Behavior
The default Voice Agent instructions tell the Agent to:
These are sensible patterns for voice conversations because spoken interaction differs from long-form AI Chat.
19.64 Voice Prompt vs. Chat Prompt
A good Voice Agent Prompt should generally favor:
Short Spoken Responses
instead of:
Long Written Explanations
A caller cannot visually scan a long paragraph the way a Chat user can.
Keep Voice Agent instructions optimized for listening.
19.65 Example Voice Agent System Prompt
A subscriber could configure:
You are a professional outbound sales qualification assistant for ABC Software. Speak naturally and keep each response under three sentences. Your goal is to determine the prospect's company size, current sales software, primary workflow problem, purchasing timeframe, and whether they want a live product demonstration. Do not invent pricing or contractual terms. If the prospect asks something outside your information, explain that a specialist can follow up. End successful conversations by confirming the next action.
19.66 Active Status
At the bottom of Agent Configuration is:
Active Status
with:
“Control whether this configuration is active globally.”
Use the switch to control whether the current Agent configuration is active.
19.67 Agent Offline
When Active Status is off, the Dialer identifies the Agent as:
Agent Offline.
When active, it displays:
Agent Ready.
19.68 Save Parameters
After changing Agent Configuration, select:
Save Parameters.
Do not assume changing a field alone has persisted the new settings.
19.69 Configuration Saved
A successful Save displays:
Configuration Saved
with:
“AI Voice Agent parameters updated successfully.”
The configuration is then refreshed.
19.70 Save Failed
If the configuration cannot be saved, PROS SUITE displays:
Save Failed
with either the returned message or:
“An unexpected error occurred.”
Do not assume unsaved changes have been persisted.
19.71 Personality Property Is Not Exposed as a Current Field
The underlying Agent configuration contains a personality property and loads it into the page state.
However, the current Agent Configuration interface does not expose a separate visible Personality field.
If you want to influence conversational personality, use:
System Prompt / Agent Instructions
and the Greeting.
This manual does not invent a Personality editor that is not currently shown.
19.72 Call Log Console
The right side of the workspace is:
Call Log Console
with:
“Real-time activity reporting, diagnostics, and call transcripts.”
The current page requests up to:
30 call records
when loading the log.
19.73 No Sessions Dispatched
When there are no call records, the Call Log Console displays:
No Sessions Dispatched
and:
“Use the interactive dialer console to place your first automated AI phone call.”
19.74 Call Direction
Each Log identifies the call as:
INBOUND
or:
OUTBOUND.
Although the current user Dialer specifically initiates outbound calls, the Call Log data model and UI can display inbound call records as well.
19.75 Current Call Statuses
The Voice Agent data model currently recognizes these statuses:
The Call Log displays the current status as a badge.
19.76 Ringing
RINGING
means the telephony system currently records the call as ringing.
19.77 In Progress
IN-PROGRESS
indicates an active call according to the recorded call status.
19.78 Completed
COMPLETED
indicates the call was recorded as completed.
19.79 Failed
FAILED
indicates the call did not complete successfully.
Review the available call information and retry only when appropriate.
19.80 Busy
BUSY
indicates the destination reported a busy state.
The intended recipient may already be on another call or otherwise unavailable.
19.81 No Answer
NO-ANSWER
indicates the call was not answered.
Decide whether another attempt is appropriate according to your business workflow and applicable calling rules.
19.82 Call Duration
When duration is greater than zero, the Call Log displays the duration beside a Clock icon.
The display converts seconds into:
as appropriate.
19.83 Call Routing Display
For outbound calls, the Call Log displays conceptually:
Twilio → Recipient Number
For inbound calls:
Caller Number → Twilio.
This makes the direction of the telephone interaction easy to identify.
19.84 Call Time
Each Log also displays a locally formatted call time.
Use the Call Log for recent-call review rather than treating it as a full billing or compliance record.
19.85 Inspect Session
To view the conversation from a call:
When no call is selected, the interface says:
Inspect Session
with:
“Select a calling log from the deck above to view complete dialogue records.”
19.86 Loading a Transcript
While call details are loading, the interface displays:
Syncing conversation blocks...
Allow loading to finish.
19.87 Transcript Session Identifier
The Transcript Inspector displays:
SESSION: [Call SID/reference]
using a shortened version of the recorded Call SID.
This helps associate the dialogue with a particular call.
19.88 Agent vs. Caller Messages
Transcripts visually distinguish:
Agent
from:
Caller.
Agent lines display the current Agent Alias.
Caller lines display:
CALLER.
19.89 Transcript Roles
The underlying transcript model identifies each dialogue record as either:
and stores:
19.90 No Dialogue Logged Yet
If a selected call has no transcript content, the interface displays:
No dialogue logged yet.
with:
“Dialogue is populated in real-time as speech is recognized and processed by Gemini.”
19.91 Closing the Transcript Inspector
Use the X in the Transcript header to deselect the call and close its active transcript view.
The Call Logs remain available.
19.92 Selecting the Same Call Again
The current Call Log interaction toggles the selected call.
Selecting an already active Log can deselect it and close the Transcript Inspector.
19.93 Refreshing a Selected Transcript
When you select the Header Refresh control while a call is selected, the current interface refreshes both:
This can be useful during or shortly after an active conversation.
19.94 Transcript Load Failure
If the Transcript cannot be loaded, PROS SUITE displays:
Error
with:
“Failed to load call details.”
Retry Refresh if appropriate.
19.95 The Voice Agent Uses a Different AI Architecture from Standard Tools
AI Voice Agent is not built on the Standard Generator's:
Prompt → Generate → Text Output
interface.
It combines:
The call-specific source components identify Twilio telephony and a Gemini-oriented voice conversation service in the current implementation.
19.96 Header Model Selector vs. Voice Agent Configuration
The current Voice Agent screen does not expose the shared PROS SUITE Model Selector as one of its local Agent Configuration fields.
Its current user configuration focuses on:
Therefore, do not assume changing the general Header Model necessarily changes the AI engine used by the Voice Agent unless the current Voice Agent interface or future source explicitly establishes that behavior.
19.97 Voice Provider vs. AI Conversation Model
These are separate concepts.
TTS Voice
Determines how the Agent sounds.
Examples:
AI Conversation Engine
Determines how the Agent generates conversational responses.
Selecting a different TTS Voice changes the spoken Voice—not the Agent's business instructions.
19.98 Voice Agent Token Cost Is Not Shown in the Current Workspace
Unlike the Standard AI Generator, the current AI Voice Agent page does not display:
A search of the current Voice Agent user page found no subscriber Token display or client-side Token deduction logic for call initiation.
19.99 Do Not Invent a Per-Call Token Price
The actual call API implementation was intentionally excluded from the sanitized User Operations bundle.
Therefore, this manual does not claim:
Those details are not established by the supplied user-facing source.
Use current subscription/billing information when AIUNIFY exposes those policies to subscribers.
19.100 Telephony Charges Are Also Not Established Here
The interface confirms that outbound calls use Twilio infrastructure, but the source does not establish the subscriber's commercial telephone-rate structure.
Therefore, this User Operations Manual does not publish or assume Twilio call rates.
19.101 Current Agent Configuration Checklist
Before using the Agent regularly, review:
19.102 Pre-Call Checklist
Before an outbound call:
19.103 Post-Call Checklist
After the call:
19.104 Best Practice — Test Before Using the Agent Broadly
Before using the Voice Agent for a larger calling workflow:
19.105 Best Practice — Keep Spoken Responses Short
Voice is different from Chat.
A caller usually responds better to concise spoken statements.
The source-defined default Prompt itself instructs the Agent to keep responses to approximately:
1–3 sentences.
19.106 Best Practice — Give the Agent a Narrow Objective
Instead of:
Handle every question about our company.
prefer:
Qualify the prospect, determine company size and purchasing timeframe, answer basic product questions from the approved information, and schedule a specialist follow-up when appropriate.
A focused Agent is easier to test and supervise.
19.107 Best Practice — Explicitly Define What the Agent Must Not Do
For business calls, consider instructions such as:
This reduces unpredictable behavior.
19.108 Best Practice — Align Greeting and Objective
If the Greeting says:
I'm calling to confirm your appointment
but the System Prompt describes a sales Agent, the conversation can feel inconsistent.
Keep:
Alias + Greeting + Objective + System Prompt
aligned.
19.109 Best Practice — Match Language and Voice
For a Spanish-language calling campaign, review the available Language and Voice combination before placing calls.
The Language selector has broader language coverage than the specifically labeled voice list, so test pronunciation and caller experience before production use.
19.110 Best Practice — Review Transcripts for Quality Assurance
The Transcript Inspector can reveal:
Use real conversation evidence to improve the System Prompt rather than changing it randomly.
19.111 Best Practice — Review Failed, Busy, and No-Answer Calls Separately
These statuses represent different outcomes.
Failed
May require technical investigation.
Busy
Recipient may be temporarily unavailable.
No Answer
Recipient did not answer.
Do not treat all three as equivalent.
19.112 Best Practice — Refresh Before Judging Call Outcome
The Call Logs are fetched from the call-service records.
If a status appears stale immediately after a call:
19.113 Best Practice — Do Not Rely Solely on Force Terminate Session
Because the current client source does not verify a provider-level hang-up request behind that button, use:
to confirm the call really ended.
19.114 Best Practice — Use Overrides for One-Off Calls
If the main Agent configuration is already working well, avoid changing the persistent System Prompt for every unusual call.
Use:
Customize Persona for This Call
for one-off objectives.
This helps preserve a stable default Agent.
19.115 Best Practice — Save Persistent Changes Deliberately
Remember:
Changing Agent Configuration field
does not equal:
Configuration Saved
After persistent changes, select:
Save Parameters
and wait for:
Configuration Saved.
19.116 Best Practice — Respect Calling Laws and Consent Requirements
AI Voice Agent provides the technical ability to initiate telephone calls, but the current user-facing source does not determine whether a particular call, recipient, recording/transcription practice, automated voice use, marketing campaign, or calling time is legally permissible.
The subscriber is responsible for using the system in accordance with applicable calling, consent, privacy, recording, and marketing requirements.
19.117 Troubleshooting — Initiate Call Session Is Disabled
Check the Twilio Infrastructure Guard.
If it says:
Twilio Configuration Missing
the current Dialer intentionally disables the call button.
Contact AIUNIFY support or the appropriate account administrator.
19.118 Troubleshooting — Agent Offline
If the Dialer says:
Agent Offline:
19.119 Troubleshooting — Wrong Country Code
If the call number looks incorrect:
Remember that the current field defaults to India.
19.120 Troubleshooting — Phone Number Required
If you receive:
Phone Number Required
“Please specify a valid phone number.”
enter the recipient number before continuing.
19.121 Troubleshooting — Calling Failed
If you receive:
Calling Failed:
19.122 Troubleshooting — Call Button Still Shows an Active Session
The local Dialer calling state is separate from the Call Log service.
If the interface seems stale:
Remember the Force Terminate limitation documented earlier.
19.123 Troubleshooting — Call Log Does Not Appear Immediately
Select:
Refresh Logs & Transcript.
The page normally requests recent Logs when the workspace opens and after a successful call initiation, but manual Refresh is available when information has not yet updated.
19.124 Troubleshooting — Transcript Is Empty
If you see:
No dialogue logged yet.
the current interface indicates that no transcript records are available for that call yet.
Try:
19.125 Troubleshooting — Transcript Will Not Load
If you receive:
Failed to load call details.
select Refresh and retry the Call Log.
If the problem persists, use the appropriate AIUNIFY support process.
19.126 Troubleshooting — Agent Says the Wrong Greeting
Check both:
Persistent Agent Configuration
Greeting Message
and:
Interactive Dialer
Customize Persona for This Call → Initial Greeting Override
A one-call override can supersede the normal Greeting for that outbound session.
19.127 Troubleshooting — Agent Is Following the Wrong Objective
Check:
Use the Transcript to determine what actually happened during the conversation.
19.128 Troubleshooting — Voice Does Not Match Language
Open:
Agent Configuration
and compare:
These settings are selected separately.
Choose and test a more appropriate combination.
19.129 Troubleshooting — Configuration Changes Disappear
Confirm that you selected:
Save Parameters
and received:
Configuration Saved.
Editing form values alone does not establish successful persistence.
19.130 Troubleshooting — Force Terminate Says Disconnect Signal Dispatched but Call Continues
The current client implementation does not source-verify a backend termination request for this control.
If the live call continues:
19.131 What Subscribers Do Not Need to Configure
This User Operations Manual does not instruct subscribers to configure:
Those are infrastructure functions, not subscriber operations.
19.132 What the Current AI Voice Agent Supports
The supplied source verifies these user-facing capabilities:
Outbound Calling
Agent Configuration
Monitoring
Transcripts
19.133 What the Current User Interface Does Not Establish
The supplied source does not establish subscriber-facing controls for:
Do not assume these functions exist simply because another AIUNIFY calling system may provide them.
19.134 Voice Agent Operating Workflow
The current subscriber workflow can be summarized as:
AI VOICE AGENT
↓
AGENT CONFIGURATION
Set:
Agent Alias
Language
Voice
Core Objective
Max Duration
Silence Timeout
Terminating Keywords
Greeting
System Prompt
Active Status
↓
SAVE PARAMETERS
↓
INTERACTIVE DIALER
↓
SELECT COUNTRY
↓
ENTER PHONE NUMBER
↓
Optional:
CUSTOMIZE PERSONA FOR THIS CALL
↓
INITIATE CALL SESSION
↓
ACTIVE CALL STREAM
↓
CALL LOG CONSOLE
↓
STATUS + DURATION
↓
SELECT CALL
↓
TRANSCRIPT
↓
REVIEW PERFORMANCE
↓
REFINE AGENT CONFIGURATION
19.135 Chapter Summary
AI Voice Agent is AIUNIFY PROS SUITE's specialized conversational telephone workspace.
The current interface is called:
AI Voice Calling Agent
and provides two main operating tabs:
Interactive Dialer
and:
Agent Configuration.
The Interactive Dialer allows the subscriber to select a Country, enter a Recipient Phone Number, optionally enable Customize Persona for This Call, specify a one-call Initial Greeting Override and System Prompt / Core Objective Override, and select:
Initiate Call Session.
A successful outbound request displays:
Call Initiated
“Dialing [phone number] via Twilio.”
The Agent Configuration tab provides subscriber controls for:
Current supported Languages include English variants, Spanish variants, French, German, Italian, Portuguese, Japanese, Korean, Mandarin Chinese, Hindi, and Arabic.
The current TTS list includes Amazon Polly Neural voices, Google Neural2 voices, and classic Twilio voices.
The Call Log Console displays recent inbound and outbound sessions, their Status, Duration, numbers, and time. Selecting a Log opens its call Transcript and differentiates Agent dialogue from Caller dialogue.
One important current limitation is that although the interface provides Force Terminate Session, the supplied client source does not show a provider/API termination request behind that action. It only clears the local calling state, displays “Disconnect signal dispatched,” and refreshes Call Logs afterward. Users should therefore verify the actual call status rather than relying on that control alone as confirmation of provider-level disconnection.
The current Voice Agent screen also does not expose a subscriber Token cost or telephony rate, so this manual does not invent a per-call Token or Twilio pricing model.
The recommended operating method is:
Configure the Agent → Save Parameters → Test with a Controlled Number → Review the Transcript → Refine the Prompt and Voice → Verify Call Status → Expand Usage Only After the Agent Performs Reliably