Apex Legends Discord LFG Bot - Monvoke Guide
Grinding to Diamond in Apex often means you're only short one or two players, yet posting a call-out and tracking who replies can eat up more time than the queue itself. Backfilling a no-show takes even longer. Monvoke turns that whole routine into button clicks and automatic notifications. Post a recruitment, let members join with a button, and the moment the squad is full, everyone gets notified and a voice channel is ready to go.
Fill a squad on Discord without pinging the whole server
Apex ranked is built around trios, so it's common to be short by exactly one or two players when you want to queue. With Monvoke's /invoke command, posting a recruitment drops a message with a Join button attached. Members fill the squad by clicking it.
The member count you enter when creating a recruitment does not include yourself. If you want two more people to make a trio, enter 2 (the actual slot count is 3, including you as the host). Missing just one player right now? Entering 1 is enough. The member count on the message updates live as people join, so there's no need to shout into @everyone and manually tally who answered.
Handle "maybe" replies and let drop-outs refill themselves
Say you want to queue at 9pm and enter 2 in the member count field for a trio. One friend, A, joins right away, filling the second slot. Another, B, isn't sure yet (maybe, depends how work goes), so they hit Maybe instead of Join.
A Maybe RSVP doesn't count toward the target. The host and A make 2 confirmed members, and B's maybe brings the total to the target of 3. That's when Monvoke DMs B asking "Can you join?" If B switches to Join, the squad hits 3 confirmed members and the recruitment is marked full. Everyone gets a DM that the squad is ready, and the recruitment message shows a menu of voice-channel actions.
Now suppose A has to drop right before the queue starts and hits Leave. If someone else, C, was already sitting on the waitlist, C is automatically promoted to a confirmed slot. Nobody has to go find a replacement and ask around.
A Discord voice channel and IDs come together the moment the squad fills
A voice-channel menu appears on the recruitment message once the squad fills. If the host picks "Create Dedicated VC," Monvoke instantly spins up a channel only the squad can join. The channel takes its name from the recruitment title, so there's no guessing which VC belongs to which group. The channel disappears on its own once everyone leaves.
If members registered their Apex in-game name (IGN) with the /id command beforehand, joining this VC posts everyone's IDs directly in the channel's built-in chat. On servers that play more than one game, setting an ID label with a flag like "apex" under /config makes sure Apex-flagged VCs only surface Apex IDs. Nobody has to scroll back through old messages to find who to friend-request.
/custom takes a private scrim from team split to final rate update
Separate from ranked queuing, when you want a 3v3 scrim among friends, /custom is the command for it. Members join with a button just like /invoke, and reaching the target count also splits everyone into Team A and Team B.
For a 3v3, enter 5 in the player count field (that's 6 total including the host, split into two teams of three). All six joined? Monvoke sorts everyone by their current rate, highest to lowest, and alternates the assignment between Team A and Team B. This rate is tracked separately from your Apex rank tier (Platinum, Diamond, and so on). It's an internal rate Monvoke keeps per player based on past matches, and it's what the team split uses to keep the two sides close in strength.
Right after teams are set, and before the match starts, players can adjust the lineup: "Switch Team" lets a participant move themselves to the other side, and "Shuffle" lets the host redo the split entirely. The host reports the result from the recruitment message once the match ends (picking "Team A wins," for example), and every participant's rate updates right away. If the match didn't happen, say because someone disconnected, it can be reported as void instead: rates stay unchanged, and only the match count is recorded.