What should a custom-cake enquiry ask before anyone quotes a price?

Which first questions establish feasibility?

Ask for the required date, approximate servings or size, and collection or delivery first. Then ask about flavour, design reference and budget. Timing and size affect whether the work can be done at all. Do not demand a full address or payment details before a baker knows the request is feasible. For a visitor seeking only a range, show published base sizes and starting prices while explaining that decoration, rush work and transport need review.

A two-stage conversation is easier than a ten-field form: first date, servings and fulfilment method; then flavour, visual preference and any special dietary requirement. Shopify's order-note guidance distinguishes instructions for an order, properties of an individual item and checkout fields. Apply the same discipline: gather feasibility facts for an enquiry and exact delivery details for a formal order.

Keep an approved feasibility sheet with minimum lead time, sizes, collection hours, delivery area and decorations requiring a human quote. Date it and give it an owner. AI may describe those published rules but cannot promise a rush slot or unusual material without the baker's assessment.

If someone says 'as soon as possible', ask for the actual needed date; 'soon' cannot be compared with a production schedule. For ten servings, clarify the intended serving size where it matters. These questions are not there to prolong chat. They give the baker enough information for an initial feasibility decision.

How do allergens, references and prices stay accurate?

A dietary concern is a question for someone with the current recipe and production details, not a guess from a flavour name. The UK Food Standards Agency's English guidance stresses allergen information in remote food sales; local legal duties differ, but a bakery should verify actual ingredients and handling before making an assurance. Do not promise allergen safety merely because a chatbot saw a menu.

A reference picture needs interpretation. Ask whether its colour, theme, lettering or full structure matters most. Before quoting, send a compact summary for correction: date, servings, collection, flavour, visual brief, dietary question and budget. The baker then reviews ingredients, capacity and labour. Standard cakes with defined prices can use published product options and a formal confirmation page; highly variable work fits a lead and human quote. Chat alone cannot turn one into the other.

A kakinang FAQ or approved document can explain standard flavours, starting prices and ordering rules. With consent, a lead can preserve the contact route and open decisions for staff. A visual reference should use a configured permitted intake path; do not assume every chat entry point accepts images. Review published lead times against the baker's current workload.

When does an enquiry become a commitment?

Use explicit stages: enquiry received, details missing, baker reviewing, quote awaiting customer acceptance, and formally accepted. The first four are not an order. Let someone who declines contact details read the public terms. Email alerts require configured recipients and SMTP; a stored lead does not prove that a phone rang.

In the fictional example, a visitor asks on Monday night for a decorated cake for thirty people on Wednesday morning. Check the approved lead-time rule and avoid a rush promise; offer a standard option or a different date for review. A second visitor with a flexible date but strict budget may benefit from base sizes and adjustable decoration. Identical sales scripts would miss the difference.

Each week examine requests with clear dates but no staff reply, quotes without a recorded customer decision, and dietary concerns never assigned to a knowledgeable person. Test duplicate requests, changed dates and conflicting picture versus description. A responsible person verifies the final summary, price and fulfilment; the customer confirms through the formal process.

A quote needs an expiry and change rule. Today's ingredient cost and open production slot may differ two weeks later. State that the quote applies to the current specification and availability until a given date; a change to servings, design or fulfilment needs a fresh review. When a customer says 'yes', identify which version of the brief was accepted. A deposit, payment route and refund terms belong in a formal authorized process, never an improvised personal payment account from AI.

Flag food concerns separately from general notes. 'Someone is allergic to nuts' should stop automatic recommendation and move the exact concern to a person with recipe and production knowledge. Not adding nuts is not the same as guaranteeing no contact in the environment. The bakery should know which requests it cannot safely accept and provide an honest refusal or alternative. AI's role is to avoid turning unknown safety facts into a promise, not to offer medical advice.

A workable lead summary names the date and time, servings, collection method, flavour, visual style, undecided wording, dietary question and consented contact route. Staff can then see what blocks a quote. If the date changes, version the request and responsibility so an old price cannot silently follow the new deadline. Measure staff response time, clarification rounds and post-quote revisions rather than inventing a revenue estimate.