Nothing external connects to Dohos today.
Dohos is the phone line and the console — the system that answers a call, and the screens a restaurant’s own staff use to see what came in. It does not connect to a point-of-sale system, hold a reservation, sync a calendar, or move money through a payment processor. That is a real limit, not a simplification, and it is worth being specific about exactly where the boundary sits.
A manual step, described as a manual step.
No system on this page is named, because none of them is connected — naming one would imply a relationship that does not exist in either direction. What is described instead is what genuinely happens, restaurant-side, once a call becomes an order, stated by function rather than by product.
The manual step is also not purely a downside. A silent, automatic sync between two systems that were never designed together is exactly the kind of thing that quietly drifts out of agreement — a price changed on one side and not the other, an item marked unavailable in one place but not the other. A manual step means a real person’s attention sits between the two. That is a genuine tradeoff, not a missing feature stated politely.
Every rung states a fact,
not a status.
No rung below carries a label about how far along something is, because that would describe an intention rather than a capability. Each states what is true of the product as it exists.
One hand-off in.
One built-in path out.
Forwarding is the hand-off.
Calls reach Dohos because the restaurant sets forwarding on its own line, at its own carrier. That works from a carrier without anything being built for that carrier specifically — it is ordinary call forwarding, not a connection between two systems. Dohos has no visibility into a carrier account and can’t set it from its side, and no carrier-by-carrier reference of dial codes is published here, because a wrong code would be worse than none. See forwarding.
The station ticket, and the record behind it.
An accepted order lands on the station screen directly. The text transcript of a completed call and the day’s closeout ledger live in the console, role-gated and retention-bound. All of that is reachable where it sits — none of it is pushed into another system, and this page does not claim a delivery mechanism it does not have.
THOSE ARE THE ONLY TWO PLACES ANYTHING CROSSES A BOUNDARY TODAY: A CALL ARRIVING BY ORDINARY FORWARDING, AND A PERSON READING A SCREEN. NOTHING ELSE MOVES BETWEEN DOHOS AND ANY OTHER SYSTEM, IN EITHER DIRECTION.
Nothing about the manual step
happens silently.
THE CALLER ASKS FOR A PICKUP ORDER
Dohos reads the order back in full, confirms it, and sends the request to the restaurant.
A STAFF MEMBER REVIEWS AND ACCEPTS IT
On the console or the staff tablet — the same acceptance step every order goes through, no matter how it arrived. Once accepted, it appears on the station screen exactly as confirmed.
AND THEN A PERSON KEYS IT IN
If the restaurant rings sales through a system at the counter, a staff member enters the accepted order into it directly — the same short step they were already taking for a phone order before Dohos was part of the call. A person’s judgment sits between what a caller asked for and what gets rung up, rather than an unsupervised sync between two systems that might quietly disagree.
PAYMENT SETTLES THE WAY IT ALWAYS HAS
The customer pays in cash on pickup, reconciled directly between the restaurant and its own customer. Dohos is not a party to that payment at any point.
None of this is a connection waiting to be quietly wired up without anyone being told. It is a deliberate boundary, and the system is built to say so plainly the moment a call reaches a point where that boundary matters — rather than guess, improvise a workaround, or fail in a way nobody would notice:
A verified secure Restaurant payment path is not available. Dohos will not take card or bank details by voice, text, or an unverified form. The order/payment remains [verified state]. Use [verified Restaurant alternative] or try again later.
That is not a hypothetical line written for this page. It is the response built into the system for exactly this situation, and it applies the same discipline everywhere else a caller reaches for something Dohos doesn’t connect to: state plainly what isn’t available, point to a real alternative, and never improvise a workaround that would misrepresent what is possible.
Asked plainly, answered plainly.
Will this replace my point-of-sale system?
No. Orders still reach that system the way described above — reviewed and entered by a person, not synced automatically. Nothing about using Dohos requires replacing what a restaurant already rings sales through.
Can it take card payments?
Not today. The isolation mechanism that keeps card data away from Dohos entirely holds regardless — a caller’s card number is never something the system asks for, whether or not a processor is ever connected.
Does my menu need to be entered twice?
Today, yes. A restaurant’s menu is set up directly with Dohos so a caller hears accurate items, prices, and availability, and that is a separate step from however the same menu is already set up wherever sales get rung in. There is no automatic sync between the two — the same honest limit described above for point of sale, applied to menu data rather than a finished order.
What if I use a system that isn't listed here at all?
Nothing is listed here at all, deliberately. Name what you actually use when you get in touch — there is no promised timeline attached to a request like that, but it is a real request that reaches a real person.
A specific system name, mentioned once, tells a more useful story than six honest categories can on their own. It is information Dohos genuinely doesn’t have otherwise about what a restaurant considering the product already relies on day to day.
Saying so commits nothing on either side, and it isn’t a signal that something gets built to order. There is no queue with a published response time behind it.
Start from what's actually real today.
Sign up or request access and run the phone line as it exists — one forwarded number in, one checked ticket out, and a person still deciding what gets rung up.