A cake order by text message is half an order. "Chocolate, for Saturday" leaves you asking how big, which filling and who is allergic to what. I would send one link so every order arrives complete.
How it works
- The customer gives a name, phone and the date they need the cake, so you can plan your week.
- They choose the occasion, servings and tiers, so you can size the cake.
- They pick a flavour, filling and icing, and link to a picture of a cake they like.
- They type the inscription exactly as they want it written.
- They name allergies and say whether they will collect or want delivery.
What a customer's AI would ask
"Which date do you need the cake?" Then "How many servings?" Then "What should the inscription say?" It shows every answer and sends them only after a yes. Learn about agent-fillable forms.
Good to know
Spelling mistakes on icing are painful, so the form asks customers to type the inscription exactly. Read the CSV each morning and reply to confirm. For biscuits and party favours, use a cookie order form. For loaves, buns and pastries, a bakery order form fits better. See forms for restaurants and food businesses and forms for ecommerce and Shopify stores.
Questions
Does the form take a deposit?
No. The form takes no payment. Agree the amount and any deposit yourself by message or invoice once you have read the order and checked your diary.
How do I avoid taking too many orders for one day?
Sort the CSV by pickup_date to see how loaded each day is. Set close_at ahead of busy holidays, so orders stop before you run out of oven space.
How should I handle allergies?
The allergy question is required, so customers write none or name the allergen. Read it first on every order, and message the customer if you cannot make a safe cake.