Your request is in.
It reached Dohos. It wasn't dropped, and it isn't sitting behind a form that quietly failed without saying so — it's now on file as its own request, tied to the restaurant, its city, and the contact just given. There's nothing else to do on this screen. What happens next — genuinely next — is described below.
On file, as its own record.
No confirmation code to copy down, no second form further down the page, no account to sign into. Reaching this page is itself the confirmation.
A real sequence, not an instant switch.
The request just submitted becomes a single, specific record — its own identity, tied to the restaurant, its city, and the contact just given, not folded into a generic inbox. It starts as a fresh, unlooked-at entry, gets picked up and read by an actual person, and settles into one of two honest outcomes: accepted, with a real setup conversation to follow, or genuinely not the right fit.
That second outcome is worth stating plainly. A review that could only ever end one way wouldn't be a real review. That's not a hidden catch — it's the plain shape of what a genuinely personal process looks like: an actual person decided, either way.
Exactly what the form asked for — nothing added, nothing inferred to fill a blank.
Who to contact, and how: name, email, and a phone number. Which restaurant this is for, and which city it's in. Which role the person submitting it holds. If a rough sense of calls per day was given, that's on file too, marked plainly as a rough figure — and the same goes for whichever real situations were picked under what matters most. Either was optional, and if left blank, nothing was filled in to replace it. None of this is echoed back on this screen; it's attached to the record for the person reviewing it. What Dohos does with information more generally is its own fuller subject, covered in full at privacy.
Not just a waiting room.
None of the three below depends on hearing back first.
This page could offer a reassuring turnaround figure, the way a lot of confirmation pages do. It won't, because no such figure is real — nothing about how long a review takes has been measured, committed to, or published anywhere, for this or any other request. Writing a number here that isn't real would be a worse answer than the honest one.
That's not an apology, and it isn't a gap waiting on a better answer later. A person looks at each request individually rather than running it through a scheduled batch with a published turnaround — no queue position or countdown exists to hand back even if this page wanted to give one.
The same discipline that keeps this site from publishing an uptime number it can't back up applies here, on its own front door, for the same reason: a number with nothing real behind it is worse than none at all.
Did this actually go through?
Yes. Reaching this page is itself the confirmation — there’s no separate email required to make a submission real.
What if something I entered was wrong?
Get in touch through contact support rather than submitting the form a second time. A second submission doesn’t correct the first — it creates a separate request tied to the same restaurant, which makes an accurate review harder, not easier.
Who do I ask if I don't hear anything?
Contact support, the same channel as above. No clock is running here to check a request against, so there’s no wrong time to ask.
Evaluating a second location already?
A different restaurant is a genuinely separate conversation, not an edit to this one — start a request for it on its own terms.