On form after form, the sharpest single drop is at the phone number field. Not the longest question, not the hardest one. The one that takes four seconds to answer.
That should tell you something immediately, because difficulty is clearly not the issue. Everybody knows their phone number. The people leaving are not stuck. They are declining.
Understanding why turns a fight about a field into a decision about what the form is for, which is a much more useful conversation to have.
What a phone number means to the person giving it
An email address is a letterbox. Things arrive, you look at them when you feel like it, and if they become annoying you stop opening them. The cost of giving one out is low and everybody knows it.
A phone number is a doorbell. It rings when the other person chooses, wherever you are, and ignoring it takes active effort. People have been trained by a decade of unwanted calls to treat handing one over as a decision with consequences.
So when a form asks for a phone number, it is not asking for a piece of data. It is asking for permission to interrupt. That is a much bigger request than the size of the field suggests, and people price it accordingly.
An email address is a letterbox. A phone number is a doorbell.
Why it is usually on the form
Ask why the field is there and the honest answer is rarely a specific plan. It is there because the CRM has a column for it, because the last form had one, or because somebody in sales said calling converts better than emailing.
That last point is often true and it is not the whole story. Calling converts better among people who wanted to be called. It converts worse than nothing among people who gave a number reluctantly to get past a required field, and it produces a measurable amount of irritation that never shows up in any report.
The number you are not seeing is the people who did not submit at all. They are not in the CRM, so they do not appear in the comparison, and the comparison quietly looks better than reality.
The three states of a phone field
There are only three options and the middle one is almost always right, yet it is the least used.
Required is the most expensive. Every person who will not give a number is lost entirely, including people who would have been excellent customers over email. Optional is nearly free. The people who want a call still give it, the people who do not still submit, and you get both.
Absent is the right answer more often than people expect, particularly on top-of-funnel forms where you have no intention of calling anyone for a fortnight anyway. A field you never use is pure cost.
- Required: the most expensive option. Reserve it for forms where you genuinely cannot deliver without calling.
- Optional: nearly free, and it doubles as a qualification signal.
- Absent: correct whenever you would not actually pick up the phone within a week.
Optional is also a qualification signal
This is the part people miss. When the field is optional, whether somebody fills it in becomes information.
A person who volunteers a phone number on an optional field is telling you they want to talk. That is a warmer lead than one who typed a number because a red asterisk made them. You have effectively sorted your submissions into call these and email these, for free, without asking anybody an extra question.
Make that explicit if you like. A label along the lines of phone, if you would rather we call, converts the field from an extraction into an offer. People respond very differently to being offered something than to being asked for it.
Say why, in six words
When you do need a number, the single most effective change is a short line under the field explaining what it is for. Not a privacy policy. Six words.
So the driver can find you. To confirm your appointment time. Only if there is a problem with your order. Each of these transforms the field from an open-ended claim on your attention into a specific, bounded use.
It works because the fear is not the number, it is the unknown. A stated purpose removes the unknown, and the drop-off at that field falls noticeably without you removing anything.
Then actually honour it
This part is not optional and it is where most of the damage gets done. If the field says the number is for delivery coordination and it ends up in a sales sequence, you have not gained a lead. You have taught somebody that what your forms say cannot be relied on.
Under UK and EU data protection rules you are also required to use personal data for the purpose you stated, so the honest version is the compliant version. That is a rare and convenient alignment, and it means you can write the line without checking with anyone.
Practically, this means the number needs to land somewhere with the stated purpose attached, and whoever runs your outbound needs to know the difference between a number given for a delivery and a number given for a sales call.
Validation makes it worse
A phone field that rejects valid numbers is the worst of both worlds. You have paid the trust cost and then refused the answer.
Strict formatting is the usual cause. Rejecting spaces. Rejecting a plus sign. Demanding exactly eleven digits, which breaks for anybody outside your country and for several perfectly ordinary numbers inside it. These rules get written once by somebody thinking about a single market and then quietly lose submissions for years.
Accept anything that could plausibly be a phone number and clean it up on your side. The person typing has better things to do than guess your format, and every rejection is a chance for them to reconsider the whole exercise.
The forms where it genuinely belongs
None of this means the field is always wrong. There are forms where a phone number is the point, and treating it as a conversion tax on those is its own mistake.
Anything with a driver, an engineer or a delivery attached needs one, and everybody knows it, so nobody objects. Bookings where a slot might move need one. Emergency and same-day services need one, and asking for it first is correct there because speed is the entire promise. Medical, legal and financial intake often need one for reasons the person already understands.
The pattern is that the number is required by the delivery of the thing, not by your pipeline. When that is true, people give it without hesitating, and the drop-off at the field is close to nothing. If you are seeing a sharp drop, that is evidence the person does not think your form is one of these.
What the rules actually require
There is a widespread belief that collecting a phone number needs a special legal basis or a tick box. It does not, in the ordinary case. Under UK and EU data protection law you need a lawful basis to process it, and for somebody asking you to quote for work, the legitimate interest of replying to their enquiry covers a reply.
Where it does change is marketing. Calling or texting someone about something other than the thing they asked about is a different activity with its own rules, and consent for that is separate, specific and cannot be bundled into the act of submitting an enquiry form. A pre-ticked box is not consent anywhere in the UK or the EU.
None of this is onerous, and the practical version is short: use the number for the reason you gave, keep it no longer than you need it, and get a separate, unticked opt-in if you want to use it for marketing later.
The international problem
If any of your customers are outside your own country, a phone field designed around one national format will quietly fail them. British mobile numbers begin with a zero that disappears when written internationally. American numbers are ten digits. Some countries have variable lengths within the same network.
The pragmatic answer for a small business is not an elaborate lookup. It is a plain text field that accepts digits, spaces, brackets, hyphens and a leading plus, with a placeholder showing the format you expect rather than a rule enforcing it. You can normalise on your side in a few lines, and the person typing never has to think about it.
If you do add a country selector, default it to wherever most of your customers are and let people change it. A selector that defaults to alphabetical order and puts Afghanistan first is a small daily insult to everybody who uses your form.
What happens to the number afterwards
A phone number is one of the more sensitive pieces of data a small business routinely holds, and it tends to end up in more places than anyone intends. The form tool, the CRM, a spreadsheet somebody exported in March, an email thread, a phone contact list, and occasionally a shared document nobody has looked at in a year.
That spread is the real risk, more than any single system being breached. When somebody asks you to delete their data, or when you are required to, you can only honour it in the places you know about. Keeping the number in one system and referencing it from the others is unglamorous and it is the difference between a five minute job and an afternoon.
Deletion deserves a decision rather than a default. Enquiries that went nowhere do not need a phone number on file two years later, and holding one is all cost and no benefit.
A note on the second phone field
Some forms ask for both a mobile and a landline, or a daytime and an evening number. This is almost always a relic of a paper form, and it doubles the trust cost for information you will never use.
Ask for one number. If the distinction genuinely matters, ask the question that matters instead, which is usually when it is best to reach somebody rather than on which device. A single field plus a best time to call option gets you more useful information than two fields and costs less.
The same applies to alternative contacts, next of kin fields and anything else inherited from a printed version. Every field on a form should be there because somebody decided it should, not because it was on the last one.
What to use instead
If the underlying need is speed, there are options that cost less trust than a phone number.
Ask for the best time to reach them and let them pick a slot, which converts the call from an ambush into an appointment. Offer a choice of contact method and let them choose. Or simply put a calendar link on the confirmation page, so the people who want to talk can book without you chasing anybody.
Each of these gets you the conversation with people who wanted one, and none of them costs you the submissions of people who did not.
What to change today
Open your main enquiry form. If the phone field is required, ask honestly whether you would genuinely rather lose the enquiry than lose the number. For most businesses, on most forms, the answer is no.
Make it optional. Add six words explaining what it is for. Loosen the validation so it accepts anything sensible. That is fifteen minutes of work and it is usually the single largest completion improvement available on an established form.
Then look at what people do. If most of them still give a number, you have lost nothing and gained a signal. If most of them do not, you have just learned something important about your audience that a required field was hiding from you.