Plan an enquiry form and follow-up before your website launches
Decide which details to ask for, where enquiries go and how to confirm receipt without confusing a request with a booking.
An enquiry form needs a working process behind it. Decide who receives the message, what information they need and how they will reply before the website launches.
The form should help customers start the right conversation. Asking for every possible detail can make that harder, while asking too little can leave you unable to assess the request.
Choose the action you are offering
Write one sentence describing what happens after submission. For example, a hypothetical garden maintenance business might receive a request, check the location and work required, then contact the customer to discuss a quote.
That form should say "Request a quote", not "Confirm your booking". If the date or price still needs agreement, make that clear before submission and in the confirmation.
If you accept online bookings through another service, check which actions belong in that booking system and which should remain enquiries. Do not create two conflicting ways to reserve the same availability.
Ask for the details needed for the first reply
For a local service, the starting information might be the service required, suburb, short description and a contact route. The right fields depend on how you assess work.
For each proposed field, ask what decision it supports. If you do not need a full street address until a visit is arranged, consider asking for a suburb first. Mark optional information as optional.
Avoid requesting sensitive personal details that are unnecessary for the enquiry. Explain why a file is useful before asking someone to upload it, and agree on file handling and access with your provider.
Respect the customer's contact preference
If you offer phone and email follow-up, let the customer indicate a preference where practical. Do not require a phone number only because the template has a phone field.
Give another contact route for people who cannot use the form. Make the address or phone number easy to copy or tap. An alternative route also helps if the form is temporarily unavailable.
Use clear labels and understandable errors. Someone should know which field needs correction without losing the rest of their message.
Agree on delivery and responsibility
Confirm the destination inbox and the person responsible for checking it. Set up any required mailbox access before launch, and decide how messages are covered during absences.
Spam protection can reduce unwanted submissions but may also affect legitimate customers. Ask how you will identify a failed delivery or submission problem. Do not rely solely on a counter in a dashboard when the team works from an inbox.
If you promise a response time, base it on the process you can maintain. Otherwise explain the next step without inventing a deadline.
Test the complete path
business.gov.au's website guide recommends testing that customers can complete the site's tasks before launch. For an enquiry form, agree on a test with the designer:
- Complete it on a phone and a desktop with valid test details.
- Check a missing required field and an incorrectly formatted email address.
- Confirm that the submission reaches the intended inbox and that a reply can reach the sender.
- Check what the customer sees after successful submission.
- Check that a failed submission is not displayed as a success.
- Try the alternative contact route.
Keep real customer information out of test messages. If analytics are configured, confirm that a successful submission event is recorded only after the form succeeds. A button click is a different event.
Review the enquiries after launch
Record whether requests contain enough information for a useful reply. If customers repeatedly misunderstand the service or send enquiries outside your coverage, improve the service page as well as the form.
Our analytics guide explains how to compare contact actions with actual enquiries. The goal is a process your business can respond to, not simply a higher submission count.
Ask Netbound to confirm the form's scope and any connected services in your website brief. The package guide distinguishes standard contact forms from advanced form requirements and other work that needs assessment.