Meera, an invented customer, wants a home loan. She has found a flat in Pune. She has the booking amount ready but needs the loan sanctioned within three weeks, or the seller will move to another buyer. This is the story we will keep returning to, because a journey map is nothing more than this story told carefully, with the places where it goes wrong marked.

The company, an invented lender, measures its contact centre well. Service level is good, quality scores are high, CSAT after calls is 4.4 out of 5. And yet applications are dropping off between login and disbursal. The calls look fine. So where is the problem? Somewhere between the calls.

What a journey map is

A customer journey map lays out the stages a customer goes through to achieve a goal, with, for each stage, what the customer is trying to do, which channels or touchpoints they use, what they think and feel, and where the company’s internal teams are involved. Its focus is the customer’s goal (“get this loan sanctioned in three weeks”), not the company’s departments. That difference is the whole point. A contact-centre report shows contacts; a journey map shows the effort and anxiety between contacts.

Meera’s journey, stage by stage

Draw the stages across the top: researching, applying, document submission, verification and sanction, disbursal. Then walk through them as Meera.

She researches online, finds an eligibility calculator and sees a rate. She applies through the app, which asks for her PAN and income details. She uploads salary slips. So far, no contact at all, so no data in the contact-centre system. Two days later she gets an SMS asking for “additional documents” without saying which ones. She calls. The agent explains politely, in a call that scores well. She uploads the documents. The verification team visits her office address; she is not told when. She calls again to ask whether the visit happened. The agent cannot see the verification status and has to raise a query. She waits a day for a callback. She chats online. The bot offers a link to the same FAQ she had read. She calls a third time and is told the sanction letter is “in process”.

Count the contacts: the call, the second call, the callback, the chat, the third call. Five contacts to learn the status of one application. The contact-centre dashboard sees five reasonably well-handled interactions. Meera sees a company she cannot trust to tell her where things stand, with a seller’s deadline approaching.

Finding the moments that matter

Along the bottom of the map, draw an emotion line: high when the customer feels in control, low when anxious or confused. For Meera it dips sharply twice: at the vague “additional documents” SMS and at the unannounced verification visit. These dips are the moments of truth, the points where the customer’s confidence in the company is made or lost. Notice that neither of them is a call. One is a message and the other is an absence of communication.

This is why mapping is useful in a BPO. You can see which contacts are caused by the journey, not by a lack of agent skill. If the SMS named the documents, one call would not exist. If a status message went out after the verification visit, two or three would not exist. These are avoidable contacts, and removing them improves experience and lowers volume at once.

How to build one without a consulting budget

  1. Pick one persona and one goal. “A salaried first-time buyer who wants a loan sanctioned quickly” is a good start. Trying to map every customer produces a map of nobody.
  2. Gather evidence from several sources: call and chat recordings, disposition codes, survey comments, and a few conversations with real customers. Agents are a rich source as well; they hear the same confusion dozens of times a day.
  3. Write the stages and touchpoints, including those outside your control, such as the client’s app or a field team.
  4. Mark the pain points, then attach numbers where you have them: contact volume per stage, repeat-call percentage, drop-off between stages.
  5. Pick two or three fixes with owners and a way of checking if they worked.

The limits of the map

A map built only from the company’s assumptions is a flattering fiction. It should come from evidence, and it should be revisited, because products and apps change. Another limit: a map is a snapshot of an average customer. Meera’s experience will differ from someone who applies with a co-applicant or one who is self-employed. Use the map to find patterns, and check with data before generalising.

Also, a BPO often does not own the journey. The lender owns the app, the SMS templates and the verification team. What the BPO can do is show the evidence: “Of the status-check calls last month, a large share were for applications in verification; here are five examples.” That is a contribution a client’s product team rarely gets from anywhere else, and it moves the BPO’s role from answering calls to improving the process behind them.

Meera, in the end, gets her sanction on day nineteen. She rates the last agent 5 out of 5 and tells her friends to avoid the lender. Both facts are true. A journey map is how you notice that both can be true at once.

Figures and names in the examples are illustrative.

Leave a Reply

Trending