Pipelines

Purpose

Pipelines are visual boards for contact journeys (sales, onboarding, support queues, collections). Each pipeline has ordered stages; contacts appear as cards you can move between stages.

What you can do

• Create and publish pipelines with named stages.
• Open a kanban board to move contacts between stages.
• Link workflows that start when a contact enters a stage (or any stage).
• Filter and combine pipeline stage with segments and AI agent tools.

Typical setup

1. Go to Pipelines → New pipeline.
2. Name stages that match how your team already works (for example: New → Qualified → Won / Lost).
3. Publish the pipeline and open the board.
4. Optionally create a workflow with a pipeline trigger for follow-up messages or internal actions.

Best practices

• Keep stage names operational ("Waiting payment"), not vanity labels.
• One primary pipeline per major journey — avoid dozens of nearly identical boards.
• Pair stage moves with tags or notes so the inbox still has context.
• Test workflow triggers on a sample contact before inviting the whole team.

Related

• Segments — audience rules that can include pipeline stage
• Workflows — automate on stage entry
• AI Agents — allow agents to move contacts across stages