Skip to main content
What youโ€™ll learn: How to create customer profiles, run automated tests on your AI agents, and interpret test results to improve performance.

What Is Automated Agent Testing?

Automated agent testing allows you to simulate real customer interactions without making actual phone calls. Think of it as a rehearsal where your AI agent practices with different types of customers before going live. Instead of manually calling test numbers, you create Customer Profiles that act like different customers, and the system automatically tests how well your agent handles each scenario.

Why Use Automated Testing? ๐ŸŽฏ

The Problems It Solves:

  • Time-consuming manual testing - No need to manually test every scenario
  • Inconsistent test coverage - Ensures all scenarios are tested systematically
  • Costly errors in production - Catch issues before real customers are affected
  • Difficult to reproduce edge cases - Create specific scenarios that are hard to test manually

The Benefits:

  • Fast iteration - Test multiple scenarios simultaneously
  • Cost-effective - Only $0.02 per customer profile test
  • Consistent results - Same scenarios tested the same way every time
  • Comprehensive coverage - Test edge cases that rarely happen in real life

How Automated Testing Works ๐Ÿ”ง

The testing flow is simple:

Step 1: Create Customer Profiles

Customer Profiles are simulated customers that interact with your AI agent. Each profile represents a different type of customer with unique behaviors, responses, and scenarios.

Accessing the Customer Profile Page

  1. Navigate to: https://app.vodex.ai/account/test-customer
  2. Click the โ€œAdd New Customerโ€ button
  3. Youโ€™ll see a form with several fields to configure

Customer Profile Fields

Hereโ€™s what each field means and how to fill it out:
  • Customer Name
  • Short Description
  • Customer Scenario
  • User Fields

Customer Name

What it is: A unique identifier for this customer profile.Purpose: Helps you quickly identify which customer scenario youโ€™re testing.Examples:
  • โ€œSarah - Interested Buyerโ€
  • โ€œJohn - Difficult Customerโ€
  • โ€œMaria - Payment Readyโ€
  • โ€œDavid - Needs More Infoโ€
Use descriptive names that instantly tell you what type of customer this profile represents.

Complete Customer Profile Example

Hereโ€™s a fully filled out customer profile for reference:
Customer Name: Sarah - Ready to PayShort Description: Customer acknowledges debt and wants to clear it todayCustomer Scenario:
You are Sarah Martinez, a 31-year-old teacher who has an outstanding balance 
of $850 with LoanCo. You received several reminder emails but have been dealing 
with family issues and forgot to pay. 

When the AI agent calls:
- Apologize for the delay and explain you've been dealing with personal matters
- Confirm you remember the loan
- Express that you want to clear it today
- Ask if you can pay by credit card over the phone
- Confirm the amount is $850
- Ask for a confirmation email after payment
- Thank the agent for being understanding
- Be friendly and cooperative throughout

If asked about your availability: You're available now and want to complete 
the payment immediately.

If asked about payment method: Prefer credit card, but can do bank transfer 
if needed.
User Fields:
{
  "Amount": "850.00",
  "LoanID": "LN-98765",
  "DueDate": "2025-11-15",
  "CustomerID": "CUST-2345",
  "CustomerName": "Sarah Martinez",
  "today": "NA",
  "time_zone": "America/Chicago"
}

Creating Multiple Customer Profiles

For comprehensive testing, create profiles that cover:
Essential Test Scenarios:
  • โœ… Happy Path - Cooperative customer who completes the objective
  • โœ… Objection Handler - Customer with concerns or questions
  • โœ… Difficult Customer - Skeptical or resistant customer
  • โœ… Busy Customer - Person who has limited time
  • โœ… Confused Customer - Doesnโ€™t understand or needs clarification
  • โœ… Edge Case - Unusual situations or unexpected responses

Step 2: Test Your AI Agent

Once youโ€™ve created customer profiles, itโ€™s time to test your AI agent against them.

Starting a Test

  1. Navigate to Your Agent:
    • Go to the Agents section in your dashboard
    • Find the AI agent you want to test
  2. Access Test Options:
    • Click the three dots (โ‹ฎ) next to your agentโ€™s name
    • Select โ€œTest Agentโ€ from the dropdown menu
  3. Configure the Test: Youโ€™ll see a test configuration screen with these options:
  • Select Customer Profiles
  • Select AI Model

Choose Customer Profiles

What to do: Select one or more customer profiles you created in Step 1.Options:
  • Single profile - Test one specific scenario
  • Multiple profiles - Test several scenarios in batch
Best Practice:
Start with 3-5 profiles that cover:
1. Your ideal customer (happy path)
2. A common objection scenario
3. A difficult customer scenario
You can run multiple profiles simultaneously to speed up testing.
  1. Start Testing:
    • After selecting profiles and model, click โ€œStart Testingโ€
    • The system will begin running automated conversations
    • Each profile will interact with your agent independently

