The fastest way to catch a wrong greeting, a missing service or a broken transfer is to talk to your AI before patients do. A test call has the AI call you, using whichever script you pick.
Start a test call
- Open Receptionist → AI Voice → Call scripts.
- Find the script you want to try and click its Test button. The button is greyed out for a disabled script ("Enable the script first to test it").
- In the Test Call window, enter the number to call under Your Phone Number. Use My Phone fills in your practice's phone number.
- Click Start Test Call. Your phone rings within a few seconds; answer it and talk to your AI.
The call uses the script you picked and your current saved voice from the Voice tab, fetched fresh each time, so a voice you just changed is picked up.
What happens during the call
| Stage | What you see |
|---|---|
| Connecting... | "Setting up the demo call". |
| Calling your phone... | Your phone is ringing; answer it. |
| Call in Progress | A timer and a Live Transcript. End Call hangs up. |
| Test Call Complete! | How long the call lasted and the Call Transcript. Test Again reruns it; Done closes. |
| Failed | The likely cause and troubleshooting tips (below). |
What a test does and doesn't do
- Inbound scripts run your real receptionist: the script is layered onto your real settings, so the AI answers with your hours, address, services, knowledge base and live availability.
- Anything that changes a record is simulated. Bookings, cancellations, reschedules and messages get realistic replies, but nothing is created on your calendar or in your messages.
- Outbound scripts play the script's own flow with sample patient details, so you hear how a reminder or recall call sounds.
- A test always runs as if the office is open, using the script you clicked, not your after-hours agent.
To hear exactly what a caller hears, including a real booking, call your FrontDesk number from your own phone: the Test call button on Settings → Phone & SMS → Calls reminds you of the number. That is a real call, so it uses AI minutes and any booking is real.
What to listen for
- Greeting. Practice name and the assistant's name are right.
- Service matching. The AI maps the caller's words to the right service ("cleaning" to your cleaning service).
- Provider names. Pronounced acceptably.
- Transfers. The right wording before the hand-off.
- Sign-off. Details read back, a polite goodbye, no awkward silence.
- Refusals. A medical question gets no advice; the AI offers to take a message or schedule instead.
Test-call allowance
| Plan | Test calls |
|---|---|
| Free | 5 a month |
| Pro, Elite, Enterprise | Unlimited |
On a limited plan the window shows how many test calls remain. At zero it shows Test Call Limit Reached with Upgrade Plan and Go Back, and the start button becomes Upgrade to Continue Testing. After onboarding, test calls also need a verified account email.
If a call fails
The failure screen names the likely cause (Line Busy, No Answer, Call Declined, Invalid Number or Call Failed) and suggests:
- Make sure your phone is on and has signal.
- Check the number for call blocking or spam filtering.
- Try a different number; mobile works best.
Try Again redials the same number; Use Different Number clears it so you can enter another.
Fix what you find
When a test shows the wrong behavior, adjust the setting on the Voice tab, edit the script on the Call scripts tab, add a knowledge entry, or write a permanent rule on the Clinical rules tab. Then test again. Test calls from the Test button don't include your clinical rules, so check a new rule by calling your FrontDesk number yourself.
Suggested cadence
| When | What to test |
|---|---|
| Before going live | The script that answers your calls, plus a few of your own real-world questions |
| After adding a service | Ask to book that service |
| After changing the greeting | Any inbound script; listen to the first line |
| After adding knowledge | Ask the new question |
| After changing transfer rules | Say the thing that should trigger the transfer |