PLATE Nº 166
Search
Type a few words and matching pages filter in below, live. This searches the public site broadly — product, pricing, how it works, restaurants, trust, and more — by title and short description, nothing further.
↑ ↓ TO MOVE · ENTER TO OPEN
EVERY PUBLIC PAGE IS LISTED BELOW, GROUPED — TYPE TO NARROW IT.
PRODUCT — 13
ProductTwelve instruments, one machine — everything Dohos does between the ring and the closeout.CallsAnswered as it rings, identified as AI out loud, and closed one of four honest ways.VoiceA voice your regulars compliment — chosen once, engraved into every greeting.OrdersSizes, halves, swaps, allergies — the whole order, read back in full for a yes.Menu intelligenceYour menu with its real rules: components, modifiers, the 86 cascade, pronunciations.PaymentsPay at pickup tonight; the card moment is isolated by design. DRAFT — payment-capability copy pending the payments gate.QuestionsHours, parking, gluten-free — answered from what you actually published, never guessed.EscalationThe moment a boundary is crossed, a person is in it — manager on duty, then owner fallback.Staff viewThe tablet by the pass: queue, wait, 86 board — zero training course.Owner consoleThe dashboard: tonight at a glance, analytics, menu, team, closeout.IntelligenceEvery call becomes data you own: demand, asked-and-missing, the closeout ledger.LanguagesWhen language is uncertain it asks, plainly — and carries the call in what works.ReliabilityIt fails open: when something breaks, callers hear the truth and reach a person — never dead air.
HOW IT WORKS — 5
How it worksFrom forwarded number to first answered call — and what happens on every ring after.SetupForward your number, load your menu, place a test call. No new hardware.Call flowRing → greet → order → readback → ticket, with every branch drawn.Order flowHow an utterance becomes a priced, structured, kitchen-ready ticket.Escalation flowWhat reaches a human, when, and with how much context.
RESTAURANTS — 6
For restaurantsDohos fits the shape of your service — pick yours.IndependentOne room, one phone, forty guests — and every call still answered.PizzaHalves, toppings, deep-dish timing — the hardest menu logic there is, handled.Quick serviceVolume is the whole game — calls don't queue behind each other.Ghost kitchenNo dining room, all phone — make the line your storefront.Multi-locationBuilt for one location first — and honest about what group rollout means today.
USE CASES — 8
Use casesSeven nights where the phone decides the margin.After hoursOrders taken at 7 AM for tonight — while the room is dark.Peak hoursThe 6–9 PM mountain, climbed every night.Missed callsEvery ring answered — even the ones that used to hit voicemail.Staff shortageShort a host? The phone doesn't know.Order accuracyRead back, priced from your own menu, allergy-flagged — exactly right.Language barrierWhen language is uncertain, it asks — and the order still lands.Demand visibilityEvery ring is demand data — see the curve, staff the curve.
PRICING — 9
PricingPriced like a utility: a plan for your call volume, minutes metered honestly, no commission ever. Final rates are being set at the press.StarterFor the single room getting started.StandardThe busy independent's plan.BusyDinner-rush volume, every night.High volumeQSR and delivery-heavy lines.EnterpriseGroups, franchises, custom terms.EstimateYour numbers in, your monthly out — the honest math, labeled an estimate.How minutes workWhat a billable minute is, what rounds where, and what never bills.Pricing FAQCommitments, overages, porting, cancellation.
DEMO — 5
DemoHear it before you buy it — recorded specimens, voice samples, or a real call with our team.ScenariosRecorded calls, replayed as transcribed — corrections, questions, transfers, the hard ones.VoicesThe voice roster — compare the signatures, pick yours.Callback demoLeave a number; Dohos calls you and takes your order.Live demoA scheduled call with our team — your menu loaded, you dial, you hear it live.
COMPARE — 6
CompareDohos against everything else you could do about the phone — honestly, including where the alternative wins.vs. answering serviceMessage-takers vs. an order-taker that closes.vs. call centerPer-seat humans vs. software that treats every line the same.vs. hiringOne person can hold one phone at a time. The math never changes.vs. online orderingThe commission channel vs. the line you already own.vs. voicemailMost callers who reach voicemail don't leave one — they call the next place.
INTEGRATIONS — 1
GALLERY — 2
ABOUT — 4
CHANGELOG — 1
PRESS — 2
TRUST — 33
TrustAvailability, compliance, privacy, security — the vendor packet, in the open.Trust FAQThe questions your IT reviewer will ask.Vendor packetEverything procurement needs, in one document.AvailabilityContinuity posture, and what happens when things fail.Business continuityFallback design and degraded-mode behavior.Incident responseDetection, comms, and postmortems.SLAService-level commitments — method defined, numbers pending approval.SupportChannels and how requests are handled.ComplianceThe regulatory surface of a phone that talks.AccessibilityWCAG posture for console, station, and site.AI disclosureHow callers are told they're talking to an AI.CCPACalifornia privacy rights and how we honor them.GDPREU data protection posture.PCICardholder data scope. DRAFT — pending the payments gate.Call recording by stateOne- and two-party consent handling.TCPAOutbound calling rules and consent.PrivacyWhose data, kept how long, used for what.AI trainingWhat is and is not trained on — owner-controlled.Caller dataWhat a call leaves behind, and who can see it.Data residencyWhere transcripts and configuration live.DPAThe data processing agreement.RetentionOwner-set retention, defaults, and deletion.Rights requestsAccess and deletion requests, handled.SubprocessorsThe approved-subprocessor register — honest about its current state.SecurityEncryption, access, infrastructure, disclosure.Access controlRoles, least privilege, audit trails.EncryptionIn transit and at rest.InfrastructureWhere it runs and how it's isolated.LoggingWhat's logged, what's redacted.Payment securityPayment-data handling. DRAFT — pending the payments gate.PracticesSDLC, review, and testing posture.Vulnerability disclosureHow to report, what to expect.Security whitepaperThe whole posture, one document.
LEGAL — 17
LegalThe engraved fine print — every agreement, current and archived.Privacy policyPLATE Nº 101Terms of servicePLATE Nº 102Accessibility statementPLATE Nº 103Acceptable usePLATE Nº 104AI voice termsPLATE Nº 105Communications consentPLATE Nº 106CookiesPLATE Nº 107Data processing agreementPLATE Nº 108Master service agreementPLATE Nº 109Order & payment termsDRAFT — payment terms pending the payments gate.Privacy rightsPLATE Nº 111Service limitationsPLATE Nº 112Service level agreementPLATE Nº 113SubprocessorsPLATE Nº 114Vendor termsPLATE Nº 115ArchivePrior revisions of every document.
CONTACT — 7
HELP — 29
HelpGuides for owners and staff — setup, calls, orders, payments, privacy.Getting startedFrom signed-up to first answered call.Your first callPlace the test call and hear it yourself.ForwardingPoint your number at Dohos.Menu setupImport, review, pronounce, publish.Tablet setupThe station by the pass.TroubleshootingWhen something's off, start here.CallsWhat happens on the line, and what to do when it goes sideways.A caller who was hard to understandPLATE Nº 132Reconnecting after a dropped callPLATE Nº 133When a call needs a personPLATE Nº 134OperationsForwarding, wait times, and the tablet.Call forwarding issuesPLATE Nº 136Current wait timePLATE Nº 137Staff tablet issuesPLATE Nº 138Orders & menuTickets, 86s, statuses, and order messages.Allergy & ingredient questionsPLATE Nº 140Duplicate orders & chargesPLATE Nº 141Marking an item unavailablePLATE Nº 142Order status, explainedPLATE Nº 143Text messages about an orderPLATE Nº 144PaymentsHow paying works today, and what to do when it doesn't.A customer disputes a chargePLATE Nº 146Payment link problemsPLATE Nº 147Refunds & cancellationsPLATE Nº 148Privacy & accessibilityTranscripts, data requests, and access for every caller.Reporting an accessibility barrierPLATE Nº 150Data requestsPLATE Nº 151Recording & transcriptsPLATE Nº 152
RESOURCES — 9
ResourcesGuides and a working glossary — the research layer under the product.GuidesLong-form, sourced walkthroughs of the problems behind the phone.The cost of a missed callWhat an unanswered ring actually costs, sourced.The phone coverage auditMeasure your own line before you change it.Staffing & phone coverageWhy the phone loses to the room, every time.Menu data for voice orderingWhat a menu needs to be heard, not just read.The escalation policy checklistDeciding what reaches a person, before it has to.Serving every callerLanguage, accessibility, and the callers you can't hear yet.GlossaryThe working vocabulary — every term, defined once.
ACCESS — 2
SEARCH — 1
SITEMAP — 1
A PLAIN MATCH OVER TITLE AND DESCRIPTION — NOTHING TYPED HERE LEAVES THE BROWSER.
HOW IT ACTUALLY WORKS
A plain mechanism, described exactly.
A PLAIN SUBSTRING MATCHEvery keystroke checks whether the text typed appears in a page's title or short description. No relevance ranking, no typo correction, no synonyms.
NOTHING LEAVES THE BROWSERThe whole index is already loaded — there's no request carrying a query anywhere, and no log of what was searched.
STILL GROWINGThis index covers what's built and catalogued so far. A real page can exist on the site without being part of this list yet — reachable by other means, just not by a query here.
THE NEXT STEP
Open the line.
Tell us about your restaurant. We load your menu, you place a call, and you hear it answered yourself.