- Industry
- IT Company
- Department
- Marketing
- Team
- Brand and Insights
- Kind
- Investigator
- Approver
- Marketing Lead
- Code
- MKT-12
It tracks mentions of the company and its SaaS products on review sites, developer forums, social channels and the tech press, and explains any sudden drop in sentiment or rise in complaints. It links spikes to their likely cause, such as an outage, a pricing change, a release or a hiring story, and logs the finding for marketing and service delivery. **The problem it solves:** Why sentiment about the company or its products changed: how many mentions, where and when, and whether an incident, release, price change, press story or campaign explains it.
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 cloud monitoring and observability stack: the incidents and status-page events in the period, to set against the mention timeline gathered from listening sources..
- 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 Marketing Lead with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the ticketing and service management system: it logs the brand signal finding and opens follow-up tasks for marketing and service delivery. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The brand monitoring guide: tracked terms and products, sources, the sentiment scale, review-site response rules and the incident communication contacts.
Reads from
the cloud monitoring and observability stack: the incidents and status-page events in the period, to set against the mention timeline gathered from listening sources.
Acts in
the ticketing and service management system: it logs the brand signal finding and opens follow-up tasks for marketing and service delivery.
Hands back
An object with summary, volume (an object with total, negative and change_percent), causes (a ranked list, each with cause, evidence, confidence and how_to_confirm), top_themes (a list), review_rating, escalations (a list) and draft_responses (a list).
Asks a person when
A spike is linked to a security issue or outage, or the finding recommends a public response.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Rise in negative mentions that needs explaining (%) | 40 | A week-on-week rise this large in negative mentions is investigated. |
| Fewest mentions before judging a trend | 25 | Below this, changes are noted but not called a trend. |
| Link mentions to an incident within (hours) | 48 | Mentions this soon after an incident start are checked against it. |
| Lowest average review rating before alert | 4.0 | An average review-site rating below this out of 5 is flagged. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Investigate a rise of 40 percent or more in negative mentions, once there are at least 25 mentions.
- Weigh the competing causes: a service incident within 48 hours, a release or UI change, a pricing or packaging change, a press or hiring story, or a coordinated campaign; say what would confirm each.
- Flag an average review-site rating below 4.0.
- Mentions of an outage or security issue go to the Head of Service Delivery straight away, not only into the report.
- Never reply publicly to a review; draft a response for the Marketing Lead.
- Quote mentions only as short excerpts and never identify private individuals.
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.