--- title: "Design an enquiry form that asks for the right information" description: "Plan the questions, labels and confirmation message for a small business enquiry without inventing a booking or price promise." author: Power of AI date: 2026-09-07 url: https://powerofai.ca/playbooks/enquiry-form-plan --- # Design an enquiry form that asks for the right information Plan the questions, labels and confirmation message for a small business enquiry without inventing a booking or price promise. Take the next useful step. A useful enquiry form helps someone explain the job and understand what happens next. AI can draft the questions and challenge unnecessary fields before you build anything. Start with the decision your business needs to make after receiving the request. The form should collect enough information to support that next step while remaining easy to complete. ## Name the next step the form supports Use a fictional bicycle-accessory repair service. The business first decides whether it can assess an item; it quotes only after inspection. The enquiry form therefore needs a description of the item and the problem, plus a way to reply. It does not need payment details at this stage. Write that purpose at the top of the planning document. Every proposed field should earn its place by supporting the next step. “We might use it someday” is a weak reason to collect more personal information from a visitor. ## Make required and optional questions explicit An authored field set is: reply email, required; item type, required; description of the problem, required; photo, optional if the business can receive it appropriately; preferred contact time, optional. The example does not establish that your own business needs the same fields. Ask the assistant to write a visible label and a short hint for each field. A placeholder alone can disappear as someone types. “Describe what is not working” is more helpful than “Details,” particularly when the visitor does not know technical terms. ### A request you can adapt Draft an enquiry-form specification for these approved service facts. For each field, state its purpose, whether it is required, a plain-language label and a useful hint. Ask only for information needed for the next step. Write a submission confirmation that does not imply a booking, quote or service guarantee. ## Explain what happens after submission An authored confirmation is: “Your enquiry has been received. We will review whether the item is within our service scope and contact you about an assessment. This is not a confirmed booking or quote.” Add a response-time promise only if the owner has approved and can maintain it. Plan an error message as well. If submission fails, the page should say so and preserve the visitor’s entries where appropriate. Do not show the success wording merely because a button was clicked. A built form needs a real end-to-end delivery check. ## Walk through ordinary and awkward examples Try a visitor who knows the product name and one who only knows that a part is loose. Both should be able to explain the request. Try leaving an optional photo blank and entering a long description. Check that the form does not force a false answer to continue. Review labels, keyboard navigation, error placement and the confirmation on a phone when the form is built. Ask the responsible person to confirm where submissions are stored and who can read them. This article prepares the specification; it does not configure a live form. ## Remove a field and defend the choice For practice, add a required home address to the fictional enquiry. Explain whether the assessment decision needs it now. If service-area screening is necessary, a broad area may be enough initially; the business should choose the least information that serves the actual process. Keep the approved field list, confirmation wording and test cases together. When the service process changes, revise the form and its replies as one piece of work. A shorter form with a clear next step can be more useful than a long one that makes the visitor guess. ## Take this into your next task Ask for the information needed for the next step and make the meaning of submission clear. [Build your learning roadmap](/for/business#roadmap). ## Questions people ask ### Can AI build the form too? It can help implement a reviewed specification. Delivery, validation, accessibility and storage still need appropriate checks. ### Should every field be required? Require only what is necessary for the stated next step. Optional context should remain optional. ### Can I promise an instant quote? Only if that is an actual approved capability of your business process. A draft should not invent it. ## Sources and editorial notes Reviewed 2026-09-07. Product capabilities depend on the app, plan, region and workspace settings. Workflows and prompts are authored teaching material, not recorded model results or measured time-saving claims. ## Keep going - [AI for Business Owners: Useful Examples and a Practical Roadmap](/for/business) - [Test one AI workflow before making it part of the business](/playbooks/small-ai-pilot) - [AI Mission Control: From Idea to Verified Result](/mission-control)