HVAC repair website: why visitors don't call

The person who finds an HVAC site during a heat wave is not shopping. They have a unit that blows warm air, a house that is getting hotter, and maybe a child or an older parent at home. They search from a phone, tap the first result, and look for a number they can call in one tap. If the booking calendar opens on a date a week away, or the service area leaves out their suburb, the visitor assumes you will not come. They often try the next result. The owner rarely sees this, because the owner already knows the town is covered.

• Is a same-day or emergency option visible before the visitor picks a date?
• Does the service area list include the suburbs you actually drive to, or only the main city?
• Is the phone number at the top of the phone screen and a tap that starts a call?
• Does the form accept a typed town that is not in the dropdown, or stop with no next step?

The first thing a stranded homeowner looks for is a phone number, and they look for it at the top of the screen. The second is the town. They check whether their suburb appears in the service area, and many sites list only the main city, so a neighboring suburb reads as not covered. The third is the calendar. A visit offered only from next week tells the visitor to call somewhere else, even if you could send a technician that afternoon.

You will not see this from inside. You know the suburbs you cover, and the number is on every page. Test it the way the homeowner arrives. On your phone, in a private window, search your own service with the words a customer would use, then open the first result. Count the taps before a phone number and a town are both visible. If the count goes past two, or a suburb you cover is missing, that is the first thing to fix.

A common form failure on these sites is a service area field that only accepts the towns in its dropdown. The visitor types a suburb, the dropdown shows no match, and the field either refuses to continue or clears the entry. The visitor has no way to say nearby and no sentence telling them what to do. A homeowner in a town you do cover can leave believing that you do not cover it.

The second failure is order. Some booking forms ask for the system type, the problem and an appointment window before they show any time. If the first open window is two days out, a visitor with no cooling sees two days and calls someone else. The cause sits in the booking, not on the phone line. Compare the first open time with the first question on the form, and note which one a visitor meets first.

Send one simulated visitor from your homepage with this task: book the earliest visit for an AC unit that is not cooling. The visitor is a homeowner searching from a phone in a nearby suburb, unsure whether you cover it. Put the suburb in the visitor profile, not in the task, so the run meets the service area list the way a customer would. Keep the task about the visit and leave the diagnosis out.

The run follows the visitor through the service area, the problem list, the calendar and the booking form. It stops at a text code, a card payment or a sign-in with Google, and the report names that step. A booking that asks for a deposit ends at the payment step. If the run stops at the service area, add the suburb to the list or let it be typed, then send the same suburb through again on a phone.

Why visitors leave a page

Each season brings a new promotion, a new calendar and sometimes a new technician schedule, and any of them can push the same-day option below the first screen. Rerun the same suburb after each change, and again when you add a service area. If booking sits behind a customer login, run the visitor with a test account, and check each preview of the site before it goes live.