Improving Your AI Employee
Use documents, business info, voice settings, and transcript review to improve your AI employee step by step.
Why an Improvement Loop Matters
The first setup is only the baseline. The best results come from reviewing real conversations, spotting weak points, and iterating on the settings you actually control in the customer panel.
The panel does not let you edit prompts or add new capabilities directly. If the employee needs a larger behavior change, contact support.
The Four Levers You Control
Business Info
Short, clear, current business context helps the employee stay on-topic.
Documents
Policies, product details, FAQs, and longer explanations depend on document quality.
Voice & Speech
Energy, pace, volume, and interruption handling strongly affect how natural the employee feels.
Call Settings
Opening behavior, silence handling, call length, and voicemail settings shape the flow of the call.
A Practical Improvement Loop
Open Contacts > Conversations and inspect the transcript, summary, and information captured from the conversation. Note where the employee sounds repetitive, misses context, or fails to move the call forward.
Avoid changing several settings at once. Update one lever, such as a document or speech pace, so you can tell what made the difference.
Use Test Employee in web or real-call mode to hear the result immediately after the change.
Check whether the new transcript is clearer, the opening is tighter, or the customer questions are handled better than before.
Most Common Improvement Areas
| Problem | First place to check |
|---|---|
| Wrong or incomplete answers | Documents and Business Info |
| Too fast, too sharp, or too flat | Voice & Speech > Voice Character |
| Interrupts the customer | Voice & Speech > Conversation Feel |
| Opening feels confusing | Call Settings > Call Flow |
| Calls end too early or run too long | Call Settings > Timing |
Outdated documents create bigger problems than imperfect voice settings. Review product details, pricing, hours, and procedures regularly.
When to Contact Support
- You need different conversation content
- You need a new capability or integration
- You need a new captured field from the conversation
- The scope of the call flow changes significantly