> 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/guides/no-show-follow-up.md).

# Follow up after a no-show

Start a follow-up journey from a recorded meeting no-show rather than inferring attendance from the clock.

## Prepare

Choose the event types that should participate and a follow-up message or sequence. Define whether the original owner should remain responsible.

## Build

1. Create a workflow with **Meeting lifecycle** and the supported no-show condition.
2. Use the source meeting and guest identity.
3. Match the CRM prospect if the action needs a provider record.
4. Notify the host or assigned owner.
5. Start the supported follow-up action for an eligible prospect.

Keep cancellation and no-show paths separate. A cancelled meeting should not receive wording that assumes the guest failed to attend.

## Record the outcome

Use the meeting's management controls to mark it as a no-show. The lifecycle source consumes the recorded outcome.

Undoing a mistaken no-show changes the meeting status, but does not prove that an already sent message was recalled. Inspect any downstream enrollment when correcting the record.

## Test

Use a controlled meeting and outcome. Verify the source run, guest mapping, owner and destination enrollment or notification.

Test a meeting outside the intended event types and one without a usable prospect identity. Keep a fallback for missing data.

See [Manage meetings](/scheduling/manage-meetings.md) and [Meeting lifecycle](/scheduling/messages.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/guides/no-show-follow-up.md?ask=<question>&goal=<user_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.