Skip to main content

Reduce the Discord pings your Rust volunteers have to answer

Ask volunteers which messages interrupted them while they were playing, working or asleep. Pick the most common interruption and ask what someone actually needed to do. The fix may be a clearer join post or a scheduled reply window instead of another person watching chat.

Read a week of pings by the action they required

Take a few real examples from the last week. For each, note who was asked, what they did and whether waiting would have changed the outcome. ‘Can’t find the practice world’ usually needs the join link. ‘When is the next tour?’ can wait for the event host. Several players getting disconnected from the same world merits a timely server check.

Read a week of pings by the action they required
Common interruptionWhere it goes next week
Same join question in several DMsPut the current join post in the channel header or a pin and link to it.
Request to repeat Saturday’s eventReply in the event thread during the next planning session.
Several people suddenly cannot playAsk the named helper for the current window to check the affected world.

Make the urgent route easy to hear

Agree which channel carries requests that need immediate attention during covered hours. Helpers can set Discord notification overrides for that channel and read the others when they have time. Send a test message during a covered window and confirm the person who should get it actually sees it.

Check a week later whether the same helper still gets most of the messages directly. Move the answer they keep typing to the place where the questions start.

Sources

Analytics settings

Analytics are off.

Help improve RustSC with page counts and performance measurements. Privacy details