FFXIV Raid Recruitment on Discord: Roles and Start Times
Recruiting for FFXIV savage or raid content usually means picking a start time and filling tank, healer, and DPS slots. With Monvoke's /invoke command, you set roles and a scheduled start time when you create the recruitment, and the message itself tracks both from then on. You can see who signed up for which role at a glance, and everyone gets a DM the moment the recruitment is complete. There's no manual headcount and no last-minute ping when it's time to log in.
Give your FFXIV tank, healer, and DPS slots their own place on the recruitment message
When you create a recruitment with /invoke, you can define roles for it. The member count field doesn't include you as the host, so for an 8-player raid you'd enter 7 (you plus 7 others makes 8). Set up tank, healer, and DPS roles on top of that, and members pick their role from a dropdown at the bottom of the message after they hit Join. The participant list is grouped by role, so you can see which roles are filled and which are still open without counting anyone by hand.
When you add a role, you can optionally set a minimum and maximum for it. Set tank 2, healer 2, DPS 4, and if DPS fills up while tanks are still short, the recruitment message shows a warning for the tank slot. You immediately know who to go recruit next, instead of scanning the participant list to work out what's missing.
These role counts are a guide, not a gate. The Join button still works even with a warning showing, and the recruitment can fill and close without every role slot being satisfied - role slots make the gap visible, they don't hold up the recruitment until it's filled. If a role is still short as the start time approaches, the host can edit the recruitment's title or description to call out exactly which role needs people.
Set a start time, and Monvoke handles the day-of ping
Static and savage groups tend to plan around "starting at X on day Y" rather than pulling people together on the spot. Monvoke handles this with the schedule argument, entered as DDHHMM with no separators. To start at 9:30 PM on the 7th, you'd enter 072130. You can schedule up to 7 days out.
A scheduled recruitment stays open until the start time you set, regardless of whether the roster is full. If the roster fills at 7:50 PM for an 8 PM start, it doesn't close early - it stays open until 8 PM. Completion itself needs two things to line up: the start time has to have passed, and the roster has to be full. If the roster was already full before the start time, the recruitment completes right when the clock hits that time; if it's still short when the start time arrives, it completes as soon as the last slot fills afterward. Once it completes, everyone gets a DM confirming the recruitment is set, and the message shows a menu of voice-channel actions. There's no need for the host to ping the group or message people individually beforehand.
The start time is interpreted using the server's configured timezone. If none is set, users on a Japanese client default to JST and everyone else defaults to UTC. For a free company or community server with members across timezones, setting the timezone under /config keeps the scheduled start time from being misread.
Treat "maybe" responses as tentative, not a firm slot
Community recruitment tends to draw more "maybe" replies than a locked-in static does. Monvoke has a Maybe button for exactly this. A Maybe RSVP doesn't count toward the target headcount, so the host can judge how full the raid actually is from confirmed members alone.
Once confirmed and Maybe members together reach the target headcount, anyone still on Maybe gets an automatic DM asking if they can join. Switching to Join at that point moves them into a confirmed slot; if they don't switch, that slot stays open. If a confirmed member drops out once the recruitment is complete and someone else is on the waitlist, that person is promoted automatically. The host doesn't need to go find a replacement.
Recruitment messages expire faster on the Free plan
If you're in the habit of posting a raid recruitment several days ahead of the actual run, the Free plan's message expiration matters. Free plan recruitment messages expire after 24 hours; Plus plan messages last 7 days. A static or free company that wants to post next week's savage clear a week out needs the Plus plan for that to work. If you're only gathering people for a same-day raid, the Free plan's 24-hour window is enough.