Playbook

Local business chatbot: AI chat that books real jobs

A local business chatbot earns its keep by booking real jobs. Set your service area, job durations, price rules and emergency route before you go live.

Key takeaways
  • Give every service a real duration and a travel buffer, and have the assistant book only into slots that fit the whole job.
  • Write price rules as fixed prices or ranges with named conditions, and have the assistant book a site visit whenever a quote depends on something it cannot see.
  • Write your emergency route into the first reply and into the rules, so anything involving safety goes straight to a person or the right emergency service.

A local business lives or dies by the phone that rings at the wrong moment. The plumber is in a crawlspace, the salon is mid-balayage, the dentist is in the chair with a drill running. For years the answer was voicemail and a callback that arrived too late to matter. A local business chatbot can take that moment instead, but only if it’s set up around the way local work actually happens: travel between jobs, jobs of very different lengths, quotes that depend on a building nobody has seen, and the occasional emergency that can’t wait for Monday.

This playbook is for plumbers, electricians, cleaners, salons, clinics, garages, landscapers and anyone else who sells a service at a location or a visit. It explains what local visitors actually ask, how to build the booking rules before you touch the calendar, how to handle price and area questions honestly, and how to route emergencies. It ends with a walk through a single realistic evening so you can see the rules working together.

The questions local customers actually type

Local visitors arrive with a short list of questions, usually in a hurry. They want to know whether you cover their area, whether someone can come soon, roughly what it will cost, and whether a specific detail is acceptable. They rarely want your history or your values statement.

The common ones read like this: “Do you cover the north side of town?”, “Can someone come today?”, “How much to replace a water heater?”, “Do you do Sunday callouts?”, “Is my dog allowed in during the visit?”, “Do you take my insurance?” Each one is short, specific and time-sensitive. A visitor who gets a vague answer will usually call a competitor who sounds more certain.

That’s the opening for a well-built assistant. It can answer the coverage question from a list of places you serve, the availability question from a calendar with real durations, and the price question from rules you’ve written down. The first reply should give a visitor enough to decide, and a clear next step to commit. Where it can’t do that, it should say so and offer a route to a person.

What a local business chatbot needs before the calendar

The most common local booking failure isn’t a technology problem. It’s a rule that nobody wrote down. The calendar says “one-hour slot,” the job takes two hours, and the crew arrives at the next customer’s door still halfway through the last one. The assistant didn’t cause that mistake, but it will repeat it faster than a receptionist would if the rules aren’t there.

Before you connect anything, write the following for every service you sell:

  1. The real duration. Measured from the time the crew leaves the van to the time they’re packed up, not the time they’re expected to spend on the work.
  2. The travel buffer. How long it takes to get to the next job, which depends heavily on the area and the traffic at that hour.
  3. The lead time. How far ahead a job must be booked, and whether same-day work is possible at all.
  4. The same-day cut-off. The latest time a same-day booking can be accepted, and the reason for it.
  5. The area. The places you serve, and the places you don’t.
  6. The capacity. How many jobs of each type a day can realistically hold, including the time you need for paperwork and parts runs.
  7. The exclusions. Jobs the assistant must never book automatically, such as large renovations, anything structural, and anything involving gas or live electrics.

Here is an illustrative set of rules for a mobile plumbing firm. Your figures will differ, but the structure is what matters.

Job type Typical duration Travel buffer Booking rule
Boiler service 90 minutes 30 minutes Book into morning or early afternoon slots; same-day allowed only before noon
Drain clearing 60 minutes 30 minutes Book same-day if a van is in the area; otherwise next available
Radiator bleed or small repair 30 minutes 20 minutes Can be added to the end of a day’s run with spare capacity
Bathroom refit Several days Not applicable Never book automatically; book a free site visit first
Leak or water emergency Varies Not applicable Route to the emergency line at once; never book into the queue

The table shows the principle. A quick job can fill a gap. A long job needs a clear window. Anything that’s really a project shouldn’t be booked at all without a visit. The assistant should be able to work out, from the job type and the calendar, which of these applies, and offer a slot only when the whole job plus the travel fits.

One crew's day, with travel built in 8:00 9:00 10:00 11:00 12:00 13:00 14:00 15:00 16:00 17:00 Crew A Boiler service Drain clear Radiator Crew B Site visit Callbacks held Urgent Solid block: booked job. Dashed block: travel or held capacity. Times are illustrative. Each block includes the buffer the rules require.
A crew's day with the travel buffers and held capacity written into the schedule, so the assistant never offers a slot that doesn't fit.

Price questions without promises you can’t keep

Price is the question local visitors ask most and the one that causes the most trouble when answered carelessly. The right answer depends on the job. Some services have a genuinely fixed price. Others vary with the building, the access, the materials or the scope, and a number given too early becomes the number the customer expects at the end.

Sort your prices into three kinds. A fixed price is quoted exactly, with what it includes: “A standard boiler service is a fixed price for most homes in our area, and it includes a safety check and a written report.” A range is quoted with the conditions that move it: “A drain clear usually sits between the basic and the extended price, depending on how far the blockage is and whether we need to access an outside drain.” A variable price is not quoted in chat at all. Instead, the assistant offers a free visit: “Replacements depend on the boiler, the flue and the access, so we’d book a free visit to quote it properly.”

The discipline is in not drifting from one category to the next. An assistant should never invent a number to be helpful. A visitor who hears “about $200” for a job that turns out to need $900 of parts will remember who gave the first number, and they won’t remember the conditions that were attached to it.

