Orders by phone get misheard, and orders by message get lost. When the lunch rush starts, nobody has time to scroll. I would send customers to one link, so every order arrives with a name, a time and the allergies written down.
Who it is for
Small kitchens, food trucks, home cooks and cafes that take takeout or delivery orders directly, without an ordering platform.
What each question is for
- Name and phone: so you can call about a missing item.
- Pickup or delivery, address, date and time: so you plan the route and the oven.
- Order box: dish names and quantities in the customer's own words.
- Sides, drinks and spice level: quick picks that save back and forth.
- Cutlery tick: a small thing that cuts waste.
- Allergies: read first, before you cook.
What a customer's AI would ask
"What would you like to order, and how many of each?" Then "Pickup or delivery?" Then "Any allergies?" The AI lists the answers and submits only after a yes. Learn about agent-fillable forms.
Before you use it
The form takes no payment, so agree that when you confirm the order. Set the close time to your last order. For weekly school meals, see a school lunch order form. For long allergy lists, use a dietary requirements form. Baking? A cookie order form fits better. More ideas: forms for restaurants and food businesses.
Questions
Can customers choose items from a menu?
They type what they want in the order box, with quantities, and tick sides and drinks from lists. The form has no menu pages or basket, and it takes no payment.
How do I stop orders after the kitchen closes?
Set close_at to your last order time on the day, and max_responses if the kitchen can only handle so many orders. The public form then stops taking orders.
What about allergies on a takeaway order?
An allergy box sits on the form so it is never missed. Read it before you cook, and call the customer if you cannot meet the need. The dietary requirements template covers longer lists.