dohosGet started
PLATE Nº 117

Contact

Every message aimed at Dohos lands in front of one of a small number of real people — not one shared inbox sorted by whoever's free. This page is the map: what each door is actually for, written from what's behind it, not guessed from the label. Picking wrong isn't a setback; that's covered below.

SALESSUPPORTBILLINGSECURITYLEGALPRESSACCESSDEMOONE MESSAGE
PLATE Nº 117 · CONTACT
SIX WRITTEN DOORS
DOOR · SALES

Sales

A restaurant or group with real questions before anything gets written down — call volume, locations, timing — and a preference for talking them through with a person first.

BRING · ROUGH CALL VOLUME · LOCATION COUNT · TIMING — ESTIMATES ARE FINEOPEN →
DOOR · SUPPORT

Support

An account that already exists, and something to sort out that isn't a step-by-step help article: a general question, an odd setting, a situation without a clean symptom yet.

BRING · RESTAURANT + LOCATION · WHAT WAS ACTUALLY HAPPENING · ANY REFERENCEOPEN →
DOOR · BILLING

Billing

Money questions on a running account — an invoice, a payment method on file, a plan question. Not a second, informal support door for everything else.

BRING · RESTAURANT · THE INVOICE OR PERIOD · WHAT LOOKS OFFOPEN →
DOOR · SECURITY

Security

A vulnerability report or a security question, whether or not it rises to a formal disclosure — a real door that reaches a person, not a staffed security desk.

BRING · WHAT'S AFFECTED · STEPS TO REPRODUCE · WHAT IT EXPOSESOPEN →
DOOR · LEGAL

Legal

A contract under review, the data processing agreement, or something served through an actual legal channel — a notice, a preservation request, a subpoena.

BRING · WHAT ARRIVED · ANY MATTER REFERENCE OR DEADLINE YOU HAVEOPEN →
DOOR · PRESS

Press

A journalist or anyone writing about Dohos who needs an actual person — an interview, a fact-check, a specific question a static page can't answer.

BRING · THE QUESTION ITSELF · OUTLET · A REAL DEADLINE, IF THERE IS ONEOPEN →
READY INSTEAD OF ASKING?

Request access is the real intake once the questions are settled, and book a demo is for watching it work on your own menu first — neither is a form about the idea of one.

TRUE OF EVERY DOOR HERE

One message, one reader, no tiers.

A PERSON READS ITEvery door reaches an actual person — not a bot with a canned line, and not a queue that only ever generates a case number back.
NO DOOR OUTRANKS ANOTHERNone is more official, and none sits in a faster or slower tier. Picking support instead of sales doesn't move a message to the back of a longer line.
NO REPLY-TIME FIGURENo staffed hours and no turnaround figure has been set for any of them, so none is printed. Each door says this plainly rather than letting you assume a number that was never real.
THE MESSAGE STAYS WHOLEA submission becomes a real, individual message tied to the door it came through — never a shared thread with someone else's question mixed in.
PAIRS WORTH PAUSING ON
Sales or access?

The closest pair on this page. If the honest answer to “are we doing this” is still no — the real questions are fit, rollout shape, your own numbers — sales is built for that conversation. If the answer is yes, or close, access is faster than a conversation that would end in the same recommendation anyway.

Billing or support?

Both assume an account already exists; only one is about money. An invoice, a charge, a payment method, a plan question — billing. Everything else on the account — a setting behaving oddly, a login problem, a “how does this work” — support.

Security or legal?

A security report or question, formal or not, goes to security. A contract, a signed agreement, or anything arriving through an actual legal process goes to legal. Where one situation genuinely touches both, start with whichever feels primary — that's enough.

Where does press fit?

It's the one door for someone who isn't running a restaurant, evaluating Dohos, or using it — a journalist on a story, a fact-check, anyone writing about the company rather than considering it. That belongs at press, not folded into sales.

GUESSING WRONG ISN'T A PROBLEM

None of the routing above is a hard gate. A billing question sent through the support door still reaches Dohos, still gets read by someone who can handle it or point it at whoever should. Nothing about landing on the “wrong” page loses a message, drops it behind a penalty queue, or makes you start over. What determines how a message gets handled is what it says about the real situation — not which door happened to carry it. The door mostly exists to save a redirect.

Where a situation genuinely straddles two doors — a security concern that also touches an invoice, a sales question that's really a billing question in a different coat — start with whichever feels primary. Splitting one message into two submissions adds work on both sides without making either half move faster.

WHAT THAT LOOKS LIKE IN PRACTICE

A multi-location group writes in through support asking what a bigger rollout would involve — really a sales conversation that arrived through the closest-looking label. It still gets read by a person and pointed to sales with the original message and its context intact. What's lost is one short redirect — not the conversation, and none of the detail already written.