Skip to content

Commit 1aaa4ed

Browse files
committed
add example ticket workflows
1 parent dd0f4ac commit 1aaa4ed

File tree

1 file changed

+13
-0
lines changed

1 file changed

+13
-0
lines changed

README.md

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -305,6 +305,19 @@ And that's all! And with that, you've just completed your first ticket—congrat
305305

306306
Happy ticketing!!!
307307

308+
### 3.4.2 Example Ticket Workflows
309+
1. Open a ticket using `/ticket` or `-ticket` without ading a user.
310+
2. Write a complete opening message. Ensure that all points are covered; use multiple messages if required.
311+
3. Add a member to the ticket using `/add`.
312+
4. Mention the member with an @ so they get notified of the ticket.
313+
314+
This is ideal for tickets that are neither critical nor time sensitive. Members can get needlessly anxious when they are added to an empty ticket while you are typing, so preparing your message beforehand can prevent unnecessary stress.
315+
316+
1. Right click on a member's profile, and click on `Create Ticket` in the apps menu. This will immediately add the member to the new ticket.
317+
2. The target member should be notified after the ticket is created. At this point you can address the member while they have your attention.
318+
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+
308321
# 4. Conclusion
309322

310323
### 4.1 Recap of Key Points

0 commit comments

Comments
 (0)