What is being booked?
For example: “30-minute new-client discovery call”, “60-minute annual review” or “15-minute support check-in”. Use wording a client will understand.
Set Up & Run
A practical setup for a 1–5 person business that wants clients to book a simple service without creating another admin system. Start with one real booking job, configure the minimum you need, test it properly, then add complexity only when the workflow earns it.
The outcome
For a small service business, the first useful Bookings setup is usually simple: one shared booking page, one clearly named service, the right staff, realistic availability, a confirmation, a reminder and a booking link you can put on your website or email signature.
Microsoft's current Shared Bookings setup flow supports creating a page from scratch, entering business information, inviting staff, adding services and choosing who can book. Bookings then lets you control availability, lead time, reminders and the customer-facing page.
Before you open Bookings
This keeps the setup proportional. If you cannot describe the first service clearly, adding more booking options will not make the process clearer.
For example: “30-minute new-client discovery call”, “60-minute annual review” or “15-minute support check-in”. Use wording a client will understand.
Name the person or small group who should actually receive these appointments. Do not add every Microsoft 365 user just because you can.
The ideal result is not “a slot appears in a calendar”. It is that the client books correctly, receives the right information and the person delivering the service knows what happens next.
Step 1
Microsoft's current guidance starts from the Bookings home page. Under Shared Bookings, choose to create a booking page.
For a first small-business setup, starting clean is easier to audit than cloning somebody else's booking page.
Microsoft says the business name is the only required field at this first stage; logo, fuller business information, staff and service details can be configured afterwards.
You can expand later. Keeping the first page small makes testing much easier.
Use the real client-facing service you defined above rather than a vague label such as “Meeting”.
Do not publish it widely yet. Finish the configuration and run test bookings first.
Step 2
Microsoft's Business information area controls details shown on the customer booking page and in Bookings messages. Treat it as a small customer-facing service page, not an internal admin screen.
Check the business name, contact number and website. Avoid internal team names that mean nothing to the customer.
Microsoft lets you specify where customer replies to booking confirmations and reminders should be sent. Use a mailbox somebody actually monitors.
Microsoft supports privacy-policy and terms URLs in the business information. Keep the booking form's data collection proportionate to the service being booked.
These are the broad hours within which bookings can operate. Service and staff availability can then be narrower.
Branding should reassure the client that they are in the right place. It does not need to become a design project.
Microsoft Bookings can display availability in the visitor's local time zone. Make sure your own booking page is configured to the business's correct local time zone before testing.
Step 3
Microsoft currently supports different Bookings staff roles. Administrators can manage settings and bookings; viewers can receive and see their own bookings; guests can be assigned to deliver services without accessing the Bookings app.
| Person | Likely starting role | Reason |
|---|---|---|
| Owner who configures Bookings | Administrator | Needs to change services, staff and booking settings. |
| Employee who only delivers appointments | Viewer where appropriate | Can receive their bookings without giving them full setup control. |
| External/non-Microsoft staff member who needs to deliver a service | Guest where appropriate | Microsoft says staff do not all need a Microsoft 365 account; a valid email can receive booking invitations and changes. |
Right-size access: a two-person consultancy rarely needs both people to be Bookings administrators. Give full control only where it has an operational purpose.
Step 4
Microsoft lets each Shared Bookings service specify its name, description, location or online meeting, duration, buffer time, assigned staff, custom fields, reminders and follow-ups.
“30-minute discovery call” is clearer than “Consultation A”.
Do not shorten a 45-minute real conversation to 30 minutes merely to create more calendar capacity.
For virtual appointments, Microsoft Bookings can create an online meeting link when that option is enabled. For in-person work, use a location the customer can understand.
Preparation, note-taking or travel are real workload. Microsoft blocks configured buffer time in staff availability so clients cannot book straight through it.
Decide whether any available qualified person can take the booking or whether the customer should choose a specific person.
Collect information needed to prepare for the appointment. Do not turn a scheduling form into a miniature CRM.
Step 5
The customer should see useful availability, not every technically empty gap in the calendar. Bookings supports booking increments, minimum lead time, maximum days in advance and service-specific availability.
If same-day bookings create chaos, stop offering them. Choose enough notice for the staff member to prepare properly.
Do not open a calendar further ahead than you can sensibly plan. Microsoft supports limiting how far into the future clients can book.
A 30-minute service does not necessarily need to start every 15 minutes. Choose increments that produce a workable diary.
Use actual staff working hours and calendar availability. Check that annual leave, closures and blocked time produce the expected result.
If discovery calls are only offered Tuesday and Thursday afternoons, configure the service that way rather than exposing all business hours.
For travel, preparation or post-call notes, build the time into the service instead of relying on staff to remember to block it manually.
Step 6
Bookings supports confirmation emails plus timed email reminders and follow-ups. Use those messages to reduce avoidable back-and-forth rather than filling them with marketing copy.
Confirm what was booked, when it happens, where/how to join and anything the client must do beforehand.
Remind at a useful interval for the appointment type. A short online consultation and a site visit may need different notice.
Use a follow-up only when there is a genuine next step: feedback, documents, booking the next session or another clear action.
Step 7
The public page can be branded, restricted, kept out of search-engine indexing, and configured with customer-data consent text. The goal is a trustworthy booking experience, not the longest possible intake form.
Step 8
Run the booking as if you were a client. A settings page can look correct while the customer experience is still wrong.
| Test | What to check | Pass condition |
|---|---|---|
| Normal booking | Book the most common service from a non-staff browser/session. | Correct availability, staff, time zone and confirmation appear. |
| Busy calendar | Block time in the staff calendar and try to book through it. | The blocked period is not offered. |
| Lead-time boundary | Try to book inside the minimum notice period. | The disallowed slot is unavailable. |
| Client change/cancellation | Use the customer flow to change or cancel where enabled. | Calendars and notifications update as expected. |
| Mobile booking | Complete the booking from a phone. | The service is understandable without zooming or guessing. |
| Reminder/follow-up | Use a test service with short intervals if needed. | The right people receive the intended message once. |
Do not skip the client-side test. The person who configured Bookings already knows what every field means. A new customer does not.
Starter configuration
This is an example configuration, not a Microsoft recommendation. Adjust it to the actual service.
| Setting | Example starting point | Why |
|---|---|---|
| Service | 30-minute discovery call | One clear first booking job. |
| Location | Teams online meeting | Automatic join details for a remote consultancy. |
| Buffer | 10 minutes after | Allows notes and next-action capture. |
| Minimum notice | 24 hours | Stops disruptive last-minute bookings. |
| Bookable window | Selected working blocks, not the whole week | Protects focused work. |
| Customer fields | Name, email and one useful context question | Enough to prepare without unnecessary data collection. |
| Reminder | One useful email reminder | Reduces avoidable no-shows without notification noise. |
Common mistakes
Launching ten appointment types creates customer choice and maintenance work before you know which ones are useful.
A free calendar is not the same as a useful appointment window. Protect delivery and focus time deliberately.
Give people the access required for their role, not maximum access by default.
Back-to-back slots look efficient until calls overrun, notes are missed or somebody has to travel.
Ask only what helps schedule or prepare for the service. Collect other information later if it genuinely becomes necessary.
One end-to-end customer test will catch problems that staring at the admin settings will not.
After 30 days
Look at real bookings. Were clients able to book? Did the correct staff receive them? Did calendar availability behave properly? Were reminders sufficient? Did you repeatedly encounter a missing requirement?
If the answer is “Bookings works, but it needed better setup”, stay with Bookings and fix the setup. If an important requirement genuinely remains unsupported after a fair test, return to the scheduling decision and consider whether a dedicated tool has now earned its place.
Implementation ladder
You should be able to complete a straightforward Bookings setup from this page and Microsoft's own documentation without buying anything from UK Software Stack.
A future optional setup pack may add reusable service worksheets, booking-page copy, intake-question templates, confirmation/reminder wording and a testing checklist. A tightly scoped done-for-you setup may also be tested later. Those would sell saved time and implementation—not access to instructions deliberately withheld here.
Sources and scope
The recommended sequence, starter configuration and “start with one service” approach are UK Software Stack editorial judgement. Microsoft sources below substantiate the current Bookings setup, staff, service, availability, notification and customer-page functionality described above.
Page reviewed: 31 August 2026. Microsoft can change Bookings labels, licensing and settings. If your Bookings screen looks different from the steps above, check the linked Microsoft guidance and follow the options shown in your current version of Bookings.