Lead Management
No lead sits untouched.
Leads arrive from a form, an inbox and a phone call, and go cold in three different places. Run them through one workflow that qualifies, follows up on a clock, and closes with a real outcome.
How it usually goes
Leads land in three places and get worked from whichever one someone happened to open.
The follow-up depends on remembering. A lead that went quiet in March is still technically "in the pipeline".
Everything closed is marked won or lost, so nobody can tell a bad lead from a dropped one.
The workflow you'd draw
The waiting is explicit: a lead parked on a reply looks different from a lead parked on your approval.
The lead arrives
From an email that you route in one click, or created by hand after a call. However it arrives, it enters the workflow at the trigger matching its channel, and the channel is recorded, so you can compare them later.
Qualify with a branch
A branch node scores the lead on the fields you capture (budget, timeline, source, region), combining conditions with All or Any. Unqualified leads take a different path instead of clogging the same one.
Send the intro
A send-email step goes out from your real mailbox with the lead's own details interpolated in, rich-text formatted, threading properly so their reply lands back on the ticket.
Wait for a reply
Waits for a personThe lead parks at an await-reply gate. Anyone replying on the thread counts. An auto-reply does not; an out-of-office will not fool the workflow into thinking they answered.
Chase, with a limit
A timeout edge on the await gate sends the follow-up, and a loop node caps how many times before it gives up. Retry and exhausted are separate edges, so a cold lead exits the flow instead of being emailed forever.
Approve before it advances
Waits for a personAdvancing a deal, sending a proposal or making an offer can park at an approval gate, so a person signs off before the lead moves to the next stage.
Resolve with the real outcome
Won, lost, no action needed: the resolve node takes an outcome, and the Outcomes card breaks the pipeline down by which one it actually was.
Stages that mean something because the workflow enforces them
The board is driven by the workflow you drew, so a lead is in Awaiting reply because it is genuinely parked at an await gate, not because someone remembered to drag a card.
What keeps the pipeline honest
Nothing sits untouched
A lead waiting on a reply is visibly parked at that gate with the time on it. Turn on SLA clocks and a first-response breach gets a badge instead of a quiet week.
Follow-ups that stop
The loop node has an exhausted edge. Your nurture sequence has an end, and the runaway-send guard stops a misconfigured cycle from emailing the same person over and over.
The whole thread, on the contact
Open a contact and see every ticket, email, reply and note exchanged with them across every workspace you can access, so the next conversation starts informed.
Find any lead in seconds
Global search runs across every ticket and inbox message you can access. Search a name, an address, or a phrase you remember from an email, and land on the right lead.
Owned, not "in the pipeline"
Each lead has one assignee of record, with Take it for self-claiming and an Assigned to me filter. Assigning never advances the workflow; that is the canvas's job.
Which source is actually worth it
Tickets by channel and source, next to resolve outcomes, answers whether the emailed leads or the referrals are the ones that close.
Start from the Sales Pipeline template and the Lead Nurturing Pipeline workflow, then change the fields, stages and qualifying conditions to your own. Nothing about sales is hardcoded; the same gates that hold a lead for approval hold an invoice or a new hire.
Other ways teams use it