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

# Test before visitors do

> Check answers, tone, and booking behavior in a private preview.

<div className="darwin-location"><strong>Find it in Darwin</strong> Top bar → Test assistant <a href="https://app.meetdarwin.ai/admin/sandbox">Open this screen ↗</a></div>

Use **Test assistant** for a private conversation, or the test chat inside guided setup. Ask real questions visitors would ask instead of only typing “hello.”

## A five-question check

| Ask                                             | Check                                                          |
| ----------------------------------------------- | -------------------------------------------------------------- |
| “What does your product do?”                    | A clear explanation grounded in your business.                 |
| “How does pricing work?”                        | Current terms, no invented discounts or guarantees.            |
| “Does this work with \[important integration]?” | A specific supported answer or an honest limitation.           |
| “Can you do \[something unsupported]?”          | No invented capability. A helpful next step where appropriate. |
| “Can I talk to someone?”                        | A meeting offer and the correct scheduling destination.        |

Keep a short list of these questions and repeat it after meaningful changes to knowledge or instructions.

## Complete the setup test

In the guided setup lightbox, the private test chat opens automatically after you save your scheduling link. Send a message and check the reply. Darwin detects the saved response and enables **Finish setup**; there is no confirmation checkbox. If relevant settings change after the test, Darwin may require a fresh conversation rather than accepting an old result.

<Note>If the screen says **Mock preview**, you are testing the interface rather than a live AI provider. A successful mock conversation is not proof that production answers, automated experiments, or verified bookings are ready.</Note>

Appearance settings have a separate sample preview. Its controls help you test the design without creating real conversation, lead, or meeting records.

If an answer is wrong, [fix the source and retest](/help/improve-answers). If the calendar fails, [check scheduling and booking tracking](/help/booking-troubleshooting).