These tools are in the development build. They are outside the first
four-feature pilot and have not been released to the official bot. An admin
should leave them off until the operator agrees to a test.
/setup module. Check roles and channel access
before using real data.
Reminders: a note for yourself
Reminders: a note for yourself
Turn on
reminders. Use /remind set amount:2 unit:hours text:check the draft.
When it is due, the bot pings you in that channel. Show reminder reveals the
text only to you. Other people can still see that you were pinged.Use /remind list to edit or cancel a waiting reminder. Pick a channel you will
still be able to read. Each member may have 25 waiting reminders per server.
The bot’s cleanup is designed to remove the text seven days after it fires.
Ask the operator to verify that cleanup runs before using private text.Try and undo: make a short reminder with made-up text. Open it as its owner,
then confirm another member cannot read it. Cancel a second reminder from the
list and check that it does not fire.Polls: one quick group choice
Polls: one quick group choice
With
events on, staff use /poll to post a Discord poll with two to five
answers. Keep the question to one choice. Use an event when you need seats,
attendance roles or event reminders.Try and undo: use a harmless choice in a test channel. Check who can vote,
then end or remove the test poll in Discord when it is no longer needed.Applications: review a request for a role
Applications: review a request for a role
Turn on
applications. An admin uses /apply form to choose a name, private
review channel, accept role and up to four short questions. Staff use
/apply post to post Apply and My application.Keep the review channel private. The member’s answers are posted there. Staff
accept, deny or ask for more. The member gets the outcome in a private thread
under the channel where they applied. Staff with thread-management rights may
also see that thread. The bot needs Create Private Threads there.The form may set a pending role, a deny role or a role needed to apply. Use
separate roles so each stage grants only what it should. Members can check
My application; staff can check /apply list.Staff may use Accept for a set time for a temporary role. They can later
extend it, make it permanent or end it. If role removal fails, the role stays
until the failure is fixed. A saved decision is not proof of a role change.Try and undo: use a role with no powers. Check the review and applicant
views. Fix a failed role change and use Retry role change. For a temporary
role, use End now and read back that it is gone. Answers are saved in a work
queue while the bot posts or tries again. That text is cleared when the job
ends. Keep review cards while you need the answers; there is no lasting backup
of them in the application record.To remove a test form, finish its requests and remove its test or temporary
roles first. /apply delete-form deletes the form and application records.
It does not take back roles already given. Remove the old Apply panel in
Discord too, after you have checked the roles.Saved answers: keep common replies in one place
Saved answers: keep common replies in one place
Turn on
answers. Staff use /answer add with a short name and optional
category, then enter the answer. Anyone offered the answer can use
/answer send; add private:True to preview it first.Staff use /answer panel for a Common questions card. It updates as answers
change. Use /answer edit, /answer remove and /answer list to keep it right.
Give each answer an owner and review it when the process changes.Use only_role for staff wording or only_channel for a reply that fits one
place. A public panel omits answers limited to a role. Check those limits as a
member before adding private wording.To show common answers before a ticket form, give the answer category the same
name as the ticket topic. Members can still press I still need help.Try and undo: preview a harmless answer, send it, then edit it and check
the panel. Remove the test answer and its posted message when finished.Announcements: schedule a channel message
Announcements: schedule a channel message
Turn on
announcements. Staff use /announce create with a channel, date and
time. Enter AM or PM. Add a daily or weekly repeat if needed. Fill in the text,
check the preview, then press Schedule it.Use /announce list to find it, /announce edit to change its text, or
/announce cancel to stop it. To change its time, cancel and create it again.
Times use the server’s time zone.Announcements do not ping people, even if the text names a role. If the bot
loses channel access, the announcement and its repeat stop. Fix access and
schedule it again.Try and undo: schedule a harmless message shortly ahead. Check the actual
post time. Cancel any repeat and remove only your test post.Ideas: collect and vote before choosing work
Ideas: collect and vote before choosing work
Turn on
ideas. An admin uses /idea board to choose a forum or let the bot
make one. Members use Suggest an idea, /idea new, or Apps → Save as idea
on a message. Each idea gets its own post.Press Vote to add a vote; press again to remove it. Check /idea top before
posting so an existing idea can get a vote instead of a duplicate. Staff use
Manage to mark it planned or done, decline it with a reason, or reopen it.Use Archive idea for an old or duplicate idea. It closes and locks the post
but keeps the discussion. Restore opens it again. The bot keeps idea text
so it can redraw the card when votes change.The task button depends on the separate
connected-app path. A native ideas test
does not prove that task creation works on the official bot.Try and undo: suggest, vote, remove your vote, archive and restore a test
idea. Use /idea board stop:True to stop the board; its posts stay. Remove a
test post in Discord only when you no longer need its record.Check-ins: collect short updates across time zones
Check-ins: collect short updates across time zones
Turn on
checkins. Staff use /checkin start to choose the channel, days,
opening time and how long each round stays open. Use up to three short
questions, or keep the defaults about work done, next work and blockers.Use /checkin team to pick up to 25 people. The bot cannot find everyone with a
role by itself. People who give an update join the list while there is room.
An optional role ping reaches the whole role once per round.The card shows who answered. Read its thread for what they said. The work queue
holds each update while it waits to post or tries again. Its text is cleared
when the job ends. The round record keeps who answered, without the update
text. Give it a quiet channel and enough hours for the team’s last time zone.Use /checkin now to open today’s round. It still counts as today’s one round.
If the bot would open more than two hours late, it skips that round. A missing
channel or thread permission stops the check-in until staff fix and restart it.Try and undo: open a round, give an update and check the thread. Use
/checkin list to review the next time, then /checkin stop. Past rounds stay.
Remove only test posts when your team no longer needs them.Feedback and the AI agent
Feedback and the AI agent
/feedback sends a note to the ApexGenius team. It is not a ticket to your own
server’s staff. Do not include keys, private member details or request contents.
Use the server’s help panel for member support./ask is separate from server tools. It needs the member’s own linked
ApexGenius account and access. Turning on a server feature does not grant it
access to a connected app. Follow the
Discord connection guide for that path.