Top handyman services online booking: no calls

A homeowner does not think in trades. They think in jobs: the tap that drips, the door that sticks, the television that needs a bracket. A booking page built from the trade's own categories asks them to translate first. General repair, mounting and assembly sound alike, so the visitor picks one at random or closes the tab and calls. The address step adds a second wall. If a postcode is rejected with only the words not available, the visitor cannot tell whether the handyman is too far or the form is broken. Both end in a phone call the booking was meant to replace.

• Does the list use job words, such as dripping tap, rather than trade categories?
• Is there a describe the job option for anything that does not fit a category?
• When a postcode is outside the area, does the page list the areas it covers?
• Does the form ask for the address only after the visitor sees a visit time?
• Does the confirmation say what happens next, without promising a phone call?

Trade categories show how the business sorts its work. A homeowner searching on a phone names the object that is broken, so the search is for a leaking tap or a bracket, not for mounting or assembly. If the booking menu uses trade words, the visitor has to match their problem to a word, and a bracket for a television may not look like mounting at all. Use the job as the label, put the most common jobs at the top, and group the rest under plain headings a thumb can scan.

Keep the describe the job option visible. A leaking tap could be plumbing or general repair, and a sticking door could be carpentry or repair. A box that asks for a sentence about the problem lets them book without choosing wrong. Test the menu with a simulated visitor who has one job and no idea of its trade. The run shows whether the first menu they open has the job, or whether they scroll and leave.

The second place a booking dies is the address. Some handymen work only inside a set radius. When the form rejects a postcode at the edge of that area, the better version lists the areas it covers and says what to do next. The worse version shows a red line that says not available and nothing else. A visitor a few streets outside the area cannot tell whether the form is broken, so they call to ask.

To separate the causes, enter one postcode inside your area and one outside it, on a phone, in a private window. If the inside postcode goes through and the outside one shows no list of areas, the message is the problem. If the inside postcode is rejected, the area rule or the map is wrong. If both reach the calendar but no visit time appears, availability is the cause. Each one needs a different fix, so note which one you see first.

Send one simulated visitor to the booking page with this task: Book a visit this week to fix a dripping kitchen tap. The visitor is a homeowner or renter with one small repair who wants a visit soon and books on a phone. Keep the job in the task and leave the trade out. A visitor told to book plumbing would pick plumbing, so the run would not show whether the page helps someone who does not know the word.

The test can reach the confirmation step. It cannot receive a text code, so a booking that needs one stops there. The confirmation email does reach the visitor's inbox, so check that it gives the visit time and the next step in plain words. Use made-up names and addresses, and do not type a real customer's address into a test.

The first run finds the menu or the message that sends the visitor to the phone. The fix changes it: job words, a describe option, and areas listed beside the postcode check. Run the same visitor again to see whether a visit time appears. Run it again when you add a service, take on a new area or change the booking tool, since a new postcode rule can bring back the message that ends in a call.