Managing Viewer Participation Slots on Discord with a Bot
Running a viewer-participation stream with slots for four or six players means counting sign-ups posted in chat, tracking the order they came in, and finding a replacement by hand every time someone drops. Monvoke moves all of that onto a Discord recruitment message instead. Viewers join with a button, a queue takes over automatically once the slots fill, and when someone leaves, the next person in line gets promoted and DM'd automatically.
Take viewer sign-ups off chat and onto a Discord join button
You post a recruitment with the /invoke command in your Discord server, which drops a message with a Join button attached. Viewers click that button to sign up instead of posting in chat.
The member count you enter doesn't include yourself as the host. For a 4-player game where you want three more people alongside you, enter 3 (the actual slot count is 4, including you). That single number is all you need, even for a one-off segment where you're only filling slots once.
Every time someone joins, the count on the recruitment message updates immediately. You don't need to scroll back through chat to recount who signed up - the message itself always shows how many spots are filled.
Keep accepting sign-ups after the slots fill, with an automatic queue
Once the slot count is reached, the recruitment closes automatically. The Join button stops accepting new members at that point, but a Waitlist button appears in its place. Viewers who missed the cut can click it to line up.
When a confirmed member hits Leave, the person at the front of the queue is automatically promoted to a confirmed slot, and they get a DM about it. You don't have to decide who replaces a dropout or message the next person yourself.
Say you're running a 4-player segment: you enter 3 in the member count field and run /invoke, three viewers join, and the recruitment fills. From that point on, anyone else who wants in clicks Waitlist. If one of the confirmed members has to leave right after the segment starts, the viewer at the front of the queue is promoted automatically and gets a DM confirming their spot. You never have to check who's next or track it yourself.
One thing to note: as the host, you can't hit Leave yourself. If you need to reset the slots entirely, the Cancel button (host-only) ends the current recruitment so you can start a fresh one.
Handle "maybe later in the stream" sign-ups with Maybe instead of Join
If a viewer isn't sure they can join until a later segment, the Maybe button is the right one for them. It doesn't count toward the slot total.
Once confirmed members plus Maybe members reach the target count, Monvoke automatically DMs everyone on Maybe asking if they can join. Switching to Join at that point locks in their spot, but if other viewers fill the remaining slots first, the Maybe sign-up is treated as not participating. Maybe doesn't reserve a slot, so tell viewers who definitely want in to hit Join instead.
The moment slots are locked in, a private VC and IDs are ready to go
When the recruitment fills, a voice-channel menu appears on the message. Creating a dedicated VC from there instantly sets up a channel only confirmed members can join (see Discord Recruitment to Voice Channel: What Happens Automatically for what else that menu can do).
If a viewer registered their in-game ID with the /id command ahead of time, joining that VC posts their ID directly in the channel's built-in chat. You and other participants can send friend requests or room invites right away instead of digging back through chat or DMs to find who to add. ID labels, separate ones for different games, for instance, are something a server admin sets up under /config, with room for up to 15 per server.
Running more than one recruitment at once during a stream
Pricing is per server. Even on the Free plan, you can run up to three recruitments at once, enough to keep a main recruitment and a separate segment's recruitment open in parallel. Create a fourth, and the oldest one ends automatically. Need more than three running at the same time? That's when Plus ($4.99/month, billed per server) comes in.