The front door for an account that's already yours
For an owner, a manager, or someone working a shift, with an account already set up and something to sort out about it. Most of what belongs here doesn't look like a technical problem at all — a general question, an account detail that needs checking, or a sense that something's off without a specific symptom to point at yet.
READ BY A PERSON · NO RESPONSE-TIME FIGURE EXISTS, SO NONE IS PROMISED
Not every account issue belongs on this exact page, and it's worth checking before writing in, since one path is usually faster than the other:
| IF THIS IS WHAT'S GOING ON | START HERE |
|---|---|
| Something specific is going wrong right now — a call that dropped mid-order, a payment link stuck on a screen, a tablet behaving oddly | Troubleshooting |
| An article's steps didn't actually resolve it, or didn't match what's on screen | This page — name the article you tried |
| A general account question, or something without a specific symptom to point at yet | This page |
| Not sure this is even the right page — a sales question, a security report, something about billing | Back to Contact |
This page isn't a second troubleshooting index — it's the door for someone whose situation genuinely isn't shaped like a help article. An account question doesn't need to be dressed up as a technical symptom just to have somewhere to go: whether a second location can join the account, whether a setting changed on its own or someone changed it, what a specific role can and can't see. None of those has an article, because none is a repeatable fix. They're account questions, plainly, and this is where they go.
What speeds a request along is naming the specifics. “The payment link on table four's order wouldn't load” reaches a fix faster than “something's broken,” because it names the actual thing that's wrong rather than leaving the guesswork to whoever picks the message up next.
It doesn't change an order, issue a refund, or reverse a charge on its own — those run through the account itself, or through whichever part of the process actually governs them. A message here starts a conversation about a problem; it isn't a shortcut around the mechanism that resolves one. And it isn't where a diner takes a complaint about their own order — that goes to the restaurant directly, exactly as it did before any call was answered by an assistant. Where a customer's complaint is specifically about something Dohos itself did during a call, that narrower situation still starts on this same page, just from the customer's side of it.
Why not just call?
No phone support line exists anywhere on this site today — this written door, and the in-console option once signed in, are the real paths, not placeholders for a number that should exist but doesn't.
What if it's urgent?
Say so, directly, in the message — what's urgent, and why. Nothing about this form infers urgency from a subject line or a tone; naming it plainly is what actually works.
Do I need to have already tried something?
No — a message that hasn't tried anything still lands in front of a real person and gets a real reply. Naming what was tried, and what happened, just skips a round of back-and-forth.
Is this the same as billing?
No — this page is for anything about the account that isn't specifically about money. An invoice, a charge, or a payment method belongs at billing instead.
Does it matter who at the restaurant sends this?
Not for getting a reply — anyone reasonably connected to running the account can write in. What matters is that the message says enough about the actual situation to be useful once it's read.
A specific, live symptom — a dropped call, a stuck link, an odd tablet — usually resolves quicker through the help section: it walks the exact screens, step by step, honest failure branches included.