Schedule recurring messages to be posted into a Discord channel on a cadence you choose — from every 6 hours up to every 30 days. The bot keeps posting on schedule until you pause or delete the auto-message.
Auto Message lets you write a message once, pick a channel, a starting date and time, a timezone, and a repeat interval, and have Mokito post that message into the channel on that schedule — automatically, forever. It is useful for daily announcements, weekly reminders, scheduled server prompts, or anything that needs to appear on a steady cadence without you typing it each time.
The settings live at Notifications → Auto Message in the guild dashboard sidebar. The page lists every auto-message you have created, with a button to create a new one and a form to edit or delete each.
Each auto-message carries a unique 7-character id (letters, digits, and dashes) that identifies it across the list, edit form, and the messages Mokito posts.
When an auto-message's scheduled time arrives, Mokito posts the message text (and any embed you attached) into the channel you chose. After posting, the next run is moved forward by the interval you picked — for example, if the interval is every day, the message posts again exactly one day later, at the same time of day in the timezone you selected.
Mokito checks every minute for auto-messages that are due, so a scheduled message goes out within a minute of its due time. There is no manual “send now” button — the schedule is the only thing that triggers a post.
Auto Message has a free tier and a Premium tier:
| Plan | How many you can create | Which ones actually post |
|---|---|---|
| Free | Up to 2 auto-messages. | Only the 2 oldest auto-messages keep posting. Any additional auto-messages are preserved but paused. |
| Premium | Up to 25 auto-messages. | All of them post on their schedules. |
Only the server owner and managers can access the Auto Message page, create, edit, or delete auto-messages. Moderators, support team members, and regular members cannot see this page. For details on what each dashboard role can do, see Dashboard Roles.
The page opens with a hero showing the name of your server, a one-line description, and a counter telling you how many auto-messages you have used out of your plan's limit. Below the hero is a table of every auto-message in the server, with a New Auto Message button above it.
If you are on the free plan and have not yet upgraded, a callout above the table reminds you that only the 2 oldest auto-messages post on the free plan, and links to the Premium page to upgrade.
Each row in the table represents one auto-message:
| Column | What it shows |
|---|---|
| ID | The 7-character auto-message id, shown as a chip. On the free plan, each id is tagged Free slot (green) or Premium slot (amber) so you can see at a glance which ones are sending and which are paused. |
| Message | A truncated preview of the message content (up to 80 characters). If the content is empty, it shows (empty). |
| Embed | Whether the auto-message has an embed attached — Yes or No. |
| Channel | The Discord channel id the message posts to. |
| Next run | The next scheduled time, formatted as a readable date and time in the auto-message's own timezone, with a relative hint (e.g. “in 3 hours”). If there is no scheduled time, a dash is shown. |
| Status | The current state of the auto-message — see Status indicators below. |
| Actions | An Edit button and a Delete button (delete is confirmed via a modal, not a popup). |
If you are on the free plan, each auto-message's id chip carries a second small badge:
If you are on Premium, no slot badges appear — every auto-message sends on its schedule.
The Status column shows one of three states:
| Indicator | Meaning |
|---|---|
| Active (green) | The auto-message is on its schedule and will post at its next run time. |
| Paused (red) | The auto-message has been paused (see Automatic pause on send failure). It will not post until you edit it and reset its schedule. |
| Paused — Premium slot (amber) | Shown only on the free plan. The auto-message is beyond the 2 free slots and is waiting for you to upgrade before it resumes. |
If you have already created as many auto-messages as your plan allows, the New Auto Message button is replaced by a greyed-out Limit reached indicator. Clicking Edit on an existing auto-message still works. To create more, upgrade to Mokito Premium.
Click New Auto Message on the list page (or Edit on an existing row) to open the form. The form is split into two sections — Message and Schedule — with the save button at the bottom. If you are on the free plan and have already used both free slots, the create form is replaced by a Premium lock callout instead of letting you fill out a form you cannot save.
This section defines what the bot posts. Every auto-message needs at least the destination channel and the message content; the embed is optional.
Search for a channel by typing its name, or paste a channel id. Only text channels and announcement channels in your server are listed — threads, voice channels, stage channels, forum channels, and category channels cannot be used. The list comes from Mokito's cached copy of your server's channels; if no channels appear, refresh your guild data from the Overview page first.
The channel id must be numeric. If you type something that does not look like a Discord channel id, Mokito will not let you save.
The message body is required and can be up to 2000 characters (Discord's message cap). This is the plain text the bot posts above any embed. It is the same field used everywhere Mokito posts text to a channel — there are no template tags for auto-messages; the text is posted verbatim every time.
Toggle the Add an Embed switch to reveal a full embed builder, identical in shape to the one on the Embed Builder page. Every field is optional — leave blank what you do not want. The embed appears below the message text in Discord. Fields available:
#ff66cc).A live preview on the right shows exactly what Discord will render as you type. The preview updates on every keystroke (debounced 80ms). If no embed fields are filled in, the preview is blank — that is expected.
This section defines when the bot posts and how often. The schedule has three parts: a timezone, a first-run date and time, and a repeat interval.
A dropdown of every timezone PHP recognises, sorted alphabetically. The default is America/New_York. The timezone tells Mokito how to interpret the date and time you pick for the first run, and is also used to display the Next run time in the list. You can change the timezone on an existing auto-message when editing — the next run time is shifted to the new timezone so the wall-clock time stays the same.
Two separate inputs: a date picker and a time picker. Both are interpreted in the timezone you selected above. Together they define the moment the auto-message should first post — and, because every subsequent run is the previous run plus the interval, they also anchor the time of day the message repeats at.
A fixed dropdown of repeat intervals. The smallest is every 6 hours and the largest is every 30 days:
| Option | What it means |
|---|---|
| Every 6 hours | Posts 4 times per day, 6 hours apart. |
| Every 12 hours | Posts twice per day, 12 hours apart. |
| Every day | Posts once per day, at the same time. |
| Every 2 / 3 / 4 / 5 / 6 days | Posts once every N days, at the same time of day. |
| Every week | Posts once per week, on the same weekday and time. |
| Every 2 / 3 / 4 weeks | Posts once every N weeks. |
| Every month | Posts once per calendar month. Months of differing lengths are handled without overflowing (e.g. a Jan 31 run advances to Feb 28). |
You cannot type a custom interval — only the values in the dropdown are accepted.
If the date and time you pick for the first run is already in the past (in your selected timezone), Mokito does not post the message late and does not jump to the next day. Instead, it advances the first run by the interval you chose — once, repeatedly — until it lands on a time that is strictly in the future.
For example, if today is Friday at 2 pm, you set the first run to Monday at 9 am with an interval of every day, the first run advances past Tuesday 9 am, Wednesday 9 am, Thursday 9 am, Friday 9 am, and settles on Saturday at 9 am. This keeps the time of day intact and respects the minimum gap (the interval itself) before the first fire.
Once an auto-message is saved and active, Mokito checks every minute for any auto-messages whose next run time has arrived. Due messages are posted into their channels in order of their next run time (oldest first). After each post, the next run time is advanced by the interval, in the auto-message's own timezone, so the cadence stays steady.
If more than one auto-message is due to the same channel at the same minute, Mokito spaces the posts out slightly to stay inside Discord's per-channel rate limits — you do not need to manage this yourself.
Mentions are never parsed — the bot posts your message text exactly as written, without pinging any roles or users that may be referenced in it.
If Mokito tries to post an auto-message and Discord rejects it because the channel no longer exists or the bot no longer has access to it (HTTP 403 or 404), the auto-message is automatically paused. Its status changes to Paused in the list and it stops posting until you fix the channel and edit the auto-message to reset its schedule. Other auto-messages are unaffected.
A temporary Discord outage or rate-limit (HTTP 429 / 5xx) does not pause the auto-message — only a permanent channel-loss error does. The next run time still advances after a temporary failure, so the message tries again on its next scheduled time.
| Limit | Value |
|---|---|
| Message content length | Up to 2000 characters. Required. |
| Embed limits | Same as the Embed Builder: title 256, description 4096, footer text 2048, up to 25 fields (each name 256 / value 1024), and Discord's 6000 total-character cap. |
| Minimum interval | Every 6 hours. |
| Maximum interval | Every 30 days (or every month). |
| Supported channel types | Text channels and announcement channels only. |
| Channel id | Must be numeric. A non-numeric value is rejected at save time. |
| Free tier | Create up to 2 auto-messages. Only the 2 oldest actually post; the rest are preserved but paused. Mokito Premium raises the cap to 25 and unpauses all of them. |
| Premium tier | Create up to 25 auto-messages; all post on their schedules. |
| First run in the past | Advances by the interval until it lands strictly in the future. The time of day is preserved. |
| Posting timing | Mokito checks every minute. A due message posts within a minute of its scheduled time, oldest-due first. |
| Mentions | Never parsed. Message text is posted verbatim with no role or user pings resolved. |
| Send failure (channel gone) | HTTP 403 / 404 pauses the auto-message automatically. Fix the channel, then edit and save to resume. |
| Temporary Discord error | Does not pause. The next run time still advances; the message retries on its next scheduled time. |
| Same-channel burst | If multiple auto-messages are due to one channel in the same minute, they are spaced out to respect Discord's rate limits. |
| Deleting | Permanent. A confirm modal asks you to confirm before the auto-message is removed. Deleting does not delete the Discord messages already posted. |
| Per-server | All settings are per-server. Auto-messages in one server do not affect any other. |