> For the complete documentation index, see [llms.txt](https://help.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.distro.so/crm/activity.md).

# CRM activity

Check whether a personal or group booking reached your CRM. When **Settings → CRM → Overview** shows deliveries needing attention, workspace admins can choose **Review delivery issues** to open activity. Search by prospect or booking title, and filter by delivery status.

You can also open the booking in **Bookings** to see its CRM status and message.

## Read the result

| Status              | Meaning                                                                        |
| ------------------- | ------------------------------------------------------------------------------ |
| **Pending**         | Delivery is waiting to run or retry.                                           |
| **Synced**          | The configured delivery completed.                                             |
| **Skipped**         | Delivery did not apply; read the explanation.                                  |
| **Needs attention** | A connection, identity, mapping, permission, or delivery problem needs review. |

This activity covers personal and group booking links. Use [Routing Logs](/reporting/routing-logs.md) for Form, Click, and Outbound Router activity.

## Resolve a delivery problem

Open the booking and read the message before changing its configuration.

| Problem                                 | What to check                                                                                                                                     |
| --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| CRM connection unavailable              | Restore the original CRM connection and check the connected user's access.                                                                        |
| Organizer cannot be matched             | Review the organizer's CRM user match in **Settings → Members**.                                                                                  |
| Multiple prospect matches               | Review duplicate person records in the CRM. Distro does not guess which one to use.                                                               |
| No matching person, creation disabled   | Decide whether future bookings should create missing prospects, or create the appropriate person in the CRM before retrying an eligible delivery. |
| Missing or unavailable field            | Restore access to the captured field, then [check the field catalog](/crm/fields-and-mappings.md).                                                |
| Required Salesforce information missing | Check required fields, mapped answers, and validation rules. Changes to mappings apply to future bookings.                                        |

Use **Retry** when the delivery is eligible and the underlying problem has been corrected. Distro reuses known record and meeting IDs. A delivery whose creation result is uncertain may need further review before it can safely continue.

Bookings keep the settings and CRM account captured when they were created. Connecting a different CRM account does not transfer pending deliveries to it. Turning the source link Off stops delivery, including manual retries; turning it back on does not restart deliveries already marked skipped.

The meeting can remain confirmed even while CRM delivery needs attention. Do not ask the guest to book again just to resolve a CRM error.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.distro.so/crm/activity.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 `automate deployments from our CI pipeline` 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.