> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/scheduling/messages.md). # Meeting messages and lifecycle Use event messages for meeting notifications and reminders. Use a workflow when a meeting change should start a broader process, such as a CRM update or Slack alert. ## Configure event messages Open **Messaging** to prepare the reusable templates your team needs. Then open the event type's **Messages** section. Select the **Message**, what to **Send**, and **When** it should be sent. Review the audience and channels. For a reminder, choose the timing relative to the meeting. For a status notification, choose the supported meeting status. Save the event configuration and use controlled recipients to verify delivery. ## Start a lifecycle workflow Create a workflow with **Meeting lifecycle**. Choose the **Meeting statuses**: Booked, Rescheduled, Cancelled, Reassigned, or Marked as no-show. Filter by the event types and booking source when needed. Use **Started from** to distinguish booking links, workflows, browser extension, or API starts. Add Branch if each selected status needs different follow-up. ## Example: notify after cancellation ``` Meeting lifecycle: Cancelled → Update CRM record or activity → Notify in Slack ``` Use the meeting and associated record details provided by the trigger. A cancellation notification should describe the retained meeting rather than create a new booking. ## No-shows and refunds Marking a meeting as a no-show is a meeting action. Its lifecycle event can start follow-up. Turn refunds are configured in the queue's routing profile. Do not add a second manual refund process without checking whether the profile already gives the turn back. ## Avoid duplicate messages Review the event's messages, workspace defaults, and workflow notifications together. For example, keep the guest's meeting confirmation in event messaging and use the workflow for an internal handoff alert. Confirm that rescheduling and cancellation produce the intended number of messages. See [Routing profiles](/routing/profiles.md) and [Workflow triggers](/workflows/triggers.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.distro.so/scheduling/messages.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.