Bookings Appointment Lifecycle Automation

Overview

This solution wraps Microsoft Bookings with the surrounding business workflow it doesn't provide. Bookings is excellent at slots and calendars but thin on CRM logging, branded communications, and post-visit follow-up. This solution turns every booking into a tracked customer interaction across three cloud flows and one Dataverse table. When an appointment is booked, the flow logs a Dataverse customer-visit record, emails a branded confirmation with an .ics calendar attachment, and posts a card to a staff Teams channel. A daily flow sends day-before reminders and post-visit feedback surveys. When an appointment is cancelled, the visit record is closed, staff are notified that the slot is free, and the customer gets a cancellation email. Why it matters: it adds the lifecycle automation - CRM record, branded comms, reminders, surveys, cancellation handling - that turns a raw Bookings appointment into a governed, tracked customer journey, entirely on first-party Microsoft connectors.

Use Case

A services team (clinic, advisory practice, salon, support desk) takes appointments through Microsoft Bookings and wants: branded confirmations with a calendar file, a CRM record per visit, automatic day-before reminders, an automatic post-visit survey, and staff notified in Teams when an appointment is cancelled so the freed slot can be re-filled.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Microsoft Bookings	shared_microsoftbookings	CreateAppointment CancelAppointment
Microsoft Dataverse	shared_commondataserviceforapps	CreateRecord ListRecords UpdateRecord
Office 365 Outlook	shared_office365	SendEmailV2
Microsoft Teams

Customization Guide

Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.

SMS reminders

Flow 3 sends email reminders via Outlook. Swap (or add) a Twilio SendMessage step for SMS reminders using the customer phone already stored on the visit record.

No-show handling

Extend Flow 3 with a third pass: visits past their end time still in Booked with no completion can be flagged No-Show and escalated to staff in Teams.

Survey engine

Point flowlibs_SurveyUrl at a Microsoft Forms / Customer Voice survey; route detractors to a follow-up flow.

Reminder timing

Change flowlibs_ReminderLeadHours (default 24) to widen/narrow the reminder window without touching flow logic.

Calendar event vs attachment

The confirmation ships an .ics attachment; to instead place the event on a shared Outlook calendar, add a V4CalendarPostItem action.

Key Expressions

The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.

concat(replace(replace(substring(coalesce(triggerBody()?['StartTime'],utcNow()),0,19),'-',''),':',''),'Z')

@and(greater(ticks(item start),ticks(utcNow())), less(ticks(item start),ticks(addHours(utcNow(),int(parameters('EnvVar_ReminderLeadHours'))))))

@less(ticks(item end),ticks(utcNow()))

flowlibs_appointmentid eq '@{triggerBody()?['Id']}'

Customize & download