Questions
Not every call to a restaurant is trying to order something. Hours, an address, a price, whether a coupon is still good, where an order already placed actually is — each is a real reason someone calls, answered from what the restaurant has actually published, and stated plainly when Dohos genuinely can’t confirm something rather than guessed at.
One number. Eight real reasons
to call it.
Hours, address, prices, delivery area and fee, promotions, order status, asking for a manager, or a vendor calling about something else entirely. None of the eight is a lesser version of an order call, and none requires talking past an ordering flow to actually reach it.
The answer comes from the record,
never from a plausible guess.
An answer given over the phone reflects what’s true right now — not a guarantee that holds until an order built around it is actually accepted. The exact line Dohos uses for an availability question is quoted in full on allergy and ingredient questions; how the underlying record stays consistent everywhere it shows up is covered on the menu page.
A promotion’s real fields — and one missing on purpose
QUOTED BACK, NEVER AUTO-APPLIED — THERE’S NO FIELD FOR THAT HERE
A promotion gets described honestly and quoted back to whoever asks about it. Nothing about mentioning one changes an order’s price on its own — that would require the restaurant itself to actually apply it, which isn’t part of what a phone call does.
An estimate is labeled an estimate.
“Verified” is earned.
A status call gets one of two honestly different kinds of answer, and which kind a caller is actually getting is stated plainly rather than blurred together:
The restaurant reports the order as [accepted / preparing / ready / completed / canceled] as of [time]. Dohos has not independently observed preparation or delivery.
That’s a report of what the restaurant’s own system says, not an eyes-on confirmation of a kitchen. It’s an honest secondhand answer, stated as exactly that.
A caller who calls back a second time, past the point their order was expected, doesn’t just hear the same estimate repeated back word for word. That second call is treated differently on purpose — it creates a real, tracked alert for a manager, not just another pass through the same script. Not a bigger promise: a person, actually looking at it.
Not every non-order call
is a customer at all.
A supplier confirming a delivery, a vendor asking about an existing account, or a caller asking directly for a manager are each their own real reason to call — none of them gets funneled through ordering questions they were never asking in the first place. A caller asking for a manager is recognized as exactly that request, immediately. What actually happens once a person is needed is covered in full on escalation.
A request outside what’s actually configured, or anything genuinely unverifiable, doesn’t get answered as if it were handled anyway:
Dohos cannot verify that this service or action is available for the current restaurant, location, person, or request. It will stay off. [Verified safe alternative.]
The alternative offered there is a genuine one — a transfer, a callback, or the restaurant’s own verified contact — never a message that quietly goes nowhere. A request to change or cancel an order already placed lands here too, forwarded honestly as a request the restaurant still has to act on, never applied automatically as if it already happened.
None of the three becomes an order.
None is treated as a smaller call.
A caller asks about a coupon that turns out to be expired. Rather than a flat no, the answer names what’s actually true — that offer isn’t currently running — and mentions an active alternative the restaurant has configured, if one exists. The same caller then asks whether delivery reaches their street. That gets checked against the restaurant’s real delivery area and fee, the same check a delivery order itself would run. Finally, the caller asks to speak to a manager directly — and gets a genuine attempt at a person, covered in full on escalation, not a redirect back toward ordering something, and not a call logged as if nothing happened on it.
What people actually ask
What if it doesn't know the answer?
It says so, and offers the restaurant’s own verified way to reach someone instead of inventing something plausible-sounding to fill the gap.
Can I get a real person for a status check?
Yes — asking for a manager is one of the eight real reasons to call, and it’s handled the same honest way any other request for a person is, covered in full on escalation.
Does it know about a change I made five minutes ago?
Only once that change has actually been published. A change made but not yet published isn’t reflected on the next call — the answer always comes from the live, published record, never from whatever was most recently typed somewhere.
What if I already ordered and now have a different question?
That’s still one of the eight reasons this page covers — a status check, a delivery-area question, or a request to speak to someone doesn’t require starting a whole new order to get a real answer.
An answer only ever comes from what the restaurant has actually configured and published — if hours, a policy, or a promotion hasn’t been set up, the honest answer is that it can’t be confirmed, alongside the restaurant’s own verified alternative. Order status is reported from what the restaurant’s own system says, not independently observed. And a genuine account or payment dispute isn’t resolved by a status call — it routes to a person, the same way any request outside what’s configured does. See how a call actually gets to a person.
GO DEEPER
Calls
Answered as it rings, identified as AI out loud, and closed one of four honest ways.
OPEN →PLATE Nº 007Menu intelligence
Your menu with its real rules: components, modifiers, the 86 cascade, pronunciations.
OPEN →PLATE Nº 013Intelligence
Every call becomes data you own: demand, asked-and-missing, the closeout ledger.
OPEN →Get a straight answer on a real number.
Request access and hear what a real caller hears when they ask.