Pick one service your business offers. What would you need to know before you could give someone a useful first reply?
Start there. Your task is to finish a short field plan: the questions to ask, why each one matters, and who will use the answers. You do not need to settle every detail of the eventual project today.
Work through the fictional garden-design example, then use the worksheet for your service. This is a planning exercise; it does not claim that ClickFunnels AI has configured a destination, sent a message or generated a quote.
Decide what the first reply needs to accomplish
Write a one-sentence instruction for the person receiving the request:
Use this information to decide [whether we can help / who should reply / what to ask next].
For example, a garden design studio might need to check whether a project is within its service area and whether the requested work matches its services. It may need more information before estimating a price. The first form does not need to collect every detail required for the eventual project.
Name the next step accurately. Request an estimate means a request is being made. Book a consultation should lead to a booking process. Get an instant quote sets an expectation of an immediate price. Use the description your actual process can support.
Give every question a job
Take the first question you want to ask. Fill in four cells: what decision it supports, who uses the answer, whether the answer is necessary now, and what happens if the visitor does not know. Repeat that check for each field.
The GOV.UK Design System recommends knowing why each question is needed and allowing uncertainty where it is a valid answer. Its advice is useful when planning a business form too; it is not evidence that a particular field count improves conversion. Question-page guidance.
Scroll horizontally to compare all columns.
| Proposed question | Decision it supports | Needed for the first reply? | If the visitor does not know |
|---|---|---|---|
| Which service do you need? | Route the request to the right person | Usually, when there are different service teams | Offer “Help me choose” |
| Where is the project? | Check service coverage | When location affects whether you can help | Ask for a broad area initially if that is sufficient |
| What would you like to change? | Understand the request | A short description may be enough | Offer a simple example of the detail needed |
| When would you like to begin? | Check timing constraints | Depends on the service | Include “I'm still planning” |
| How can we reply? | Contact the requester | Yes, through the chosen reply channel | Explain the required contact method |
| What is your budget? | Assess a real planning constraint | Only if the team uses it at this stage | Allow “Not sure yet” if it is a valid response |
“Usually” and “depends” are decisions for your process, not reasons to make every field required. If an answer does not change the next step, consider asking for it later.
Worked example: a garden-design enquiry
The following studio and workflow are fictional. The studio serves a defined region and replies by email. It reviews the request before discussing scope or price.
Page promise: Tell us about the garden you want to change. We will review whether the project fits our service and explain the next step by email.
Button: Send my project enquiry
Scroll horizontally to compare all columns.
| Field | Example label and help text | Planned requirement |
|---|---|---|
| Reply email | Email for our reply — We will use this to respond to your project enquiry. | Required in this example because the studio replies by email |
| Name | Your name (optional) | Optional; does not determine service fit |
| Project area | Town or postal code — This helps us check whether the project is in our service area. | Required in this example; an exact address is not needed for the first review |
| Service | What would you like help with? — Courtyard design; planting plan; full garden design; help me choose. | Required, with a useful uncertainty option |
| Goal | What would you like to change? — A sentence or two is enough. For example: “I want a shaded seating area in a small courtyard.” | Required in this example to give the reviewer context |
| Timing | When are you hoping to start? (optional) — Soon; later this year; still planning. | Optional unless real capacity rules make it necessary |
A phone number, file upload, exact address or detailed budget could be useful later. Add one to the first form only when you can explain its purpose and support the resulting process.
Now try the same exercise with your service. Keep the questions that help someone respond. If you cannot explain what an answer changes, ask the person handling enquiries before making it required.
Use your approved privacy and consent wording. The example sentence about replying describes a specific fictional process; it is not a substitute for the notices your business requires.
Explain what happens after submission
Plan the confirmation alongside the form. It should state what has actually happened and what the visitor can expect next.
For the fictional studio, this could be:
We received your project enquiry. Our team will review the details and reply to the email address you provided about the next step.
Use that message only when the request has been saved successfully. If the business can support a specific response time, include the verified commitment. Avoid inserting “within 24 hours” because it sounds reassuring if nobody owns that deadline.
Also decide what to show if the request cannot be saved. A useful error should explain what the visitor can do next without falsely confirming receipt. Keep a review of failure behavior separate from writing the confirmation copy.
Make the questions understandable
Put a clear, persistent label beside each field and keep supporting instructions close to the question. Labels need to remain meaningful when the visitor navigates with assistive technology. W3C's form guidance explains how labels identify controls and connect them to their purpose. W3C labeling guidance.
During review, check whether optional fields are clearly identified, whether the choices cover a reasonable “not sure” case, and whether a visitor can describe their situation without knowing your internal service names. A blank placeholder alone should not carry the full explanation of a field.
Copy the field worksheet
Use the field-planning CSV or copy this table for each proposed question.
Scroll horizontally to compare all columns.
| Question | Decision supported | Person using it | Required now? Why? | Valid unknown answer | Later follow-up instead? |
|---|---|---|---|---|---|
Then add these operating decisions:
- Request destination: Where should the completed enquiry be saved?
- Reply owner: Who checks new requests and sends the next response?
- Promised next step: What exact wording can the business support?
- Success evidence: Where will the team confirm that a test request arrived?
- Failure handling: What will the visitor see if saving fails?
Turn the worksheet into a page plan
You now have a field list and a reason for each question. Read it with the person who will handle the enquiries. Can they explain the first reply they would send? If something is missing, make that your next question.
Hand over the field list, approved wording, request destination and reply responsibility together. Ask the builder to flag any missing destination or unsupported promise before implementation. Review a real test request through the intended process before promoting the page.
If you are preparing this for ClickFunnels AI, keep the worksheet with your project instructions and consult the agent guide for its workflow and access requirements. This planning guide does not establish that a particular integration or form behavior is available in your account.
Common questions
How many fields should a quote form have?
There is no field count established by this worksheet. Include the information needed for your next real decision, then review which questions can wait. Test the resulting form with the people who will use and respond to it.
Should a budget question be required?
Only make it required if the next step genuinely depends on it and the visitor can give a meaningful answer. If “I don't know yet” is a realistic situation, decide how your team will handle it.
Can a confirmation page say a quote is ready?
Only when the actual process has produced the promised quote. If the team still needs to review the request, the confirmation should describe that review and the next response.