# How do you review a Capsule CRM pipeline?

Review Capsule opportunities, milestones and tasks with AI to find missing next steps and prepare a focused sales meeting.

Published: 2026-09-30
Source: https://atso.ai/blog/capsule-weekly-pipeline-review/

---

A useful weekly Capsule pipeline review ends with a short list of opportunities that need a decision or a next step. Read the selected pipeline, its milestones and the relevant tasks, then ask each owner to resolve the exceptions. Avoid spending the meeting reading every deal aloud.

Atso connects business software to AI assistants through MCP. Its Capsule connector can read supported CRM records so an assistant can help prepare the review. The assistant organises the information; your team decides what the customer needs and updates Capsule.

## What should the review answer?

The review should answer which opportunities need attention, what evidence triggered that concern and who will take the next action. A pipeline total alone cannot answer those questions.

Choose a scope before retrieving the records. For example, review one pipeline, open opportunities and the tasks due before your next meeting. Confirm which date fields and relationships are available in the returned records. If a field is absent, record that limitation rather than reconstructing it from a name or a guess.

Agree the criteria with the sales team. “No visible open task” and “expected close date has passed” are useful review signals when supported by the records. “This customer will not buy” is a much stronger conclusion and needs evidence from the customer relationship.

## What can Capsule already show without an AI assistant?

Capsule already has pipeline views, task management and sales reports. Use those native features when they answer the question without additional preparation.

The [pipeline overview](https://capsulecrm.com/support/sales/an-overview-of-the-sales-pipeline/) describes inspecting an opportunity and its next task. The [task guide](https://capsulecrm.com/support/calendar-and-tasks/managing-your-tasks/) describes dashboard views for overdue, current and upcoming work. These are sensible starting points for a team that needs a clearer weekly habit.

Capsule also documents [sales reporting](https://capsulecrm.com/support/business-insights/reporting-on-your-sales/). An article about an AI review should not imply that Capsule lacks reporting. The reason to add a conversational layer is flexibility: asking a follow-up question about the selected records and preparing a meeting brief around the criteria your team has chosen.

If the existing view already produces a clear action list, keep using it. Adding another tool is worthwhile only when it makes the review easier to perform or easier to understand.

## What does Atso add to the preparation?

Atso can supply supported Capsule records to an AI assistant, including opportunities, tasks, pipelines and milestones. The assistant can use those records to propose a review list while preserving links between the findings and their source identifiers.

There are two defaults worth checking before a review. Capsule task reads default to open tasks, so a completed-work review needs a deliberate status selection. Milestone reads without a pipeline identifier can return the oldest active pipeline's milestones. Atso includes a note about that default.

Those details affect a real meeting. Reading open tasks alone cannot establish that nobody contacted a customer. Reading the wrong pipeline's milestones can produce a misleading explanation of where a deal sits. Ask the assistant to confirm the selected pipeline and task status before it labels the result.

A review should stay within the connected Capsule account and describe the records it actually accessed. It should not imply that the assistant has searched every conversation, email or activity history your team has elsewhere.

## Which fields should go into the meeting brief?

Keep the brief centred on an opportunity identifier, the review reason and a proposed next action. Add the owner, milestone and relevant task details only where the returned records support them.

A practical format is:

| Field | What to include |
| --- | --- |
| Opportunity | Name plus its source identifier |
| Pipeline and milestone | The selected pipeline and the matching milestone |
| Review reason | A specific observation, such as a past-due open task |
| Supporting record | Task or opportunity identifier behind the observation |
| Missing context | Information the owner needs to confirm |
| Next action | A proposal for the team to accept or change |

Keep monetary values in their own currencies and preserve the meaning of forecast fields. An expected amount is not collected revenue. If you want to compare the pipeline with accounting data later, define that separate question carefully rather than adding the two totals together.

Limit the first meeting brief to the few exceptions the team can realistically discuss. A list of every open deal simply moves the same administrative work into a new document.

## What should you ask the assistant?

Ask for a bounded review with explicit rules and no writes. Then check its first few findings in Capsule before using the brief in a meeting.

Here is a proposed prompt:

> List the Capsule pipelines I can access and ask me to choose one. Read its open opportunities, the matching milestones and relevant open tasks. Prepare a short review of opportunities with overdue tasks or no visible next task, but only where the records support that relationship. Include source identifiers and missing context. Do not infer that a customer is inactive from missing data. Propose next actions without creating or changing any records.

The prompt is a suggested starting point, not a record of a customer result. It deliberately asks the assistant to confirm relationships. A task with a similar title may concern a different opportunity, and an opportunity without a visible task may still have a next step agreed outside the CRM.

If the assistant cannot retrieve all relevant pages, narrow the scope or complete the review in Capsule. Label an incomplete list as incomplete. An opportunity omitted from the response has not necessarily passed the review.

## How should the team use the result?

Use the result to ask better questions of opportunity owners. Resolve uncertainty with the person who knows the relationship, then record the agreed action in Capsule.

For example, an overdue task could mean that a follow-up was missed. It could also mean the follow-up happened and the task was not completed. Those situations need different actions. Ask the owner which is true before changing the forecast or escalating the deal.

Atso's Capsule connector is read-only, so it will not create the proposed tasks or change milestones. Keep a simple handoff: one owner confirms each decision, updates the source record and sets the next review date. That makes the following meeting easier to prepare.

You can [open Atso](https://app.atso.ai/) to connect Capsule and try a small review. Read [MCP for business software](/blog/mcp-server-for-business-software/) if you want to understand the connection first. Judge the workflow by whether the team leaves with clearer next steps, rather than by the length of the generated summary.