Checking External Staff Availability in Microsoft Bookings

Before an answering team confirms an appointment through Microsoft Shared Bookings, identify whose availability the page represents. A staff member receiving a booking email does not establish that their other calendar commitments were checked.

Have the scheduling owner identify the Shared Bookings page, the service, and the staff member who will deliver the appointment. Keep that role separate from the answering agent entering the request; this checklist concerns the appointment recipient’s availability.

Microsoft says staff members need a valid email address but do not all need Microsoft 365 accounts. It also states that staff outside the tenant cannot share free/busy information with Bookings. Confirm which arrangement applies to each appointment recipient instead of assuming everyone listed has the same calendar connection.

Microsoft documents a setting that uses staff Microsoft 365 calendar events to affect availability, enabled by default. Bookable hours can follow business hours or narrower custom hours. Have the scheduling owner verify the actual settings rather than relying on the default.

For an external staff member, published working hours are not evidence that another appointment on their separate calendar has been checked. Ask which approved process supplies current availability and who maintains it. Do not describe a displayed slot as conflict-free without that evidence.

If the scheduling owner cannot verify external availability through the proposed workflow, agree on how the answering team records a preferred time for review. Assign a person to obtain confirmation and tell the caller which next step remains outstanding.

Check the messages the selected booking workflow sends before using it for tentative requests. Avoid creating an appointment that sends a confirmation while telling the caller it is only pending. The owner should choose an approved request process whose notifications match the actual status.

Use owner-approved practice scenarios and authorized test recipients before launch. These checks are a proposed acceptance plan, not results from an AnSer or customer configuration.