levelpartner.ai
Reporting and attribution

Customer journey management: how it works and how to set it up

Customer journey management is the weekly operating rhythm that keeps contacts moving: who looks at what, when, and what they do about a contact that has stalled. Drawing the journey is a project. Managing it is a habit, and most companies stop at the drawing. This article answers how to run that habit inside the levelpartner.ai platform, with stale-deal alerts, owner tasks and a short weekly review, so stalled contacts are caught in days rather than discovered at quarter end.

The difference between mapping and managing

A map tells you the route. Management tells you who is stuck on it today. The two use the same stages, but management cares about individual contacts and deadlines, not averages.

In practice, managing the journey means three things. Every stage has a time limit. Every contact over that limit is visible to the person who owns the stage. And someone checks once a week that the limits are being respected.

Before you start

  • Defined stages with owners. The customer journey framework guide covers how to set those.
  • A pipeline in Opportunities that mirrors the stages.
  • Agreement on a maximum number of days a contact should spend in each stage.
  • Users set up for each stage owner with access to Opportunities and Conversations.

How to set it up

  1. Write down the maximum days allowed in each stage next to its name.
  2. Go to Automation > Workflows and click + Create Workflow.
  3. Click + Add New Trigger and choose Stale Opportunities.
  4. Set Duration in Days, In Pipeline and Pipeline Stage, then Save Trigger.
  5. Add an Add Task action and a Send Internal Notification action.
  6. Repeat at twice the limit, notifying the sales or operations lead.
  7. On the dashboard, add a Stages Distribution widget for open deals.
  8. Hold a 30-minute weekly review with all stage owners.
  9. During the review, open the over-limit list and agree one action per contact.

The weekly review

Keep it short and keep it to the list. The review is not a pipeline forecast or a sales meeting. Go through the stale-deal tasks raised since last week, and assign one action each: call, send, close as lost or move back to nurture.

Anything that cannot be decided in a minute goes to the owner to resolve before the next review. This discipline is what separates management from reporting. Reporting describes; management decides.

Illustration: a 45-person mortgage brokerage introducing stage limits

Suppose the brokerage sets limits of two days for new enquiries, five for fact-find, ten for application and 21 for offer. In the first weekly review, say 38 contacts are over limit, 22 of them in fact-find. If four weeks of reviews brought the over-limit list down to nine, that improvement would have come from follow-up discipline alone, with no change to marketing. These figures are illustrative.

Closing what is dead

A managed journey closes opportunities. If a prospect has not replied to three attempts across a month, mark the opportunity lost with a reason and move the contact to a nurture list. Open cards that will never close distort every stage count and hide the live ones.

What it replaces

It replaces the Monday sales meeting that walks through every deal, the end-of-month chase for updates and the moment, usually too late, when a director asks what happened to a large enquiry from six weeks ago. It also replaces individual to-do lists that hold follow-ups nobody else can see.

Time it takes each week

Setting up the workflows and dashboard takes a day. Running it costs each stage owner about ten minutes a day working their open tasks and 30 minutes a week in the review. That is usually less than the time the old update meetings took.

The mistake most people make

The common mistake

Setting time limits from wishful thinking. If your fact-find genuinely takes eight days, a two-day limit puts everything on the alert list and people stop reading it. Start with the time it currently takes, then shorten the limit once the backlog is cleared.

When not to use it

If your volume is under a handful of new contacts a week, a single person can hold the whole journey in view without alerts. Start managing formally when contacts outnumber what one person can remember, or when a contact passes between two people. For tracking where contacts came from, use customer journey tracking alongside this.

Troubleshooting

Alerts fire for opportunities that already moved

The workflow is checking the wrong field. Base the condition on the current pipeline stage, not on a tag set when the contact first entered.

Owners receive too many notifications

Batch them. Send one daily summary task per owner rather than an alert per contact.

Contacts sit in a stage nobody owns

A stage was added without an owner. Every stage needs one named role before it goes live.

The over-limit list never shrinks

The weekly review is producing discussion instead of decisions. Enforce one action per contact and close lost opportunities rather than leaving them open.

Frequently asked questions

Is this the same as pipeline management?

It overlaps. Pipeline management usually stops at the sale. Journey management carries on into onboarding and renewal, and the customer success customer journey guide covers that part.

Who should run the weekly review?

The person accountable for revenue, typically the sales or operations lead. They need the authority to close dead opportunities.

Can AI agents help manage stalled contacts?

Yes, for the first touch. An AI agent can send a check-in by SMS or email when a contact passes its limit, and hand the reply to the owner in Conversations.