Your caller should lead the fight Not rebuild parties at form-up.
If healers, tanks, or support are missing at engage, the mass is already behind. Ironkeep keeps one live roster with roles and builds visible before the CTA — so callers lock parties early and stop firefighting in voice.
Connect your guild is for owners/officers. Discord asks you to select a server where you have Manage Server permission, then Ironkeep signs you in and adds the bot in one step.
Already in an Ironkeep guild? Sign in to view and sign CTAs.
Demo uses sample guild data. No signup, no Discord install, about a minute to try.
Real product screenshots
Try demo — no signupDiscord signup message, optional web signup, then caller role assignment board.
Same word. Different way of operating.
Before
- Signups scattered in Discord
- Roles and comps unclear until showtime
- Caller rebuilds the roster from memory under pressure
After
- Structured signup on web or Discord
- Roles and builds visible before the CTA
- Caller opens one live roster — everyone sees the same state
Want to see this exact flow with real UI?
Open the interactive demo with sample data — no signup required.
Core modules
CTAs
Schedule and announce — one place for the mass.
Roster
Live headcount, parties, who is on what.
Builds
Library and per-mass assignments callers can trust.
Three steps. No thread archaeology.
Create the CTA, let people sign up, assign roles. Everything else hangs off that spine.
-
Create the CTA
Time, comp template, Discord mirror if you want it — posted once, linked everywhere.
-
Collect signups
Members pick role and build on web or from Discord — no screenshot ping-pong.
-
Assign roles
Caller locks parties from the same board the guild already watches.
Try the board on sample data
No signup: open the demo, click through a CTA, see how signups and roster stay in one lane.
Rough signal, not a sales metric.
18
Guilds
4
CTAs
20
Sign-ups
~30 days.