What Happens During Testing?

Test Duration: Each test conversation runs automatically and completes within 1-3 minutes depending on complexity. Each test costs $0.02 per customer profile.

Step 3: View Test Results

After testing completes, you can review the results and identify areas for improvement.

Accessing Test Results

  1. Return to Your Agent:
    • Go back to the Agents section
    • Find the same AI agent you tested
  2. Open Test Progress:
    • Click the three dots (โ‹ฎ) next to the agent
    • Select โ€œTest Agent Progressโ€
  3. Review Results Dashboard:
    • Youโ€™ll see a list of all test runs with their status

Understanding Test Status

  • Success โœ…
  • Failed โŒ
  • Turn Limit

Success Status

What it means: The conversation completed gracefully without errors.Success indicators:
  • Agent followed the prompt correctly
  • All custom fields were accessible
  • Conversation reached a natural conclusion
  • No system errors occurred
What to check:
  • Read the conversation transcript
  • Verify the agent achieved its objective
  • Check if the tone and responses were appropriate
  • Confirm all tags (like (disconnect)) worked correctly
Even if marked โ€œSuccessโ€, you should review:
  • Did the agent sound natural?
  • Was the conversation efficient?
  • Could anything be improved?
A โ€œSuccessโ€ status means technical success - still review for quality!

Analyzing Conversation Transcripts

When reviewing test results, look for these key elements:

โœ… Natural Flow

  • Agent sounds conversational, not robotic
  • Smooth transitions between topics
  • Appropriate pauses and acknowledgments
  • Natural response to customer questions

โœ… Objective Achievement

  • Agent stayed focused on the goal
  • Successfully completed the intended action
  • Didnโ€™t get sidetracked by irrelevant topics
  • Used appropriate closing statements

โœ… Objection Handling

  • Acknowledged customer concerns
  • Provided helpful responses
  • Didnโ€™t sound defensive or pushy
  • Offered alternatives when appropriate

โœ… Technical Correctness

  • All custom fields displayed correctly
  • Tags triggered appropriate actions
  • No error messages in conversation
  • Transfers and disconnects worked properly

โœ… Professional Tone

  • Maintained consistent personality
  • Used appropriate language
  • Showed empathy when needed
  • Ended conversation gracefully

Testing Costs and Billing ๐Ÿ’ฐ

Automated testing is extremely cost-effective:
Pricing Structure:
  • Cost per test: $0.02 per customer profile test
  • Pay as you go: Only pay for the tests you run
  • Billing cycle: All charges accumulate throughout the day and are deducted at the end of the day
  • No subscription fees: No daily or monthly charges - only pay when you test

Cost Examples

Testing ActivityNumber of TestsCost
Run 5 customer profile tests5$0.10
Run 10 customer profile tests10$0.20
Run 50 customer profile tests50$1.00
Run 100 customer profile tests100$2.00
No testing0$0.00
Example Billing Cycle:
Monday:
  - 9:00 AM: Test Agent with 3 profiles = $0.06
  - 2:00 PM: Test Agent with 5 profiles = $0.10
  - 5:00 PM: Test Agent with 2 profiles = $0.04
  
  Total deducted at end of Monday: $0.20
Value Proposition: At just 2 cents per test, you can thoroughly validate your agents before deploying them to real customers, ensuring quality and reducing costly mistakes.

Best Practices for Automated Testing

1. Create a Comprehensive Test Suite

Build a library of customer profiles that cover all scenarios:
Essential Profiles to Create:
โ”œโ”€โ”€ Happy Path
โ”‚   โ”œโ”€โ”€ Eager customer
โ”‚   โ””โ”€โ”€ Cooperative customer
โ”œโ”€โ”€ Common Objections
โ”‚   โ”œโ”€โ”€ Price concerns
โ”‚   โ”œโ”€โ”€ Timing issues
โ”‚   โ””โ”€โ”€ Need more information
โ”œโ”€โ”€ Difficult Scenarios
โ”‚   โ”œโ”€โ”€ Angry customer
โ”‚   โ”œโ”€โ”€ Skeptical customer
โ”‚   โ””โ”€โ”€ Very busy customer
โ””โ”€โ”€ Edge Cases
    โ”œโ”€โ”€ Language barriers
    โ”œโ”€โ”€ Hearing difficulties
    โ””โ”€โ”€ Unexpected situations

2. Test Before Every Major Change

Run your test suite whenever you:
  • โœ… Update your agent prompt
  • โœ… Add new custom fields
  • โœ… Change call flow logic
  • โœ… Modify greeting or voicemail messages
  • โœ… Update objection handling strategies

