From the first join to the resolved request.
Support with clear ownership
Requests reach the right category. Your team claims tickets, replies in Discord or the dashboard, and sees what still needs an answer.
- Your categories, priorities and access rules
- Add participants, put tickets on hold or reopen them
- Inactivity reminders and a clear closure process
A good start for new members
Show what matters, ask members to accept rules and let them choose suitable roles. Access that needs a review goes to your team instead of being granted to everyone.
- Information, quizzes and role selection in your own flow
- Approvals, temporary roles and follow-ups
- Start by DM, with a server panel as an alternative
Plan once. Send at the right time.
A reminder every other Monday or an announcement on the last Friday of the month: set the pattern, check upcoming dates and pause it when plans change.
- One-off dates and calendar rules with daylight saving support
- Reminders by ping or DM, with delivery history
- Announcement drafts, approvals and multiple destinations
Your server sets the workflow. Not the bot.
Umi should take work off your hands without forcing your team into a fixed setup. Start with what you need. Add other modules when they make sense for your community.
- One dashboard, separate responsibilitiesSupport, community and analytics have their own workspaces. Give each role only the dashboard access it needs.
- Your words and your rulesFAQ answers, close reasons, role rules and reminders fit your server. Disabled modules keep their settings.
- Numbers you can traceTicket analytics show your team's work. Activity history, coverage and missing values are distinguished; message content is not stored for activity analytics.
Go further with Umi Premium
For teams that want a closer view of their workflows: advanced ticket analytics, server activity with history scans and explainable security findings. Plus DM tickets, ratings, ban appeals and the user portal.
Compare plans and features