DocsStart here
Callaroo documentation
Set up the phone assistant, test it with real calls, and keep the menu, hours and team queue in good order.
By the Callaroo team. Updated November 2026
Callaroo answers your business phone. It is an AI phone assistant for restaurants and small service businesses. It can take a pickup order, book a table, leave a callback request or pass a call to your team. It saves the conversation so you can read what happened and fix the cause of a bad answer.
Start with the task
How a call moves through Callaroo
Swipe the diagram sideways to see the full flow.
The caller reaches the phone company, then the Callaroo number, then the assistant. The workspace keeps the order, booking, callback or message that the caller agreed to.
A worked example: a pickup order
- Caller“Can I get two chicken wraps for pickup at 6:30?”
- Assistant“Two chicken wraps for 6:30. What name should I put on the order?”
- Caller“Sam.”
- Assistant“Two chicken wraps, pickup at 6:30 for Sam. Is that right?”
- Caller“Yes.”
- Assistant“The order is confirmed. Your order number is 1042.”
This is an example, not a customer recording. The assistant uses the saved menu; it does not invent an item or price.
| Record | What it holds |
|---|---|
| Order 1042 | Two chicken wraps, pickup at 6:30, name Sam, status confirmed |
| Conversation | Transcript, summary, outcome and the voice minutes used |
| Menu snapshot | The item names and prices used when the order was created |
The read-back is the important part. The assistant confirms only after the caller agrees to the saved order. If the order is above the review threshold, it is saved for staff instead of being confirmed automatically.
What the assistant can do
What a call can leave behind
| Record | What it holds | Where to find it |
|---|---|---|
| Conversation | Transcript, summary, outcome and voice minutes | Conversations |
| Order | Items, name, pickup time, status and short code | Orders |
| Reservation | Date, time, party size and status | Reservations |
| Callback | Number, reason and status | Callbacks |
| Message | Thread and the last delivery state | Messages |
A call does not have to create every record. A question about opening hours can leave only a conversation. A failed transfer can leave a conversation and, if the caller asks, a callback request.
The tool catalog
A tool is a named action. The assistant cannot change an order, book a table or send a text by improvising; it has to call a tool, and the tool checks the workspace before it writes anything. There are 16 local tools today.
| Tool | Who | What it does |
|---|---|---|
| create_order | Caller | Save a draft order with a snapshot of the menu. |
| update_order | Caller | Change a draft using its current version. |
| confirm_order | Caller | Confirm only after the read-back and the caller agrees. |
| create_callback_request | Caller | Queue a callback for staff; it does not dial the customer. |
| check_availability | Caller | Offer only the reservation slots the saved schedule returns. |
| book_appointment | Caller | Save a booking after the caller agrees to the details. |
| cancel_appointment | Caller | Cancel a booking the caller owns. |
| send_sms_confirmation | Caller | Request a text only when messaging is approved and connected. |
| transfer_to_staff | Caller | Dial the staff number saved in Agent settings. |
| end_call | Caller | Hang up through the phone company, politely. |
| get_recent_orders | Staff | Read bounded order history for the signed-in workspace. |
| get_order_details | Staff | Read one order in the signed-in workspace. |
| count_item_sales | Staff | Count item sales from saved order records. |
| update_order_status | Staff | Apply an allowed status change, with confirmation where needed. |
| queue_customer_callback | Staff | Queue staff follow-up for an order; it does not place a call. |
| block_number | Staff | Add a number to the workspace blocklist after staff confirm. |
Web search is separate from the 16. It runs in the live call, is off by default, and cannot read your menu, orders or reservations. With web search, the catalog has 17 named tools: 11 caller-side (10 local caller tools plus web search) and 6 staff-side.
- Full tool catalogEvery tool, its prerequisites and what it will never do.
- Order toolsDrafts, changes, read-back confirmation and review.
- Staff toolsOrder history, item counts, status changes and callbacks.
- Choose when tools runTurn a tool on or off and edit its instruction.
What every workspace gets
- Phone number
- One number for each workspace
- Roles
- Owner, manager and staff
- Tools
- 16 local tools plus web search
- Records
- Calls, orders, bookings, callbacks and messages
- Billing
- Monthly in US dollars. One shop number is included.
Plans and included minutes
The bars show the included allowance. Plans are monthly in US dollars. New calls and outbound texts pause when the allowance is used; the next paid cycle restores it. No extra usage charge applies.
- Compare plans in detailHow to choose by call volume, menu size and team use.
- Understand usage and resetsWhat counts as a voice minute and when the allowance resets.
- See public pricingThe current monthly prices and what every plan includes.
How this site is organised
| Section | Use it when you want to |
|---|---|
| Start here | Set up a workspace and test it before a real call. |
| How-to | Finish a task or change a setting. |
| Reference | Look up a tool, a limit, a plan or a stored record. |
| Explanation | Understand how a call or a decision works. |
| Help | Work through a problem or contact support. |
A safe first path
Create the workspace and add the menu items callers ask for most.
Set the weekly hours and write the greeting and shop notes.
Read the default guardrails. Add one only if a rule is missing.
Review the tools. Leave web search off unless the shop has a clear reason to use it.
Test in the browser, then make one small real call before you forward the main line.
Read the saved conversation and change one thing at a time.
Terms used in these docs
| Term | What it means |
|---|---|
| Workspace | One business: its number, menu, hours, records and team. |
| Agent | The saved greeting, notes, guardrails, voice, language and tools that answer the phone. |
| Menu | The item names, prices and availability the assistant may offer. |
| Schedule | The weekly opening hours and reservation slots. |
| Tool | A named action the assistant can call, such as create_order or check_availability. |
| Conversation | The saved transcript, summary, outcome and voice minutes for one call. |
| Voice minute | Connected assistant time, rounded up once per call. Texts and dashboard visits are not voice minutes. |
| Review queue | Orders above the review threshold that staff must approve before they are confirmed. |
Common questions
| Question | Short answer |
|---|---|
| Does Callaroo call my customers? | No. It answers the business number. The only number it dials is the staff transfer destination. A callback is a queue request, not an automated call. |
| Can it take a card payment? | No. There is no payment tool. It can take the order; your team takes payment as usual. |
| What happens when the included minutes run out? | New calls and outbound texts pause until the next paid cycle. No extra usage charge applies. |
| Is every call recorded? | No. Recording depends on the phone company and workspace storage. The transcript is saved separately and is the reliable written record. |
| Can it handle a second location? | A second location with its own number, menu or hours needs its own workspace. |
| How many tools does it have? | 16 local tools: 10 caller tools and 6 staff tools. Web search is separate, off by default, and makes 17 named tools when it is counted. |
- Read the full FAQPlans, calls, records, billing and limits.
- Troubleshoot a problemStart with the symptom and work back to the cause.
Where to go next
- Set up the workspaceCreate the business, add the menu and save the agent.
- Test before you go liveUse the browser test, then one small real call.
- Read the call recordTranscript, summary, outcome and voice minutes.
- Review data handlingWhat is stored, who can read it and how long it stays.
- Understand recording and consentWhen audio exists and what the business must tell callers.
- See security and accessThe boundary between the browser, the server and the database.
- See the restaurant pageWatch the product demo and read a full restaurant example.
- Start with a testCreate an account, add your menu, and test the assistant in your browser before moving a number.
What it is not
- It is not a call centre. No person listens in and there is no queue of agents behind the assistant.
- It is not a card terminal. It has no payment tool and cannot take a card payment for food or a service.
- It is not a voicemail box. It tries to finish the order, booking or request.
- It is not a marketing tool. Confirmation texts are transactional and there are no campaigns.
- It is not an emergency line. A caller with an emergency should hang up and call the emergency services.
Reservations, messaging and transfers can be switched on for each business. If a control is missing, the workspace may not have that capability yet. The dashboard is the record of what is switched on.