No roster. One signed voice. The work itself.
Dohos does not publish employee names, titles, or headshots. What's public is narrower and more checkable: a real first-person account signed by the founder, and the work of running this product — described below as it actually happens.
A visitor evaluating a vendor expects a page like this to answer who am I actually dealing with. This page answers a more honest version of that question: what's real, said by a real person, in public, right now — rather than a grid of names and titles that would be easy to publish and impossible for an outside reader to verify. A name and a title on a page are easy to state and hard to check. A few hundred words written in a specific, checkable voice, about specific time spent working restaurant service, are harder to fake and easier to weigh — and that account exists, signed, at /why.
NO HEADCOUNT IS PUBLISHED, IN EITHER DIRECTION. WHAT'S PUBLISHED IS WHAT'S ATTRIBUTABLE.
The team, described as the work.
Every role below is anchored to a mechanism this site already claims — nothing here is a title invented for a grid. Some of these are the same person. No count is implied either way.
The founder — the one publicly attributable voice at the company, writing in first person about the restaurant floor this product is built from.
READ AT /WHY →Before your first test call, your menu — its real rules, prices, and pronunciations — is loaded and reviewed with you. That's a person's work, done before the line opens.
SEE SETUP →Signup is self-serve when you want it. When you'd rather a person drove the setup instead, every access request is read and answered by one — that's the mechanism on that door, not a courtesy line.
REQUEST ACCESS →Support, billing, security, legal, press — each channel routes to a person who replies, not to a queue that absorbs.
THE CHANNELS →When something breaks, the account of it is written by the people actually handling it, published on the status record from day one — never generated by a probe, never quietly skipped.
THE RECORD →Where the product's sense of a call comes from.
Direct experience inside a family restaurant — not a lab, and not a general theory of phone calls. Real restaurant calls are not clean exchanges:
It's worth being precise about what that experience doesn't imply. A restaurant owner already understands labor, margins, and customer behavior — often better than any software vendor does. The claim here is narrower: direct time on one restaurant's floor, on the specific problem this product exists to address — an unanswered phone during the busiest hour. How decisions get made from that starting point is written down, with proofs, at how the company operates.
The fastest way to meet the team is on a call — which is fitting.
FIG — THE INVITATION, STANDING