A customer opens a checking account at a branch and leaves thinking everything is set. That evening, she tries to enroll in online banking and gets stuck. She calls for help the next day and gets access. A week later, she mentions the trouble in an onboarding survey.
At the bank, three teams see three different parts of that experience. The branch sees a completed account opening. The contact center sees a resolved call. The digital team may see an unfinished enrollment. The survey comment connects those events, but it can still end up in a monthly report with a note to “look into it.” When the same complaint appears the next month, who’s expected to do something about it?
Give the problem an owner
A CX team can pull together survey comments, call reasons, and enrollment data to pinpoint where customers get stuck. The next decision is who can change that step. If customers are entering the right information and still getting an error, the digital banking lead may be in the best position to own the fix. If customers leave the branch without knowing what they need to enroll, retail banking may own the change. The contact center can help either team understand what customers are trying to do when they call.
Give the owner a specific problem to solve and a date to report back. “Improve onboarding” leaves room for several teams to work on different things. “Find out why new checking customers get stuck at identity verification and propose a fix by next Friday” gives everyone a shared question and a next step.
Decide when to bring in leadership
Some fixes fit within a team’s day-to-day work. A branch manager might update the account-opening checklist and try it for two weeks. Other changes require vendor work, budget, or a decision across departments. If the digital banking lead needs the core provider to investigate how new accounts are passed to the enrollment platform, the issue may need a sponsor who can move that request up the queue.
Bring leadership a decision it can make. “We’re hearing complaints about enrollment” is an update. “We need to decide whether to move this vendor fix ahead of the next scheduled update” makes the request clear. Include how many customers appear to be affected, what they’re unable to do, and what staff are doing to help in the meantime.
Weigh what the problem keeps customers from doing
Start with frequency and consequence. A confusing label might draw more comments than an enrollment error, while the error leaves customers without access to their accounts until someone intervenes. That difference matters when both fixes compete for the same team’s time.
Survey comments help explain what happened from the customer’s perspective. Call logs and enrollment records can help estimate the size of the problem and show whether it’s concentrated in a particular channel, branch, or step. If the records point to one confusing instruction, the bank may be able to test a small change quickly. If they show customers repeatedly failing verification, the team has a clearer case for investigating the underlying issue.
Check whether the fix worked
Choose the measures before making the change. For online banking enrollment, the bank could track the share of new checking customers who enroll within seven days and the number of enrollment-related calls per 100 new accounts. Compare similar groups before and after the change, using the same follow-up window. Then read the latest survey comments to see whether customers still describe getting stuck at that step. An overall satisfaction score can stay steady even when a specific part of onboarding gets easier.
In your next CX review, take one issue that keeps coming back. Before the meeting ends, agree on who owns it, what they can do next, and when you’ll check whether customers are having an easier time. That gives the next report a different question to answer. Did the change help?