Questions on a form that people refuse to answer, and why

5 days ago
3 min read

Updated: 3 days ago

Introduction

Some questions produce answers, some produce abandonment, and some produce fiction. Businesses rarely distinguish between the three, which means a form can be simultaneously losing enquiries and collecting data that is not true. Both are invisible: nobody reports abandoning a form, and an invented budget looks exactly like a real one.

The pattern is consistent enough to be predictable. Questions that feel like a commitment, that expose something the buyer would rather keep back, that they genuinely cannot answer yet, or that seem irrelevant to the request all cause problems. Knowing which of your fields fall into those categories is a fifteen-minute review with an immediate effect.

1. Questions on a form that people refuse to answer fall into four groups

The classification.

Too committing, too revealing, not yet knowable, or apparently irrelevant. Each fails for a different reason and each has a different remedy. Go through your own form and assign every field to one of the four or to none; the ones that land in a category are your candidates.

2. Phone number is the classic too-committing field

The most expensive common requirement.

Many people are not ready to invite a call from a stranger. Making it optional generally raises completed enquiries and loses almost nothing, because those intending to talk supply it anyway. It is the single change most likely to increase your enquiry volume this month.

3. Budget is the classic too-revealing field

The one that produces fiction.

Buyers believe stating a budget means being quoted up to it. The answers are therefore low, vague or absent, and the field costs submissions to collect unreliable data. Publishing a range and asking whether it works gets you a truthful answer in the conversation instead.

4. Timescale is frequently not yet knowable

The unanswerable category.

Somebody at the research stage genuinely does not know when they will proceed. Forcing an answer produces a guess that then misleads your own prioritisation. An option meaning not sure yet rescues both the enquiry and the accuracy of your data.

5. Company name and job title deter individuals

The relevance failure.

A field implying a business context makes consumers hesitate, and one implying a large organisation deters sole traders. Both eliminate people you wanted.

6. Address at first contact feels premature

The privacy reaction.

For anything involving a visit it will be needed, and not yet. Asking for it before any relationship exists reads as excessive and is easily left until the conversation.

7. Anything marked required raises the stakes

The mechanism behind all of it.

An optional version of the same question costs almost nothing and is completed by a substantial proportion. Required status is what converts a mild reluctance into an abandonment.

8. Test by making them optional rather than removing them

The safer experiment.

You keep the data from those willing to give it, you stop losing those who are not, and you learn the real completion rate for each field.

9. Watch for answers that are obviously invented

The data quality check.

Repeated placeholder values, round-number budgets, implausible timescales. These indicate a field people are answering to get past rather than to inform you, which is worse than not asking.

Be careful about collecting more personal data than the enquiry requires. Every field creates obligations to protect, justify and retain the information, and asking for less is both a compliance improvement and a conversion one.

Conclusion

Identify which of your fields are too committing, too revealing, unknowable or irrelevant.

Make phone number optional, give a price range instead of asking for a budget, avoid forcing a timescale people cannot know, remove company and job title fields that deter individuals, leave address until after contact, prefer optional to required wherever possible, test by making a field optional rather than deleting it, and watch for placeholder answers that indicate a field is being answered rather than completed.