DocsHow-to
Review calls and fix the cause
Most bad calls come from missing data or a setting that was never enabled, not from a bad sentence.
By the Callaroo team. Updated November 2026
A call can sound polite and still fail. The caller may have asked for an item you do not sell, a time you are closed or a person who was not available. Read the transcript before the summary, then fix the cause in the dashboard.
Swipe the diagram sideways to see the full flow.
The assistant reads saved settings, menu and schedule. The conversation connects those facts to the work your team sees.
Pick a small sample
- Choose one busy day and read three calls end to end.
- Include one call that created an order or booking.
- Include one call that ended without work.
- Include one call where the caller asked for a person.
Read in this order
Read the transcript first. The summary is shorter and can hide the detail that matters.
Check what the caller asked for and what the assistant answered.
Check the menu, schedule or setting behind the answer.
Decide whether the cause was missing data, a disabled capability or unclear wording.
Change one thing, save it and test it again.
A summary is a short description, not evidence. The transcript is the record of what was said.
Common causes
| What you heard | What to check first |
|---|---|
| It offered the wrong item | Is the item saved and available on Menu? |
| It quoted an old price | Is the price current? Existing orders keep their saved price. |
| It said the shop was open | Does the saved schedule match the real hours? |
| It could not book a table | Is Reservations enabled, and is the date inside the booking window? |
| It could not transfer | Is a transfer number saved, and can the line take a live transfer? |
| It did not send a text | Is messaging enabled, approved and connected? |
| It missed a note | Was the note said clearly, and is the item name correct? |
Write the fix down
- Add the missing fact to the menu or shop notes.
- Use a guardrail for a rule that must apply to every call.
- Use a tool rule for when a tool may run, not for a price or an hour.
- Remove old notes that contradict the new fact.
- Tell staff what changed so they do not keep giving the old answer.
Do not change the menu, the greeting and the instructions on the same day. If the next test fails, you will not know which change caused it.