Two menus, two clocks
Friday lunch for 18 and tonight’s dining room are different jobs. They still land on the same phone. A manager screenshots an office order into a group text, the PDF on the site still lists a March special, and the kitchen hears about the drop-off when someone asks where the pans are. Pickup ordering can be fine. An event request is not a pickup ticket with a bigger number.
This is for independent restaurants and small catering kitchens that already run Toast or Square and still track parties in personal texts. A new website will not, by itself, fill a private dining room. TwoQM works from the inquiry: what the guest must send, who answers, how the phone menu stays current, and when a message becomes a prep the kitchen can cook.
Guests decide on a phone. They need today’s menu, hours, and a way to order or call without pinching a PDF. Name who owns item changes, holiday hours, and sold-out dishes. Toast and Square can publish an ordering menu separate from the printed board. If you use it, the public page should point at that live menu, not at last season’s file.
Catering needs a second clock. A common rule for independent restaurants: group portions, a minimum that makes the trip worth it, about a day of lead time for a drop-off and longer when you staff the event, and a delivery boundary you will honor.
Toast Catering Online Ordering runs apart from regular online ordering, with its own hours, lead times, menus, minimums, and daily capacity. Toast Catering & Events, a separate module, can place a lead form on your site; submissions can become an order, an estimate, and a deposit. None of that is in the product unless the restaurant bought it. A Square kitchen can do the same job with a form, a catering menu, and a shared inbox. What matters is that Thursday’s request is still findable on Friday.
What the request has to contain
“Can you do food for my thing?” cannot be priced. Ask for the same fields every time:
Date, start time, and drop-off, pickup, or on-site service
Headcount or a range, and the style: trays, boxed lunches, or staffed service
Address or room, plus stairs, a dock, or a gate code you need
A budget band, or an honest “not sure yet”
Dietary notes the guest volunteers, and who can approve a change
How they want to be reached, and permission to text that number
Send a plain acknowledgment at once: received, who replies, and by when—the next business morning, not “as soon as we can” during dinner. That note can be automatic. The estimate should not.
With or without Toast, keep stages the closer and the kitchen both open: New, Waiting on headcount, Estimate sent, Deposit paid, On the prep calendar, Done. A personal text thread fails when the owner is on the line and the prep cook is not in it.
Here is an original example, not a client and not a result. A neighborhood restaurant accepts a Friday office lunch by text to the owner while the site still offers a spring PDF. The pans go out. The deposit does not. The fix is one record with a stage, a lead time, and a person who owns the reply.
Messages after the yes
Split the host stand from catering. OpenTable, Resy, Yelp, or the point-of-sale waitlist owns tables. One event owner owns catering. Google Business Profile and Instagram can stay as doors if the request is copied into the event record the same day. If it is not copied, the guest is in a channel nobody checks after 2 p.m.
If the only accurate menu is the chalkboard, say so, and put hours and the phone where a thumb can reach them. If the ordering link is the accurate menu, do not also leave three PDFs in the footer. TwoQM’s public project for Spartan Greek Authentic Food (https://twoqmllc.com/work/spartan-greek-restaurant) is a restaurant website with a mobile menu and visit details. It is not a catering system and not a metric to copy. Software for restaurants and food businesses (https://twoqmllc.com/industries/restaurants) can organize menus, ordering links, and event requests. A custom menu tool is scoped apart from whoever already takes payment.
Use the restaurant website checklist (https://twoqmllc.com/guides/restaurant-website-checklist) when the public page hides hours, ordering, or the event path. The stages above are what staff do next.
A rule, then a draft
Use ordinary automation for the acknowledgment, a lead-time refusal, a day-before reminder, and a stop when Saturday is full. Those rules do not need AI.
AI helps when one email mixes a menu question, a headcount change, and “make it nicer.” A draft can use your catering menu and the fields you stored, list what is missing, and offer language a manager edits. It must not send a price, invent a dish, or confirm a date the calendar has not accepted. AI integrations (https://twoqmllc.com/ai-automation) at TwoQM keep a person on guest-facing messages. Connected systems (https://twoqmllc.com/connected-systems) let the form, the inbox, and the prep list share one record. If a module inside your point of sale already does that, use the module. Custom software is for the gap: multi-step tastings, English and Spanish estimates from the same facts, or a prep sheet the kitchen will follow.
Discuss a software project
Name the path that breaks: the form nobody finishes, the menu guests still download, or the thread that never becomes a prep list. Discuss that software project (https://twoqmllc.com/custom-software) with TwoQM. We will look at the tools you run, separate a settings change from a build, and agree on scope and operating costs before a sketch is treated as a finished system. TwoQM is based in Brownsville, Texas, and delivers this work nationwide.