DocsStart here
Test before you go live
A saved setting is not a tested setting. Chat with it in the browser, then call it.
By the Callaroo team. Updated November 2026
The assistant can sound right in the editor and still fail on the phone: a missing menu item, a stale opening time, a transfer number that was never saved. Test in the browser first, then make a small real call and check what the workspace recorded. Do this before you forward your main line, not after.
Two ways to test
- Try it live, in the browser: a chat and voice panel on Dashboard → Agent. It is quick, it does not need a phone, and it saves the test on Conversations with a Try it live label.
- A real call: dial your business number. It is the only way to prove the phone company, the number, transfers, texts, recording and the minutes on your plan.
Use the browser for wording and data. Use a real call for anything that leaves the dashboard.
The Try it live panel
Open Dashboard → Agent → Open agent. Choose Caller practice to test the saved greeting, instructions and speech settings. Workspace assistant is a separate mode for owners and managers to check calls and orders and review proposed changes.
- Opening the panel does not start a live call and does not use plan minutes.
- Type a message for a written reply, or choose Start voice and allow microphone access to speak.
- Both voice and typed replies appear in the transcript.
- Mute stops microphone input. Stop closes the connection. Caller practice also closes after a minute of inactivity.
- The transcript stays after the line closes. Use New chat for a clean test, or choose a saved chat at the top to reopen one.
- Audio lets you choose a microphone and speaker for the next session and open the Speech settings.
- Tool activity appears in the chat when the assistant looks up information.
Choose Stop when you finish. Connected browser voice and typed replies appear under Browser agent in Usage.
What the panel can check
- The greeting, the voice and the speaking speed.
- Whether it knows your hours, address and pickup rules from the instructions.
- Menu search: item names and prices from your saved menu.
- Today's order count and item totals for this workspace. It reads item names and quantities, not customer names or notes.
- How it handles an item you do not sell, an unclear request, or a request to pay by card.
- Public facts through web search, when that switch is on.
- The transfer and text tools report that nothing was placed or sent. In this panel, that is the correct result.
- end_call ends the test after a short goodbye.
What it cannot check
- Saving or confirming an order. The panel has no create, update or confirm tool.
- Reservations and callbacks. Those tools are not in the panel.
- A real transfer or a delivered text.
- The phone company, number provisioning, call recording, invoices or plan minutes.
- What a customer hears on a real phone line.
Use a real call to verify customer-facing ordering, transfers and texts. The Workspace assistant has separate review cards for saving a rule, creating or updating an order, or sending an operator text. New owner orders enter Needs review.
Who can use it, and what is saved
This is a workspace test, not a customer call. It follows the same workspace boundary as the rest of the dashboard.
- Who can open it
- Owners and managers
- Settings used
- The saved settings for this workspace
- Saved as
- A Try it live conversation, titled with the first message
- Stored
- The text turns and how long the voice line was open; no audio recording
- Phone minutes
- None. No plan minutes, extra charges or invoice line
- Who can read it
- Workspace members, on Conversations
Each test saves automatically after a reply and when the line closes. If a save fails, the panel keeps the transcript and offers Retry save. Saved tests appear on Conversations labeled Try it live; they are not phone calls and they have no recording.
In short: saved settings only, this workspace only, no writes, no audio, no phone minutes. The saved transcript is the only lasting record. Do not type customer names, phone numbers or card details into a test: the transcript is still workspace data, and the assistant may repeat a name or an order as part of a read back.
Example scripts
Use your own menu and hours. Change the item, the time and the name; keep each test to one question and one expected answer.
Hours: “What time do you close on Friday?” It should answer from your instructions. If it guesses, the hours are missing or unclear.
Menu: “Do you have chicken rice, and how much is it?” It should search the saved menu and read the saved price.
Unavailable item: “Do you have [an item you marked unavailable]?” It should say no, without inventing a substitute.
Order read-back: “Two chicken rice, one without onion, for pickup at 6:30, name Sam.” It can rehearse the order and repeat the request, but it cannot save the order here.
Totals: “How many orders today?” Then “How many chicken rice today?” It should use the summary result only.
Payment: “Can I pay by card over the phone?” It should decline and explain how payment works at your business.
A person: “I need to speak to someone.” It should say a transfer was not placed in this test.
A text: “Text me the confirmation.” It should say no text was sent in this test.
Public fact: “Will it rain tomorrow?” If web search is on, it should check and answer from the result. If it is off, it should say it cannot look it up.
The order script is a wording test, not a save test. Finish the same order on a real call and check it in Orders.
Then make a real test call
Save your settings and run two browser scripts: one about hours, one about the menu.
Call the business number from your own phone and place a small order, including one note such as no onion.
Call again from a withheld or unknown number and confirm it still reaches the assistant.
Try one case that should fail. Use an item you do not sell, a time outside your hours, or a party larger than your limit.
Open Conversations and check the transcript, summary and outcome for each call.
Open Orders and check the items, notes, name and pickup time. Confirm whether anything was flagged for review.
Open Usage and confirm the minutes match the calls you actually made.
Read the saved record
A Try it live chat saves text only. A phone call saves a transcript, a summary and an outcome, and may also save a recording. Both appear on Conversations, but they are not the same kind of record.
- Try it live chat
- Text turns, a title and how long the line was open; no audio
- Phone call
- Transcript, summary, outcome and minutes; recording only when enabled
When recording is enabled at the phone company and workspace storage is configured, a phone call shows a recording panel with a short-lived playback link. The status tells you where the audio is: pending or processing while it is copied, available when it can be played, failed if storage did not complete, and unavailable when there is no recording for that call.
- The playback link is temporary and is not a public URL. Reload the conversation to request a fresh one.
- If storage is not configured, a phone company link may be shown instead, and it can expire on the phone company's schedule.
- A failed recording does not mean the call failed. Use the transcript, which is saved separately.
- A transcript can be exported when its stored copy is available; the export is the conversation's own record, not a public share link.
Common test failures
- The microphone is blocked
- Allow microphone access for the site, then press Start voice again. Nothing was sent.
- The line closes while I am thinking
- It closes about three seconds after a reply. Send a message or press Start voice.
- The chat was not saved
- Keep the panel open and press Retry save. A failed save is shown above the transcript.
- It offers the wrong item
- The menu was not saved, or the item is still marked available.
- It gives the wrong hours
- The instructions are missing, stale or contradicted by another line.
- It will not confirm an order
- The browser test cannot confirm. Use a real call.
- The transfer does not happen
- There is no phone line in the browser test. Test transfers on a real call.
- No text arrives
- The browser test never sends. Test messaging on a real call.
- No recording appears
- The browser test does not record. On a real call, check phone company recording and storage.
Before you forward the main line
- Run one typed test and one voice test. Typing checks the answer; voice checks pace, interruptions and pronunciation.
- Open the saved test on Conversations and confirm it is labeled Try it live, not a phone call.
- Read the greeting out loud. If calls are recorded or transcribed, include the notice your jurisdiction requires.
- Check that hours, address, pickup rules and closure days are in the instructions, not only on a website.
- Decide what happens when a person is needed: a saved transfer number, a callback, or both.
- Keep the old line reachable for the first shift and have someone ready to take a transfer.
- Confirm an owner can open Billing and that the billing email is correct.
- Change one thing at a time. If you change the menu, the greeting and the instructions together, a failed test will not tell you which change caused it.
If a real call ends without a result, check the transcript before changing the instructions. Most failures are a missing fact or a capability that was never enabled, not a wording problem.