Guide · September 1, 2026 · 3 min read
Saying the same thing without repeating it yourself
Three different mechanisms often get confused: the message sent once at a given time, the message that comes back at a regular interval, and the one that stays stuck to the bottom of a channel. They do not serve the same purposes.
Contents
The fixed-date message
Written today, sent on Thursday at 8 p.m. This is the tool for the prepared announcement: an event, a maintenance window, the opening of a contest.
Its value lies less in the automation than in writing it cold. An announcement written calmly the day before is better than the same one written in a rush five minutes ahead. And somebody else can proofread it before it goes out.
One thing to check: the time must be read in the server's time zone. Scheduling for 8 p.m. and watching the message go out at 10 because the tool was thinking in UTC is the kind of mistake you only make once — but it makes you miss the event.
The recurring message
The same text, every hour or every day. Useful for a rule reminder in a busy channel, for the server's link, or to announce a weekly get-together.
It is also the mechanism easiest to misuse. A message that comes back too often becomes invisible within days: the regulars have memorised it and no longer see it, and it takes up screen space for those trying to read the conversation.
Frequencies that hold up
- Rule reminder — once a day at most, and only in the channel concerned.
- Weekly get-together — the day before, then an hour ahead. No more.
- Information message — prefer a sticky message to a repeat.
- Never — a recurring message with a mention. The mention loses all its meaning.
The sticky message
A message that automatically puts itself back at the bottom of the channel as soon as the conversation pushes it up. It is almost always what people are after when they set up a repeat.
It solves the problem pinning does not: a pinned message is at the top, two clicks away, and nobody makes those clicks. A sticky message is in front of your eyes, without piling up — there is never more than one copy of it.
Typical uses: the expected format in a help channel, the rule of a classified-ads channel, the sign-up link for the duration of an event.
What makes a reminder get read
A repeated automatic message becomes scenery. Three ways to delay that moment.
Vary it. Alternating two or three wordings is enough to break the visual habit.
Make it actionable. A reminder containing a clickable link or a button gets a reaction; a purely informative reminder gets none.
Delete it when it no longer serves. An event reminder still running three weeks after the event teaches the server that the bot's messages mean nothing. That is the main damage done by a schedule you forget to switch off.
Personal reminders
Different from the above: a member asks to be reminded in two hours or tomorrow. The reminder goes to them alone.
One requirement here: the reminder must survive a restart of the bot. A reminder held in memory disappears at the first update, and the user only learns that by receiving nothing — which is worse than never having offered the feature.
Frequently asked questions
How many scheduled messages per server?
Technically many; in practice, three or four active ones are enough. Beyond that, the server feels like it is being run by a machine.
Can a message be scheduled in a thread?
Yes, as long as the thread stays open. A thread archived automatically receives nothing more, and the send fails silently.
What happens if the bot is offline at the scheduled time?
A missed message is caught up on restart if it is recent; past a certain delay it is dropped rather than sent out of time.
Can a sticky message get in the way?
In a very busy channel it gets republished often and clutters the history. It suits channels with a moderate pace best.
Read next : Day-to-day activity, Twitch alerts, Embeds and messages.