Skip to main content
Use these workflows only in an enabled pilot server. Finish server setup first. Ask your server admin if a command is missing.
Pick one job and agree who owns it. A small test with a clear end is easier to check than turning on every feature at once.

Help someone without losing the next step

Use a ticket when a member needs a private back-and-forth with staff.
  1. The member opens a ticket from the help panel.
  2. A staff member presses Claim before they reply.
  3. If staff need an answer, they press Waiting on member.
  4. The member answers, then presses I still need help on the reminder when it is shown. Staff can also press Back to open.
  5. When the work is done, close the ticket. Keep its channel as the record.
Start with auto-close off. If the team later turns it on, tell members that a typed reply alone does not stop the clock. Choose the wait time your team can support, and check /ticket list each day. Turn ratings on only if someone will read them. Use /ticket stats to review the period you care about. A low score is a reason to read the ticket, not proof of what went wrong. Check: the member can read their closed ticket, another member cannot see it, and the saved status matches the card.

Plan a small event with limited seats

Use an event when you need a clear headcount.
  1. Staff create an event with a small places limit and the usual Yes, Maybe and No answers.
  2. Check the date, AM or PM, time zone and reminders in the preview.
  3. Press Post it. Ask members to use the buttons.
  4. When seats fill, the next Yes waits. If someone gives up a seat, the first person waiting moves in.
  5. Cancel the test from Manage and check that any attendee role comes off.
Use custom answers only when every answer means someone is coming. Early and Late share the same seat limit; they do not make two groups of seats. Use two events if each session needs its own limit. Use a role ask for a headcount from a group. It pings that whole role. Use event reminders for people who already have a place. Keep event cards in a quiet channel so people can find those replies. Check: one person waits, a free seat moves to that person, and a cancelled event no longer grants its role. Members must fix their own calendar entries.

Plan time away without sharing the reason widely

Use leave requests when an approver needs dates and a reason.
  1. The admin sets a request channel and approver role with /leave setup.
  2. The member uses /leave request and checks the dates.
  3. A different person approves, denies or asks for more.
  4. Staff use /leave list or the Who is away card to plan cover.
  5. The member uses /leave return if they return early, or /leave cancel to withdraw leave that has not started.
Keep reasons in the request channel. The Who is away card shows dates, not reasons. Choose a leave role with no extra powers. Keep the leave feature on until every active leave has ended and its role has come off. Check: the requester can answer a question, another member cannot decide the request, and the role is removed on return.

Get a clear decision on a draft

Use an approval card when a person must say yes or no.
  1. Write a title that names the choice, such as “Use this draft reply”.
  2. Use /approval ask, or Apps → Ask for approval on the draft message.
  3. Add just enough detail to decide. Check who can read the request channel.
  4. An approver uses Ask for more if needed. The requester uses Answer.
  5. A different person approves or denies with a short note. The requester withdraws it if the choice is no longer needed.
Set channel notifications so approvers see new cards. A new request does not ping them. Use /approval list to review what still waits. Approval records a choice. It does not send the draft, buy an item or run a connected-app tool. The person who owns the next step must still do it. Check: the first decision stands. If a card is deleted, use /approval mine and /approval withdraw, or ask an approver to use /approval deny with its number. Deleting the card alone leaves it waiting.

Keep the test honest

Check both the forward action and its cleanup. Record what people actually did separately from scripted checks. A short test can show that a role comes off on return. It cannot prove that a real midnight job or a three-day timer has run. Do not use real private details for a demonstration. Finish requests before deleting their cards, and check roles before deleting test roles. See the command guide for limits and recovery.
Last modified on November 18, 2026