Customer Journey: Map the Path to a Qualified Contact

To map a journey from a first question to a qualified contact, do not start by drawing an ideal funnel. Start with one defined audience and one decision, gather evidence of the touchpoints people actually use, agree what “qualified” means for the team, and give every stage an action, owner and checkable signal. The result should help marketing, website and sales teams make choices together, rather than decorate a workshop wall.

For the query “parcours client”, Ahrefs showed an estimated Morocco search volume of 40 and an estimated keyword difficulty of 6 as of 22 October 2026. Those estimates can help prioritise an editorial topic; they do not predict visibility, contacts or commercial results.

Choose the journey you need to understand

Begin with a situation, not “all customers”

One organisation can have several distinct journeys. Someone researching a problem, someone comparing providers, and an existing customer asking for additional help may need different information and follow different routes. Combining them into one map hides the differences that matter. Pick an observable situation, such as: “an operations lead researches a problem, assesses whether the service fits, then asks for an initial conversation.”

A current-state map should describe what happens today, including dead ends. A future-state map can follow once the team has a credible diagnosis; it should not replace one. Shopify distinguishes current-state, future-state and service-blueprint maps, and lists personas, stages, actions, touchpoints, emotions, owners and opportunities as useful elements in a map Shopify.

State the decision question first

Write the decision in plain language before opening a board: “Where does understanding of the offer fail before a form submission?”, “What information is missing before an enquiry?”, or “What context must reach sales with a request?” This prevents a channel inventory with no operational outcome.

A team investigating early discovery needs a different timeframe and evidence set from a team repairing the marketing-to-sales handoff. A deliberately narrow scope is a quality choice, not a gap in the work.

Define a qualified contact before you count one

Keep action, contact and qualification separate

A click on “Contact us” is an interest signal. A completed form may create a contact. Neither act alone proves that the need, scope or person is suitable for the service your organisation can deliver.

Agree on a definition that people can apply consistently. Depending on the sales model, it may include:

a stated need within the service scope;
enough contact information to respond reasonably;
context or timing that helps prepare the conversation; and
a role or decision process compatible with the way you sell.

Do not turn that list into an intrusive questionnaire. Separate information required to give a useful response from information that would merely be convenient to know. The purpose is to prepare a valuable conversation, not manufacture a lower form-completion rate.

Specify the handoff

Show exactly where marketing's responsibility ends and where sales begins. Record the request receipt, completeness check, assignment, first response and post-conversation status. Give the handoff an owner, a transfer channel, a minimum data set and a rule for feeding outcome information back. If the map ends at the form, it cannot teach the team whether requests were appropriate.

A digital strategy engagement can align offer, content, channels and qualification criteria. If the problem is already clear, request a quote to discuss an appropriate scope of work.

Gather evidence before filling in the map

Combine observed behaviour with what people say

Treat the first map as a hypothesis. Look for evidence in on-site searches, incoming emails, calls, sales notes, support questions, analytics, and a small number of conversations with recent contacts, including people who did not progress. Numbers can show where to investigate, but they do not always explain the reason.

GOV.UK's experience-mapping guidance advises capturing the experience of several users before making a map and then aligning common events. It also recommends separate maps where user groups go through materially different stages or steps GOV.UK. For a service business, that may support one map for search-led prospects and another for referrals, if their questions and touchpoints truly differ.

Make uncertainty visible

Label each important item as observed, reported, assumed or to be verified, alongside its source and date. A phrase heard once is not evidence about an entire audience. This distinction stops an internal opinion becoming “customer knowledge” through repetition.

Build a map people can act on

Use consistent rows at every stage

Put the stages across the page and use these rows beneath each one:

The person's question or goal: what they are trying to understand or achieve.
Observable action: a search, article read, comparison, download, call or form submission.
Touchpoint: a search result, post, service page, email, phone call or staff member.
Needed information and friction: missing proof, ambiguous wording, risk, effort or unanswered question.
Response and next action: the content, page element, person or process that makes progress possible.
Owner, evidence and measure: who acts, what supports the assumption and which signal will be reviewed.

This structure keeps facts, interpretations and improvement ideas from being blended into one vague cell.

Let the stages follow real work

A simple service journey may move through an initial question, discovery of options, fit evaluation, trust checking, contact, qualification and conversation preparation. It is not necessarily linear. Someone may land directly on a service page, return after speaking to a colleague or skip a resource that the team considers essential.

