DocsReference
What the assistant can do
A plain list of what the assistant can actually do, what it needs switched on first, and what it will never do.
By the Callaroo team. Updated November 2026
The assistant is not a fixed script. It can only use the menu, hours and settings saved in your workspace. Every action it takes is written into the call record.
A call, step by step
The phone company hands the call to Callaroo and the assistant reads your settings for that workspace.
If the welcome is on, the caller hears your greeting. If a number is on the blocklist, the assistant is told not to take a new request from it. Filtering at the phone line depends on the phone company setup and is not verified in every workspace.
The assistant listens, answers in short turns, and asks one thing at a time.
When the caller wants something, it calls a tool, such as searching the menu, checking a slot or saving an order, instead of making the detail up.
It reads the order or booking back, and only confirms after the caller agrees.
It saves a transcript, a summary and the outcome of the call against your workspace.
If a person is needed, it transfers the live call or queues a callback before the call ends.
The tools it can use on a call
Swipe the diagram sideways to see the full flow.
Caller tools change or read records during a call. Staff tools work from the signed-in workspace. Web search is a separate option and is off by default.
There are 16 tools in the assistant today: 10 it can use with a caller and 6 that staff can use from the workspace. The list below is the real catalog, not a roadmap.
- Create an order
- create_order saves a draft with a snapshot of the menu
- Update an order
- update_order changes a draft using its current version
- Confirm an order
- confirm_order confirms only after the read back and the caller agrees
- Request a callback
- create_callback_request queues work for staff. It does not place a call
- Check availability
- check_availability offers only the slots your schedule returns
- Book a reservation
- book_appointment saves the booking after the caller agrees
- Cancel a reservation
- cancel_appointment cancels a booking the caller owns
- Send a text
- send_sms_confirmation runs only when an approved number is connected
- Transfer to staff
- transfer_to_staff dials the transfer number saved in your settings
- End the call
- end_call hangs up through the phone company, politely
The six staff tools read order history, read one order, count item sales, apply an allowed status change, queue a follow-up for an order, and add a number to the blocklist. They work from the signed-in staff workspace, so one business cannot read another business's orders.
There is one more capability outside that count: web search. It is off by default. When it is switched on, the assistant can look up current public information such as weather or a holiday, and the voice service runs the search. It is an outside search rather than a workspace action, so it is not one of the 16 local tools, and it cannot read your menu, orders or reservations.
The Tools page is the full catalog, with the setup each tool needs. Order tools covers menu search, drafts, changes and read-back confirmation; Staff order tools covers history, item counts, status changes, callbacks and blocking.
Dialing, transfers and messages
Callaroo answers your business number. It is an inbound assistant: it does not cold-call your customers and it does not run outbound campaigns. The only number it dials is the transfer destination you save in Agent settings.
- A transfer is a live hand-off. The assistant asks the phone company to dial your staff number and only reports “transferred” when the phone company acknowledges it. If the transfer fails, the call stays open; the assistant says it could not connect them and stops, and a caller can ask for a callback.
- A callback is a queue request, not a call. It appears in Callbacks so a person can ring the customer back.
- A text confirmation can be sent after the order or booking is accepted, and only when messaging is enabled, the number is approved by the phone company, and the message service is connected. Otherwise the assistant will not promise a text.
- If a caller opts out, the number is recorded and no further message is sent to it.
Languages
You can set a language hint in Agent settings, or leave it on automatic. There are 20 language choices plus automatic. The hint keeps the assistant in one language for the call instead of drifting between them.
- Automatic
- Follows the caller's language
- Arabic
- Egypt, Saudi Arabia and the UAE
- Bengali
- bn
- Chinese
- zh
- English
- The default
- French
- fr
- German
- de
- Hindi
- hi
- Indonesian
- id
- Italian
- it
- Japanese
- ja
- Korean
- ko
- Portuguese
- Brazil and Portugal
- Russian
- ru
- Spanish
- Mexico and Spain
- Turkish
- tr
- Vietnamese
- vi
A hint is a strong instruction, not a certified interpreter. If most of your callers speak one language, set it and test real calls in that language before you switch the number over.
What has to be switched on
- Ordering works from whatever menu you publish. An empty menu means nothing to offer.
- Reservations need the feature enabled and a weekly schedule with opening windows.
- Transfers need a saved transfer number; without one transfer is unavailable, and a caller can ask for a callback.
- Text messages need an approved, connected business number.
- Transfer and hang-up also depend on the phone connection, not on a setting alone.
- Web search is a separate switch. It is off by default, and it is not required for ordering, bookings or messages.
What it will not do
- Take a card payment or process card details.
- Invent hours, prices, addresses or pickup times it was not given.
- Call your customers on its own, or send marketing messages.
- Promise a table, a time or a refund it cannot see in your data.
- Act as an emergency line. Callers should hang up and call the emergency services.
Where to see it in the dashboard
- Agent
- Greeting, instructions, voice, language, transfer number
- Menu
- What the assistant is allowed to sell
- Orders and Reservations
- The work the calls produced
- Callbacks
- People waiting for a person to ring them
- Conversations
- Transcript, summary and outcome
- Usage
- Voice minutes behind the plan allowance
A worked example: a pickup order
The caller asks for two chicken wraps. The assistant gathers the item and any required choices.
The assistant asks for the pickup name before it saves the draft.
create_order saves a draft with a snapshot of the menu, so a later price change does not rewrite history.
The caller changes one item. update_order applies the change against the draft's current version rather than starting over.
The assistant reads the whole order back and asks the caller to confirm.
confirm_order marks it confirmed only after that agreement; an order above the review threshold is saved for staff instead.
If the caller asked for a text and messaging is approved, send_sms_confirmation can go out after the order or booking is accepted.
If something fails mid-call
- A failed transfer does not end the call. The assistant says plainly that it could not connect them and stops; if the caller asks, it can queue a callback.
- A failed text is never reported as sent. The call record shows what the phone company actually reported.
- An empty menu means nothing to offer. The assistant will not invent an item or a price.
- A reservation tool that is switched off is not offered to the assistant at all, so it cannot promise a table.
- A tool timeout does not end the call. The assistant should say the action failed and stop; it should not invent a different tool result.