Skip to content

Commit 7fe051e

Browse files
committed
add instructions for unresponsive tickets
1 parent bb73619 commit 7fe051e

File tree

1 file changed

+22
-0
lines changed

1 file changed

+22
-0
lines changed

README.md

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -318,6 +318,28 @@ This is ideal for tickets that are neither critical nor time sensitive. Members
318318

319319
This works for immediate concerns that need to be addressed quickly. You can run tickets this way for cases that are easily resolvable or just to promptly pull someone aside.
320320

321+
## 3.5 Addressing Unresponsive Members
322+
Sometimes, you will not get a response after some time. This could be a number of reasons, so it is best to assume good faith until the addressed party repeatedly fails to respond in a timely manner.
323+
324+
Depending on severity, here are some methods you can use to remind a member to respond to your ticket.
325+
1. Send additional mentions in the ticket.
326+
2. Remind them in a channel they are currently active in.
327+
3. "Jail" them.
328+
329+
"Jailing" a member will lock them out of all channels except for tickets. You must give a 12–24 hour heads up before jailing. This should be used as a last resort if softer methods do not work.
330+
331+
You can jail a member in two ways:
332+
- `/jail`
333+
- `$jail @member`
334+
335+
If neither of these commands work, you may add the `Jail` role manually.
336+
337+
To unjail a member you can run:
338+
- `/unjail`
339+
- `$unjail @member`
340+
341+
Again, if the commands fail, you can remove the `Jail` role yourself.
342+
321343
# 4. Conclusion
322344

323345
### 4.1 Recap of Key Points

0 commit comments

Comments
 (0)