Back to all articlesLead capture

Choose which fields belong on the first enquiry form

Alactic Editorial9 min read

Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.

Your enquiry form asks for a name, company, email, phone number, project description, budget and address. Each field has a defender. Nobody can explain what would stop working if the visitor left one blank.

The first form should collect enough information to receive a request and take the promised next action. Require an answer only when its absence prevents that action and no workable fallback exists. Keep useful but nonessential answers optional, defer questions belonging to established later workflows, and remove fields with no established collection need.

There is no universal field list. An email-response service and a callback service need different contact details. Start with the action your team promises, not everything it might eventually want to know.

1. Define the promise before choosing fields

Hypothetical worked example: A fictional business-services firm receives website enquiries. A shared team reads each submission, assigns a responder and sends an initial email. It does not prepare a quote, arrange a site visit or assess commercial suitability at capture.

The form promises: Briefly describe what you need help with, and our team will respond by email. Visitors may also request a callback, but it supplements the initial email.

Successful capture therefore means the team receives a stated request, has a return email address and can respond or ask a focused clarification question. A completed company profile, confirmed budget and postal address are outside that boundary.

This promise deliberately distinguishes an enquiry from a contact-only submission. The team offers to respond to a stated need, not to start a discovery exchange with anyone who leaves an email address. That distinction matters when deciding whether enquiry text is required.

Define your own boundary in one sentence: After submission, we will use [contact route] to take [next action], using [minimum context]. Resolve disagreement about this handoff before adding fields.

2. Give each field one of four decisions

For each field, record its immediate use, the consequence of a missing answer and the fallback. Then assign a decision:

  • Required: The capture promise cannot reasonably be fulfilled without the answer, and no workable fallback exists.
  • Optional: The answer has a named immediate use, but leaving it blank does not prevent the promised response.
  • Deferred: The answer belongs to an established later workflow with a defined collection trigger.
  • Removed: There is no established collection need. A speculative future use is not a trigger.

Deferred and removed fields both disappear from the first form, but they produce different instructions. A deferred question moves to a known step. A removed question has no scheduled collection point.

A fallback must describe an action. “The team will work it out” is not enough. Sending an incomplete request to the general enquiry queue and asking which service the visitor needs is actionable.

Apply the fallback test honestly. A missing name prevents a personal greeting, not a response. Equally, a field is not genuinely optional if staff refuse to handle submissions without it. When a clarification email would fulfil the form's promise, that is a valid reason to make the relevant information optional.

3. Filled worksheet: seven fields and their handling rules

Fictional worked example continued: This worksheet applies to the email-first firm above. It is a reusable decision record, not a universal specification or an Alactic customer result. Copy the headings and replace the reasoning with your own operating facts.

Name — optional

  • Immediate use: Personalise the greeting and help staff recognise the conversation.
  • Missing-answer consequence: No personal greeting; handling can continue.
  • Fallback: Use a neutral greeting and refer to the request.
  • Form treatment: One optional name field rather than mandatory first and last names.

Company — deferred

  • Immediate use: None in the shared first-response process.
  • Missing-answer consequence: The organisation remains unknown; the response can proceed.
  • Fallback: Leave company unknown rather than guessing from an email domain.
  • Collection trigger: Ask during the established scoping conversation, when the team identifies the organisation for which work is being discussed.

Email — required

  • Immediate use: Send the promised first response.
  • Missing-answer consequence: The agreed response route is unavailable.
  • Fallback: Before submission, direct visitors who cannot provide email to an existing alternative contact route, if offered. That is a different route, not fulfilment through this form.
  • Form treatment: Check basic format and make the address easy to review and correct. A plausible format does not establish that an inbox exists or a reply will arrive.

Phone — optional

  • Immediate use: Arrange a requested additional callback.
  • Missing-answer consequence: Staff cannot place the callback yet; the initial email can proceed.
  • Fallback: Ask for a number in that email if the visitor requested a call.
  • Form treatment: Label the field as an optional number for an additional callback.

Enquiry text — required

  • Immediate use: Identify what the visitor wants help with and choose a response.
  • Missing-answer consequence: Contact details arrive without a stated request.
  • Blank-text fallback assessment: Staff could email asking what the visitor needs. However, that would initiate discovery rather than respond to a stated enquiry—the narrower service this fictional form offers. The form's promise explicitly asks visitors to describe their need.
  • Incomplete-text fallback: A vague request still states a need, even if it needs clarification. Ask a focused follow-up rather than demand complete requirements.
  • Form treatment: Ask what the visitor would like help with and explain that a brief description is enough. Do not impose a detailed specification as a condition of capture.

