Every page here answers one question: what happens after the phone rings.
This is the map, not a page of its own. It shows how the pages below actually fit together — what a caller experiences, what a restaurant’s own staff and owner see, and the one thing sitting underneath both. Start anywhere; each page finishes what it opens.
Not a smaller version of any page below.
A map of how they relate.
Every page linked here already exists in full, and none of them is summarized again on the way in. No mechanism gets explained twice — that happens once, on the page that owns it. What this page does instead is show how the pages relate: which claim each one proves, who it is actually written for, and which order makes sense depending on what is being asked.
If a paragraph here starts explaining how something actually works, that is the signal to follow the link rather than keep reading. Depth lives at the destinations, not on the way to them. Nothing below assumes the pages get read in order, and every one of them stands on its own without the others.
A small number of claims.
Each one proven somewhere specific.
Everything on this site rests on a small number of claims about how Dohos actually behaves, and each page below is where one of them gets worked through with the real mechanism behind it. Most carry one claim outright. A few carry a second in support, because the mechanism they describe genuinely touches both.
A page appearing more than once is not a sign the claims overlap loosely. Orders proves exception, not approval outright and separately carries a supporting role in your menu decides, because the same page genuinely does both jobs rather than being stretched to look more central than it is. Card data never reaching Dohos has exactly one page behind it, because that claim does not spread across the system the way the others do — it is a single structural fact about one moment in a call.
Read as a flat list they look interchangeable.
They are not evenly aimed.
Most of the pages below describe something a caller actually experiences during a call. A smaller set describes what a restaurant’s own staff and owner see instead, once the call is already over or already in progress. One sits underneath both, and it is drawn apart on purpose. A reader who already knows they are the one making the decision, not the one fielding the calls, can go straight to the second group without missing anything the first was written to answer.
THE MACHINE — WHAT A CALLER MOVES THROUGH
Calls
Answers first, in plain terms, then follows what is actually said toward a real, finished result.
OPEN →PLATE Nº 006Orders
Read back in full and checked against the real menu before anything reaches the kitchen.
OPEN →PLATE Nº 007Menu intelligence
One record behind every price and every answer, honest the moment something runs out.
OPEN →PLATE Nº 009Questions
Hours, an address, a price, a status check — answered from what the restaurant actually published.
OPEN →PLATE Nº 010Escalation
What happens when a call or an order needs a person's judgment instead of a guess.
OPEN →PLATE Nº 008Payments
What a caller actually pays with today, and why a card number never reaches Dohos.
OPEN →PLATE Nº 005Voice
A generated signature behind every voice a restaurant can pick for its own line.
OPEN →PLATE Nº 014Languages
Never assumed, always asked, and honest about what has actually been tested for a restaurant.
OPEN →THE INSTRUMENTS — WHAT THE RESTAURANT READS
Three real starting points.
Not a ranking, and not a sequence.
The order that makes sense depends on the question someone showed up with. None of the three below is the correct one — a reader curious about more than one reason is free to follow more than one.
The path for a reader whose real question is trust: what happens at the two hardest moments — a person being needed, and a card being read out loud — and what happens if the system itself runs into trouble.
The path for a reader focused on throughput: how an order actually gets checked and accepted, what sits underneath deciding what is sellable at all, and what the calls that never become orders are worth noticing for.
The shortest real path through any of this: how a call actually starts and ends, and where it lands once it is over. Everything else is detail underneath these two.
Arrives worried about cost.
Leaves without being told one.
Someone looking into Dohos mainly because an answering service already feels expensive lands here first, without a specific question yet beyond that worry. The trust path above is the one that actually matches what is bothering them — not throughput, not the mechanism itself, but whether handing calls to something automated is safe to do at all. They follow it, starting with escalation.
What that page gives them: the real ways a call or an order ends up in front of a person, and an honest account of what happens once it does. What it deliberately does not give them is a price, or a judgment about whether Dohos costs less than what they are paying now. It does not guess at that in either direction — it sends them onward. The actual number lives at pricing, never folded into a page built to explain when a person gets involved.
From there the same path continues as named — payments next, then reliability. By the time all three are read, the trust question they arrived with has a specific answer: what happens when a person is needed, what happens to a card number, and what happens if something breaks mid-call. None of the three ever told them what any of it costs. That is still one click away.
What this page sends you elsewhere for
Asked plainly, answered plainly.
Why isn't there just one big product page?
Because separate, specific pages beat one page vague enough to cover all of them. Each goes deep on exactly one mechanism; a single combined page would have to get either shallow or enormous to hold what the pages below actually say.
Do I have to read all of them?
No. The reading paths exist because most readers arrive with one real question, not general curiosity about the whole system. Pick the one that matches, and stop once it is answered.
Where's the pricing?
Not here, deliberately. Pricing is its own page. Nothing linked from here estimates a cost or gestures at one.
Is one of the three reading paths the right one?
No. They are three real starting points, not a ranked list, and none is treated as the preferred way in.
What if I only care about one thing?
Then start there. Every page below stands on its own, and none of them assumes you arrived through this one.
It does not teach a mechanism — every explanation, every script, every honest limit lives on the page that owns it, never summarized again here. It does not rank the pages by importance either: grouping them by who they are for is not the same as saying one matters more than another. And it does not require a reading order.
Start wherever your own question actually points.
Sign up and put the mechanism these pages describe on a number of your own, or request access and hear it run with a person alongside you.