Help
If you already use Dohos and something needs an answer, start here. This section isn't the place that argues what Dohos is — it assumes an account that's running, a phone that's forwarded, and a real question about how something works or what to do when it doesn't. Nothing below is ranked by importance, and none of it is meant to be read start to finish.
Start from where you are, not from a label.
The three entries below sort by situation; the topics underneath sort by subject, for when you already know roughly what you're looking for.
Setting up for the first time
Between a Dohos account — opened self-serve or set up with a person — and a first real call: phone forwarding, the menu, a test call, and the staff tablet, in the order that makes each one easier. Reference material for those four tasks, not the fuller configuration flow.
START →ENTRY · SOMETHING'S WRONGSomething's wrong right now
A dropped call, a payment link that won't load, an order that looks doubled. Start from the symptom and go straight to the fix, instead of guessing which topic owns the moment first.
DIAGNOSE →ENTRY · BROWSINGBrowsing a topic you already know
Skip to the topics just below. Neither entry assumes you know which specific article you need — only which general area it lives in.
TOPICS ↓Calls
Anything about a call itself, while it's happening or right after — a drop and reconnect, a transfer that went sideways, a caller who was hard to understand. Not the order that came out of it.
OPEN →PLATE Nº 135Operations
The tools staff touch every shift: the wait time the assistant quotes, whether calls are actually arriving, and what the tablet's sync states mean.
OPEN →PLATE Nº 139Orders & menu
Whether an order's facts are right: its real status, what was said about an ingredient, 86'ing something mid-shift, a duplicate that might not be one.
OPEN →PLATE Nº 145Payments
A card, a payment link, a refund, or a dispute — a refund request and a chargeback move through genuinely different processes, kept distinct here.
OPEN →PLATE Nº 149Privacy & accessibility
What's kept from a call and for how long, a caller's rights over their own data, and reporting a barrier to using Dohos at all.
OPEN →A payment link that won't load and a duplicate-looking order can start with the same dropped connection — one belongs under Payments because the money is what's stuck, the other under Orders & menu because the order itself is in question. When a single moment touches more than one topic, each article says so and links to the other rather than covering the whole moment alone. Not sure which fits? Troubleshooting starts from what's happening instead.
Everything here is the same for every reader — signed in or not, one restaurant or another. It doesn't know anything about your own account: it can't surface a specific order, a specific call's transcript, or your invoice history, because none of that lives in a help article. A question about one particular order belongs in the operator console, where that record actually is; a question about one particular invoice belongs in billing settings. What lives here is the general explanation of how something works and what to do about it — never your own account's version of it.
There's also no live chat anywhere in this section. Every path from here is either a written article that answers the question directly, or the real support door, matched to what kind of problem it is. If an article's steps don't match what's on the screen in front of you, that's worth reporting through support rather than assumed to be a mistake on your end — the articles describe the real interface, and if one has drifted from it, Dohos wants to hear it.
No account yet? This section still answers honestly, but it isn't written for you first. Self-serve signup or requesting access is the actual next step for a restaurant that hasn't started — no article here is written to persuade rather than explain.
Every article ends with its own next step for exactly that case — and support is the honest end of the line for a question this section can't answer on its own. A real person reads it; no particular channel is promised to feel fastest, only to be the real one for the situation.