Banking customer journey: connecting autonomy, advice and trust

Observe the banking relationship from the customer’s point of view

In a bank, the internal organization naturally splits the relationship into products, channels and departments. Customers, however, only see a series of tasks: opening an account, blocking a card, preparing a home purchase, understanding an unexpected direct debit. Each one starts with a need and ends when they have received a clear answer.

Looking at the relationship from their point of view changes the question. You no longer ask whether the app works or whether the branch is well rated, but whether the task gets done without unnecessary effort.

The Voice of the customer is the most direct source for adopting this point of view. App store reviews, Google reviews of branches, complaints, post-interaction surveys: verbatims describe the entire task, with its expectations, hesitations and breaks, where channel indicators only show a fragment of it.

This article is written for Directors and Heads of CX in charge of the customer journey or Voice of the Customer at a large bank or neobank serving a broad base of individual customers. It offers a method for reading banking journeys, from onboarding through to managing improvements.

Define journeys according to banking needs

Trying to analyze a bank’s “customer journey” on a single map rarely leads to a decision. A journey is defined by a need, with a starting point and an expected result.

Separate onboarding from everyday transactions

Onboarding is a rare and dense moment. Customers discover the institution, provide documents, accept terms and form a first impression of the quality of service. Their expectations focus on clear steps, fast approval and visibility on their application.

Everyday transactions follow a different logic: transfers, balance checks, card limits, address updates. Customers repeat them often, expect autonomy and have little patience when a simple transaction requires a phone call. Mixing both types of journeys in the same analysis blurs priorities, because the pain points and expectations are not alike.

In practice, name each journey after its result: “account opened and usable”, “limit changed”, “direct debit disputed”. A result-oriented name avoids confusing the journey with the screen or the department that supports it.

Isolate the moments that require more advice

Some moments call for more than a well-designed interface: a first mortgage, an estate settlement, a repayment difficulty, a savings investment. Customers make a binding decision and often look for someone who can guide them.

In the logic of a customer journey, these moments are stages in their own right. Spot them in the verbatims: customers use words of worry or hesitation, ask specific questions and request a conversation with an advisor. These are the moments when autonomy alone is not enough.

For each one, specify the channel customers expect, the acceptable time to get an appointment and what the advisor should already know before the conversation. Advice is not an extra: it is a journey stage that is designed, measured and improved like the others.

Make onboarding understandable

Onboarding concentrates many regulatory and technical requirements. For customers, though, it comes down to one question: do I understand what is being asked of me? When the answer is no, they give up, call or go to a branch, often without the institution knowing why.

Explain the process before the first steps

Announce the steps before they start: how many there are, roughly how long they take, which documents to prepare and what happens after the application is sent. A customer who knows they will need proof of address prepares it in advance, instead of stopping halfway through the sign-up.

Every request for a supporting document is worth explaining in one sentence: why this document, in what format, what happens if it is rejected. Onboarding verbatims often contain phrases like “I didn’t know what to send” or “my document was rejected without explanation”. They point to a lack of understanding, not to a careless customer.

Once the application is sent, its status must remain visible: received, under review, incomplete, approved. A clear confirmation at each status change reduces follow-up calls and reassures customers that the process is being taken seriously.

Preserve an informed decision

Simplifying a sign-up does not mean removing useful questions. For savings products such as life insurance and for financial instruments, the French regulators ACPR and AMF have set out their expectations on collecting information about customer knowledge: situation, knowledge, objectives, investment horizon. These questions enable suitable advice and protect the customer as much as the institution.

The journey challenge is therefore understanding, not reducing the number of questions. Explaining why a question is asked, rephrasing a technical term, allowing customers to go back before confirming: these choices help them decide with full knowledge.

The same goes for consent. A checkbox buried in a long screen informs no one. Understandable consent clearly states what the customer is committing to and gives them time to read what they accept.

Organize continuity between the app and the advisor

Your customers constantly move from the app to the branch, the phone or messaging. The most frequent break is not within a channel but in the move from one to another, when customers have to explain everything again.

Pass on the context when the channel changes

When customers leave the app to contact an advisor, the advisor should see what has already been done: the transaction attempted, any error message, the documents already uploaded. Without this context, the conversation starts with an interrogation and customers feel they are starting from scratch.

For each journey, define the information that must follow the customer when they switch channels. The list is often short: reason, step reached, documents sent, last confirmation issued.

