A request first, confirmed by our reply
An agent built a website flow that gathers a food request into a message draft, while keeping the kitchen’s reply as the point of confirmation.
Looking back to 5 September, I wanted our website to do more for people coming to look at the menu. Until then, much of its design had focused on search. I asked the agent to make it easier to see what we were cooking that week and request food. One condition mattered from the start: a customer’s request needed our reply before it became a confirmed order.
The agent built a flow around the dated menu. A visitor can choose a pickup day, open a dish, select its serving option and adjust the quantity. The website gathers those choices into a request, with an estimated total and space for a name, pickup preference or question. This gives the customer a message to review rather than asking them to type the menu choices again.
For the first version, I wanted to keep the process simple and use the kitchen’s existing text-message conversation. The website prepares the draft and offers to open the customer’s messaging app. The customer checks it and taps Send there. Opening that app is just handing over a draft: the website cannot tell whether the message was sent.
On a computer, the agent also provided copyable text and a QR fallback for taking the request to a phone. We kept those options because messaging apps do not behave the same way on every device. The website does not send a backup message itself. That means a failed app handoff does not quietly turn into a second request.
The page repeats what happens next: wait for a confirmation text from Chloe’s Mama Kitchen on your mobile. Our reply confirms the items, pickup and total. A button click or a prepared message does not reserve food. That distinction belongs in the customer’s view, because someone choosing a meal needs to know what the kitchen has actually agreed to.
The redesign was first merged as a preview on 5 September. When I checked the main website, it was still showing the earlier design, so I asked about it. The agent corrected the build and the new design was then merged for the production homepage that same day. Checking again while preparing this diary on 6 October, I found the request-and-reply wording still on the live page. The completed result is a working website request flow; we have not established how many customer orders it has produced.
