> 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/crm/pipelines.md). # Pipelines {% hint style="info" %} User permission: CRM {% endhint %} Use pipelines to track deals, bids, quotes, projects, or other sales items as they move through your sales process. A pipeline is a board made up of stages. Each item appears as a card in the stage it is currently in. As work progresses, you can update the item, add activities, and move the card to another stage. Your business might use one pipeline or several pipelines, depending on how your administrator has set them up. For example, you might have separate pipelines for new business, quotes, project work, or tender submissions. {% embed url="" %} Use pipelines to track sales progress {% endembed %} ### View pipelines Select the **CRM** menu button > **Pipelines**. The Pipelines page displays the pipelines you have permission to view. It is a good starting point for reviewing sales items, adding new items, and updating items as they move through your sales process. What you see depends on how your administrator set up pipelines for your business. The Pipelines page typically includes the following areas: 1. **Pipeline selector:** Use the pipeline buttons at the top of the page, such as Deals or Samples, to switch between the pipelines you have permission to view. 2. **Toolbar:** The options you use to filter items in a pipeline or add a new item. 3. **Pipeline board:** A board layout where each column represents a stage in the selected pipeline. Each item appears as a card in one of the stage columns.
For example, a pipeline might include stages such as **New**, **Proposal**, **Negotiation**, **Contract sent**, **Closed won**, and **Closed lost**. ### Add an item to a pipeline Add an item to track a deal, bid, quote, project, or other sales item in a pipeline. Select the pipeline name, then select **Add item**. #### Enter the item details Enter the item’s details. Mandatory details are marked with an asterisk. The details you enter depend on the item you are tracking, but typically include: * **Name:** Enter a name for the item. * **Account, contact, or lead:** Select the record associated with the item. * **Stage:** Select the initial stage for the item. * **Description:** Add any background information or notes about the item. * **Expected close date:** Change the default date, if required. * **Value:** Enter the item value. * **Owner:** Select a different owner, if required. By default, you are set as the owner, but you might want to transfer ownership to another user. * **Campaign:** Select the campaign associated with the item, if applicable. Select **Save** when you have entered the details.
After you save the item, you can add an activity for it, such as a **Business note**, **Meeting**, **Phone Log**, or **Task**. You can also come back to this later. Select **Close** to return to the pipeline, where the new item appears as a card in the stage you selected. ### Update an item Update an item when its details change or when you need to add more information about the work associated with it. You can also add activities to the item, such as notes, meetings, phone logs, or tasks. In the pipeline, select the item card to open its details page. Make your changes, then select **Save** > **Close**. ### Move an item to another stage Drag the item card to a different stage column to move it through the pipeline as it progresses. For example, you might move a deal from **New** to **Negotiation** if the proposal stage is not needed.
### Filter a pipeline Use the filters in the toolbar to focus on specific items in a pipeline. This is useful when you want to review your own items, items linked to a campaign, or items owned by a particular team. * **Owner:** Select an owner to view only the items they own. For example, you might filter the pipeline to focus on your own items. * **Campaign:** Select a campaign to view only the items associated with that campaign. * **Team:** Select a team to view only the items owned by users in that team. * **Search:** Enter a search term to quickly find specific items. The board updates to remove the cards that don’t match the filter. ### Add an activity to an item {% hint style="info" %} See [Add an activity](/crm/activities.md#add-an-activity) for information and examples of activity types in CRM. {% endhint %} Add activities to keep a record of the work associated with an item. For example, you might add a business note after a customer conversation, create a task for a follow-up action, or record details of a meeting or phone call. In the pipeline, select the item card to open its details page, then select **Add activity**. Select the type of activity you want to add, such as **Business note**, **Meeting**, **Phone Log**, or **Task**, then enter the activity details.
Select **Save**, then select **Close** on the item page to return to the pipeline. --- # 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.phocassoftware.com/crm/pipelines.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.