A healthcare enquiry form needs enough fields to route the request and send a useful reply, but no more. There is no honest universal number. A callback request may need only a name, contact method, and reason category. A referral or partnership enquiry may need different information. Decide field by field from the receiving workflow rather than copying a conversion benchmark.
The practical question is not "How short can we make this?" It is "What will staff do differently because this answer is available before they respond?" If nobody can name that decision, remove the field or make it optional.
Use the receiving team's first five minutes
Watch what happens after a real enquiry arrives. Who opens it? How do they decide which location, service, or team owns it? What information do they need before they can send a helpful first response? Which details do they ask for later, after the person has chosen to continue?
This observation separates routing information from intake information. A public marketing form is usually there to begin a conversation. It should not quietly become a clinical history form just because the software makes it easy to add boxes.
The Office of Disease Prevention and Health Promotion recommends keeping required information on forms to a minimum. Its guidance also favors visible instructions and a simple vertical layout. That does not prescribe a field count, but it does put the burden of proof on every extra question.
Run every field through this worksheet
Copy the table into a working document and complete it with the person who handles enquiries.
Proposed field • Decision it changes before reply • Must be known now • Can be asked later • Keep, optional, or remove
- Name | Lets staff address and identify the enquiry | Usually | No | Keep
- Preferred reply method | Tells staff whether to call or email | Often | Sometimes | Keep or optional
- Service of interest | Routes the request to the right team | When several teams receive enquiries | Yes if one team reviews all requests | Depends on workflow
- Preferred location | Routes multi-location requests | When availability and teams differ by location | Often | Depends on workflow
- Detailed symptoms | May invite clinical interpretation in a marketing workflow | Rarely | Use an approved care workflow if genuinely required | Remove from a general enquiry form
- "How did you hear about us?" | Supports marketing analysis, not the immediate reply | No | Yes | Optional or remove
- Free-text message | Captures a question not covered by categories | Often useful | No | Keep with a clear prompt
The example decisions are not a universal policy. Your privacy, clinical, legal, and operational owners may set different requirements. The point of the worksheet is to make the reason for each field visible.
Which three kinds of information are being mixed?
Most overgrown forms mix routing, response, and later-stage intake questions into one premature request.
**Routing information** decides where the request goes. This might be the service, location, or enquiry type.
**Response information** lets the team contact the person in the way the form promises. This might be an email address, phone number, or preference.
**Intake information** supports a later operational or care process. It may be important, but that does not mean it belongs on the first marketing form.
Mark each current field with one of those labels. If an intake question appears early, ask whether the same information can be collected through the practice's approved intake process after the request has been acknowledged. Do not move sensitive information between systems without the appropriate privacy and security review.
Design around the task, not one master form
A single site-wide contact form often grows because every department adds one more question. The result is a compromise that fits no task particularly well.
Use distinct forms when the receiving workflows are genuinely different. A short "ask about this service" form can carry the service and page context automatically rather than asking the visitor to select it again. A media enquiry can go to a communications team. A careers form can direct applicants to the recruitment process. An existing-patient request should use the practice's approved route rather than a general marketing inbox.
Do not create a different form for every page merely for reporting. Too many versions become hard to maintain. Split forms only when the fields, owner, promise, or next step meaningfully changes.
Write prompts that produce usable answers
Field labels should tell people what to enter without relying on placeholder text that disappears when typing. "Message" is vague. "What would you like help with?" is clearer. If the form is not for medical advice, state that beside the message field rather than burying it in a footer.
Use a specific label for contact preferences. "Best way to reply" followed by "Phone" and "Email" is easier to understand than an unexplained "Contact type" dropdown. If a phone number must include an area code or an email is required for a confirmation, explain that at the field.
The U.S. Web Design System recommends identifying required and optional fields in text, aligning validation with the affected input, and keeping form controls in a simple vertical order. The World Wide Web Consortium also emphasizes explicit labels and useful error feedback. Those details matter because a short form can still be unusable if people cannot tell what went wrong.
A worked reduction
Imagine a general service enquiry form that asks for all of these details before anyone replies:
- First name
- Last name
- Date of birth
- Phone
- Preferred contact method
- Home address
- Service
- Location
- Insurance company
- "How did you hear about us?"
- Message
The receiving team says it needs a name, one reliable contact route, service, location, and the visitor's question. It does not use date of birth, home address, or insurance information until a later approved workflow. Marketing can get acquisition information from campaign and page data without forcing an answer on every visitor.
The revised form could ask for name, email or phone based on the chosen reply method, service, location, and question. That is not better because it meets a fashionable number. It is better because every remaining field has a job and every removed field lacked one at this stage.
Test completion and response together
Test the form on a phone with realistic entries, not perfect dummy text. Trigger a missing required field, an incorrectly formatted address, and a longer question. Confirm that the error says what to fix and returns focus to a useful place. Submit the form and check the confirmation message, notification, inbox routing, and first response.
Then review a small set of real enquiries with appropriate handling. Ask staff what they still need before replying and which collected answers they never use. This is more useful than watching form submissions alone. A high completion rate cannot tell you whether the form produces routable requests.
Decide one field at a time
Start with the longest or highest-volume enquiry form. Put every field into the worksheet, invite the receiving owner to defend its immediate purpose, and remove questions that belong later. Keep the route honest about what happens after submission.
That is how a healthcare lead generation form becomes both easier for the visitor and more useful to the team receiving it.