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

# Test her, then go live

> How to test your AI receptionist before real clients reach her — the free preview call, dashboard test calls that don't use your minutes, and a go-live checklist.

## Call her before you pay for anything

Three questions into the builder — once she has a name — a **Call** button appears.
That's a real call to the receptionist you've built so far, with a live transcript. No
account, no card, no commitment.

Use it. Say what a real client says, not what you hope they'd say:

* *"Uh, hi — I don't really know if this is the right place. I got rear-ended on the
  405 last Tuesday?"*
* *"I need to talk to someone about custody. My ex took the kids to Arizona."*
* *"How much do you charge?"* — check she handles fees the way you set.
* *"I'm a current client, I just need an update on my case."*

## Test calls don't cost you minutes

Calls you start from the builder or from **Dashboard → Agent** are marked as tests and
**do not count** toward your plan's minutes. Real calls — her phone line and your
website widget — do.

So test as much as you like. There's no meter running.

## Go-live checklist

<Steps>
  <Step title="Verify your email">
    Required before she can get a number or go live.
  </Step>

  <Step title="Call her number with three different scenarios">
    A good new client, a current client, and a salesperson. Three calls, five minutes.
  </Step>

  <Step title="Check the intake email actually arrived">
    And that it landed somewhere a human reads — not a shared inbox nobody opens.
  </Step>

  <Step title="Test the transfer, if you set one">
    Confirm it rings the right phone and that she introduces the caller before
    connecting.
  </Step>

  <Step title="Test a booking, if she books">
    Book a real slot, confirm it appears on the right calendar, then delete it.
  </Step>

  <Step title="Then forward your office line">
    Conditional forwarding first — she picks up what your team misses. See
    [her phone number](/studio/phone-number).
  </Step>
</Steps>

<Check>
  Do the whole checklist before you publish her number anywhere. Ten minutes now beats
  one bad first call with a real client.
</Check>

## The first week

<CardGroup cols={2}>
  <Card title="Read the transcripts daily" icon="file-lines">
    **Dashboard → History**. You'll spot missing intake questions and wrong assumptions
    faster than any settings review.
  </Card>

  <Card title="Adjust one thing at a time" icon="sliders">
    Change a question, then call her about that question. Batch edits make it hard to
    tell what fixed what.
  </Card>

  <Card title="Watch your minutes" icon="gauge">
    **Dashboard → Settings → Usage**. The first week tells you whether your minutes fit.
  </Card>

  <Card title="Tell your team" icon="users">
    Especially whoever's number receives transfers. A surprise warm transfer from an AI
    goes badly.
  </Card>
</CardGroup>


## Related topics

- [How to build an AI receptionist and intake system](/guides/build-an-ai-receptionist.md)
- [Put her on your website](/studio/website-widget.md)
- [Her phone number](/studio/phone-number.md)
- [Studio FAQ](/studio/faq.md)
- [Managing her after launch](/studio/dashboard.md)