- Industry
- Banking
- Department
- Marketing
- Team
- Brand and Insights
- Kind
- Investigator
- Approver
- Head of Communications
- Code
- MKT-12
It tracks mentions of the bank across news, social media, review sites and forums and explains sentiment spikes, such as an app outage, a fee change, a scam using the bank's name or a branch closure. It drafts a holding statement when a spike may become a crisis. **The problem it solves:** Why sentiment about the bank turned: which topic and sources, since when, which events explain it, and how far it has spread.
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 social listening tool: mentions, sentiment, reach and top posts by source and topic..
- 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
Weighs competing explanations against the evidence and shows which one holds up.
- 05Asks a person
Hands the work to Head of Communications with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the social listening tool: it logs the diagnosis and alerts the escalation contacts. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The reputation playbook: monitored sources, sentiment baselines, the crisis levels, holding statement templates and the escalation contacts for outages, scams and regulatory news.
Reads from
the social listening tool: mentions, sentiment, reach and top posts by source and topic.
Acts in
the social listening tool: it logs the diagnosis and alerts the escalation contacts.
Hands back
An object with period, sentiment_change, causes (a ranked list, each with cause, evidence, confidence and how_to_confirm), reach, crisis (true or false), holding_statement (text or null) and escalations (a list).
Asks a person when
Reach exceeds 250000, a holding statement is drafted, or the spike concerns the bank's safety, deposits or a regulator.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Baseline (days) | 30 | Sentiment is compared with this period. |
| Negative spike (%) | 50 | A rise this large is diagnosed. |
| Reach that is a crisis | 250000 | Negative reach above this triggers the crisis process. |
| Draft a holding statement | On | When on, a crisis gets a holding statement draft. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Diagnose negative rises of 50 percent against the 30-day baseline, ranking causes by evidence.
- Check for outages, fee or rate changes and impersonation scams first; a scam using the bank's name goes to the fraud team at once.
- Reach above 250000 triggers the crisis process and, when on is true, a holding statement.
- A holding statement never confirms facts about a customer, an investigation or a regulator; it is approved before release.
- Signs of a run on deposits, such as many posts about withdrawing money, go to the Head of Communications and treasury at once.
See the Brand Monitoring Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.