<aside> 💡 Use case: reply to every review in your voice, ask happy customers for more, and hear about mentions before they turn into problems. Bad reviews always wait for you.

</aside>

<aside> 👀 Who reads this folder: Reviews & reputation (together with brand-brain/), and the orchestrator. The playbook "One-star review lands" reads gbp-response.md and review-flow.md. Market radar shares the watch list in mentions-rules.md.

</aside>

gbp-response.md

<aside> 💬 Controls: how Claude drafts a reply to each kind of review, from five stars down to one, plus the special cases that should never get a drafted reply.

How to fill it: set who signs replies and the contact line you are happy to share in public. Keep the "never include" lines: no order numbers, no private details, no asking for a changed rating.

Save as brand-os/reputation/gbp-response.md.

</aside>

# Review reply guide (Google Business Profile)

> Read by: reviews-reputation, which drafts replies with Claude. Use the same guide for reviews that arrive through Podium or NiceJob.
> One block per kind of review. Who approves each kind lives in review-flow.md.
> Every reply passes brand-brain/tone-rules.md. A reply never argues, never shares a customer's details and never promises what messaging-bank.md does not back.

## Every reply
- Opens with: [FILL IN: e.g. the reviewer's first name as shown on the review]
- Signed by: [FILL IN: a first name, a role, or the brand]
- Length: [FILL IN]
- Never include: order numbers, phone numbers, email addresses, anything private about the reviewer
- Never ask for a changed rating

## 5 stars
- Goal: thank them for something specific they said
- Shape: thanks + the detail they mentioned + an invitation back
- Must include: [FILL IN]

Example (Northwind Coffee): "Thanks, Sam. Glad the Ethiopia roast made your Sunday. See you for the next bag."

## 4 stars
- Goal: thank them and pick up the one thing that held back the fifth star
- Shape: thanks + what they liked + a short answer to the gap
- Must include: [FILL IN]

## 3 stars
- Goal: show you read it, fix what you can, take detail offline
- Shape: thanks + the issue in their words + what you are doing + how to reach you
- Contact line: [FILL IN: the public contact point you are happy to share]

## 1 or 2 stars
The playbook one-star-review-lands reads this. These replies always wait for the owner.
- Goal: calm, sorry for the experience, move it to a private conversation
- Shape: sorry + the issue in their words, without admitting fault the facts do not support + the contact line + who will help
- Must include: [FILL IN]
- Never: blame the customer, guess what happened, offer a refund or discount without the owner's OK

Example (Northwind Coffee): "Sorry your order arrived late, Alex. That is not the experience we want for you. Please reach us at [contact] so we can put it right."

## Rating with no text
- Reply: [FILL IN: a short thanks, or no reply]

## Special cases
| Case | What to do |
|---|---|
| Names a member of staff | [FILL IN: thank or address without repeating anything private] |
| Looks fake or is not a customer | Draft nothing. Send it to the owner with the reason. [FILL IN: your process for reporting it to the platform] |
| Mentions safety, health, a legal threat or discrimination | Draft nothing. Alert the owner right away. |
| Is in another language | [FILL IN: reply in that language, or in yours] |
| Is about a competitor or a different business | [FILL IN] |

review-flow.md

<aside> 🔀 Controls: what happens from the moment a review lands to the moment a reply goes up, who approves each kind, and how you ask customers for reviews through Podium or NiceJob.

How to fill it: decide which star ratings you are happy to auto-approve. One and two stars always go to you. Before you write the review ask, check each review platform's own policy on incentives.

Save as brand-os/reputation/review-flow.md.

</aside>

# Review flow

> Read by: reviews-reputation. Tools: Google Business Profile for reviews, Podium and NiceJob for reviews and review requests, Brand24 for mentions.
> What happens from the moment a review lands to the moment a reply goes up, and how you ask happy customers for reviews.

## From review to reply
1. A review lands (Google Business Profile alert, or a new row in the reviews export).
2. Reviews-reputation reads it, sorts it by the table below and drafts a reply from gbp-response.md.
3. The draft goes where the table says. Nothing is posted until that step is done.
4. Every review and reply is logged at the bottom of this file and in logs/activity.md.

| Review | Who approves the reply | Reply within | Also do |
|---|---|---|---|
| 5 stars | [FILL IN: auto-approve, or the owner] | [FILL IN] | [FILL IN: add to customer words in messaging-bank.md, if they agree] |
| 4 stars | [FILL IN] | [FILL IN] | [FILL IN] |
| 3 stars | [FILL IN] | [FILL IN] | [FILL IN] |
| 1 or 2 stars | the owner, always, through queue/needs-your-ok.md | [FILL IN] | tell [FILL IN: who fixes the problem] |
| Safety, legal, fake | the owner, right away | none drafted | [FILL IN] |

Example row (Northwind Coffee): | 1 or 2 stars | the owner, always | [your time] | tell the dispatch lead |

## Who to tell
| Problem in the review | Person | How to reach them |
|---|---|---|
| [FILL IN: delivery, product, staff, billing] | [FILL IN] | [FILL IN] |

## Asking for reviews (Podium or NiceJob)
- Ask after: [FILL IN: the moment a customer is most likely happy, e.g. after delivery]
- Ask through: [FILL IN: SMS, email]
- Never ask more than: [FILL IN: how often one customer can be asked]
- Incentives: [FILL IN: your rule. Check each review platform's own policy before offering anything]
- The ask message:
  [FILL IN: two or three lines in your voice, with the review link]

Example (Northwind Coffee): "Hi Sam, your beans arrived on [date]. If they made your mornings better, a quick review helps other home brewers find us: [link]"

## Review log
Agents may add rows.
| Date | Platform | Stars | One-line summary | Reply draft file | Approved by | Posted |
|---|---|---|---|---|---|---|
| [FILL IN] | [FILL IN] | [FILL IN] | [FILL IN] | [FILL IN] | [FILL IN] | [FILL IN: yes or no] |

mentions-rules.md

<aside> 👂 Controls: what Brand24 listens for, how each mention is sorted, and what each kind triggers, including the "Competitor drops a promo" playbook and the crisis rule.

How to fill it: add your brand name with its common misspellings, your products, and the competitors from positioning.md. Then decide what makes a competitor promo worth a response and what counts as a crisis for you.

Save as brand-os/reputation/mentions-rules.md.

</aside>

# Mentions rules

> Read by: reviews-reputation (Brand24 mentions watch). Market-radar uses the same watch list for competitors.
> What to listen for on the web, how to sort what comes back, and what each kind of mention triggers.

## Watch list
| Term | Kind | Watch on |
|---|---|---|
| [FILL IN: your brand name and its common misspellings] | brand | [FILL IN: web, news, social, forums, reviews] |
| [FILL IN: product names] | product | [FILL IN] |
| [FILL IN: founder or spokesperson name] | person | [FILL IN] |
| [FILL IN: each competitor from brand-brain/positioning.md] | competitor | [FILL IN] |
| [FILL IN: an industry phrase you want to join] | topic | [FILL IN] |

Example row (Northwind Coffee): | "Northwind Coffee", "North Wind Coffee" | brand | web, news, social |

## Sorting a mention
| Kind of mention | Looks like | Goes to | Action | Needs the owner |
|---|---|---|---|---|
| Praise | A happy customer or a kind post | reviews-reputation | draft a thank-you reply | [FILL IN: yes or no] |
| Complaint | Something went wrong for someone | reviews-reputation | draft a reply from reputation/gbp-response.md, 3-star shape or lower | yes |
| Question | Someone asks about you | leads-conversations (through the orchestrator) | answer from conversation/faq-library.md | [FILL IN] |
| Press or a blog mention | An article, a feature, a list | the owner | no reply drafted | yes |
| Competitor promo | A competitor launches an offer or a campaign | market-radar | the orchestrator runs /competitor-drops-a-promo | yes, before any counter-offer |
| Crisis | Many complaints at once, a safety or legal issue, a viral negative post | the owner, right away | pause scheduled posts (brand-brain/tone-rules.md, sensitive moments) | yes |

## When a competitor promo counts
- Counts when [FILL IN: what makes a competitor promo worth a response: which competitors, which products, how big an offer]
- Never: copy their offer without the owner's OK, or mention them by name in a reply

## When it counts as a crisis
- [FILL IN: how many negative mentions, in how long, count as a crisis]
- Who is called: [FILL IN: name and how]

## Do not engage
| Account or site | Why |
|---|---|
| [FILL IN] | [FILL IN: known troll, legal dispute, spam] |

<aside> 👉 Next: /conversation

</aside>