Write the price rules as conditions, not adjectives: "$85 for a standard service, plus $20 if the boiler is outside the main house" is clear and checkable. "Reasonable rates depending on your needs" is neither, and the assistant will simply make it up.

Say your service area in words

Area questions look simple and cause expensive mistakes. A booking outside your area can cost a crew half a day, and a visitor who is turned away after a confirmed appointment will be angry. Write the coverage down as a plain list of places, plus a clear rule for the edges: “We cover the town and everything within about fifteen miles of the centre. For anywhere beyond that, we’ll check the travel time before confirming.” Postcodes or neighbourhood names work well, because visitors use them when they search.

The assistant should ask for the postcode or the nearest landmark before offering any slot. If the visitor is outside the area, it should decline politely, explain the boundary, and offer something useful: a referral to a partner business, a note in the waiting list, or a reminder to get in touch if you expand. A refusal with an alternative is far better than a confirmation that has to be unpicked later.

Edge cases need an explicit rule too. Some businesses cover a larger area for a bigger job, or charge a travel fee beyond a certain distance. Put that in the rules, so the assistant can explain it rather than improvising a boundary.

Emergencies come first

Local services sometimes receive messages that involve immediate danger. A gas smell, a flooded floor with a live electrical fitting nearby, a child who has swallowed something, or a sudden loss of heat in a home with a vulnerable person in it. None of these belong in a booking queue, and an assistant that tries to schedule one is doing harm.

Write the emergency route into the rules and into the first reply. The assistant should recognise the common phrases that signal danger and respond immediately, with the instruction to contact the emergency service that’s appropriate for the situation. For a gas smell, that generally means leaving the building, avoiding switches and flames, and calling the emergency line for your gas network from outside. For a medical emergency, the instruction is to call emergency services directly. The assistant should not try to triage the situation beyond that.

Keep the emergency route visible on the page as well. A visitor who is frightened shouldn’t have to find it in a chat.

Never let the calendar book by job type alone: a two-hour re-pipe booked into a one-hour slot starts a bad day for your crew and ends with an angry customer. Booking must check the full duration, the travel buffer and the capacity for the day.

When a person has to take over

Some situations need a person even when they aren’t emergencies: a complaint about a previous job, a request for an exception, a question about an insurance claim, or a visitor whose access needs are complicated. The assistant should hand these off, and the handoff should turn into something useful rather than a dead end.

The best option is usually a callback in the next working window, or a booked site visit where the person can see the problem. Capture the details that matter for the work: the property type, the nature of the problem, access notes such as parking or a gate, and a preferred time. Avoid collecting anything you don’t need. A gate code or a key-safe location may be necessary for a visit, but it should go into a secure channel and not sit in a chat log.

Be honest about the response window, as with any handoff. “Someone from our office will call you back before noon tomorrow” is a promise you can keep if the rule is written down and staff know about it. “They’ll be with you shortly” is not.

A realistic evening

Here’s how the rules come together on an ordinary Wednesday, with the details illustrative.

At 7:12pm a visitor on a local plumbing firm’s site types: “Can you do a drain clear tomorrow morning on the north side? It’s been backing up since this afternoon.” The assistant recognises a drain job, checks the coverage list and finds the north side inside the service area. It checks the rules: a drain clear takes about an hour, plus thirty minutes’ travel. It checks the calendar for the next morning and finds two open windows, one from 8:30 and one from 10:00.

The assistant doesn’t offer the 8:30 slot straight away, because the rules say same-day work needs a van in the area, and tomorrow isn’t same-day yet. It offers the 8:30 and 10:00 slots, asks for the address and a contact number, and asks whether there’s anything about access the team should know. The visitor says the drain is in the back garden, and there’s a side gate that’s usually locked.

The assistant records the gate note, confirms the booking details in full, and reads them back: “Tomorrow, Thursday the fifteenth, at 8:30 in the morning, for a drain clear at the address you gave, with the side gate noted.” The visitor confirms. A written summary goes to the dispatcher and to the visitor. The rules have done their job: the slot fits, the area is right, the access is noted, and nothing has been promised that the crew can’t deliver.

Now imagine the visitor had written, “There’s a strong smell of gas in the kitchen.” The assistant should not have offered any slot at all. It should have told the visitor to leave the building, avoid switches and flames, and call the gas emergency line from outside, as its first reply and in clear words. That’s the difference a well-written route makes.

What to measure after launch

Measure what matters to the schedule and to the customer. Track bookings per week, and check how many fit within the buffer and duration rules, because a booking that overruns is an early warning. Track how often the assistant hands off, and what the handoffs are about. Track no-shows and cancellations, and whether they cluster around particular job types or time slots. And read a sample of conversations each week, looking for quotes the assistant gave too confidently and emergencies it may have missed.

Those numbers will tell you where to tighten the rules. A rise in overruns usually means a duration is wrong. A cluster of handoffs about one job type usually means a price rule is unclear. A missed emergency is the one result you should treat as urgent, and the fix is the first reply, not a quiet adjustment.

Start small and keep the rules honest

A local business chatbot is only as good as the rules behind it. Start with three or four services, each with a real duration, a buffer, a price rule and an exclusion list. Launch on the page where local visitors book, read every conversation for the first two weeks, and widen the scope once the rules hold up.

Voxy books appointments into your calendar, answers from your own content, and brings in your team when a person is needed, in nine languages. Start with the live demo to see a booking conversation, and read how after-hours support can run without a night shift if most of your urgent enquiries arrive in the evening. You can also see how AI booking into a calendar works before deciding what to switch on. When you’re ready to test it on your own site, try Voxy free for 14 days, no card required.