Your “Contact Us” Page Is Quietly Losing Jobs

Owners will argue about logo size and homepage video before they look at /contact. That is backwards.

A Frisco HVAC shop can rank, run ads, and still lose the click on a form that asks for company name, job title, and “how did you hear about us?” before the homeowner can say “AC won’t cool.”

A Manila plumbing page can look busy on Facebook, send people to a site, and then ask them to fill eight English-only fields on a slow mobile connection — while a competitor is already replying on Messenger.

The contact page is not a formality. It is often the last step before a booked estimate. If it feels like homework, the urgent customer leaves.

One job only: get enough information to start a useful reply and a path to a calendar window.

It is not for:

• Collecting marketing survey data on first touch
• Proving your tech stack with twelve integration logos above the fold
• Filtering “tire kickers” with friction so hard that hot jobs bounce too

If you need qualification, do it in the reply or on a short second step after they commit. Do not charge an urgency tax on the first submit.

1. Too many fields. Name, phone or chat handle, service needed, location (city / barangay), and optional message is enough for most trades. Everything else is negotiable later.
2. Required fields that block mobile thumbs. Company name, website URL, budget dropdowns, and “best time to call” as required fields are classic job-killers on a phone in a driveway or on the MRT.
3. No “what happens next”. After submit, say when they will hear from you and how (call, SMS, Viber, Messenger). Silence after “Thank you” feels like a void.
4. Trust is nowhere near the button. License, insured, years in market, Google rating, service area — put one or two proof points beside the form, not buried in a footer.
5. Wrong channel for the market. DFW: phone + SMS-friendly form still wins a lot of work. Manila: if half your jobs start on Messenger or Viber, a contact page that only offers email is arguing with reality. Offer the channel they already use, or a click-to-message path, not only a long form.
6. Slow, broken, or captcha-heavy on mobile. If the page takes forever or fails on Android Chrome, you will never see those leads in the CRM. They just vanish.

Above the fold on mobile:

• Headline that names the service and area (“Book a plumbing estimate in DFW” / “AC repair visits in Metro Manila”)
• 4–5 fields max
• Primary button with a clear verb (“Request a window,” not “Submit”)
• One trust line under the button
• Click-to-call (and click-to-Viber/Messenger where it matters)

Below: service area, hours, emergency note if you offer it, and a short FAQ (“Do you charge for estimates?”).

Skip the essay. They already decided to reach out. Do not make them re-read your about page to finish the form.

DFW

• Click-to-call prominent
• SMS consent line if you text back fast (keep it plain-language)
• City / ZIP optional if phone is enough for first reply — or one “primary city” field for routing

Manila

• Messenger / Viber buttons next to the form, not hidden
• Location as city + barangay or landmark
• Language: clear English is fine; short Taglish labels help if that is how you already talk to customers

Do not build two unrelated sites. One contact pattern, channel options that match the metro.

A prettier form that emails a shared inbox nobody owns is still a leak. Connect:

• Form submit → CRM lead with timestamp
• Auto acknowledgment on the customer’s preferred channel when you can
• Duty owner for the five-minute useful reply
• Calendar or estimate slot that dispatch will honor

If you are tightening first-response time this month, fix the contact path in the same sprint. Fast replies to fewer, better-captured leads beat slow replies to a flood of half-filled junk.

Before a full redesign, baseline:

• Contact page mobile load (rough is fine — does it feel instant or sticky?)
• Form starts vs submits (if you can see it)
• Submits → first useful reply time
• Submits → booked estimates

Then remove two fields, add a “what happens next” line, and move one trust proof next to the button. Re-check the same numbers. Small changes here often beat a new homepage.

Your contact page should feel like the start of a job — not a committee application. Strip it to what dispatch needs, say what happens next, put trust beside the button, and respect how DFW and Manila customers actually message.

If you want a straight read on your live URL, run a free audit. We will mark the friction that is costing booked work and the fastest fixes before you spend on a rebuild.