When the AI should hand a booking to a person

Which requests should never be settled by the AI alone?

Anything that needs judgment, a promise, or care for the customer's feelings. Routine bookings follow your rules. These don't.

Hallucination is the term for an AI response that presents false or misleading information as fact¹. When a request is unusual, there's no rule for the tool to follow, so a wrong answer is more costly. That's the moment to stop.

What counts as an odd job?

A job that doesn't match any service on your list. A plumber's tool knows "blocked drain" and "hot water service". It won't know what to do with a request to look at a cracked retaining wall. Nobody can say what's causing it yet.

Odd jobs need a person because:

• the time needed is unknown
• the right staff member is unclear
• the price may depend on a look first
• you may not want the job at all

Have the tool collect the basics (name, contact details, what the job is, where, photos if you accept them) and then pass it on. It shouldn't promise a time or a price.

What about complaints?

Always a person. Someone who writes "my colour was uneven last week" or "the tradesperson left a mess" wants to be heard, not processed.

An AI that offers a new booking in reply to a complaint can come across as dismissive. Even a polite, accurate answer can make things worse.

The tool's only job is to recognize that it's a complaint, say that a person will follow up, and pass on the whole message. Set a realistic time for the reply and stick to it.

What counts as urgent?

You decide, and you write it down. For a trade it might be flooding, a gas smell, or no power. For a salon or studio it's rarer, but a customer stuck outside the door or a last-minute clash for a big event might count.

The tool should react to urgent words by:

• telling the customer to call your phone number, if it's staffed
• pointing them to the local emergency number for real emergencies
• alerting a person at once, by text or call, not only by email

This site covers front-desk work. For anything involving someone's health or safety, the tool shouldn't try to judge the situation. It should send the person to the right emergency service.

What other cases need a person?

• price negotiation, discounts or refunds
• requests to waive a cancellation fee
• bookings for a large group or a special event
• customers who say they have a disability or access need, so a person can plan properly
• anyone asking to speak to a person, at any point
• the tool being unsure what the customer wants after two tries
• a customer who is upset, confused or repeating themselves
• bookings that need a legal, safety or insurance judgment

That list isn't complete. Add to it as you read real conversations.

How should the hand-over work?

Phone menus called IVR systems are automated systems that gather information and route calls to the appropriate recipient². A booking tool should do the same job: gather the details, then send them to the right person.

A good hand-over has four parts.

First, the tool tells the customer plainly. "I'll pass this to Sam, who can help with that." It shouldn't pretend to be human or imply it's still working on the problem.

Second, it passes the full conversation. The customer shouldn't be asked the same questions again.

Third, a named person is responsible. A shared inbox nobody watches is a dead end. Decide who covers it each day, and who takes over when they're away.

Fourth, there's a deadline. If nobody picks up a hand-over within your set time, the tool should alert someone else.

Should customers always be able to ask for a person?

Yes. Chatbots and virtual assistants have been added to scheduling software for automated customer interactions and self-service booking³. They're an option for the customer, not a wall.

Put "talk to a person" in the first message or the menu, and make sure the tool honours it straight away. Test it before launch. Ask the tool a few awkward questions and see whether it hands over or bluffs. Then look at the booking rules you set, and add the cases you found.