DocsReference
Calls and transcripts
Every call leaves a written record, linked to whatever it created.
By the Callaroo team. Updated November 2026
Answering
The assistant answers your number at any hour. Your greeting, your instructions and your menu shape what it says; the rest comes from the tools connected to your workspace.
Conversations
- Each phone call appears as a conversation with the caller label, transcript, summary and outcome.
- Saved browser tests also appear here, labeled Try it live.
- A conversation is linked to the order, reservation or callback it created.
- Tool calls made during a phone call are stored with their request and response, so you can see what the assistant looked up.
- Use the transcript when an order is disputed or a caller says something different later.
Try it live chats
Saved Try it live tests appear in the same list, labeled Try it live. They are workspace tests, not phone calls: the record is text from the browser panel, and no audio is recorded.
- The title is the first thing you typed in the test.
- Only text turns and how long the line was open are stored.
- They do not add phone minutes, an extra-minute charge or an invoice line.
- Open Chat history in Caller practice to find a saved test by title and time.
- Workspace members can read them, like other conversations.
Recordings and transcript export
When recording is enabled at the phone company and workspace storage is configured, the audio is copied to private storage and the conversation shows a recording panel. Playback uses a short-lived link that the dashboard requests when you open the panel; it is not a public URL.
- Pending or processing means the audio is still being copied. It is not playable yet.
- Available means the recording can be played from the panel.
- Failed means storage did not complete; the phone company's own link may already have expired.
- Unavailable means there is no recording for that call, usually because recording was off at the phone company.
- If workspace storage is not configured, a phone company link may be shown instead, and it can expire sooner.
The transcript can be exported as a stored copy when it is available. The export is the conversation's record; it is not a public share link. A recording and a transcript are separate records. One can be missing while the other is intact.
Recording is a phone company setting plus workspace storage, not a dashboard toggle you can assume is on. Check the conversation for the status instead of relying on a recording always being there.
Transfers
If transfers are enabled and a destination number is saved, the assistant can pass the caller to your team. It only says the transfer is happening after the phone connection confirms it; otherwise it says it cannot connect them and stops, and a caller can ask for a callback.
Callbacks
A callback request records the reason, the caller's name, an optional preferred time and the verified number to call back. It queues work for staff. It does not dial the caller.
A worked example: a failed transfer
- Caller“I need to speak to someone about a large order.”
- Assistant“I can try the kitchen line. One moment.”
- Assistant“The line did not connect. I can take a callback request instead.”
- Caller“Yes. Ask them to call me after two.”
- Assistant“What name should I put on the callback?”
- Caller“Sam Rivera.”
- Assistant“A callback for Sam Rivera after 2 PM about a large order. I will use the number you are calling from. Is that right?”
- Caller“Yes.”
- Assistant“The request is saved for the team.”
This is an example, not a customer recording. The assistant does not claim a transfer happened until the phone connection confirms it.
The callback is the fallback, not a second attempt to transfer. The record is the work item staff see in Callbacks, with the reason, name, preferred time and verified number.
Blocked numbers
The blocklist saves each blocked number and the reason. The phone company is expected to stop a blocked caller before the assistant speaks, but the dashboard cannot verify that until the phone company is fully connected. Test a real call from a number you control before you rely on it. Blocking is for repeated nuisance calls, not ordinary customers, and you can remove a number at any time.
Call outcomes
- Order
- Items, name and pickup time saved
- Reservation
- A table booked or cancelled
- Callback
- Work queued for staff
- Transferred
- The caller was passed to your team
- No result
- The call ended without work attached
When a call goes wrong
Open Conversations and find the call by time or caller number.
Read the transcript before the summary. The summary is shorter and can hide the detail that matters.
Check whether the cause was data (a missing menu item, a closed reservation window) or a misunderstanding.
Fix the data first. Only then consider changing the instructions.
If the caller is waiting on an answer, call them back yourself; the assistant cannot reopen the call.
At close
- Clear callbacks that were handled so the queue stays honest.
- Review anything flagged for review before the order is collected.
- Note the one question callers asked most; that belongs in the instructions.