Schedule a Discord LFG Post with a Start Time
Set a start time up front, and Monvoke handles the ping
Add a start time to /invoke with the schedule parameter, and the recruitment post closes itself the moment that time arrives, notifying everyone who joined. No pinging required.
Without it, a host has to remember the start time and ping the group by hand once it rolls around. With a scheduled recruitment, Monvoke checks whether the start time has passed and whether enough people have joined, and sends everyone a DM the instant both are true. Say your server plans sessions around a fixed time: "tonight at 9pm," "Saturday 8pm EST." You set that time when you create the post, and the reminder is handled for you.
Add a start time with schedule on /invoke
When you fill out the /invoke modal (title, description, number of members), you also set the schedule parameter on the command itself. The format is DDHHMM, no separators. To start at 21:30 on the 7th, enter 072130.
Once a recruitment has a schedule, the number of members, start time, and mention target can't be edited afterward. If you get the time wrong, cancel the post and create a new one. The same schedule parameter works the same way on /custom and /preset.
What happens when the start time hits
A scheduled recruitment closes once the start time has passed and the actual member limit is reached. Say the group needs 6 to be complete. If those 6 people join before the scheduled time, the post keeps showing "Recruiting" until the clock reaches that time, then closes. If the clock passes and the group still isn't full, the post closes the instant the last spot fills.
When it closes, every member gets a DM. From the VC action menu on the post, the host can create a dedicated voice channel, pull members into it, and so on. What happens from there through getting everyone into a voice channel is covered in From recruitment complete to voice channel.
Set your server's timezone, or the start time will drift
The date and time in schedule is interpreted using your server's configured timezone. If none is set, it falls back to whoever ran the command: Japan Standard Time for a Japanese Discord client, UTC for everyone else. On a server with hosts in different regions, that means the same 072130 can point to two different actual times depending on who typed it, a 9-hour gap either way.
Set a fixed timezone under /config → Timezone (a UTC offset, e.g. -5 for US Eastern), so every host's schedule resolves to the same time no matter who creates the post.
You can schedule up to a month out
schedule accepts any date and time within one month from now. There's no difference between plans here: a server on the Free plan can point a recruitment at a date next month. Enter something beyond that range and the post isn't created; you get an error instead.
The post's own expiry is counted from the start time rather than from when you created it: 24 hours on Free, 7 days on Plus. Scheduling far ahead never causes the post to expire before the session starts. Plus plan details covers what changes between plans.