Alarms, Repeaters & Scheduler
This module covers three time-based tools: reminders (a one-off ping to you or a channel), repeaters (a message sent on a recurring interval), and scheduled messages (a one-off message sent at a specific future time).
Note
Repeaters and scheduled messages are also available from your server's Alarms page on the dashboard, which additionally covers recurring scheduled entries (see Recurring entries below) - there's no slash command for those. Reminders are DM/self-service and are not on this dashboard page.
Note
Every duration/interval option below (/remind set, /repeat add) takes the standard time code (e.g. 1d3h2m) - or a Discord timestamp mention referring to a future time - described in Time Format Code.
Reminders
/remind set
Command Syntax
/remind set where:(me|here) duration:{time code} message:{text} Command Description
Sends you a message after a certain amount of time has passed.
where:mesends the reminder to you via DM,heresends it in the current channel.duration: how long to wait, e.g.2h,1d,30m.message: the reminder text.
Permissions Needed
- User: None.
Examples
/remind set where:here duration:2h message:It's party time!
/remind list
Command Syntax
/remind list
Command Description
Lists all reminders you created within the server.
Permissions Needed
- User: None.
Examples
/remind list
/remind delete
Command Syntax
/remind delete reminder:{pick from the list} Command Description
Deletes one of your reminders. Start typing in the reminder option to pick it from an autocomplete list, instead of looking up an index with /remind list first.
Permissions Needed
- User: None.
Examples
/remind delete reminder:2h reminder about the meeting
Repeaters
Repeaters send a message on a recurring interval in a channel, deleting their own previous message each time they fire.
Note
Premium: Each server can have a maximum of 5 repeaters. Premium-enabled servers have no limit (see Premium Perks).
Note
Manage Messages is enforced only through Discord's own command-permissions picker for every /repeat subcommand below - there is no separate in-code re-check (no Layer 3). If a server's admin grants a role visibility into /repeat from Discord's Integrations settings without Manage Messages, the bot won't refuse them on Manage Messages grounds - module authorization (Layer 2) still applies.
/repeat add
Command Syntax
/repeat add channel:{channel} interval:{time code} message:{text} [start_time:{HH:mm}] Command Description
Starts a new repeater in a channel.
channel: where to send the repeating message.interval: how often to repeat, e.g.1h,30m,1d1h.message: the text to repeat.start_time(optional): anHH:mmdaily anchor time; leave it out to start the first send right after the first interval elapses.
Permissions Needed
- User: Manage Messages
Examples
/repeat add channel:#general interval:6h message:This is not a spam channel, please behave correctly.
/repeat list
Command Syntax
/repeat list
Command Description
Lists all repeaters within the server, along with when each one is due next.
Permissions Needed
- User: Manage Messages
Examples
/repeat list
/repeat remove
Command Syntax
/repeat remove repeater:{pick from the list} Command Description
Removes a repeater. Start typing in the repeater option to pick it from an autocomplete list.
Permissions Needed
- User: Manage Messages
Examples
/repeat remove repeater:abc123
/repeat trigger
Command Syntax
/repeat trigger repeater:{pick from the list} Command Description
Immediately sends a repeater and restarts its interval, so the next scheduled send is recalculated from now.
Permissions Needed
- User: Manage Messages
Examples
/repeat trigger repeater:abc123
/repeat enable
Command Syntax
/repeat enable repeater:{pick from the list} Command Description
Re-enables a paused repeater.
Permissions Needed
- User: Manage Messages
Examples
/repeat enable repeater:abc123
/repeat disable
Command Syntax
/repeat disable repeater:{pick from the list} Command Description
Pauses a repeater without removing it.
Permissions Needed
- User: Manage Messages
Examples
/repeat disable repeater:abc123
Note
Everything about recurring entries is dashboard-only - see Recurring entries below.
Scheduled Messages
/schedule schedules sending a single message (or automated action, see /schedule action leaderboard below) to a channel, at a specific future time.
You need View Channel and Send Messages permissions yourself in the target channel to schedule something there, and GiselleBot needs the same permissions both when you schedule it and again when it's actually due to send.
Note
Limits: A server can have up to 5 scheduled entries (25 for a Premium-enabled server), and can schedule at most 1 hour ahead by default. Premium tiers raise that horizon: Tier 1 to 12 hours, Tier 2 to 1 week, Tier 3 to 1 month. See Premium Perks.
/schedule message
Command Syntax
/schedule message channel:{channel} Command Description
Opens a form asking for the send time (in UTC) and the message content, then schedules it to be sent in the chosen channel.
Permissions Needed
- User: View Channel, Send Messages (in the target channel).
/schedule's command-permissions picker is open to everyone; this is enforced in-code instead (see Layer 3).
Examples
/schedule message channel:#announcements
/schedule list
Command Syntax
/schedule list
Command Description
Lists the scheduled entries you can manage within the server. Users with Manage Server permissions see (and can manage) every entry created by anyone in the server; everyone else only sees their own.
Permissions Needed
- User: None.
Examples
/schedule list
/schedule remove
Command Syntax
/schedule remove entry:{pick from the list} Command Description
Removes a scheduled entry. Start typing in the entry option to pick it from an autocomplete list. The same author/Manage Server scoping as /schedule list applies to what you're allowed to remove.
Permissions Needed
- User: None.
Examples
/schedule remove entry:abc123
/schedule action leaderboard
Command Syntax
/schedule action leaderboard channel:{channel} when:{UTC date/time} [scope:{server/global}] [days:{number}] Command Description
Schedules a one-off EXP leaderboard post, instead of a static message.
channel: where to post the leaderboard.when: the UTC date/time to post it, e.g.2026-09-10T12:00.scope(optional):server(this server's leaderboard, default) orglobal.days(optional): limit the leaderboard to EXP gained in the last N days (defaults to all-time).
Permissions Needed
- User: View Channel, Send Messages (in the target channel).
/schedule's command-permissions picker is open to everyone; this is enforced in-code instead (see Layer 3).
Examples
/schedule action leaderboard channel:#leaderboard when:2026-09-10T12:00 /schedule action leaderboard channel:#leaderboard when:2026-09-10T12:00 scope:global days:7
Recurring entries
Recurring scheduled entries have no slash command - they're configured entirely from the server's Alarms page on the dashboard, Scheduled Messages tab, via New Scheduled Message with Kind set to Recurring.
On the Dashboard
Your server's Alarms page mirrors and extends everything above, with a Repeaters tab and a Scheduled Messages tab:
- Each entry's row shows its channel, status, and a summary of its message, with Edit, Pause/Enable, Send now, and Delete actions.
- New Repeater / New Scheduled Message opens a full form for creating an entry, with the message composed in the same channel/content/embed editor as the dashboard's Message Composer.
- The Repeater form's Start options go beyond
/repeat add'sstart_time: "After the first interval" (/repeat add's default), "Every day at a fixed time (UTC)" (/repeat add'sstart_time), and "At a specific time, then every interval" - a one-time start date/time with no slash-command equivalent. It also has a Skip a repeat when nothing was posted since the last one toggle, also dashboard-only. - The Scheduled Message form's Kind field is "Once, at a specific time" or "Recurring, every interval" - recurring entries, not available via any slash command, are created by picking Recurring here - plus a Silent (No 'Scheduled by' Line) toggle, also dashboard-only.
- The Repeater form's Start options go beyond
- Checkboxes let you select multiple entries at once for bulk Pause, Enable, or Delete.
- A Premium usage gauge (e.g. "3 / 5 repeaters used") shows how close the server is to its limit.
See also
Full migration mapping for these commands: Migration Guide.