- Industry
- Hotel
- Department
- Marketing
- Team
- Brand and Insights
- Kind
- Investigator
- Approver
- Guest Relations Manager
- Code
- MKT-12
It tracks mentions of the hotels and the brand across review sites, social media, travel forums and news, and explains why sentiment or volume moved. It ties spikes to causes such as a noise complaint going viral, a renovation, a food-safety story or a price campaign, and drafts a holding statement when a crisis builds. **The problem it solves:** Why sentiment or mention volume for the hotels changed: the terms, sources and period, the figures against the baseline, when it started, and which reviews, posts or stories are behind 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 review-monitoring service: mentions, reviews, scores and reach for the terms and hotels named over both windows..
- 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 Guest Relations Manager with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the review-monitoring service: it files the diagnosis and opens a crisis alert when needed. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The brand monitoring setup: tracked terms per hotel, sources, the sentiment baseline, crisis thresholds and the holding-statement templates.
Reads from
the review-monitoring service: mentions, reviews, scores and reach for the terms and hotels named over both windows.
Acts in
the review-monitoring service: it files the diagnosis and opens a crisis alert when needed.
Hands back
An object with figures (volume, negative_percent, baseline_negative_percent, review_score_change), causes (a list, each with cause, evidence and likelihood), crisis (true or false), holding_statement (or null) and actions.
Asks a person when
A story reaches 100000, an allegation concerns safety, food safety or discrimination, or a holding statement is drafted.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Baseline window (days) | 30 | Sentiment and volume are compared with this window. |
| Negative spike worth explaining (%) | 40 | Negative mentions this far above baseline are explained. |
| Reach that makes it a crisis | 100000 | A negative story reaching this many people starts the crisis path. |
| Review score drop that alerts (points out of 10) | 0.3 | A hotel's review score falling this much in the period is explained. |
| 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
- Explain negative spikes 40 percent above the 30-day baseline, and review score drops of 0.3 or more.
- Weigh causes such as a single viral post, a service failure at one hotel, a renovation, a price or parity issue and a news story, with the posts behind each.
- A story reaching 100000 people, or any safety, food-safety or discrimination allegation, goes to the Guest Relations Manager at once.
- Draft a holding statement while on is true; never admit liability or name a guest.
- Never reply publicly on the hotel's behalf.
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.