ShotCaller bot + Guild Manager: voice relay and raid attendance

Your raid is split across squad channels. The leader calls a regroup, each party needs to hear it, and an officer still has to work out who showed up. Moving everyone into one crowded voice channel makes the headcount easier and the conversation worse.

The ShotCaller bot and Guild Manager work together here. ShotCaller relays voice across Discord channels. Guild Manager uses its synced channel assignments when an officer takes activity attendance, so the squads can stay where they are.

This guide covers the setup and the command you'll use on raid night. For an overview and the partner offer, visit our ShotCaller partnership page.

What is the ShotCaller Discord bot?

ShotCaller carries a leader's voice into multiple Discord voice channels. Your raid leader can address the group while each squad keeps its own channel for local coordination. That's useful when parties have different jobs during a raid, siege, or PvP event.

Promotional image from ShotCaller's homepage. The Discord scene illustrates voice relay; it is not a Guild Manager screen.

Guild Manager handles the guild work around the event: members, characters, scheduled activities, attendance, and loot. The integration connects one specific part of that workflow. It lets an officer include the active, synced Shotcaller channels in a manual attendance snapshot.

How the integration works

Configure your voice setup in ShotCaller, then sync it in Guild Manager. Guild Manager's Shotcaller settings show the speaker bots, their assigned channels, and their active status. Those active channel assignments tell the attendance command where to look.

For example, your raid might use Alpha, Bravo, and Charlie voice channels. When it's time to take attendance, an officer selects the activity in /track-activity and turns on shotcaller-mode. Guild Manager gathers the members in the synced active channels and processes them against that activity's attendance rules.

You don't need to move the squads into one channel for the snapshot. You do need to choose when to take it. Enabling the integration does not start continuous voice monitoring or schedule future snapshots.

If you only need multi-channel attendance, Guild Manager can also use selected channels, a Discord category, or a channel name prefix without Shotcaller. These selections work with manual and scheduled snapshots. The voice attendance guide covers those options. Shotcaller remains useful when you want attendance to follow the channels already assigned for your voice relay.

Set up ShotCaller with Guild Manager

1. Connect the guild's Discord server

In Guild Manager, connect the Discord server your guild uses. Install and configure ShotCaller in that same server. Run Shotcaller attendance commands there too; the command checks that it is in the guild's configured server.

Create or select the Guild Manager activity you want to track and enable its Discord voice attendance method. The officer running the command needs permission to manage or modify activities. If their Discord command is using the wrong character, they can use /set-character to select one that belongs to the guild.

2. Choose the voice channels in ShotCaller

Open the ShotCaller dashboard. Choose a listener channel for the leader, then assign speaker channels for the squads. Configure the Starter Role for the people allowed to begin voice relay and the priority roles for callers.

ShotCaller's configuration guide explains these controls. Keep your channel names recognizable so officers can match each squad to its channel during setup.

ShotCaller's configuration documentation, captured for this guide. Make the actual changes in its dashboard.

3. Enable the integration and sync

Open your guild's Shotcaller settings in Guild Manager. Confirm that the Discord server is connected and the Shotcaller bot is configured. Enable the integration, then select Sync Now.

Review Voice Channel Coverage before the event. Check that the expected speaker bots have channel assignments and are active. If you change the setup in ShotCaller, sync again and check the coverage before taking attendance.

4. Take a manual attendance snapshot

In the configured Discord server, use Guild Manager's command:

/track-activity activity:[select your activity] shotcaller-mode:true

Choose the activity from Discord's selector. The bracketed text above is a placeholder, not something to type as an activity name.

Guild Manager processes the snapshot and reports the outcome. Review the result for newly attended members, people already checked in, and anyone who could not be included. The activity's eligibility and signup rules still apply. Being in a voice channel does not override them.

The command also has options for deafened members, non-RSVP members, no-shows, and finalizing attendance. Leave those at your intended guild defaults unless you mean to change that behavior for this run. In particular, don't finalize attendance while you still expect to take more snapshots.

A raid-night workflow

Before people gather, check the synced channel coverage and the activity's voice attendance setting. Once the squads are ready, the caller can start ShotCaller's relay with /start. Use /status to check the relay and /stop when the event ends. ShotCaller's command reference explains its role requirements.

At your agreed attendance time, an officer runs Guild Manager's /track-activity command with Shotcaller mode enabled. Read its result before treating the headcount as complete. If someone joined late, take another snapshot while attendance remains open. The result distinguishes members who were already checked in from newly attended members.

The caller can keep leading the fight while another officer handles attendance. Neither needs to ask every squad to change channels.

Fix missing channels or attendance

Does ShotCaller cross-server relay mean cross-server attendance?

ShotCaller offers cross-server voice relay. Guild Manager's Shotcaller attendance command gathers members from channels in the guild's configured Discord server. Don't assume an allied server's listeners are included in your guild's snapshot just because they can hear the same caller.

Get started with the partnership

If your guild already uses ShotCaller, start by connecting and syncing it in Guild Manager. If you're setting up both, begin with the server and channels, then try a manual attendance snapshot with a small group before your next event.

See the ShotCaller partnership overview, compare Guild Manager plans, or use ShotCaller's partnership offer for its current signup terms. Preparing a new guild as well? Our Aion 2 legion tools and WoW Forever guild tools cover the game-specific setup.