Pipeline

An opportunity needs a clear stage, owner and next action so the team knows how to move it forward. Open Pipeline to review those details alongside the customer, conversations and tasks. A manual stage change saves to the opportunity; use evidence from the customer’s response or agreed next step.

What lives here

Open opportunities, ranked for the work that moves revenue forward. Won and lost deals leave this working set once they close, because they no longer need daily attention, though their recorded opportunity values stay visible beside current active client agreements in Revenue. Its start-month chart groups the contracts active today, and an incomplete read offers Retry instead of partial totals.

When the assistant suggests a move

propose_stage_change never writes the stage directly. It stages a proposal with the evidence it read to support it, and you approve that proposal the same way you would any other approval. A customer reply that sounds like a yes is still just a proposal until you confirm it, because the assistant reading "sounds good, let's move forward" is not the same as you deciding that deal advanced.

Using the board covers the day-to-day mechanics of moving a card yourself.

The records behind a card

An opportunity links to contacts, companies, conversations, tasks, and proposals, and opening the card is how you see that whole graph in one place. Duplicate people do not get merged from this board, though; that review lives specifically under Contacts, where the evidence for a match is.

Read movement and current position

When an opportunity moves backwards or closes, Analytics keeps its recorded progress separate from its current position. The funnel uses the furthest recorded sales stage, while open value and weighted estimates use the current stage and stored probability. Today, Pipeline and the assistant use the same current-value calculation, including your custom stages.

Check the data-quality rows alongside the funnel. Missing stage history means there is no usable recorded movement, so the report identifies its current-stage fallback. Incomplete stage history means the records contain a gap, an invalid transition, a mismatch with the current position, or an incomplete read. Open the opportunity's activity before using that history to explain a result, and ask your technical owner to inspect a persistent gap rather than adding events to make the report agree.