Customer journey mapping means documenting the steps a person takes with your business, alongside the teams, systems and decisions that shape those steps. Its value is not the finished diagram. It is the ability to see where customers are delayed, asked to repeat themselves or handed between departments without context.

Follow a customer, not a department

A business may think of marketing, sales and service as separate functions. The customer experiences one organisation. They might discover a business through LinkedIn, ask a question on the website, receive an email, speak to sales, sign up and later ask for support.

At each stage, the customer has a need and an expectation. Someone inside the business has to fulfil it. If those two views are mapped together, gaps that are invisible in departmental reports become obvious.

Salesforce research has reported that 79% of customers expected consistent interactions across departments, while 55% said interactions felt like dealing with separate departments. These figures come from Salesforce’s customer research and should not be presented as a South African market sample. They illustrate the cost of fragmented journeys. Source.

Six stages worth putting on your map

• Discovery: where people first hear about your offer and what information they need.
• Consideration: which questions they ask, what proof they want and how quickly they receive answers.
• Enquiry: how a form, call or message becomes an owned lead or service request.
• Decision: which sales steps and approvals must happen before the customer can proceed.
• Onboarding or fulfilment: whether the promises made during marketing and sales are reflected in delivery.
• Support and retention: how issues, feedback and repeat opportunities are recorded and acted upon.

A small business may not need more than a single-page map. The point is to include actual touchpoints and exceptions rather than presenting an idealised funnel.

Build a map that people can use

Start with one clearly defined customer type, such as a prospective client requesting a quotation. Interview staff who handle real enquiries and, where possible, listen to customer feedback. For each stage, record the channel, customer question, responsible team, system used, data needed, typical delay and next action.

Then trace two real or anonymised cases through the process. One should follow the normal route; the other should include a common exception, such as missing information or a delayed approval. This prevents a map that only describes what the process manual says should happen.

Look for recurring phrases: “I thought someone else was handling it”, “The customer had to send that again”, or “We cannot tell where the lead came from.” Each signals a possible hand-off or visibility problem.

Turn gaps into priorities

Not every friction point warrants automation. Score each gap against its frequency, customer impact, effort to fix and operational risk. A broken enquiry notification may be more urgent than an advanced recommendation engine. Agree on who owns the improvement and the metric that will show whether it works.

For example, instead of “improve communication”, set an operational goal such as “every website enquiry is assigned to an owner with a visible next step”. The goal describes a behaviour that can be tested.

Connect the journey to data and consent

A customer journey includes personal information. In South Africa, direct marketing and customer data processing require attention to POPIA. A map should show where data is collected, why it is needed, where it is stored and how opt-outs are propagated. The Information Regulator’s guidance is a useful starting point, but individual organisations should obtain advice appropriate to their situation.

For related reading, see our CRM overview and our article on follow-up gaps.

A quick workshop exercise

Gather representatives from marketing, sales and service for one hour. Choose a recent enquiry. Write each step as a card, including every manual transfer and approval. Ask where the customer could get stuck. Choose one change to test over the next month, then review actual cases rather than relying on opinions alone.

Frequently asked questions

What should a customer journey map include?

At minimum: customer stages, goals or questions, touchpoints, responsible team, systems, hand-offs, pain points and measures of success.

Is journey mapping only for larger companies?

No. Small teams can benefit because informal processes become difficult to see as volumes grow. A simple map often reveals useful fixes quickly.

How often should the map be updated?

Review it whenever you change major channels or workflows, or when customer feedback shows that the journey differs from the documented process.

Sources and further reading

• Salesforce: Customer expectations and connected journeys
• South African Information Regulator: guidance notes
• Datsu Tech: The Future of CRM

A useful map shows where the customer experience depends on a hand-off, and what the business will do to make that hand-off reliable.