Getting started
For a restaurant that already has a Dohos account — opened self-serve or set up with a person — and is somewhere between that and answering a first real customer call. This page doesn't configure anything itself — it covers four specific tasks worth understanding on their own terms, in the order that actually makes sense, before a caller ever reaches the number.
Onboarding is where every setting actually gets entered — hours, fulfillment, payment rules, policies, and the rest. This page duplicates none of it. It exists because four of those steps involve a decision or a moment that benefits from more explanation than a form field has room for: a phone-routing choice with real consequences if misunderstood, a menu import that goes better with a little preparation, a structured test worth understanding before you run it, and a physical device that needs checking, not just configuring. Everything else onboarding asks for is answered directly on its own page — start at the onboarding overview, which tracks what's answered, what's blocking, and lets you jump to any step by name.
Read this page once, in order, before starting the four tasks. Each links out to its own article with the specific steps, the real field names, and what to do when something doesn't go as expected.
FORWARD THE NUMBER
Nothing else is testable until a call can actually reach Dohos. Working on the menu or the tablet first means testing against a system no caller can reach yet — any problem found could just as easily be a forwarding problem wearing a different costume.
GET THE MENU READY
A call that reaches Dohos still needs something real to order against. The structured test in the third task places an actual pickup order, and that only proves anything if the menu behind it is accurate — items priced, modifiers set, nothing missing that a caller would ask for.
RUN THE FIRST CALL
Once the two things it depends on are in place, this is the task that proves they worked — a fixed set of scenarios rather than an improvised call, so a failure points at something specific instead of a vague feeling that it “didn't sound right.”
SET UP THE TABLET
Deliberately last. Everything before it is about the system answering calls and producing orders correctly; the tablet is the separate, physical question of whether staff can see what was produced. Once the first call has produced a real test order, checking the tablet has something concrete to check against.
Read left to right, the throughline is dependency, not difficulty — each stop needs the one before it finished, not just attempted. It's fine to work in parallel where tasks genuinely don't depend on each other: gathering menu material while forwarding is still being confirmed wastes no time. And none of the four requires deep technical knowledge — just its own kind of access: the phone provider's account, whatever document the menu lives in, a few uninterrupted minutes, and the physical tablet itself. The person who manages the phone bill isn't necessarily the person who knows the menu best, and neither needs to be.
Joining partway through — someone else forwarded the number weeks ago, and you're only now on the tablet? The order is still worth knowing, not to redo finished work but to know what to trust: confirm the specific thing the current task depends on actually happened, rather than assuming it did because time has passed.
A later step in onboarding — activation — is the actual switch a restaurant flips to go live, and it stays unavailable until nothing required is still missing. Readiness isn't a clock, it's a state. What this page can tell you is what the four tasks look like when they're genuinely finished — the parts a checkbox alone can't prove:
None of this substitutes for whatever onboarding itself still lists as blocking — review & activate remains the authoritative list. This page only adds judgment to the four items on it that genuinely need a person's eyes rather than a saved field.
A setup task that won't behave the way its article describes is worth a message, not a guess — write to support — a real person reads it. Name the location, what you were doing, and any order or call reference you have.