The reverse matters just as much. What was agreed in the branch or on the phone must appear in the app: appointment set, document expected, next step.

Keep support accessible

Autonomy is a strong expectation, but it must not become an obligation. Customers stuck in the app should easily find how to reach a human, without giving up on their task.

Accessibility is also part of support. The Council of the European Union points out that the European Accessibility Act covers consumer banking services, among others, since 28 June 2025. Beyond the obligation, a journey that is readable for a visually impaired person or someone less comfortable with digital tools is generally readable for everyone.

Across the whole customer experience, the quality of support is judged by one simple criterion: do customers find help when they need it, in a channel that suits them?

Spot friction with a business grid

Not all friction is equal. Some of it comes from necessary controls, some from complications that serve no one. A business grid helps tell them apart and route each observation to the team able to act.

Distinguish symptoms from their possible causes

Customers describe a symptom: “my transfer is blocked”, “I’m being asked for a document again”, “I don’t understand these fees”. The cause may be technical, regulatory, organizational or related to the information provided. The table below links a few key moments to a signal, a diagnostic question and the team involved.

The same sentence can stem from several causes. The table does not decide for the teams: it frames the question to ask them and avoids treating a symptom without understanding what produces it.

Share observations in a decision-ready format

A list of verbatims does not trigger a decision. A decision-ready format presents, for each friction point, the journey concerned, the volume of feedback, the observed effect on satisfaction, a hypothesis about the cause and the team responsible for it.

This format also makes it possible to track each observation until it is resolved, instead of rediscovering it at every committee meeting.

Adapt the analysis to business customers

Business customers, such as tradespeople, shopkeepers, self-employed professionals or very small businesses, have journeys similar to those of individuals, but with several contacts on the customer side. The owner is not always the one carrying out transactions, and everyone’s rights must be clearly defined.

Take a hypothetical case, built to illustrate the method and not drawn from a real one: a shop manager wants to give her accountant read-only access to the company’s accounts. She needs to understand which access rights to request, how to grant them, what the accountant will be able to see or do, and how to revoke that access later. If any of these steps remains unclear, she calls her advisor or gives up, and the accountant keeps receiving statements by email.

This case shows that access rights are both a security issue and an experience issue. The deeper considerations of the B2B customer journey apply here: several decision-makers, more technical needs, a longer relationship. Read feedback from business customers separately from that of individuals, otherwise their pain points get lost in the mass.

Protect information when analyzing feedback

A bank’s customer feedback often contains sensitive information: account numbers, amounts, personal situations. Confidentiality must be built in from the design of the analysis, not added afterwards.

The principle of data minimization, recalled by the CNIL in its overview of the GDPR principles, applies: only process the data needed for the intended purpose. To analyze a pain point, the theme, the journey and the sentiment are enough; the customer’s identity and banking details are rarely necessary.

In practice, mask identifying data before analysis, restrict access to raw verbatims to authorized people and document how they are used. A VoC for banking and insurance approach relies precisely on this balance between depth of analysis and customer protection. Fortuneo is one of the banking institutions that are Glanceable customers. Your compliance teams remain the reference on these points.

Choose improvements that can be evaluated

A useful improvement is defined before it is launched: which journey, which pain point, which expected effect, and how you will know it happened. Without this framing, there is no way to tell whether a change actually helped customers.

Prioritize pain points by their measured impact in NPS points, rather than by how often they are mentioned. A very frequent pain point may weigh little on the relationship, while another, rarer one costs several NPS points among the customers who encounter it or increases their risk of non-renewal. A VoC platform links each pain point to the scores of the customers concerned and makes this comparison possible across all your feedback.

For each improvement selected, set a baseline before the change: share of verbatims mentioning the pain point, task abandonment rate, follow-up contacts. Then compare the same measure over an equivalent period, reading the verbatims to check that the problem has not simply changed shape.

Steer progress with the teams involved

Steering a banking journey brings together teams that do not always share the same indicators: digital, branch network, customer contact center, compliance, security. A shared dashboard, organized by journey rather than by channel, gives them a common reading of priorities.

Regularly review how pain point themes evolve, journey by journey. Customer insights analysis lets you track these themes over time and check that an improvement produces the expected effect, across all channels at once.

See Glanceable on your data.
A 30-minute conversation, on your own data.

Request a demo →