Six ways a call can end, and none of them is a score
Every call ends in one of six outcomes: verified, captured, handed off, escalated, refused or failed. Why they are kinds rather than degrees, and why presenting them on a green-to-red ramp is the mistake.
Most call reporting grades a call: good, partial, poor. That framing is wrong in a way that costs you money, because a refusal and a failure look adjacent on a scale and are opposites in practice — one is the system working and the other is a fault.
Balaay is an AI receptionist for businesses that run on calls. Balaay is an AI receptionist for businesses that run on calls. It learns a business from that business’s own website, answers its phone, holds the conversation, takes the next step where it can, and records what it actually did.
The six
Different kinds of outcome, not degrees of success.
- Verified — done, and read back from the source. The only outcome that may be spoken to a caller as complete.
- Captured — the request was recorded accurately and no external action was performed. Correct behaviour, not a half-booking.
- Handed off — a structured item was created for a person, with enough in it to act on.
- Escalated — the urgency path was triggered and the booking path was suppressed.
- Refused — the receptionist declined to assert or do something it could not stand behind. This is the product working.
- Failed — a genuine fault, reported to the caller rather than disguised.
Why a scale is the wrong shape
On a green-to-red ramp, "refused" sits near "failed" and an owner learns to treat both as noise. But a refusal is the single most valuable event in the log: it is the moment the system chose not to invent something. Burying it next to faults trains people to stop reading, and then they miss the faults too.
The seventh state, which is not an outcome
An ambiguous response — a timeout, a connection dropped mid-write — is deliberately not one of the six. It routes to a person instead. Calling it failed invites a retry that double-books; calling it done tells a caller about something that may not exist.
Reading a week of calls without reading a week of calls
The point of a taxonomy is that it lets you skip most of the log. A week of clean verified bookings needs no attention. What is worth ten minutes is every refusal — each one is a question your business could answer and your website does not — and every escalation, because that is a customer who needed a person and you can check whether they got one. Failures matter too but they are usually already known. Sorting by kind rather than by time is what makes that triage possible.
What this page will not claim
These outcomes describe what Balaay did, not whether the customer was satisfied. Nothing here measures how the call felt to the person on the other end.
Related pages
- What is an AI receptionist?
- What an AI receptionist does
- AI phone receptionist
- AI answering service
- After-hours answering
- AI appointment booking
- How this category is priced
- vs an answering service
- vs a human receptionist
- vs voicemail
- vs a virtual receptionist
- AI front desk
- Call Truth
- Action receipts
- Verified actions
- False completion
- Business Twin
- Website to receptionist
- Pre-flight testing
- Reliability
- All industries
- Pricing
Explore Balaay
Hear it answer before you decide anything
The live voice demo is the same receptionist your callers would reach.
Book a demoIn summary
Six ways a call can end, and none of them is a score — Every call ends in one of six outcomes: verified, captured, handed off, escalated, refused or failed. Why they are kinds rather than degrees, and why presenting them on a green-to-red ramp is the mistake. Balaay is an AI receptionist for businesses that run on calls. It learns the business from its website, answers the phone, takes the next step, and shows what it did.
Loading interactive experience…