A Contact Form That Gets Replies: Fields and Setup

A contact form that turns into jobs asks for five or six things at most: name, phone number, town or ZIP code, what the person needs, and an optional photo. Every field has a visible label, the phone field brings up the number keypad, and every request goes straight to a phone you carry. Then you reply the same business day, and you stop spam without making real customers solve puzzles.

Most small business forms fail on one of those points, and usually quietly. The owner never sees the requests that didn't arrive.

Which fields, and how few

Every field you add is one more reason to give up on a small screen. The Nielsen Norman Group, which studies how people use websites, puts it plainly in its guidelines for web forms: "Every time you cut a field or question from a form, you increase its conversion rate."

So start from one question: what do you need to make the first call back? For most local businesses, that's:

Name
Phone number, required, because that's how you'll reply
Email, optional
Town or ZIP code, so you know right away whether they're in your area
What they need, as a short list to tap, plus a message box
Photos, optional

Leave out what you can learn on the call: the full street address, their budget, how they heard about you. One extra often earns its place, though: a choice between "Call me" and "Text me." Plenty of people at work can't take a call but will answer a text within minutes.

NN/g also advises keeping optional fields to one or two and labeling them clearly as optional. If most fields are required, mark the optional ones instead of putting a red star on everything else.

What changes by business

Plumber or HVAC: add "How soon?" with three choices: today, this week, or just planning. It tells you who to call first.
Contractor: add rough size and "When would you like it done?" Photos matter most here.
Restaurant: the form is for catering and private events, not tables. Ask for the date, the number of guests and whether it's lunch or dinner. Table reservations belong in a booking system that shows open times.
Salon: service, preferred stylist, new or returning client, and preferred days. If you take online bookings, put that button above the form and keep the form for questions and group or bridal bookings.
Shop: what they're looking for, and whether they'd like you to hold it or order it.

Make it easy on a phone

Small details decide whether a form takes thirty seconds or three minutes on a phone.

Labels that stay visible. Put each label above its field. Gray hint text inside the box disappears as soon as someone starts typing, and halfway through they forget what the box was for.
The right keyboard. The phone field should open the number pad, the email field a keyboard with the @ key. That's one setting per field.
Autofill. Browsers can fill in a saved name, phone and email with one tap. Google's web.dev guide to autofill says "Autofill makes filling out forms faster and easier," and explains the settings that let browsers offer it. Ask whoever builds your site to turn them on.
One column. Fields stacked top to bottom, one under the other. No side-by-side boxes on a phone.
Errors that make sense. If something's missing, say which field and what's needed, right next to it, and keep everything else the person already typed.
A send button that says what happens. "Send my request" tells people more than "Submit."

Photo uploads

For a trade, a photo is often worth more than the message. The leaking valve, the cracked foundation wall, the hail damage, the kitchen as it is now. You see the job before you drive out, and sometimes you can tell the person it's a quick fix, or kindly, that it's not work you do.

Let people choose a photo or take one. On a phone, a photo field opens both the camera roll and the camera.
Allow several photos, and say how many: "Up to 5 photos."
Expect big files. A photo from a recent phone can be several megabytes. The form should shrink photos before sending, or at least accept large files without failing at the last step.
Test with an iPhone. iPhones usually save photos in a format called HEIC. Make sure your form, and the email it sends you, handle those files, so you don't receive an attachment you can't open.
Keep photos optional. Someone with water on the floor shouldn't be stopped by a required upload.

Where the messages should go

A form is only as good as the place it sends to.

To the phone you carry. An email to the inbox you read on your phone, and if you can set it up, a text alert as well. Not to an info@ address that forwards somewhere nobody remembers.
To two people, if you have two. The owner and the office, or two partners, so a request still gets seen when one of you is up a ladder.
With the customer as the reply address. When you hit reply on the notification, it should go to the customer, not back to your website.
Out of the junk folder. Form notifications often look like spam to email providers, especially when the website sends them "from" an address it isn't allowed to use. Have email set up properly for your domain, and check the junk folder during the first week.
Saved somewhere besides email. A copy of every request in a list, a spreadsheet or a simple CRM, so a deleted email doesn't mean a lost job.

Then test it. Send yourself a request from your phone, on mobile data, with a photo attached. Do it again once a month and after every change to the site.

Reply speed

Someone who fills in your form may well be filling in the same kind of form on other sites, especially for bigger jobs where people collect several quotes. The business that answers first gets the first real conversation.

Say on the form when you'll reply, and keep it. "We call back the same business day" is a promise. Pick one you can keep in your busiest week, not your quietest.
Show a clear thank-you message after sending, with that promise and your phone number for anything urgent.
Send the customer a copy of what they sent, by email or text, so they know it went through and have your number saved.
After hours, send an automatic text saying when you'll call. It keeps people from moving on to the next company overnight.

Form spam basics

Every form on the internet gets spam. Bots fill it in with links, fake offers and nonsense. A few quiet measures stop most of it without asking real customers to do anything:

A hidden trap field. A box people can't see but bots fill in. Anything that arrives with it filled in gets dropped.
A time check. A person needs at least several seconds to fill in a form. A submission that arrives one second after the page loaded is a bot.
An invisible check, such as Cloudflare Turnstile or Google reCAPTCHA, which scores the visitor in the background. Skip the versions that make people click every traffic light. They cost you real requests.
Checks on the server, not only on the page, so bots that skip your page and post straight to the form still get filtered.

Don't let a filter delete anything silently. Send suspected spam to a separate folder and look through it once a week. Now and then a real customer pastes a link or types in a hurry, and you don't want to lose that job to a filter.

Keep the phone next to it

A form works alongside the phone, not instead of it. Keep a tap-to-call button beside the form for people who'd rather talk. Real jobs in your own photos help people decide to send that form in the first place, and our guide to job photos that win work covers what to shoot. On our websites for contractors, the request form takes the job type, rough size, a ZIP code and photos straight from the phone, all in one message.

To see where your current form stands, run our free website checker. It looks for a quote or contact form on your home page or contact page, or a link to a booking or request tool, and checks your tap-to-call link and Google's mobile speed test at the same time.