Microsoft Bookings Booking Page Setup Planner: Service Durations and Buffer Times, Staff Availability, Scheduling Policy Lead Times, Custom Booking Questions, Reminder Emails, and a Break It Test Plan

Act as a Microsoft 365 administrator who configures Microsoft Bookings booking pages for small service teams so customers can self book without double bookings, no shows, or missing intake details.

Inputs:
- Business name, booking page type (shared booking page or personal page), and time zone: [BookingPageBasics]
- Services: name, length, price or free, in person or Teams meeting, group size, and prep or cleanup time needed: [ServiceList]
- Staff: names, roles, which services each delivers, working hours, and regular days off: [StaffRoster]
- Booking rules: shortest notice you accept, how far ahead customers may book, cancellation window, and slot increments: [BookingRules]
- Details you must collect before the appointment, and anything that must never go in a booking form: [IntakeNeeds]
- Reminder preferences and your current no show pattern: [NoShowHistory]
- Output format: [Format]

Generate:
1. A booking page decision from BookingPageBasics: shared or personal page, who can book (anyone or only people in your organization), and whether customers may choose a particular staff member.
2. A Bookings service table from ServiceList: default duration, buffer time before and after, price display, location or Teams meeting toggle, maximum attendees for group services, and the staff assigned from StaffRoster.
3. Staff availability: for each person in StaffRoster, business hours or custom hours, blocked days, and a flag for anyone assigned to a service they cannot fit inside their hours.
4. A scheduling policy from BookingRules: minimum lead time, maximum lead time, time increments, and cancellation and reschedule notice, each with one line on why it fits the service table.
5. Custom booking questions from IntakeNeeds: exact question text, answer type, required or optional, and which services show it. Move anything sensitive out of the form into a secure follow up step.
6. Confirmation, reminder, and follow up emails per service: timing and the custom reminder text, sized to NoShowHistory.
7. A break it test plan: five test bookings that try back to back slots, buffer overlap, too short notice, a staff day off, and a full group class, with the expected result for each.
8. A launch checklist: where to link the booking page, what to tell staff, and what to review after the first two weeks.

Constraints:
- Use only services, staff, and hours from the inputs; mark any missing value NEEDS DECISION instead of guessing.
- Bookings menu labels change over time; tell the user to confirm each setting name in their own tenant.
- No em dashes.