3. Iterate Based on Results

Use this continuous improvement cycle:

4. Document Your Test Scenarios

Keep a record of:
  • What each customer profile tests
  • Expected outcomes for each profile
  • Changes made based on test results
  • Performance improvements over time

5. Test with Realistic Data

Important: Use realistic but not actual customer data in your test profiles. Create fictional but plausible scenarios that mirror real situations.

Troubleshooting Common Issues

Issue 1: Test Shows Success but Conversation Quality is Poor

Problem: Test passes technically but the conversation doesnโ€™t sound good. Solution:
  1. Read the full transcript carefully
  2. Identify specific lines that sound unnatural
  3. Update your prompt with better instructions
  4. Add more example responses to guide the agent
  5. Test again with the same profile

Issue 2: Tests Keep Failing with Custom Field Errors

Problem: Agent canโ€™t access custom fields in the conversation. Solution:
  1. Check field names are exactly the same in:
    • Your agent prompt
    • Your customer profile
  2. Field names are case-sensitive (Amount โ‰  amount)
  3. Ensure all fields referenced in your prompt exist in the customer profile
  4. Verify field values are in the correct format
Example Fix: โŒ In Prompt: The amount due is {total_amount}
โŒ In Profile: "Amount": "500"
โœ… Fixed: Both use "total_amount" or both use "Amount"

Issue 3: Hitting the 25-Turn Limit Regularly

Problem: Conversations are too long and hit the maximum turn limit. Solution:
  1. Simplify your agentโ€™s objectives
  2. Remove unnecessary questions from the prompt
  3. Add clearer exit criteria to end calls sooner
  4. Check for conversation loops (agent repeating same questions)
  5. Use tags like (disconnect) more strategically

Issue 4: Customer AI Doesnโ€™t Follow the Scenario

Problem: The AI impersonating the customer doesnโ€™t behave as described in the profile. Solution:
  1. Make the customer scenario more specific and detailed
  2. Use clear imperative language (โ€œYou shouldโ€ฆโ€, โ€œAlwaysโ€ฆโ€, โ€œNeverโ€ฆโ€)
  3. Provide example responses in the scenario
  4. Test with a more advanced AI model (GPT-4 or Claude)
  5. Break complex scenarios into simpler ones

Issue 5: Tests Pass But Real Calls Fail

Problem: Automated tests work but real customer calls have issues. Solution:
  1. Create more realistic customer profiles
  2. Add profiles for unexpected customer behaviors
  3. Include interruptions and side questions in scenarios
  4. Test with more varied customer personalities
  5. Review real call recordings and create profiles that match

Advanced Testing Strategies

Regression Testing

Create a baseline test suite that you run before every deployment:
Baseline Test Suite:
1. Happy path customer (should always pass)
2. Common objection (tests objection handling)
3. Difficult customer (tests resilience)
4. Quick call (tests efficiency)
5. Complex scenario (tests advanced logic)

A/B Testing Your Prompts

Test different versions of your agent:
  1. Create Agent Version A with one prompt approach
  2. Create Agent Version B with a different prompt approach
  3. Run the same customer profiles against both
  4. Compare results to see which performs better
  5. Deploy the winning version

Stress Testing

Test extreme scenarios:
  • Very long customer responses
  • Customer who constantly interrupts
  • Customer who goes completely off-topic
  • Customer who is extremely emotional
  • Multiple objections in one call

Progressive Testing

Start simple and increase complexity:
Week 1: Test basic scenarios (happy path)
Week 2: Add common objections
Week 3: Add difficult customers
Week 4: Add edge cases
Week 5: Add stress tests

Success Metrics

Track these metrics to measure testing effectiveness:
MetricHow to CalculateTarget
Test Pass Rate(Successful tests / Total tests) ร— 100>90%
Average TurnsTotal turns / Number of tests<15 turns
Scenario CoverageNumber of scenarios testedAll critical paths
Issues FoundProblems identified before productionTrack trend
Time to FixTime from issue found to resolved<1 day

Next Steps

Now that you understand automated testing:
  1. Start small - Create 3-5 customer profiles for your most common scenarios
  2. Run your first test - Test your agent with these profiles
  3. Review results - Carefully read the transcripts and identify improvements
  4. Iterate - Update your prompt based on findings
  5. Expand coverage - Gradually add more profiles for edge cases
  6. Make it routine - Run tests before every significant change
Ready to start testing? Head to https://app.vodex.ai/account/test-customer and create your first customer profile today!

Want to improve your agentโ€™s responses? Check out our Prompt Guide to learn how to write more effective instructions. Need to add automated actions? Visit our Tags Guide to learn about special commands like (disconnect) and (transfer). Just getting started? Read our Agents Overview to understand the basics of AI agent creation.