Community Response

Community Response

The response is more durable than the thing being responded to. Players screenshot it, quote it back, and hold the company to it long after the event has ended.

When to use

• A change lands badly.
• A player-signals row is confirmed and public.
• Something broke and players noticed before the company did.

Steps

1. Check the scale first. player-signals with its channel and count. Loud is not the same as common, and responding to a small loud group as though it were everybody creates the impression that it was.
2. Check whether they are right. They frequently are, and telemetry usually settles it in minutes.
3. Acknowledge specifically. "We hear you" without naming the thing reads as a template, because it is one.
4. Say what will happen, or say you do not know yet. Never a date you do not hold — anything given goes on commitments.
5. Do not argue the numbers publicly. A company explaining why a complaint is statistically unrepresentative has lost regardless of being right.
6. Record it. Close the signal with what was said and done; the same complaint returns every few months and the last response is the baseline for the next.

Output

A response the operator has approved, and the player-signals row updated. Anything published to the community is the operator's call, whatever the policy tier allows.