Plumber booking website: why customers drop

Plumbing customers book in a hurry. Water is on the floor, or a fixture has been dripping all night, and the person searching would rather call a number than fill in a form. When they do use the form, they meet a job list written in trade terms: drain service, water heater repair, fixture installation. A leaking faucet may match none of them. Then the address field wants a street picked from a suggestion list, and the time slots appear only after that. Each step asks for something the customer has to stop and think about.

• Does the job list include the words people use, such as leaking faucet, clogged drain and no hot water?
• Does a typed address work when the suggestion list shows nothing close to it?
• Do the first open times show before the address and the contact fields?
• Does a text code reach the number typed on that same phone, and can a customer fix a wrong number?

Customers often arrive with a symptom, not a trade. They know the sink drips, the toilet keeps running, or the shower pressure fell. The booking tool, though, often asks them to pick from categories like service call, repair or installation. A running toilet can sit under repair, under drain, or under nothing at all. A customer who cannot match the symptom to a category has to guess, and a wrong guess sends them to a time that does not fix the problem.

The owner cannot see that gap, because the owner knows the trades by heart. Read your job list aloud as a renter would, one item at a time, and mark each item where a customer could not find their symptom. Then check the phone screen. A list that scrolls inside a small box is hard to read with one thumb, and a customer may pick the first item without reading the rest.

Many booking forms ask for an address and then accept only a choice from a suggestion list. If the list shows nothing close to what the customer typed, they cannot continue. Some forms clear the field when the customer taps away, and the customer starts again. The cause sits in the address step, not in the plumbing. Test with an address that has an apartment number, and one written the way a customer would type it.

Phone verification is the other stop. A form that sends a text code makes the customer wait for a message, and a code sent to a wrong number, or a field that rejects a number with a country prefix, ends the booking with no way out. A simulated visitor cannot receive a text, so the run stops at that step, and the report says so. Test that step yourself, on your own phone, over a mobile network.

Send one simulated visitor from your homepage with this task: book a plumber for a dripping kitchen faucet this week. The visitor is a renter searching on a phone for someone to fix a leak, who wants the earliest slot. Put the symptom in the task, since a renter describes the leak, not the job code. Leave the address out of the task and let the visitor type a made-up one into the form.

The run follows the visitor through the job list, the address, the time slots and the contact fields. It stops at a text code, a card payment or a sign-in with Google, and the report names the step. A booking that takes a deposit ends at the payment step. If the run stops at the address step, retype a street with an apartment number and send a renter through again on a phone.

How a checkout flow test works

Booking tools get updated, service areas grow and new job types get added, and each change can reset the address check or the code step. Rerun the same renter after each update, and after you add a town or a job type. If customers book through a portal behind a login, run the visitor with a test account, and check each preview of the site before it goes live.