One call runs the whole spine. Everything else branches from inside it — or comes before it.
Call flow, order flow, escalation flow, and setup each explain themselves in full on their own page. None of them states how they relate — which one carries the whole call, which one runs only inside part of it, which one can start from more than one place, and which one has to already be true before any of this runs at all. That’s this page’s job.
Not four parallel articles. A spine, a branch, a convergence — and a prior condition.
Read as a flat list, these look like separate pages about separate topics, roughly equal in size and weight. They aren’t parallel, and treating them that way is the fastest way to misread how any one of them fits against the others.
Knowing this before opening any of the four changes what to expect once you click through. Order flow stands on its own — but it makes more sense once it’s clear the branch it describes only exists because call flow already routed a caller there. The reverse is also true: nothing about call flow requires reading order flow first, because it only gestures toward that branch rather than depending on it.
Not a last step. A separate, prior condition.
It would be easy to read setup as the end of the sequence, the way a checklist finishes with “go live.” That’s not the relationship. Setup doesn’t happen during a call, and it doesn’t happen after one — it happens once, on the restaurant’s own side, before any of the other three pages can run for that restaurant’s line at all.
A call can’t fork toward an order, and an order can’t cross into escalation, until the settings that make each of those possible have been decided somewhere. That’s why it’s drawn apart on the map above rather than tacked onto the end — it isn’t a smaller or later version of the other three. It’s a separate condition all three quietly depend on every time any of them runs. Setup covers its real shape in full.
Before a restaurant works through setup, its line does one thing: it rings. No fork, no check against a menu, no record kept afterward — a phone connecting a caller to whoever happens to pick up, the same way it always has. After setup, the same line runs everything the other three pages describe. Nothing about the ring itself is different. What changes is everything that happens once it’s answered.
Start from your question, not from the list.
The four don’t need to be read in the order they’re listed anywhere. What matters is the question that brought you here. None of these is a required starting point — each answers a specific question completely on its own, whether or not you ever open the other three.
One reader, following the system rather than the list
Someone arrives with no specific question — just curious what Dohos actually does once someone calls in. Their path through these pages isn’t the listed order. It’s this:
CALL FLOW, FIRST
The default entry with no particular question. It walks the one shared opening every call has, and the real, honest ways a call can go from there.
A BRANCH CATCHES THEIR EYE
Partway through, one fork stands out — what happens when a caller asks for a person outright. They follow the link into escalation flow from inside that section instead of finishing call flow first. It answers that exact question in full: where a request like that goes, and what the restaurant’s side of it looks like once it arrives.
SETUP, READ LAST
Having seen the call and the handoff, the question changes — from what Dohos does to whether they’d want it on their own line. That’s setup’s page. By the time they reach it, they already recognize why its settings matter — the response window they just read about is exactly the kind of thing that page describes getting decided, once, on the restaurant’s own side.
Three pages, followed in the order this one reader actually needed them — not the order they happen to be listed in. What started as one open-ended question ends with a specific reason to sign up or request access, not just more reading.
Asked plainly, answered plainly.
Do these always happen in this order?
No. Only order flow is fixed inside another page’s sequence. Escalation flow can interrupt either of the first two at more than one point, and setup happens separately, on its own, before any of this runs for a given restaurant at all.
Is setup part of every call?
No. It happens once, on the restaurant’s own side, before a call ever reaches any of the other three pages — never during one, and never repeated for a call already underway.
Why isn't payments its own flow here?
Because it isn’t a separate sequence. It’s a stage inside order flow, not a parallel path a call can take on its own — see order flow for exactly where it sits.
Where's the actual detail?
On each flow’s own page first, and from there on the specific product page that owns the underlying mechanism in full. This page only states how the four relate — the real mechanics live one click further in, never summarized twice.
What if I've already read one of the product pages?
Nothing here assumes you arrive cold. If you’ve read a product page, you’ll recognize its mechanism the moment a flow references it — this page adds the sequence on top of what’s already known.
Of the real ways a call can end, only one ever crosses into order flow at all. The others are complete, finished results on their own terms — none of them touches it.
Each page owns its own sequence and its honest limits. And no duration is put on any of it here, including setup — that page states its real shape without a clock, and this one doesn’t borrow a figure from elsewhere to fill the gap.
What’s fixed is the topology: which page nests where, which converges, which comes first. What varies, restaurant to restaurant, is what’s configured inside that shape — a given order’s threshold, who’s on duty to receive a request when one arrives.
The four, in full — each on its own plate.
Setup
Forward your number, load your menu, place a test call. No new hardware.
OPEN →PLATE Nº 018Call flow
Ring → greet → order → readback → ticket, with every branch drawn.
OPEN →PLATE Nº 019Order flow
How an utterance becomes a priced, structured, kitchen-ready ticket.
OPEN →PLATE Nº 020Escalation flow
What reaches a human, when, and with how much context.
OPEN →The mechanics beneath every one of them live on product — each instrument owning its own detail in full, never summarized twice.
See the real sequence.
Sign up and watch your own line run this — call flow through to whatever it actually resolves into — or request access and watch it with a person first.