The customer journey is the full sequence of steps a person takes from first noticing your business to becoming a client and, ideally, coming back or referring others. This article answers the starting question: what is a customer journey in practical terms, and how do you create customer journey records on the levelpartner.ai platform so the journey is something you can see and manage, not just a diagram? Once it exists in the platform, you can tell at a glance where each prospect stands and where people drop out.
A working definition
Strip away the jargon and a customer journey has three parts: the stages a person passes through, the touchpoints where they meet your business, and the decisions they make between stages. Awareness, enquiry, first conversation, proposal, decision, onboarding, delivery, renewal or referral. The exact stages vary by industry, but every firm has some version of them.
The useful version is not a poster. It is the same journey expressed in your pipeline stages, your follow-up rules and your reports, so that what the diagram says and what the business does match.
The customer journey online and offline
Most journeys now start with the customer journey online: a search, a social post, a review, a visit to your website. Then they often move offline: a phone call, a meeting, a site visit. Then back online for a proposal, an e-signature and an invoice.
The trap is tracking only the online half because it is easier. A journey that loses the phone call and the meeting is missing the part where the decision was made. On the platform, calls, meetings and messages sit on the contact's timeline beside page visits and form submissions, so both halves stay in one record.
Before you start
- A rough list of how clients currently find you and what happens next.
- A pipeline in Opportunities, even a basic one.
- Lead forms and booking pages built in Sites and Calendars.
- One person responsible for keeping the journey current.
How to set it up
- Write your journey as six to eight stages from first contact to repeat business.
- Name the event that moves someone from each stage to the next.
- In Opportunities > Pipelines, set Stage Names to match those events.
- Add a Form Submitted workflow that creates an opportunity at stage one.
- Add a Customer Booked Appointment workflow that moves the deal forward.
- Add a Stale Opportunities workflow to any stage where deals stall.
- Record lost reasons when a deal leaves the journey.
- Check the pipeline weekly to see where opportunities are building up.
A brokerage might write seven stages: enquiry, fact-find booked, fact-find held, documents received, application submitted, offer issued, completed. Say a month on the pipeline brings 120 enquiries, 70 booked fact-finds and 30 sets of documents. Then 40 of the 70 people who booked a fact-find would be stalling before their documents arrive, which makes a reminder text sequence at that stage the obvious first change to test.
What the journey is for when revenue is flat
When turnover stalls, the instinct is to buy more leads. A defined customer journey often shows that you already have enough enquiries and are losing them at one specific step. Fixing that step is cheaper than buying more traffic, and the gain compounds because every future lead passes through it.
It also gives everyone a shared vocabulary. Marketing, sales and delivery stop talking about "leads" and "clients" loosely and start saying "stuck at proposal" or "no fact-find after five days". For detailed stage definitions, see customer journey stages.
Time it takes
The first version takes half a day to write and another half day to build into the pipeline. After that, a weekly pipeline check of 15 minutes and a quarterly review of the stages themselves. If you want a structured workshop format first, try a customer journey canvas.
The mistake most people make
Ending the journey at the sale. For most service firms, repeat business and referrals are worth more than the first job. Add stages for delivery, review and referral so the journey keeps working after the invoice is paid.
When not to formalise it
If you are a very small team where one person handles every client from start to finish, a formal journey may add little. They already hold it in their head. Formalise it when more than one person touches a client, or when you want to hand part of the work to automation or AI agents.
Troubleshooting
Opportunities pile up in the first stage. Nobody is responsible for first contact, or the response is too slow. Assign an owner automatically and add an instant reply.
Stages are skipped. The stage definitions are vague. Tie each stage to a specific event, such as a meeting held, not a feeling, such as "interested".
The pipeline does not match the diagram. Someone changed one without the other. Treat the pipeline as the master and update the diagram from it.
Frequently asked questions
How is a customer journey different from a sales funnel?
A funnel describes how numbers shrink from leads to clients. A journey describes the experience and decisions behind those numbers, including what happens after the sale.
How many stages should a journey have?
Six to eight for most service firms. Each should mark a real decision or event.
Do we need a separate journey for each industry we serve?
Only if the steps genuinely differ. A mortgage application and an agency retainer follow different paths. Create a separate pipeline for each path that differs, and keep the rest shared.
How do we know if the journey is working?
Track conversion between stages and time spent in each. Customer journey analysis explains how to read both.