dohosGet started
PLATE Nº 144

Text messages about an order

The direct, honest answer up front: today, an order's status is confirmed and communicated on the call itself — spoken, in the moment — not through a follow-up text message. Everything about a caller's order is already given to them, out loud, before they hang up.

PLATE Nº 144 · TEXT MESSAGES ABOUT AN ORDER

This page explains why that's actually a complete answer rather than a gap, what a compliance disclosure some callers may notice is actually for, and exactly what to say when this question comes up. It applies to any restaurant taking phone orders through Dohos, regardless of size, location, or how long it's been live — there's no setting, plan, or configuration anywhere that changes the answer here. Every order, from every caller, gets the same spoken confirmation described below, and none gets a follow-up text today.

01Why the call itself is the complete record

Every order Dohos takes goes through a full spoken review before anything is submitted — the exact items, the fulfillment details, the subtotal, taxes, fees, and total, read back in full and confirmed before the request goes anywhere. Once the restaurant accepts it, that acceptance is stated back to the caller too, along with the pickup or delivery details and the payment status, kept as its own separate, honestly-stated fact. Nothing about that process depends on a caller having a phone capable of receiving texts, being somewhere with a signal for one to arrive, or checking their messages before they need the information. The call itself carries the complete record, spoken clearly enough to act on immediately.

Worth explaining to a caller who's expecting a text the way an order from a delivery app might send one — the comparison is natural, but the two aren't actually solving the same problem the same way. A delivery app sends a text because the confirmation happens somewhere the customer isn't necessarily paying attention to in the moment, often through an app or a web checkout with no one narrating it back. A phone order is the opposite: the caller is present and engaged for the entire confirmation, hearing the full order read back to them directly, with an explicit chance to correct anything before it's sent. For a caller who was actually on the line for it, the spoken confirmation is a more complete version of a text receipt, not a lesser one — nothing summarized away, nothing waiting to be opened later.

The one real limitation worth being upfront about: there's nothing to look back at afterward the way a text thread would provide. If a caller wants something to hold onto for reference, the honest and useful thing to suggest is writing down the order reference number given during the call — the detail that actually matters if anything needs to be checked or discussed later, covered in full on Order status explained, and it works whether or not any text ever arrives. That reference number is the practical stand-in for a text receipt — it points directly at the real order record, the same one the restaurant and Dohos both actually use to look anything up.

02One order, heard in full

It's worth walking through exactly what a caller actually hears, because “the call is the complete record” is a stronger claim than it might sound like on its own. A caller orders a sandwich, a side, and a drink for delivery. Before anything is sent anywhere, the whole order is read back — the exact items and any modifiers, the delivery address and time window, the subtotal, tax, any fees, and the total — and the caller confirms that exact figure before it moves forward. Once the restaurant accepts it, the caller hears that too: the accepted total, the delivery window, and the payment status, stated as its own separate fact rather than assumed from the acceptance alone.

Compare that with what a typical order-confirmation text actually contains: usually a short summary, a total, and a link to see more detail if you want it. The phone call a Dohos order goes through covers the same ground and more, spoken directly rather than left for the caller to open later — and unlike a text that can sit unread in a notification list, the call requires the caller's own active confirmation before anything is finalized. A caller who hung up after confirming their order already has everything a status text would have told them; they just have it as something they heard rather than something sitting in a messages app.

A restaurant using Dohos has a real compliance disclosure page that exists to meet the requirements carriers set before any business can send transactional text messages at all. It's a genuine, required piece of groundwork, not a page describing something already happening. A caller who comes across it, or asks about it, isn't looking at evidence that texts are being sent today; they're looking at the compliance disclosure that has to exist before that capability could ever be turned on for anyone. Communications covers the fuller legal detail behind consent, recording, and messaging generally, for anyone who wants the complete picture rather than this page's narrower, practical answer.

Worth being precise about this distinction specifically because getting it backwards causes real confusion: the disclosure page existing is not the same claim as texts being sent, the same way a restaurant having a fire extinguisher mounted on the wall isn't evidence there's currently a fire. One is groundwork prepared in advance; the other is something actually happening. Today, it's the former.

This is also why it's worth not guessing at what a future text-based system would say or how it would behave. Whatever eventually gets built around that groundwork is a separate, later question with its own separate answer, and nothing about today's honest limit changes what a restaurant should tell a caller right now. The accurate, complete, present-tense answer stays the same regardless: an order's status lives on the call itself, in full, today.

04What to actually say

Three versions of this question come up in practice, and each has a short, honest answer.

  1. “Will I get a text about my order?” No — tell the caller plainly that everything about their order, including the total and the pickup or delivery details, was already covered on the call itself, and that's the complete record today.
  2. “I was told I'd get a text and I never did.” Worth taking seriously rather than dismissing, since it means either a genuine misunderstanding happened on the call or the caller is remembering a different order, a different restaurant, or a different service entirely. Check the actual order and its recorded events for what was actually said, rather than assuming either the caller is mistaken or something is broken.
  3. “I don't want to get texted.” An easy one to reassure directly: nothing about placing a phone order results in unwanted messages, because no text messaging is active for order updates today in the first place. There's nothing to opt out of that isn't already off by default.

None of these three requires apologizing for a missing feature or promising one is coming. The honest, complete answer in every case is the same: the call is where the real information already lives, and it always has everything a text would have covered anyway.

A fourth version worth planning for, even though it's less common: a caller who wants to change or check on an order after the call has already ended, without calling back and going through a whole new conversation. Today, that's a genuine limit worth being upfront about rather than working around with a guess — there's no self-service text or web link a caller can use after hanging up to check status on their own. The honest, complete answer is the same one that opens this page: calling back and referencing the order number given during the original call reaches a real person or the same order-status process, and gets a direct answer rather than a delayed one.

It's worth raising this topic proactively during a new restaurant's own setup, rather than waiting for the first caller to ask about it. A staff member who already knows the honest, direct answer — “we confirm everything on the call itself, and that's the complete order” — sounds confident stating it, while one caught off guard by the question for the first time can accidentally imply a text is coming when it isn't, simply by fumbling for an answer in the moment.

STILL STUCK?

If this page didn't cover what's actually happening, or its fix didn't hold, write to support — a real person reads it. Name the location, what you were doing, and any order or call reference you have.