Orm

---
name: orm
description: Online reputation management handbook — monitoring, triage, response craft, escalation, and amplification, with fintech/prop-firm compliance notes.
---

# Online Reputation Management (ORM) Playbook

Brand-neutral craft for monitoring and responding to what people say about a
brand across social, review sites, and comment sections. The goal is not
"respond to everything" — it's respond to the right thing, in the right way,
fast enough to matter, and never make a bad moment worse.

## Monitoring — what to watch

- **Direct mentions and tags** across every platform the brand is active on
  (comments, replies, quote-posts, DMs where platform norms make DMs public
  enough to matter).
- **Untagged mentions** — brand name or product name used without an @, which
  is where a lot of honest sentiment (positive and negative) actually lives.
  Search brand name, common misspellings, and product nicknames.
- **Reviews and ratings** on any third-party site relevant to the category
  (app stores, Trustpilot/G2-style sites, industry-specific review boards,
  Reddit threads that function as de facto reviews).
- **Comment sections on the brand's own posts** — these are higher-intent
  than random mentions because the commenter is already engaged with brand
  content.
- **Competitor and industry conversations** where the brand gets compared —
  worth watching for both risk (unfair comparison) and opportunity (a chance
  to add value without being asked).
- **Cadence:** high-volume channels (X, comments on active posts) need
  near-real-time or same-day monitoring; lower-volume channels (review sites,
  niche forums) can be checked daily. A crisis-severity mention on any
  channel escalates the check frequency for that channel immediately.

## Triage — sort before you respond

Every incoming mention gets a severity classification before anyone drafts a
reply. Speed of response should scale with severity, not with how easy the
message is to answer.

| Type | Signal | Response urgency |
|---|---|---|
| **Praise** | positive sentiment, no ask | Low — batch these, a like/heart or brief thank-you is enough |
| **Question** | genuine ask about product/service | Medium — same-day answer, factual, helpful |
| **Complaint** | specific grievance, real user, fixable | High — fast acknowledgment, move to resolution |
| **Troll / bad-faith** | inflammatory, no real ask, seeking a reaction | Special handling — see below, usually no public reply |
| **Crisis** | complaint gaining velocity, credible harm claim, or press/influencer pickup | Immediate — escalate before drafting anything |

Triage errors run in both directions: treating a real complaint as a troll
(and ignoring it) breeds resentment that resurfaces later; treating a troll
as a real complaint (and engaging at length) feeds the exact behavior you
wanted to starve.

## Response craft per type

**Praise.** Keep it short and specific — react to what they actually said,
not a generic "thanks for the love!" A specific reply signals a human read
the comment; a generic one signals a bot did.

**Question.** Answer the actual question first, then add anything extra.
Link to a canonical resource (help doc, product page) rather than re-typing
a long answer that will drift out of date. If the answer requires account
specifics, that's the cue to move to DM (see below) — don't ask for account
details in a public thread.

**Complaint.** Acknowledge fast, in public, briefly — even if the full fix
takes longer. A public "we see this, we're on it, DMing you now" does more
reputational work than a perfect private fix that never gets a public
acknowledgment. Then move the specifics to DM or a support channel. Never
argue the facts of the complaint in public, even if the complainer is
factually wrong — correct gently and privately; a public factual
argument reads as defensiveness regardless of who's right.

**Troll / bad-faith.** The default is no public reply. Engaging rewards the
behavior with attention and reads to onlookers as the brand taking the bait.
Exceptions: if the troll comment is gaining real traction and onlookers are
starting to believe a false claim, a single calm, factual correction — once,
not a back-and-forth — can be worth posting. After that, disengage. Never
argue, never get sarcastic, never delete a comment just because it's
unflattering (deleting a fair-but-harsh comment escalates faster than
leaving it).

**Crisis.** Do not improvise a public response before escalating internally.
See Escalation below.

## When NOT to respond

- Bad-faith trolling with no real audience traction (responding creates the
  traction).
- Spam and bot mentions.
- A complaint already being handled in a parallel thread — one clear
  response beats three redundant ones.
- Anything where a public reply would require disclosing another user's
  private information to defend the brand — don't do it, even if it would
  win the exchange.
- Legal, regulatory, or safety-adjacent complaints before the appropriate
  internal function (legal/compliance/support lead) has seen it — see
  Escalation.

## Escalation

- **Define the trigger before you need it:** velocity (a complaint getting
  shared/quoted faster than normal), reach (an account with real audience
  picks it up), or content (any claim involving safety, fraud, discrimination,
  legal threat, or financial harm) all escalate immediately regardless of
  follower count.
- **Escalate to a real person, not a queue** — a crisis-tagged mention should
  reach a named owner (support lead, founder, comms) within minutes, not sit
  in a shared inbox.
- **Freeze automated/scheduled posting** during an active crisis window —
  nothing looks worse than a cheerful scheduled promo post landing next to
  an active complaint thread.
- **One voice, one message.** During escalation, designate who is authorized
  to post publicly on the brand's behalf — multiple people improvising
  responses in parallel is how crises get worse.
- **Document the resolution** once it's handled — what happened, what was
  said publicly, what was fixed — so the next similar case doesn't start from
  zero.

## Turning positive mentions into amplification

- **Ask before you reshare.** A quick "mind if we share this?" costs nothing
  and avoids the (rare but real) case where someone didn't want the
  attention.
- **Reshare specific, credible praise** over generic compliments — a
  detailed positive story ("switched after X and saw Y") is more persuasive
  reshared than "love this brand!"
- **Engage genuinely before asking for anything.** A real reply to a fan's
  comment does more long-term goodwill than immediately pivoting to "can we
  feature this?"
- **Route strong organic praise into other channels** — a great review can
  become a testimonial on a landing page, a case-study seed, or a quote in
  a future post, with credit and permission.
- **Treat power users and repeat positive commenters as a mini community** —
  acknowledging them consistently (not just once) turns them into reliable
  amplifiers over time.

## Compliance sensitivity for a prop-firm / fintech brand

Reputation responses for a trading or financial platform carry compliance
risk that a generic consumer brand doesn't. Apply these on top of everything
above, every time:

- **Never make or imply an earnings, profitability, or pass-rate guarantee**
  in a reputation response, even casually, even when trying to reassure an
  upset user ("you'll definitely pass next time" is a claim the brand cannot
  make).
- **Never confirm or discuss another user's specific account, balance, or
  trading results in public** — this is both a privacy problem and, in some
  jurisdictions, a disclosure problem. Move to a verified private channel
  immediately.
- **Be careful with "we fixed it" language on anything execution- or
  rule-related** — overclaiming a fix on a technical issue that affects
  trading outcomes can itself become a financial claim if worded loosely.
- **A complaint alleging financial harm, fraud, or a rule/payout dispute is
  automatically crisis-tier**, regardless of the complainer's reach — these
  are the categories most likely to involve regulators, press, or legal
  exposure if mishandled publicly.
- **Keep standard disclaimers ready to paste** ("Trading carries substantial
  risk of loss," "No guarantee of challenge pass or payout," "Not financial
  advice") for any public response that touches outcomes, and default to
  brand-neutral language about firms/rules rather than disputing a user's
  characterization of a specific firm in public.
- **When in doubt, say less in public and more in private.** A terse, calm
  public acknowledgment plus a real private resolution is always the safer
  default over a detailed public defense of a financial claim.