You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+22Lines changed: 22 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -318,6 +318,28 @@ This is ideal for tickets that are neither critical nor time sensitive. Members
318
318
319
319
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.
320
320
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.
0 commit comments