4 min read

Requested or confirmed? Getting bookings right with AI

Why a good assistant requests a slot rather than promising one, and how to design the handover.

The fastest way to lose a customer is to confirm an appointment you cannot keep. When an AI assistant handles bookings, the difference between a requested slot and a confirmed booking needs to be designed in from the start.

Two different promises

• A requested slot says: this time suits the customer, and the team will confirm.
• A confirmed booking says: someone will be there.

Your calendar rarely tells the whole story. Travel time, the job before, parts on order and staff availability all affect whether a slot really works. Until those checks can be made reliably, the assistant should request and a person should confirm.

Design the handover

• Show the team everything the assistant collected, so nobody asks the customer twice.
• Make confirming or proposing another time a single action.
• Tell the customer clearly that their slot is requested, not yet confirmed, and when they will hear back.
• Measure how long confirmation takes; a slow handover undoes a fast first reply.

When to automate confirmation

Automatic confirmation can make sense for simple, predictable appointments where the calendar is the single source of truth. Agree the rules in writing, test them against awkward cases such as double bookings and cancellations, and keep a way for staff to step in.