A customer journey flowchart shows every decision point a prospect hits, and what happens on each branch, so nobody in your team has to guess what comes next. Where a map shows stages in a line, the flowchart shows the forks: did they book or not, did they show or not, did they buy or go quiet. This article answers one question: how do you turn those forks into pipeline stages and workflow branches in the levelpartner.ai platform, so the chart describes what really happens rather than what you hope happens.
Why the branches matter more than the boxes
Most firms can name their stages. Few can say what happens to the prospect who does not take the expected path. That missing branch is where revenue leaks. The enquiry that never books a call, the booked call that never shows, the proposal that sits unanswered for three weeks.
A flowchart forces you to draw the "no" path for every "yes". Once it is drawn, you can see which branches end in nothing. Each dead end is either a follow-up you need to build or a loss you have decided to accept.
Before you start
- A list of every way a prospect currently reaches you: forms, calls, chat, referrals, walk-ins.
- Your current pipeline in Opportunities, even if it is rough.
- Someone from sales and someone from delivery in the same room for two hours.
- Permission to edit workflows in Automation, or a colleague who has it.
- Paper, a whiteboard or any diagramming tool. The drawing tool does not matter.
How to set it up
- Draw the entry points on the left edge of the page, one box per source.
- Draw the first decision each prospect faces, usually whether they book a conversation.
- For every decision diamond, draw both the yes branch and the no branch.
- Mark each branch end as either a next stage, a follow-up or an accepted loss.
- Count the diamonds and confirm each has exactly one owner in your team.
- Go to Opportunities > Pipelines and create the yes path as stages.
- Build one workflow per no branch that should trigger a follow-up.
- Add an If/Else action in each workflow to mirror its diamond.
- Add a contact tag at each accepted loss so you can count them later.
- Run three test contacts through each branch and check where they land.
Reading the flowchart against your data
Once the pipeline and workflows mirror the chart, the chart becomes measurable. Each diamond has a count going in and two counts coming out. A Funnel widget on the dashboard shows stage-to-stage conversion for the yes path. Tag counts and workflow statistics show the no paths.
Compare the two. A diamond where most prospects take the no branch is your bottleneck. If you want to go deeper into what those numbers mean, read the guide on analysing the customer journey.
Suppose the firm draws four diamonds: booked a call, attended, received a proposal, signed. Say 240 enquiries enter in a quarter: 130 book a call, 110 attend, 70 receive a proposal and 22 sign. The biggest single loss would then be at the first diamond, where 110 enquiries never book. A firm busy rewriting proposals would be working two stages too late. These figures are illustrative.
What it replaces
It replaces the unwritten rulebook that lives in your best salesperson's head. When that person is on holiday, prospects on the no branch simply stop hearing from you. It also replaces the long email thread that tries to explain the sales process to a new hire.
A flowchart on the wall plus matching workflows means the follow-up happens whether or not the person who designed it is in the office.
Time it takes each week
The first drawing takes two hours. Building the workflows takes a day or two, depending on how many no branches you decide to act on. After that, allow 15 minutes a week to check workflow error logs and branch counts, and an hour each quarter to redraw any diamond that has changed.
The mistake most people make
Drawing only the happy path. A flowchart with no "no" branches is a stage list with arrows. The value sits entirely in the branches you would rather not think about. If a diamond has one exit, you have not finished drawing it.
When not to use a flowchart
If you sell a single product with a one-step purchase, a flowchart adds little. A list of customer journey stages will do the job. Flowcharts earn their keep when a sale passes through three or more decisions, involves more than one person in your team, or takes longer than a week.
Avoid them, too, when the process changes every month. Redraw costs time, and an out-of-date chart misleads new staff more than no chart at all.
Troubleshooting
Contacts sit in a stage that has no exit
A branch in the chart has no matching workflow. Find the diamond, check whether the no path should trigger a follow-up, and build it. If the loss is acceptable, tag and close the opportunity so it stops cluttering the pipeline.
The workflow branch fires for the wrong people
The condition does not match the diamond. Usually a tag or field is set by two different forms. Narrow the condition to one field with one meaning.
Dashboard counts do not match the chart
Staff are moving opportunities by hand and skipping stages. Agree that stages move only forward, one at a time, and use a workflow to move them where possible.
The chart has grown too large to read
Split it. Keep one top-level chart with five to eight diamonds and draw a separate detail chart for any complex branch, such as the proposal stage. A Lucidchart customer journey map guide covers swimlane layouts for this.
Frequently asked questions
What is the difference between a flowchart and a journey map?
A journey map shows stages, touchpoints and how the customer feels. A flowchart shows decisions and branches. Use the map to understand the customer and the flowchart to design what your team and your workflows do at each fork.
How many decision points should a flowchart have?
Five to eight at the top level is readable. More than that and people stop reading it. Push detail into sub-charts rather than one large drawing.
Do I need a special tool to draw one?
No. A whiteboard photo works. What matters is that every branch is mirrored by a pipeline stage or a workflow in the platform. The customer journey visualization guide covers how to show live numbers on top.
Who should own the flowchart?
One person, usually the sales or operations lead. They keep the drawing current and sign off any workflow change that alters a branch.