# Activities and next actions

The activity timeline on a deal, where typed events come from, and the boundary where Boni Tasks takes over.

## The timeline

Every opportunity and every organization carries an activity timeline: the running story of the relationship in the order it happened. Opening a deal should let anyone understand it in about thirty seconds without asking a colleague.

Activities are typed rather than free-form, so the timeline can be read by a person and queried by a system:

| Source | Typical activity |
|---|---|
| Your team | Notes after a call or meeting, and explicit milestones |
| Stage changes | An entry recorded automatically when a deal moves |
| Voice | Call outcomes, including when the call happened and how long it lasted |
| Conversations | The reference that connects a relationship to where it is being discussed |
| Campaigns and email | Source events, where those channels are connected |
| Commerce orders | A minimized placed, updated, fulfilled, or cancelled order outcome linked to the buyer contact |

A commerce-order activity may include the customer-facing order number, state, currency, total, payment state, and item summary needed to understand the relationship. Checkout data, addresses, payment references, payer handles, raw payloads, and chat transcripts are rejected from this projection.

The product that owns a channel or order remains authoritative for its own data. CRM keeps the relationship view.

## Next actions belong to Boni Tasks

CRM records what happened. [Boni Tasks](/tasks/overview) owns what happens next: an owner, a due date, a status, and evidence of completion.

The practical rule is that a next action worth tracking becomes one task, not a note that hopes to be re-read. Create one when there is a concrete, owned step—a proposal awaiting a decision, a promised call, a customer waiting on your team. Do not create one for every reply, every open, or work another task already owns.

When the outcome arrives, it belongs in both places: the result is written back to the deal, and the task closes. A deal whose task is done but whose stage never moved is the pattern this boundary is designed to make visible.

Canonical: https://docs.boni.one/crm/activities-and-next-actions
Version: 2
Updated: 2026-08-18T10:32:58.139Z