> For the complete documentation index, see [llms.txt](https://docs.phocassoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.phocassoftware.com/sales-insights/explore-customer-insights/review-a-customer-profile/follow-up-in-crm.md).

# Follow up in CRM

{% hint style="info" %}
To use this feature, you need access to [CRM](https://docs.phocassoftware.com/crm/).
{% endhint %}

Turn customer insights into follow-up activities without starting from scratch. Create activities from the AI summary or opportunities, with the relevant details carried into CRM so you have the context for your next conversation.

See [Activities](https://docs.phocassoftware.com/crm/activities.md) for information about activity types and fields.

#### Create a follow-up task

1. On the **Customer profile** page, choose the information to follow up:
   * For the AI summary, select **Add CRM activity** beside **AI Summary**.
   * For one opportunity, expand it and select **Add CRM activity** within the opportunity.
2. On the **Task** tab, enter a **Subject**. Review the **Owner**, **Start**, **End**, **Campaign**, and **Status**, and update them as needed.
3. Review the **Description** and add any details you need. For an AI summary activity, the summary is already included. For an opportunity activity, the opportunity details are added when the activity is created.
4. Select **Add 1 task**.
5. Select **View tasks** in the confirmation message to open the task list in CRM.

<div align="left"><figure><img src="https://3487206470-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQGQGMazAMTVRZA3vjjb5%2Fuploads%2FBh5D7mcWAsvOPYGkuzfq%2FScreenshot%202026-10-27%20at%2011.52.11.png?alt=media&amp;token=589786a2-ed05-4772-9b75-32579e153c0d" alt="Add CRM activity beside AI Summary opens the Add 1 task dialog, with the AI summary included in Description." width="315"><figcaption></figcaption></figure></div>

The dialog also has **Meeting**, **Phone log**, and **Business note** tabs if another activity type better suits your follow-up.

#### Follow up multiple opportunities

Create a separate task for each opportunity currently shown.

1. Use the opportunity filters to display the opportunities you want to follow up, then select **Add CRM activities** at the top of **Opportunities**.
2. Check the number of tasks shown in the dialog. On the **Task** tab, enter a **Subject**, review the other task details, and add any notes in **Description**. The relevant opportunity details are added to each task when it is created.
3. Select the button at the bottom of the dialog to add the tasks. Its label shows the number to create, such as **Add 5 tasks**.
4. Select **View tasks** in the confirmation message to open the task list in CRM.

<div align="left"><figure><img src="https://3487206470-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQGQGMazAMTVRZA3vjjb5%2Fuploads%2FuntPCorR4jpfRfjFCLBz%2Fcrm-multiple-opportunities-analytics.png?alt=media" alt="Add CRM activities in Opportunities opens the Add 5 tasks dialog, with fields shared by the five tasks and an Add 5 tasks button." width="307"><figcaption></figcaption></figure></div>


---

# 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://docs.phocassoftware.com/sales-insights/explore-customer-insights/review-a-customer-profile/follow-up-in-crm.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.
