What the form is for
A bank customer feedback form captures structured feedback on a specific visit or digital journey, from customers who would never write a public review.
After a branch visit
- How satisfied were you with your visit today? (1 to 5)
- How easy was it to get what you came for? (1 to 5)
- How long did you wait? (Under 10 minutes / 10 to 30 / Over 30)
- What is one thing we could do better?
After a digital journey
- How easy was it to [open your account / make the transfer] today? (1 to 5)
- Did anything go wrong? (Yes / No; if yes, what?)
- What is one thing we could improve?
Rules
- Short: under a minute.
- Sent soon after the visit or journey.
- No requests for account numbers, PINs, OTPs or other sensitive details.
- Clear that it is optional.
- Available in the customer's language.
Analysing answers
Track scores by branch and journey, and classify open answers with the same topics you use for reviews, so form and review findings can be compared.
Open-ended survey analysis alongside reviews.
Analysing open ended survey comments alongside reviewsFree review snapshot
Want this done for your own reviews?
No commitment. We use your details only to send your snapshot and follow up. Privacy policy
An example
A bank sends a three-question form after account-opening appointments. Effort scores are low at branches where customers were asked to return with extra documents. A checklist sent before the appointment raises effort scores the next quarter.
Common mistakes
- Long forms.
- Asking for sensitive data.
- Forms only in English.
- Not linking answers to branch and journey.
Common questions
CSAT or effort score?
For service journeys, an effort question is often more useful; use one score per form.
How do we send it?
SMS or app notification soon after the visit or journey.
Should we offer rewards?
Keep rewards unrelated to the answers given.
How many responses per branch?
Enough for stable monthly scores; use longer windows for small branches.
Checklist
- Short form.
- Specific to the visit or journey.
- No sensitive data.
- Local languages.
- Same topics as reviews.
In short
Ask about the specific visit or journey right after it, in under a minute, without sensitive data, and analyse answers with the same topics as reviews.
Writing the open question
The open question produces the most useful answers. Ask for one specific thing, such as "What is one thing we could do better?", rather than "Any other comments?". A narrow question gets concrete answers; a broad one gets blanks or general praise.
Read a sample of open answers every month, not only the counts. They explain why a score moved and often name the exact step that went wrong.
Sending the form
Send the form through a channel the customer already trusts, such as the bank's app or an SMS from the bank's registered sender, and say clearly that the bank will never ask for passwords or OTPs. Customers are rightly wary of links that look like phishing; a clear, consistent sender helps both response rates and safety.
Closing the loop
When a customer leaves a low score with a comment, give branch staff a way to follow up within a few days. A short call to say what was done turns a poor visit into a recovered relationship, and tells the customer the form was read.
Doing this with Falcon
Falcon reads the Google Maps reviews of each of your locations, sorts them into the topics customers in your industry actually raise, built from your own reviews, and shows which locations and months are slipping, with the reviews behind every number. Small samples are flagged rather than ranked, so a location with only a handful of reviews is not compared unfairly.