Skip to main content
Test Chat allows you to interact with your agent via text messages. It’s a quick way to verify conversation logic without needing audio.

​
Overview

Test Chat provides:
  • Text-based conversation with your agent
  • Faster iteration than voice testing
  • Visual flow tracking on canvas
  • Transcript for easy review

​
Starting a Test Chat

  1. Open your flow agent in the Flow Builder
  2. Click the Test button in the toolbar
  3. Select Test Chat
  4. Type your message and press Enter

​
During the Test

​
Chat Interface

The test panel shows:
  • Your messages (right-aligned)
  • Agent responses (left-aligned)
  • Timestamps
  • Active node indicator

​
Canvas Visualization

The canvas updates in real-time:
IndicatorMeaning
Purple glowCurrently active node
Green edgeActive transition
Path highlightConversation progression

​
Extracted Data

If using Data Extraction nodes, collected variables appear in the panel.

​
When to Use Test Chat

  • Quickly verify conversation logic
  • Test multiple scenarios rapidly
  • Debug flow issues
  • Iterate on prompts
  • Test without audio setup

​
Testing Strategies

​
Quick Validation

Test basic flow: 
You: "Hi, I need help with my order"
Agent: "I'd be happy to help with your order. Can you provide your order number?"
You: "AB123456"
Agent: "Thank you. I found order AB123456. What would you like to know?"

​
Transition Testing

Test each transition path: 
Test 1: "I want to return something" → Should go to Returns
Test 2: "I have a billing question" → Should go to Billing
Test 3: "Let me speak to someone" → Should go to Transfer
Test 4: "That's all, thanks" → Should go to End Call

​
Edge Case Testing

Test unusual inputs: 
You: "asdfghjkl"
Agent: (Should handle gracefully, not crash)

You: ""
Agent: (Should prompt for input)

You: "I hate your company"
Agent: (Should de-escalate or transfer)

​
Reading the Results

​
Successful Conversation

The flow works when:
  • Correct nodes activate at the right time
  • Transitions fire on expected conditions
  • Responses are accurate and helpful
  • The conversation reaches the intended goal

​
Identifying Issues

Watch for:
IssueSymptom
Wrong transitionFlow goes to unexpected node
Missing transitionFlow stays stuck in one node
Bad responseAnswer is inaccurate or off-topic
No KB retrievalAgent doesn’t use knowledge base

​
Tips for Effective Testing

Focus on a single path or feature in each test session.
Create a set of standard test inputs you run every time.
Screenshot or copy transcripts that show issues.
Test the same intent with different wording.

​
Chat vs Call Differences

AspectTest ChatTest Call
SpeedFasterSlower
SetupNoneMicrophone needed
Voice testingNoYes
Timing/pacingNoYes
InterruptionsNoYes
Iteration speedFastModerate

​
Best Practices

Test Early

Start testing as soon as you have a basic flow.

Document Failures

Keep track of what doesn’t work and why.

Use Both Modes

Chat for logic, Call for voice and final validation.

Test Regularly

Retest after every significant change.

Test Call

Voice-based testing

Flow Canvas

Visual flow building

Transitions

Debug transition issues