Calls
A restaurant’s line, picked up by software that identifies itself before it asks for anything, listens for what a caller actually wants instead of routing through a menu of numbered options, and closes every call in one of a small number of honest, specific ways — never a guess dressed up as a result.
Before it can take an order,
it says what’s answering the phone.
Every call opens with the same disclosure, and it comes before an order is asked for and before a question gets answered. The restaurant only gets named once its number is actually verified — never a guess at which location picked up — and the fact that this is software, not a person, is stated plainly, unprompted.
That one line does three separate jobs, not one — and none of the four callouts above is conditional on the caller speaking up first. When the restaurant genuinely can’t be verified, the call says so and stops, rather than guessing at a place it was never confirmed to be:
Hi, you’ve reached Dohos’s AI ordering assistant. I can’t verify which restaurant this call is for, so I won’t take an order yet. Please check the number or use the restaurant’s verified contact information.
That isn’t a hypothetical listed for completeness. It’s the same fail-closed instinct that runs through everything else on this page: when something can’t be confirmed, the honest response is to say so, not to continue on a best guess.
No phone tree. No digits to press.
There’s no menu of numbered options to sit through, and no phone tree to guess a way down. What a caller says first is what moves the call forward — toward an order, toward a question, or toward a person — because the system is listening for what’s actually being asked rather than waiting for a digit to be pressed.
A caller who opens with “is the kitchen still open” gets moved toward an answer. A caller who opens with “I’d like to order” gets moved toward the menu. Neither has to say a specific keyword the system was listening for — ordinary language is enough, and the routing happens on what was actually meant, not on a rigid phrase match.
“How did it go” and “what did it
accomplish” are tracked apart.
They sound like one question. They’re tracked as two separate ones, on purpose — a caller can be told the truth about how a call is unfolding without that implying anything about what it will have accomplished by the end.
Every call moves through the same two stages first — it’s initiated, then it’s active — before ending in one of a small set of ways: it completes, it’s transferred, it fails, or it’s abandoned. None of those endings is treated as more real than another. A transferred call isn’t a failed call that got lucky; it’s its own distinct ending, tracked as such from the moment it happens.
What a call actually accomplished
Separate from where a call technically ended up, there’s the question of what it was actually for. A finished call accomplishes one of four things — and those four are the entire list. A call is never quietly logged as something vaguer than one of them, and no branch below is drawn larger than another: an answered question isn’t a smaller box than an order. It’s a different one, not a lesser one.
FOUR OUTCOMES, EQUAL WEIGHT · SEE ORDERS AND QUESTIONS FOR THE FIRST TWO · ESCALATION IS THE MECHANISM BEHIND THE OTHER TWO — NOT A FIFTH OUTCOME
A dropped call doesn’t throw away
what was already said.
If the draft items are still verifiably intact, the call can pick back up from exactly where it left off instead of starting the conversation over from nothing:
We were briefly disconnected. This is still Dohos’s AI ordering assistant for [verified restaurant spoken name]. I have your draft items through [safe non-sensitive summary]. Would you like me to review them before we continue?
If the earlier context can’t be safely confirmed instead, the call doesn’t pretend otherwise. It reviews from the beginning rather than assume a dropped connection left everything exactly where it was.
And at any point in a call — not only once a script has run its course, and not only once an order is already underway — “human help” works as a request:
You can say “human help” at any time. I’ll try the available restaurant or support handoff.
What that handoff actually involves — who gets notified, what happens if nobody responds, and how the caller is told either way — is covered in full on escalation, including the honest current limits of what “trying” means.
A text record by default.
Audio only by a separate choice.
These are two different mechanisms, never one setting wearing two names — and this page keeps them apart the way the system does.
The text record
A finished call keeps a text transcript by default. That isn’t something a restaurant switches on — it’s a standard part of how a call is handled.
- Access is limited on the restaurant’s own side — role-gated, not open to anyone.
- How long it’s kept follows the account’s configured retention window.
- What staff actually see from a finished call is covered on console.
Audio recording
Raw audio is the separate, opposite case: it stays off unless a restaurant has deliberately turned it on for a location — and even then, Dohos asks before it starts.
- Enabled per location, by the restaurant, never a Dohos default.
- Disclosed on the call itself, with a direct question before anything records.
- Saying no doesn’t end the call — it continues through the described alternative.
Dohos would like to record this call for [approved specific purpose]. The recording would be available to [approved recipient categories], kept for [approved period or clear criterion], and handled under [approved privacy reference]. Recording is optional. If you say no, you can continue through [truthful nonrecorded option]. May Dohos record this call?
A caller the restaurant has blocked
Any staff member can block a caller from a restaurant’s line. What actually gets stored isn’t the phone number itself — it’s a fixed-length digest derived from it, paired with the number’s last four digits, so a restaurant can recognize the block again without anyone holding the raw number on file anywhere.
The asymmetry is deliberate: any staff member can add a block, but only a manager or owner can remove one, or see the list of who’s been blocked. An unfamiliar or withheld number is never blocked automatically — blocking is a decision a restaurant’s own staff makes, one caller at a time, never a default judgment the system applies on its own.
The disclosure doesn’t get cut short
to answer faster.
A caller dials a restaurant’s number. It resolves to a single verified location, and the opening line plays in full: what’s answering, which restaurant, the human-help option named up front. Partway through that line — before the human-help sentence has finished — the caller cuts in with a menu question, asking whether a specific topping is available tonight. The identity statement and the human-help sentence finish playing before anything else happens, because what the call is has to be established before what it’s about does.
Once the opening has actually finished, the question routes the way a question does — away from an order-taking path and toward an answer sourced from what the restaurant has actually published, the same territory covered in full on questions. If the caller follows that answer with an actual order a moment later, the call simply continues into that path from wherever the conversation already is. Answering the question first doesn’t force anything to restart.
What people actually ask
Can I still just talk to someone?
Yes, at any point, just by asking. What that handoff can and can’t promise today is stated plainly rather than assumed — see escalation.
What if it picks up for the wrong location?
It doesn’t proceed on a guess. A call that can’t be matched to exactly one verified location says so and stops, rather than taking an order for a place it isn’t actually confident about.
Does it record everything?
No. A text record of a finished call is kept by default; raw audio is the separate, off-by-default case that only runs once a restaurant has turned it on for a location and the caller has been asked directly.
What happens if a scam caller keeps calling?
A restaurant’s own staff can block the number after one call, and every call from it afterward is declined before it’s ever answered — not silently, and not as an automatic judgment the system makes on its own.
Not every call is an order, and that isn’t treated as a shortfall — an answered question, a transfer, and a callback are each a real, finished result on their own terms. A live transfer isn’t promised on every call: it’s only offered when a person is actually available to take it, otherwise the caller gets a verified way to reach the restaurant instead. A language is only ever used once every step of a call in it has been tested — see languages. And whether audio gets recorded at all is a restaurant’s own configuration, disclosed honestly when it applies — never a default Dohos decides on a restaurant’s behalf.
GO DEEPER
Orders
Sizes, halves, swaps, allergies — the whole order, read back in full for a yes.
OPEN →PLATE Nº 010Escalation
The moment a boundary is crossed, a person is in it — manager on duty, then owner fallback.
OPEN →PLATE Nº 018Call flow
Ring → greet → order → readback → ticket, with every branch drawn.
OPEN →Hear the opening line on a number of your own.
Request access and hear the disclosure exactly as a caller hears it — before anything is asked of them.