Skip to main content
By the end of this guide you’ll have an active pipeline, with stages, a doorway connected to your conversations, and at least one automatic transition.

Before you start

Salesflow write permissions (salesflow.write and salesflow.edit_structure).
At least one working agent — WhatsApp, SMS, or voice — so there are conversations feeding the pipeline.

Steps

Create the pipeline

Go to CRM → Salesflow and create a new pipeline. Give it a Pipeline name and a Description.
The description isn’t decorative: if you later enable the orchestrator, the AI reads it as context for its decisions. Describe the actual sales process — don’t just write “sales pipeline”.
You can also start from a template instead of a blank slate.

Define the stages

Switch to the Flow view and use Add Stage in the toolbar.A good starting point is four or five stages that reflect real decisions in your process, not internal tasks. For example: NewContactedQualifiedProposalClosed.The last one should be type Final, with Outcome type Won or Lost. It’s common to have two final stages: one won and one lost.

Stages

The three stage types and what each one does.
Four stages placed on the diagram with no transitions, showing the dead-end warning

The pipeline stages in Flow view, not yet connected

Open the doorway

Without an input node, the pipeline only fills by hand.Click Add Input Node, choose the Source type (for example WhatsApp Chat), and drag from the node to a stage to connect it. An unconnected node shows as Not connected and does nothing.Then configure it: Entry conditions (which agents, which tags, at what moment) and Target stage.
If you leave the conditions empty, everyone enters. If you fill them in and nothing matches, nobody enters and you’ll see no error — the non-match is silent. Review them carefully.

Input nodes

The five sources and all their filters.

Connect stages with transitions

Drag from the edge of one stage to another to create a transition. Configure Transition opens, where you pick the Trigger type:
  • Manual — only a person moves the card.
  • Static — exact rules about the call or chat outcome.
  • Orchestrator — the AI decides, based on a prompt you write.
Start with static transitions wherever you have clear criteria: they’re free, instant, and predictable.

Transitions

The three types, priority, and strict mode.

Activate the pipeline

Change the pipeline Status to Active.
While the pipeline isn’t active, input nodes and idle timers won’t run. The status pill is the only in-product signal — there’s no banner warning you.

Check that people are entering

Generate a real conversation that matches your input node’s conditions — for example, write to your WhatsApp agent and resolve the session.Chat and call entry happens when the conversation ends, and processing runs every minute, so the card can take up to ~1 minute to appear. Client entry is scanned every 2 minutes.If it doesn’t show up, check the Processing History and the troubleshooting page.

Next steps

Events and sequences

Automate what happens inside each stage.

The orchestrator

Let the AI move the leads that don’t fit an exact rule.

Lead assignment

Distribute leads across your team automatically.

History and troubleshooting

What happened, why, and what to do when something doesn’t move.