> ## Documentation Index
> Fetch the complete documentation index at: https://docs.retoneai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Test Chat

> Test your agent with text messages

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:

| Indicator          | Meaning                  |
| ------------------ | ------------------------ |
| **Purple glow**    | Currently active node    |
| **Green edge**     | Active transition        |
| **Path highlight** | Conversation progression |

### Extracted Data

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

## When to Use Test Chat

<Tabs>
  <Tab title="Use Test Chat">
    * Quickly verify conversation logic
    * Test multiple scenarios rapidly
    * Debug flow issues
    * Iterate on prompts
    * Test without audio setup
  </Tab>

  <Tab title="Use Test Call">
    * Verify voice quality and pronunciation
    * Test turn-taking and interruptions
    * Evaluate timing and pacing
    * Final testing before go-live
    * Test audio-specific features
  </Tab>
</Tabs>

## 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:

| Issue              | Symptom                           |
| ------------------ | --------------------------------- |
| Wrong transition   | Flow goes to unexpected node      |
| Missing transition | Flow stays stuck in one node      |
| Bad response       | Answer is inaccurate or off-topic |
| No KB retrieval    | Agent doesn't use knowledge base  |

## Tips for Effective Testing

<AccordionGroup>
  <Accordion title="Test one thing at a time">
    Focus on a single path or feature in each test session.
  </Accordion>

  <Accordion title="Use consistent test cases">
    Create a set of standard test inputs you run every time.
  </Accordion>

  <Accordion title="Save problem conversations">
    Screenshot or copy transcripts that show issues.
  </Accordion>

  <Accordion title="Vary your phrasing">
    Test the same intent with different wording.
  </Accordion>
</AccordionGroup>

## Chat vs Call Differences

| Aspect          | Test Chat | Test Call         |
| --------------- | --------- | ----------------- |
| Speed           | Faster    | Slower            |
| Setup           | None      | Microphone needed |
| Voice testing   | No        | Yes               |
| Timing/pacing   | No        | Yes               |
| Interruptions   | No        | Yes               |
| Iteration speed | Fast      | Moderate          |

## Best Practices

<CardGroup cols={2}>
  <Card title="Test Early" icon="clock">
    Start testing as soon as you have a basic flow.
  </Card>

  <Card title="Document Failures" icon="clipboard">
    Keep track of what doesn't work and why.
  </Card>

  <Card title="Use Both Modes" icon="arrows-left-right">
    Chat for logic, Call for voice and final validation.
  </Card>

  <Card title="Test Regularly" icon="rotate">
    Retest after every significant change.
  </Card>
</CardGroup>

## Related

<CardGroup cols={2}>
  <Card title="Test Call" icon="phone" href="/test-agent/test-call">
    Voice-based testing
  </Card>

  <Card title="Flow Canvas" icon="diagram-project" href="/agent-builder/flow-canvas">
    Visual flow building
  </Card>

  <Card title="Transitions" icon="arrow-right" href="/agent-builder/transitions">
    Debug transition issues
  </Card>
</CardGroup>