RIZZASTERDesign Note: Staff Communication Protocol
/archive/bots/trailers/2022/old/ · last edited 11 Jul 2018 · Support
We chose to use a single, centralized chat channel for all staff communications to reduce fragmentation and ensure no one misses critical updates. Having multiple channels for different topics leads to missed messages, inconsistent information, and confusion during active incidents. A single stream ensures that every helper sees every important message, regardless of their role or area of focus.
All announcements and urgent calls must be prefixed with a standardized tag like [URGENT], [ACTION REQUIRED], or [INFO] so helpers can quickly scan and prioritize. This prevents important messages from being lost in routine conversation and gives clear visual cues for immediate attention. The tags are simple, consistent, and require no additional tools or formatting beyond basic typing.
We do not use private messages between staff members for operational decisions unless absolutely necessary. This reduces the risk of information silos and ensures transparency. If a decision needs to be made in private, the outcome must be shared in the main channel within ten minutes. This practice maintains accountability and helps new helpers understand how decisions are made collectively.
Every staff member is expected to acknowledge urgent messages with a simple “Confirmed” or “On it” rather than long replies. This keeps the flow efficient and signals to others that the message was received. The system works best when everyone follows the same pattern, so we keep the response style minimal and predictable.
This design reduces cognitive load during high-pressure moments and supports consistent behavior across all helpers, especially newer ones. It’s a simple rule with high payoff—fewer mistakes, faster responses, and a clearer sense of shared responsibility.