← All documentation

Test the Voice Agent, and understand the fallback

Test before you go live, and know what callers experience when AI minutes run out — because that moment will happen, and it should feel like a handover, not a failure.

Step 1 — Try Simulated Chat first

  1. In the portal, open Assistant, click the AI Voice Agent node, then TRY IT IN SIMULATED CHAT — FREE. This opens the Simulated Chatbot panel. This is a dry run — no real call is placed.
  2. Simulated Chatbot panel showing Voice Agent mode, Call and Hang Up buttons, and no conversation yet
    Screenshot: Simulated Chatbot start state, cropped to the panel. The fake number shown in the panel is the portal's own test number, not a real caller number.
  3. Play a caller: ask about hours, ask about pricing, ask for an appointment, and give a ZIP outside your area.
  4. Check that every answer matches your notes and your live booking check. Fix the notes where the agent guessed, and re-test.
  5. Try the awkward cases: a caller who interrupts, a caller who asks for a person, and a caller who changes their mind mid-booking.

Step 2 — Make a real test call

  1. Call your number from a second phone and run the same script.
  2. Listen for pauses, misheard names, and ZIP codes. If the agent mishears a ZIP, the service-area answer will be wrong — that is the most common real-world error.
  3. Check call history and messages in the portal after the call. What the portal recorded should match what you heard.

Step 3 — Understand the fallback and minutes

Tip: After any change to hours, pricing, or booking, re-run Simulated Chat once. It takes two minutes and catches the change that would otherwise reach a real caller first.

Checklist

← Back to all documentation