A simple “Tell us what you need” field can ask too much of someone planning a bespoke product. Customers often know the problem and have a photo on their phone. They may be unsure which measurements matter or how to explain the site. The enquiry page can guide them through those details without turning a first conversation into a specification exercise.
The Tint & Screen enquiry page for custom screens shows how this can work. It explains what to photograph and asks about the purpose, location and approximate size of the screen. Its form prepares a WhatsApp message the customer can review before sending. The same page structure can support a conventional form or email handoff.
Describe what to prepare before the first field
Put a short checklist above the form. Ask for a wide photo showing the whole opening or area, a closer view of any obstacle or adjoining surface, and approximate width and height if the customer knows them. Add an example so “the whole opening” has a concrete meaning. In a patio, that could mean stepping back until both sides of the opening and the area in front are visible.
Clearly label a render as a design concept. It can help someone recognise the kind of screen they want. A site photo from the customer answers a different question. It shows the surroundings the supplier needs to work with. Tell people how and when they can share their photos, especially if you use a messaging handoff.
Ask for information you can act on
Start with the request. Does the customer want privacy, a divider or help screening equipment? Give “I’m still deciding” as an option if your team can help at that stage. Ask for the town or service area and one way to get back to them. Follow with space for approximate size, finish preferences or a pattern reference as useful.
One optional question about site conditions can prevent several follow-ups. An enquiry about equipment might need a model number or a photo of the service side. A patio project might need a note about the opening or an adjacent gate. Ask for the practical detail in context. Final dimensions and technical suitability can be confirmed when the supplier reviews the project.
Write one example brief for the field help
Try a plain-language example such as “We’d like more privacy on our patio in George. The opening is about two metres wide. I can send a photo of the whole area and another showing the wall and gate.” This gives the customer a sense of how much detail is useful at the first contact. The dimensions can remain approximate until someone checks them on site.
If the business uses pattern references, place that prompt near the optional notes. A customer arriving from the catalogue may already have a favourite. Someone without a pattern in mind should still feel able to start the enquiry. Share the example with whoever receives the enquiries and see where it would leave them with a follow-up question.
A town can be enough to confirm coverage at the start. Ask for a full address when the business needs it to arrange a visit, and explain why. The form should ask for the details the team can use at the enquiry stage.
Give the form a clear place in the page
In MaxiBlocks, plan separate content groups for preparation, the form and what happens next. On a desktop the preparation note can sit beside the form if both have enough width. On a phone it should come first and remain short. Keep field labels visible after typing. Mark optional items in the label and give an example beside any measurement field, including the units.
Use the form or enquiry component that matches your delivery method. The surrounding layout gives it context. The form itself handles validation, attachments if supported and delivery. Preview the actual result in WordPress. With a phone keyboard open, it should still be possible to see the active field and understand what information it asks for.
Write the button for what it does
“Prepare my WhatsApp enquiry” tells people that another step follows. “Send enquiry” fits a form that sends the brief immediately. Add one short sentence about what to expect near the button. If they will review a message and add photos in another app, describe those steps before they leave the page. If the form sends the enquiry directly, provide a confirmation they can read after submitting.
Make error messages specific and keep the information a person already entered visible wherever the form supports it. An empty phone field can say what to enter. A photo upload problem can explain the accepted size or file type. A customer still gathering measurements should know what details they can leave for later.
Check the flow with a sample enquiry about a patio screen, then try again using only a phone. See whether the recipient could start a conversation from the details provided. If the same question would still need to be asked every time, adjust the page’s prompt before making the whole form longer.