Each afternoon, cafe and hotel customers get tomorrow's standing order on WhatsApp and reply in plain text with changes. An AI agent updates the order sheet and confirms, and at the 6 PM cutoff the night shift gets a bake sheet and route packing lists.
Typical results
≈1.5 hrs/day
Office time back from taking and writing changes
≈75%
Fewer route packing errors
6 PM
Daily cutoff that locks tomorrow's orders
Figures reflect typical results for this kind of automation.
The challenge
Wholesale customers change their standing orders almost every day, mostly through phone calls and voice notes in the late afternoon. Someone in the office writes each change on the order sheet, the night shift bakes from a list that is often out of date, and short or extra trays turn up on the delivery routes the next morning.
Before and after
Order-change phone calls per day
−71%Route packing errors per week
−75%Minutes to prepare the night shift bake sheet
−92%The automation
At 2 PM each customer receives tomorrow's standing order on WhatsApp and can reply in plain text, such as 'add 10 croissants, no rye'. An AI agent turns the reply into quantity changes on the order sheet and sends back the updated order to confirm. Unclear replies go to the office. At the 6 PM cutoff the orders lock, and the system produces the night shift's bake sheet by product and a packing list for each delivery route.
How it works
- 01
Tomorrow's order at 2 PM
Each cafe and hotel customer gets tomorrow's standing order on WhatsApp, listed by product and quantity.
- 02
Changes in plain text
Customers reply in their own words, such as 'add 10 croissants, no rye', or simply 'ok' to keep the order as it is.
- 03
AI updates the order sheet
An AI agent turns the reply into quantity changes on the order sheet and sends back the updated order to confirm. Unclear replies go to the office.
- 04
Orders lock at 6 PM
At the cutoff no more changes are accepted, and late messages get an automatic reply with the office number for urgent cases.
- 05
Bake sheet and packing lists
The system totals every product for the night shift's bake sheet and produces a packing list for each delivery route.
Starts from
- Standing order sheet
- Customer WhatsApp replies
Delivers
- Confirmed order to customer
- Night shift bake sheet
- Packing list per route
The impact
Order-change phone calls drop by about 70%, and the office gets back roughly 90 minutes a day it used to spend rewriting the order sheet. The night shift bakes from a locked list, packing errors fall from around 12 a week to 3, and every change has a written confirmation.
Questions about this automation
How does the agent handle vague replies like 'same as last week'?
The agent can read each customer's order history, so 'same as last week' or 'double the baguettes' becomes exact quantities that are shown back to the customer for a yes. Anything it cannot map to a product and quantity with confidence goes to the office as a flagged message well before the cutoff.
Does it need an ERP, or will a sheet do?
A sheet is enough to start. The flow needs a business WhatsApp number for the messages, the order sheet or ERP where standing orders live, and a printer or shared folder for the bake sheet and route packing lists. Many bakeries run on Google Sheets first and connect an ERP later.
What happens with a change sent after the 6 PM cutoff?
The order stays locked so the night shift is not working from a moving target. The customer gets an automatic reply saying the change will apply from the following day, with the office number for genuine emergencies, and the office sees the late request first thing in the morning.
