What this is good for
A waiting room without a notification is just an empty voice channel with somebody sitting in it and hoping. That is exactly the usual state: the channel is called “Support”, but nobody notices that somebody is waiting in it.
This building block closes that gap. If somebody joins one of the defined waiting rooms, the team gets a message, with the name, the channel and the number of people waiting.
Setup
Two ways of reaching the team
- Direct message, reaches the person even when they do not have the server open at the moment. More reliable, but only as long as DMs from server members are allowed.
- Notice in the channel, visible to everyone in the team, including those whose DMs are closed. But it gets lost if the channel is not watched.
The two together are the safest combination and cost nothing extra.
Why not every movement is reported
Somebody who joins a channel and leaves again after five seconds has no request, they misclicked. That is why the bot waits a moment before reporting, and does not send new messages for the same person every minute.
It also limits the number of direct messages per event. A team with forty members should not produce forty notifications just because somebody briefly looked in.
Your own text
The message to the team can be written freely. The bot fills in these building blocks:
| Placeholder | Becomes |
|---|---|
{user} | the person who is waiting |
{channel} | the waiting room |
{waiting} | number of people waiting |
{server} | name of the server |
If you leave the field empty, the bot sends the translated default sentence in your server's language.
Common pitfalls
- Nobody is notified. Check whether waiting rooms and team roles are entered, without both, nothing happens. Also check whether anyone from the team is online at all.
- Only some people get the DM. Anyone who has disabled direct messages from server members cannot be reached. That is what the alert channel is for.
- The settings are empty again after saving. That was a bug in an earlier version of the dashboard and has been fixed. Should it occur again, it is a fault on our side, please report it.