An interactive customer journey map is one you can click. Select a stage and you see the actual contacts sitting in it today, who owns them and how long they have waited. This article answers how to build that clickable version inside the levelpartner.ai platform, using the pipeline board, smart lists and a dashboard, so a manager can go from "this stage looks slow" to "these are the eleven people stuck in it" in one move.
What makes a map interactive
A static map tells you the shape of the journey. An interactive one lets you act on it. The difference comes down to three behaviours: every stage shows a live count, every count opens a list of named contacts, and every contact opens a record with the full history.
You do not need a separate mapping tool for this. The pipeline board in Opportunities already shows stages as columns with cards you can open. Smart lists in Contacts cover the stages that happen before a deal exists. The dashboard supplies the counts and the conversion between stages. Put the three together and the journey becomes something your team works from, not something they look at once.
Before you start
- A journey with agreed stages, each defined by an event you can record.
- A pipeline in Opportunities whose stages match the journey after the first sale conversation.
- Tags or custom fields for the stages that come before an opportunity, such as "downloaded guide" or "attended webinar".
- Access to Contacts, Opportunities, Automation and Dashboard.
- Owners assigned to opportunities, so each card has a name on it.
How the three layers fit together
The early journey lives in Contacts. A buyer who has read an article and filled in a form is not a deal yet, so their stage is a tag. A smart list filtered on that tag becomes the clickable view for that stage.
The middle and late journey lives in Opportunities. Once a call is booked, an opportunity opens and moves across the board. Clicking a column shows its cards, and clicking a card shows the contact, their conversations and their appointments.
The dashboard sits above both. It shows totals per stage and conversion between stages. When a figure looks wrong, you click through to the list or the column underneath it.
How to set it up
- Write the stage list in order and mark where the first opportunity is created.
- Open Contacts and create a tag for each stage before that point.
- In Contacts > Smart Lists, create a smart list for each tag.
- Open Opportunities and check that pipeline stages match the rest of the journey.
- Build a workflow that applies each early-stage tag when its event fires.
- Add a Create/Update Opportunity action for the first pipeline stage.
- Go to Dashboard and click + Add Dashboard, named after the journey.
- Add a Funnel widget covering the pipeline stages.
- Add a Stages Distribution widget for open deals per stage.
- Add a Stale Opportunities workflow that flags deals stuck too long.
- In Edit mode, add a text element listing the saved smart list names.
- Share the dashboard and the lists with the people who run the weekly meeting.
What it replaces in a firm of 10 to 250 people
Without this, the weekly pipeline meeting runs on recall. A manager asks who is waiting on a proposal, and three salespeople each try to remember. With an interactive map on screen, the manager clicks the stage and reads the names.
It also replaces the spreadsheet someone builds every quarter to chase stalled deals. The stalled deals are already visible: they are the cards your stale-deal workflow has flagged.
Imagine the dashboard shows 34 open opportunities at proposal sent, and the stale-deal workflow has flagged 12 of them after 14 days without movement. The sales lead could open that stage on screen and assign each of the 12 a follow-up task before the meeting ends. The time would then go on named deals rather than on totals.
Weekly time cost
Building the three layers takes four to six hours if your pipeline is already in use. Running it costs nothing extra, because the clicks happen inside a meeting you already hold. Budget 15 minutes a month to check that every early-stage tag is still being applied by its workflow.
The mistake most people make
Making every stage a pipeline stage. Teams want one board for the whole journey, so they create opportunities the moment someone downloads a guide. The board fills with hundreds of cards that nobody will ever work, and the real deals get lost among them. Keep early stages as tags and lists. Open an opportunity only when there is a sales conversation to have.
When not to use it
If your sales team is two people who already know every live deal, the clickable layer adds little. A weekly look at the pipeline board is enough. It is also the wrong tool for planning a new journey from scratch: draw it first, agree the stages, then make it interactive. The customer journey design guide covers that earlier step.
Troubleshooting
A smart list shows more contacts than the dashboard widget. The list has no date filter and the widget does. Decide whether each view should show everyone currently at that stage or only those who arrived this month, and label it accordingly.
Cards sit in a column with no owner. Opportunities are being created by a workflow without an assignment step. Add round-robin or fixed assignment to the workflow that creates them.
Contacts carry two stage tags at once. The workflow adds the new tag but does not remove the old one. Add a remove-tag action alongside each add-tag action so a contact sits in one early stage at a time.
Nobody clicks through. The dashboard is shared but not shown. Open it on screen at the start of the weekly meeting and click one stage live.
Frequently asked questions
Can buyers see the interactive map?
No. This version is an internal working view built from your CRM data. If you want buyers to see their own progress, that is a client portal or membership area, which is a different job.
How is this different from a journey dashboard?
A dashboard shows totals. The interactive map adds the click-through from each total to the named contacts behind it. The customer journey management article explains how to run the team around those views.
Do I need a pipeline for every journey?
One pipeline per sales motion is usually enough. If new clients and repeat clients follow different paths, give each its own pipeline and its own early-stage tags.
What should I check first if a stage looks slow?
Open the stale-deal tasks for that stage. Then look at three of the flagged cards and read their conversation history. For a structured way to diagnose the numbers, see customer journey analysis, and for the static version of the same picture, the Miro customer journey map guide.