How long did you think about it before actually moving?
Bank Switching Research
Interviewer agent · 1.7K uses
Transaction volume measures what people did there, not what the branch was holding together. A branch closure looks clean on a transaction model and lands very differently for the customers who used it for the things that do not show up as transactions: complex problems, reassurance, cash for a business, a person who knows them. This conversation finds out what those were and whether the relationship survived.
Start from this conversation and adapt it to your team — change any question, add your own logic, and connect the tools you already use.
The core fields every response captures.
Always ask what they used the branch for beyond routine transactions
Always ask whether the closure made them consider moving banks
Follow-ups that change based on what people say.
If they run a business, ask specifically about cash and check handling
If they have considered moving, ask how far they have taken it
Different paths for different answers.
Send at-risk relationships to retention before the branch actually closes
Escalate accessibility problems to the operations and compliance teams
Actions that fire the moment a response comes in.
Alert #retail-banking in Slack when closure-driven switching intent appears
Update the customer record in Salesforce with post-closure risk
Trigger a retention outreach for customers flagged at risk
The conversation asks what they genuinely used the branch for and how often, pushing past routine transactions to the occasions that mattered. It then asks what they do instead now, whether that substitute works, and whether the closure changed how they feel about the bank. It closes by asking directly whether it made them consider moving, which is the number the closure model never included.
Select customers within the catchment of a closing or recently closed branch
Distinguish routine transactions from the occasions that actually needed a branch
Capture whether they have considered moving, as the real cost measure
Route at-risk relationships to retention before the closure completes
Static forms force complex situations into rigid dropdowns. Perspective captures structured data and the reasoning behind it — so your team makes better decisions, faster.
No context. No follow-up. No next step.
"Tell me more about the timeline — when did this start, and is there a deadline your team is working against?"
Extracted & structured automatically
Category
High-priority
Urgency
Deadline: 2 weeks
Sentiment
Frustrated but hopeful
Next step
Route to senior team
Right team. Full context. Instant action.
It is research with customers in the catchment of a closing or recently closed branch, measuring what the branch was actually used for and what the closure costs in relationship terms. It complements the transaction-based model that justified the closure by capturing the activity that model could not see.
More banking templates for switching, branch experience and call center.
How long did you think about it before actually moving?
Interviewer agent · 1.7K uses
What did you open that account for?
Interviewer agent · 1.1K uses
How did you first find out about the change?
Interviewer agent · 2K uses
What did the credit union do well?
Interviewer agent · 1K uses
What decided it in the end?
Interviewer agent · 2K uses
How often did you hear from your adviser?
Interviewer agent · 1.6K uses
How banks measure the relationship cost of a branch closure.

How banks close the gap between a satisfaction score and a fixable cause.
Read article
How a challenger bank rebuilt onboarding around conversation instead of forms.
Read article
How a member-first fintech uses conversation to understand financial intent.
Read articleReplace drop-off, poor qualification, and missing context with AI conversations that capture structured data and real understanding. Set up in minutes.
No credit card required • Cancel anytime