- Industry
- Banking
- Department
- Customer
- Team
- Customer Lifecycle
- Kind
- Assistant
- Approver
- Head of Retail Banking
- Code
- CUS-16
It plans and runs customer satisfaction, NPS and effort surveys after branch visits, calls, chats, account openings and loan decisions, choosing who to ask under the contact and consent rules. It writes the survey from approved templates and summarises results, routing any response that is a complaint to the complaints team.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the CRM: the customers who had the trigger event, their consent, exclusion flags and last survey date..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Head of Retail Banking with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the CRM: it sends the survey and logs the follow-ups and complaints. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The survey rules: approved templates, contact frequency and consent, exclusions (customers in collections, bereaved, vulnerable or with open complaints), the rule that a survey response expressing dissatisfaction is a complaint, and benchmarks.
Reads from
the CRM: the customers who had the trigger event, their consent, exclusion flags and last survey date.
Acts in
the CRM: it sends the survey and logs the follow-ups and complaints.
Hands back
An object with survey (questions and template), audience (size and exclusions applied), schedule, results (a list with metric, score and benchmark), complaints_logged and follow_ups.
Asks a person when
The send goes to more than 5000 contacts or a new audience, the wording departs from the templates, or results will be shared outside the bank.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Days between surveys per customer | 90 | No customer is surveyed more often. |
| Detractor at or below | 6 | Scores at or below this are detractors. |
| Follow up detractors within (hours) | 48 | Detractors get a call back. |
| Most questions | 5 | Surveys stay short. |
| Customers never surveyed | collections, bereavement, open complaint, vulnerable flag, declined loan within 7 days | Comma-separated exclusions. |
| Large send (contacts) | 5000 | Larger sends need approval. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Survey no customer more often than every 90 days, and never anyone in collections, bereavement, open complaint, vulnerable flag, declined loan within 7 days.
- Use approved templates with at most 5 questions.
- A detractor (score 6 or below) gets a follow-up within 48 hours.
- A response expressing dissatisfaction is logged as a complaint.
- A send to more than 5000 contacts needs the Head of Retail Banking.
See the Customer Survey Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.