If your team is willing to begin discovery from contact details alone, use a different decision: make enquiry text optional and adjust the form promise accordingly. Required text is justified by this workflow boundary, not by a universal rule that every enquiry needs a description.

Budget — deferred

  • Immediate use: None before the team understands the request.
  • Missing-answer consequence: No effect on initial handling.
  • Fallback: Continue without a budget value; do not substitute zero.
  • Collection trigger: Ask when the enquiry enters the established scope-and-estimate discussion about spending expectations.

Full address — removed

  • Immediate use: None; location does not determine the first response.
  • Missing-answer consequence: No established task is blocked.
  • Fallback: Leave it absent; staff should not search for an address to complete the record.
  • Collection trigger: None. A possible future site visit does not create an established collection need. Reassess if an address-dependent service is introduced.

The resulting form has required email and enquiry text, plus optional name and callback phone. Company and budget move to named later steps. Full address has no collection point.

4. Make requirements follow the response choice

Change the worksheet when the service promise changes, not merely because another team prefers fuller records.

Hypothetical variation: Another form lets visitors choose email or telephone as their primary response route. Phone becomes required when telephone is selected; email becomes required for the email choice. Requiring both needs a separate operational reason.

The form summary and confirmation should reflect that choice. Someone selecting telephone should not discover later that staff only respond by email. Conversely, the optional callback in the original worksheet must not silently replace the promised initial email.

Dependencies apply to context as well as contact details. If the first action genuinely depends on service location, determine whether an area or postcode is enough before asking for a full street address. Record the action that depends on the answer and the minimum information needed.

5. Test the form and receiving workflow together

A shorter form fails if the receiving process still demands every old field. Before publishing, submit a hypothetical enquiry with every optional field blank. Follow it through receipt, assignment and first response. Staff should complete the promised action without inventing missing information.

Then test these distinct paths:

  • Blank enquiry text: The form explains that a brief request is needed, preserves the other entries and lets the visitor correct the omission.
  • Vague enquiry text: The request reaches the team, which can ask a useful clarification question.
  • Callback requested without a number: The first email can ask for the missing number.
  • An email address entered in an unacceptable format: The error identifies the email field and explains what needs correcting.

Check whether the receiving record can exist without company, budget or address. Confirm that a blank phone field does not prevent assignment and that staff can distinguish information not collected from an answer the visitor actually supplied.

If a receiving system demands an unnecessary value, investigate the constraint rather than automatically transferring it to the visitor. Check the current workspace and plan for available configuration. These are recommended workflow tests, not claims that a particular Alactic product control exists.

W3C guidance supports labels that identify each control's purpose and are programmatically associated with it. Validation errors should be understandable and accessible, and checks should accommodate varied input formats. Client-side checks do not replace server-side validation.

6. Define recovery for unusable answers

A required marker cannot ensure a usable answer. A visitor may mistype an email or submit a request that staff cannot interpret. Recovery belongs in the operating instructions, not just the form validation rules.

For an unclear enquiry, ask the smallest question that unlocks the next step. For example, in a hypothetical submission asking for help with “our reporting,” the responder might ask which reporting task is causing difficulty rather than send a full requirements questionnaire.

If an email proves unusable, inspect whether a suitable alternative route was supplied and whether its explained purpose supports a recovery contact. Do not treat the presence of a callback number as permission for unrelated outreach. If no suitable route exists, mark the enquiry as unable to contact instead of leaving it indefinitely awaiting a normal reply.

Record what failed and what recovery was attempted. Where another supplied route also fails, record that outcome rather than fabricating a replacement or repeatedly attempting the same failed action.

This separates missing information from unusable information. It also prevents a contact failure from becoming an automatic demand for two contact routes from every visitor. Review the actual failure before changing the collection burden.

7. Maintain a short observation and decision record

Hypothetical review plan: Review the next 20 enquiries after a change. This is a manageable review batch, not a statistical benchmark. Record the intended action, missing or unusable answer, recovery attempted, outcome and collected answers actually used.

Filled hypothetical observation: Visitor requested a callback without a phone number. Initial email asked for a number. Visitor supplied one; staff could arrange the call. Outcome: fallback worked. Decision: retain the existing field treatment.

Filled hypothetical maintenance record: Owner: enquiry operations lead. Review point: after the review batch, or sooner if the response promise changes. Change rule: document the blocked action, attempted fallback and reason for the proposed change before revising a requirement.

Use those observations to update the worksheet: remove optional questions nobody uses, retain named collection triggers for deferred questions, and investigate repeated handling failures before adding mandatory fields.

Lead captureEnquiry formsForm designBusiness operations

Put the next conversation to work.

Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.

Explore Communications