yodai Academy Build your website

Academy › Build › Create your website

Why I'm asking for this, before you even ask

You'll know how to write, in a line below each field that isn't self-explanatory, the real reason you're asking for it, so no one closes the tab out of suspicion.

By Yodai · Published on September 6, 2026 · Updated on October 12, 2026

4 min read

You're filling out a booking form. After your name and email, which you expect by now, up pops the phone number. Or the zip code. And even though it's just one more field, something shifts: you pause for a second and wonder why they'd need it. Are they going to call me to sell me something? Are they tracking where I live?

That doubt doesn't come up with the name or the email: you already know what those are for, every form in the world asks for them. It shows up exactly with the fields that don't explain themselves. And that's where someone closes the tab, even if the field was necessary, even if it was in the right spot, and even if it was last on the list, right where it should be.

A field that doesn't explain itself scares people

Asking for only what you need, and saving the awkward field for last, helps. But that's not enough when a field, even well placed, is the kind that catches people off guard. A phone number for a simple appointment, a zip code for a service that doesn't look local, a tax ID before you even pay: none of these explain themselves just by reading the label.

When a field doesn't explain itself, people fill in the blank with their own suspicion. And suspicion always imagines the worst: a phone list for endless sales calls, an address stored for who knows what. The real reason is almost never that, but if you don't say it, suspicion wins.

The rule for knowing whether you need that line is to put yourself in their shoes: if you'd wonder why they're asking for that piece of info, write it right next to the field. If the field is obvious, like the name or email, don't put anything underneath it. It's not needed there, and a form packed with explanations for everything starts to feel like a contract instead of a conversation.

The line, right next to the field that needs it
Phone number We'll only call if there's a last-minute change to your appointment. Zip code So we know whether we service your area. Tax ID This is just for your invoice, nothing else.

A common mistake is swapping that short line for a link to the privacy policy. On paper, it's more complete, but it doesn't answer what the person is wondering right then: why this field, not what the company does with all its data in general. And a link that opens a new tab is one tab that might never come back, leaving the form half filled out. That doesn't do away with the privacy notice the law requires: privacy law lets you give it in two layers, a short summary next to the form (who you are, what you'll use the data for, and that people can exercise their rights) and a link to the rest. That notice comes in addition to the line under each field, not instead of it.

The line goes right under the field, in small text, visible without clicking anything: no dropdown, no question-mark icon you have to tap, nothing that opens a new window on your phone. It's not a permission you have to request separately. It's an answer that's already there before anyone needs to ask, and that's why it works: it shows up right when the doubt is born, not a minute too late.

Explain every field, or only the one that raises doubt
A line under every field
  • The form reads like a document, not a conversation
  • Explaining the name or email field sounds like filler and makes the rest feel less credible
A line only where the doubt begins
  • Name and email get nothing extra: the label alone says it all
  • Phone number, zip code, tax ID, or any piece of info that catches people off guard gets its reason in one line

Which to choose: Add the line only where the doubt starts: explain only what a stranger would wonder about when reading it, and leave the rest clean. Switch to a line under every field, even the name, only if the business itself raises suspicion by its nature, like health services or legal paperwork; there, an extra line on each field reassures instead of feeling like clutter.

The costly mistake: justifying it from the business's side, not the person's
Writing "We need your phone number for our database" or "for exclusive offers" confirms the suspicion instead of easing it: it sounds like the data is for the business, not for the person giving it. The line needs to say what the person gets in return for typing it in: that they'll be notified if something changes, that the business can tell if it delivers to their area, that their invoice comes out right from day one. And if the real reason is purely internal (stats, marketing, a list to call later), then that field simply doesn't need to be on this form.
What you walk away with
  • Every field that doesn't explain itself gets its reason in one line, right underneath, visible with no clicks or links
  • Name and email don't need a line; phone number, zip code, or tax ID do
  • The reason is written from what the person filling out the form gains, not from what the business needs
  • If the only reason is internal, the field doesn't belong on this form
  • Up next: what the form says when someone makes a mistake filling it out

Yodai builds the site from what you tell it, with a store, bookings or quote requests depending on what you do. See what the website for your business looks like.

NextThe error message says what to type, not that something failed