What is the difference between a request and a booking?
When a caller names a service and a preferred day, I treat that as a request. Your team still needs to decide whether it can accept the work. We name the person doing that review and the place the request will wait. I want the caller and your staff reading the same status: scheduling still needs confirmation. Otherwise, you can have a perfectly readable note sitting untouched while the customer thinks an appointment is coming.
A booking means the supported calendar workflow completed the reservation. I will ask which behavior you need configured. Saying the assistant handles appointments tells me too little. Does a person still have to finish scheduling after the call? That is the question I want settled before you rely on the calendar.
Will it work with the calendar I use now?
Bring me the calendar you use and show me how you schedule work now. I need to check support for that calendar, the appointment types, the people who can take them, and the hours you actually offer. Direct booking requires a supported connection that passes testing. The calendar's name alone does not settle it.
Tell me who changes availability, which commitments already occupy the calendar, and what must appear in a reservation. I map the setup against that work. If the connection cannot support what you need, request capture still has a job: record the preferred time and leave your team responsible for confirming it.
What needs to pass before booking goes live?
I test availability, time zones, conflicts, and what happens when the connection fails. An empty block on a screen does not prove the booking works. We also check appointment length and any travel allowance against your rules. I want the reserved time to fit the work your business is being asked to do.
Put existing commitments and unavailable times into the test. Ask for a slot the assistant should not offer. Then choose an acceptable appointment and inspect the calendar. I want to see the reservation in the right place and hear wording that matches its saved status. The spoken answer and the calendar must agree.
What happens if the calendar connection fails?
We decide what a failed calendar action means before direct booking goes live. I do not accept a confirmation when no reservation succeeded. Collecting a request for your team may be the fallback. We still need to confirm that behavior in your setup. I will not treat a possible fallback as an already configured one.
I include an unavailable calendar in the acceptance test. Listen to the caller's answer, then read what staff receive. Does the person following up know scheduling is unresolved? If the note sounds like an appointment already exists, someone may skip the callback. That would turn a connection failure into a second scheduling problem.
How do we keep the booking rules useful?
I write booking rules around the services you deliver. Different work can require different commitments, even when the calendar looks open. Keep exceptions with a person when they need judgment outside the approved instructions. An available block tells us about time. It does not authorize the assistant to accept work you do not offer.
Bring changes in hours, staffing, services, or connected systems back to whoever manages the setup. I want the affected booking behavior retested. During rollout, examine requests alongside completed reservations. Keeping those records distinct lets your team catch confusion and finish unresolved scheduling before more callers use the same path through your calendar.