Banks · Customer satisfaction, NPS and feedback programmes
Ask the borrower after disbursal, and send the answer to someone who can act.
A feedback programme for a bank asks customers about a defined moment, such as account opening, loan disbursal or a branch visit, and sends each answer to a named person at the branch or the loan desk. GullySales designs the questions and trigger points, sets up the feedback record, and agrees who calls back when a customer is unhappy.
Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

What customer satisfaction, NPS and feedback programmes means
Customer satisfaction, net promoter score (NPS) and feedback programmes collect structured feedback about a purchase, service experience, or ongoing relationship, with a defined response to what customers say. GullySales designs the questions and survey timing, sets up the feedback record, and assigns follow-up responsibilities so poor experiences reach someone who can act.
Last updated 14 Nov 2026. Rules for this trade differ by state and professional body, and they change. We describe restrictions in general terms, so check the current position with your own council or adviser before you publish anything.
For banks
Where it usually goes wrong, and what we would do.
“A branch score that only reflects the counter”
A survey handed out at the teller window reaches the customer who is already standing in the branch. It misses the borrower who waited for a sanction letter, the depositor who stopped renewing, and the account holder who moved the salary elsewhere. The average looks calm because the unhappy customers never reached the form. Before any question is written, the first decision is which moments of the customer's relationship the bank wants to hear about, and which customers sit outside the counter altogether.
“Feedback and complaints are different records”
A customer who writes that a debit card was blocked without warning is making a complaint, and the bank already has a formal route for it under the regulator's rules for grievances. A customer who says the loan officer explained the documents clearly is giving feedback. Mixing the two in one spreadsheet means a complaint can sit in a survey export, waiting for someone to notice. The programme keeps them apart and agrees with your compliance team where a survey answer must be handed over to the grievance process.
“Branch staff influence the answer”
When a relationship manager hands the phone to a customer and asks for a high score, the number measures the relationship manager's persuasion. Branch teams that are judged on a score learn how to protect it. A bank programme needs a collection route that staff cannot steer, such as a message sent from a central number after the visit, and a review rule that stops the score from becoming a quota that rewards pressure instead of honest answers.
“Different customers want different things asked”
A retired depositor deciding about a fixed deposit renewal, a small trader waiting for a working capital limit and a non-resident customer waiting for an account to open do not share one experience. One generic question about overall satisfaction hides all three. The programme sets a short question for each moment, in the language the customer uses at the branch, so a low answer points to the step that failed, such as document collection, a pending verification or an unreturned call.
What we do
What we deliver for banks.
The work available for this need. We agree the deliverables and responsibilities for your engagement in writing.
Moment-by-moment survey map
A written list of the points in a bank relationship worth asking about, such as account opening, loan sanction, loan disbursal, deposit renewal and loan closure. For each point it states what decision the answer supports and who would act on it. You approve the map before a single question is drafted.
Result: You can read, for each survey, the decision it supports and the person who receives the answer.
Approved question set
Short questions with a fixed scale, one open comment prompt, and wording your compliance team has reviewed so nothing reads as a sales pitch or a promise of a product. Versions are prepared in the languages your branch customers use. The same question is used across branches so scores can be compared.
Result: Every branch asks the same question in the same words, which you can verify by reading the approved set.
Audience and trigger rules
A record of which customers receive which survey, at which event in your core banking or loan system, and which customers are left out, such as those in an open grievance or a recovery process. It also sets a repeat-contact rule so one customer is not asked after every small transaction.
Result: You can check any customer's record against the rules and see why they were or were not asked.
Feedback and follow-up log
A shared record that links each answer to the customer, the branch and the staff member concerned where identification is agreed. Fields cover the issue named, the person assigned, the status of the callback and the recorded outcome. Complaints are tagged so they move to the grievance route instead of staying in the log.
Result: Any low answer in the log shows a named owner and a status, so you can see which callbacks remain open.
Low-score callback guide
A short script and routing table for the person who calls back after a critical answer. It covers what the caller may say, what must go to the branch manager, and what must go to the compliance or grievance officer. It avoids promises about loan outcomes or rates.
Result: The branch manager can read the guide and say who receives each kind of critical answer.
Baseline and branch comparison view
A view showing scores next to the number of responses, the share of customers asked and the number of callbacks completed. A branch with few responses is marked as thinly sampled instead of being ranked beside a branch with a full sample. Recurring causes are listed apart from one-off comments.
Result: You can compare branches fairly, and see which scores rest on too few answers to trust.
How the result is measured
- Survey invitations and response rate, with reply counts
- NPS or satisfaction trends against the baseline
- Response coverage by agreed customer group or branch
Recorded as a baseline before work starts, so every later report has an honest comparison.
Who it is for
This is written for these banks.
- Private sector bank branches
- Public sector bank branches
- Regional rural banks
- Cooperative banks
- Small finance banks
- Business correspondent networks
- NRI-focused branches
- MSME-focused branches
Before you decide
Agree the work. Know how to judge it.
Customer satisfaction, NPS and feedback programmes for banks: use these checks to prepare, choose the scope, and review what changes.
Bring the right evidence
Review repeat orders, inactive customers, and reasons for leaving. Separate a normal buying interval from a customer who stopped because of an unresolved problem.
Make the scope clear
Choose the customer group and the reason to contact them. Agree how complaints, renewal decisions, and additional offers are handled, including when a sales message is inappropriate.
Check the work in use
Track the response through to a retained or repeat order, with discounts and service costs visible. Record why the customer returned rather than crediting every repeat purchase to the campaign.
Know when to change course
If customers leave because delivery is unreliable, fix that before offering a loyalty reward. Repeated promotions can hide the cause without improving the experience.
These are discussion points, not a fixed package. GullySales confirms the deliverables, responsibilities, fee, and term in writing after reading your brief and speaking with you.
Before we start
What to have ready before the work starts.
The records, access and decisions this work needs from banks. Anything missing is noted in the written scope, with who will supply it.
- Your current feedback and complaint records
- Share the counter forms, helpline notes or complaint register you already keep, with customer names removed if you prefer. They show what customers already say and where the bank loses track of it. Without them, the survey questions are guesses, and the first set of answers may repeat things your team already knows.
- Event data from your core banking system
- We need to know which events the bank can detect and export, such as account opening, loan disbursal or deposit maturity. A survey tied to a real event reaches the right customer at the right moment. When the event data is missing, the survey falls back to manual lists, which branch staff must keep up to date.
- A named callback owner at each branch
- Pick the person who calls back an unhappy customer, and a second person who covers when the first is absent. A survey that finds a problem and has nobody to deal with it does more harm than no survey. Name the escalation route to the branch manager, and from there to the grievance officer.
- Your compliance officer's availability
- The notice, the consent wording and the handover of any complaint to the grievance process need your compliance officer's review. Advertising and customer-contact rules differ by country and change. Without that review the programme waits, because GullySales prepares the text but your adviser decides what the bank may send.
- A list of customers to exclude
- Decide which customers should never receive a survey, such as those in an open dispute, a recovery process or a pending legal notice. A satisfaction message sent to a customer in recovery damages trust and can create a record the bank does not want. The list needs an owner who keeps it current.
How it works
How the customer satisfaction, NPS and feedback programmes work runs
The work itself, in order. How an engagement starts, from your brief to a written scope, is set out on our method page.
- 1
Review of current branch forms
You share whatever the bank already collects, whether a paper form at the counter, a suggestion box log or a helpline note, along with a few examples of how a complaint was handled. We read them to find which customers are never asked and who currently decides what happens after an unhappy answer. The figures on record at this point become the baseline.
- 2
Choice of moments to ask
We propose the moments in the customer relationship worth surveying and the question each one serves. You decide which two or three to start with, based on where your branches hear about problems too late. We also agree which customers are excluded, for instance those in recovery or in an open dispute.
- 3
Question and notice approval
We draft the questions, the scale and the notice that tells a customer why the bank is asking. The branch head, the product owner and your compliance lead each review their part. Wording that could read as a rate promise, an offer or a pressure to answer well is removed before anything is sent.
- 4
Log and routing set-up
We build the feedback log in the sheet or CRM you already use and connect the trigger events your teams can provide. Each answer is assigned to a callback owner, and complaints are routed to the grievance officer. Sample records are tested to confirm that a low answer reaches the right person.
- 5
Trial at selected branches
The survey runs at a small group of branches that you choose, including one that is busy and one that is quiet. Staff are briefed on what they may and may not say to customers about the survey. We watch whether callbacks are made and whether the sample reaches borrowers, not only counter visitors.
- 6
Reading results against the baseline
After the trial, the scores, response numbers and callback records are set against the figures recorded before the work began. You decide whether to widen the survey, change a question or leave a moment out. Any branch with too few answers is flagged so its score is not used to judge the team.
Where this fits
Three pieces of sales work, in this order.
This work sits inside sales process design, at stage 1, prospecting and lead generation. The audit comes before it, and sales management keeps it running.
Step 1
Sales audit
Find where deals are being lost and what to fix first.
Start here if you cannot say where orders are lost.
Step 2 · you are here
Sales process design
One written way to sell, from first enquiry to repeat order.
Start here if every salesperson sells differently.
Step 3
Sales management
A target, a review routine and someone who owns the number.
Start here if the team has targets and no routine.
FAQ
Questions owners ask before they call.
Not here? More answers, or ask on WhatsApp.
What does an NPS programme for a bank measure?
Should a bank survey customers whose loan was declined?
How is a complaint handled when it appears in a survey?
Can branch staff be rewarded for a high satisfaction score?
Which channel should a bank use to ask?
What if our branches get very few responses?
How much does it cost?
How long is the contract?
How soon will we see results?
Who will actually do the work?
From the blog
Further reading for banks.
6 min read · 6 Oct 2026How buyers decide which lender or adviser to trustPeople choosing a bank, lender, adviser or insurer start with a name someone gave them, then check you before calling. See what they look for.
7 min read · 21 Sept 2026How to advertise to airport travellersA terminal is a small number of regular flyers counted many times, and the crowd changes completely between the six o'clock bank and the summer holidays.
6 min read · 29 Jan 2026Local search for a financial services office: profile, reviews and what you can sayHow a financial services office can set up its Google Business Profile, ask for reviews and reply to them without breaking client confidentiality.
More for banks
Related work to consider.
Closest to this: customers after the sale
Also for banks
Or start from the overview: sales and marketing for banks.
Your next practical step
Tell us what you are trying to grow, and we will read it before we call.
Eight short steps, mostly taps. Skip anything you would rather answer on the call.