Show meaningful branches. A person who calls may not follow the same screens as one who submits a form. A good map reveals those distinctions instead of erasing them in pursuit of a tidy diagram.

Match the content, page and next action to the question

Answer the first question before pushing the sale

Early in the journey, people often need comprehension. A page or resource can explain the problem addressed, the situations it fits, the terms it uses, its limits and the sensible next step. A broad promise or an isolated “Contact us” button does not replace those answers.

During evaluation, the question shifts to fit: method, scope, possible outputs, participants, constraints and what starting will require. Use accurate, verifiable evidence. Do not invent client outcomes or guarantees to fill a supposed “proof” gap in the map.

Design contact as a continuation, not a cliff edge

A contact page should state what happens after submission, offer an appropriate route for the need and ask only for information that helps the response. W3C's explanation of WCAG 3.3.2 says that labels or instructions should be provided where content requires input, and notes that clear labels and instructions can help prevent incomplete or incorrect submissions W3C.

That is why a conversion-focused landing page must be reviewed in context: entry question, available proof, mobile readability, form friction and the follow-up after receipt. Changing a button colour alone may not address the barrier identified in the map.

Measure transitions without mistaking data for motive

Write a measurement plan before configuration

For each stage, select a signal that supports a decision: service-page view, resource use, form start, successful submission, confirmed contact, qualification or a held conversation. Record the event name, trigger, permitted parameters, owner and test method. Do not place personal data in event names or measurement URLs.

Google Analytics documents generate_lead for a lead generated, qualify_lead for a lead marked as meeting qualification criteria and working_lead when a person contacts, or is contacted by, a representative Google Analytics. These event names do not set a commercial policy for you. They should represent statuses your team genuinely uses.

Read funnel analysis carefully

GA4 Funnel exploration can visualise the steps people complete, with up to ten steps. Google distinguishes an open funnel, in which a person can enter at any step, from a closed funnel, in which they must enter at the first step Google Analytics. When people arrive through multiple pages, an open funnel may better represent entry. A prescribed sequence may justify a closed funnel for a different question.

A fall between steps is not a verdict on an individual's intent. Check the date range, consent, website or campaign changes, implementation and volume before reaching a conclusion. Pair aggregate data with observations and feedback from the people handling enquiries.

Prioritise improvements and keep the map current

Turn opportunities into testable statements

Phrase each opportunity as: “For [audience] who need [answer], we will change [touchpoint] so that [next action] is clearer; we will review [signal].” Compare work against the likely impact on the identified barrier, risk, effort, dependencies and reversibility. A small verifiable change is often more responsible than a broad redesign based on assumption.

Keep a change log with the date, hypothesis, audience, measure and observed result. It helps prevent a misleading interpretation when several site, campaign or process changes happen at once.

Limits worth keeping on the page

A map cannot read individual minds, and it simplifies non-linear behaviour. Its quality depends on the research behind it. It may miss offline interactions or behaviour outside consent. Analytics tools show only the information they receive. A measured conversion also does not prove that one channel alone caused a commercial decision.

Do not promise a conversion rate, number of contacts or search ranking because you have mapped a journey. Its value lies in clearer decisions and in the team's willingness to revise it when evidence changes.

FAQ — customer journey mapping and qualified contacts

Do we need one map for every persona?

Not automatically. Start with the audience connected to the decision you are investigating. Create a separate map when another group genuinely follows different stages, uses different channels or needs different information to move forward.

How is a customer journey different from a sales funnel?

A sales funnel often describes organisation-defined conversion stages. A customer journey starts with a person's goal and can include returns, off-site channels, hesitation and exchanges after contact. They can complement one another, but they are not the same thing.

What should a form ask without adding unnecessary friction?

Ask only for information necessary to respond and route the enquiry. Add a context question only if it changes the response or owner. Review the clarity of labels, required fields and the post-submission message as well.

How many stages should we measure?

Measure only the stages needed for a decision. Four or five reliable signals can be enough for a simple path. Add detail when it answers a specific question; many poorly understood events make analysis harder, not better.

When should the map be reviewed?

Review it after a meaningful change to the offer, site, channel or sales process, and at a rhythm that matches the evidence available. A review should not become a recurring ritual with no new information.