Voice treeRaid ↔ parties
The complete platform difference
Built for the guild. Not the channel list.
Shout begins with the way real groups gather: one shared hall, focused parties when the moment demands them, and enough context to move between voice, video, and conversation without losing the people around you.
Platform features and defaults vary by provider and plan. “Conventional platforms” describes common product patterns—not every competing service.
SHOUT / GUILD SIGNALOne connected realmLIVE
THE GUILD HALLRally together
Rooms, people, and plans remain connected.
Guild WatchYour view, live
ContextPlans beside talk
CommunityA hall, not a feed
/shout
One call can cross the active voice tree.
Designed from a different starting point
The difference is not a coat of paint. It is the flow.
Voice has structure
A main room can branch into parties while everyone keeps sight of the larger group.
Viewers control the canvas
Each person can tile, spotlight, arrange, or hide live shares without changing anyone else’s view.
Content keeps its context
Polls, gatherings, media, and alerts can return people to the conversation that created them.
The guild stays central
Friends, discovery, inbox, bots, rooms, and members form a community home—not an ad-driven feed.
Feature by feature
See where Shout changes the experience.
This is a comparison of interaction models, not a checkbox contest. Every Shout item below is represented in the current application or its account and guild settings.
01 / Connected voice
Coordinate the whole raid
Focused rooms without cutting the larger group into isolated calls.
| Capability | Shout | Conventional platforms | Why it matters |
|---|---|---|---|
| Parent + party rooms | Connected by designThe main raid and every party branch remain visible as one voice tree. | Voice rooms are commonly presented as separate, flat destinations. | Split into focused groups without losing the shape of the raid. |
| Zone-wide intercom | /shout is built inLeaders can speak across the connected parent and party rooms. | Cross-room coordination commonly depends on switching rooms or an added bot workflow. | Make one urgent call without collapsing every party into one noisy room. |
| Room context | Hierarchy stays on screenParty members can see and return to the parent room from their focused view. | Moving rooms often replaces the previous room context. | People always know where they are in the larger group. |
| Leader controls | Operational controls includedAuthorized leaders can move, disconnect, mute, or deafen voice participants. | Comparable controls vary by role setup and voice implementation. | Raid leadership can resolve disruption without breaking momentum. |
| Voice preferences | Personal and explicitDevice, input, output, push-to-talk, and keybind settings live in the app. | Usually available, with organization and terminology varying by client. | Members can make voice reliable before the pull starts. |
02 / Live Guild Watch
Let every viewer direct the moment
Streams are shared together, but no one is forced into the same layout.
| Capability | Shout | Conventional platforms | Why it matters |
|---|---|---|---|
| Multiple live shares | One shared watch spaceActive guild streams can appear together in the voice lobby. | Multi-share viewing exists on some services, often within a conventional call layout. | Follow the main tank, scout, and map without bouncing between calls. |
| Viewer-owned layout | Tiles, spotlight, and canvasEvery viewer chooses their own arrangement. | The call or application often decides more of the presentation. | Your layout can match your screen and your role. |
| Rearrange and hide | Local controlsMove, emphasize, or hide a share without changing the room for others. | Per-viewer control varies and may be limited to a primary stream choice. | Remove clutter without interrupting a broadcaster. |
| Free stream quality | Up to 1080p includedHigh-definition sharing is part of the free community foundation. | Resolution and frame-rate limits vary by provider and plan. | A guild can share readable gameplay without paying first. |
| Premium stream quality | Up to 4K 60 FPS with Shout+Higher-quality personal broadcasting is available as an upgrade. | Premium quality tiers use provider-specific caps and pricing. | Members who need more detail can choose it without gating basic use. |
03 / Conversation + context
Keep the reason beside the message
Conversation, decisions, gatherings, and shared media remain connected.
| Capability | Shout | Conventional platforms | Why it matters |
|---|---|---|---|
| Message flow | Conversation-shapedIncoming and outgoing messages have clear sides, while consecutive posts group into readable chains. | Dense chronological logs are a common default. | Fast chat remains easy to scan without wasting space. |
| Rich messages | Built into chatReplies, reactions, spoilers, markdown, embeds, GIFs, stickers, and attachments are supported. | Most mature platforms offer a mix of rich-message tools. | Shout preserves familiar expression while improving the surrounding flow. |
| Polls | Inline and collectedVote in the conversation or review active polls from the dedicated view. | Polls may live in chat, an app, or a separate activity view. | Decisions stay discoverable after the chat moves on. |
| Gatherings + RSVP | Openable event cardsGuild gatherings have details, timing, and response context. | Events are often separated from the channel conversation that prompted them. | Members can understand the plan before committing. |
| Media gallery | Every item has a way backGrid or list views can return directly to the source message. | Media browsers commonly show the file with limited conversational context. | A screenshot keeps the instructions and discussion around it. |
| Forums and durable topics | Structured discussionsTags, search, pinning, locking, and archiving support longer-lived threads. | Forum features vary or may be represented as a specialized channel type. | Knowledge does not have to disappear into a fast room. |
| Search and pins | Dedicated retrievalSearch, pinned messages, and deep-linked alerts return members to the original location. | Search and pins are common; notification destinations vary in precision. | An alert becomes a useful path instead of a dead-end summary. |
04 / The Guild Hall
Enter through a community home
People, guilds, rooms, tools, and discovery have an understandable front door.
| Capability | Shout | Conventional platforms | Why it matters |
|---|---|---|---|
| Guild home | A real entry hallFriends, discovery, inbox, and the bot marketplace are available from the guild-level home. | A server-icon rail and channel destination are common starting points. | Members begin with people and purpose, not navigation chrome. |
| Room map | All by defaultMembers can see the full channel map, then filter voice or chat to match their preference. | Channels are commonly grouped by category in one persistent list. | New members understand the whole guild before narrowing their view. |
| Friends and direct messages | First-class relationshipsFriend requests, blocking, presence, and direct conversations are part of the home experience. | Commonly supported, often as a separate route beside servers. | Personal connections remain accessible without competing with the guild. |
| Discovery | Built for guild browsingSearchable, scrollable guild discovery supports joining a new community. | Public discovery availability and eligibility vary widely. | Communities can be found without turning the product into a feed. |
| Start from a template | Purpose-built foundationsGaming, community, study, and creative templates accelerate setup. | Templates or copied structures may be available depending on the service. | Organizers can begin with useful rooms instead of an empty shell. |
| Bots and webhooks | Guild integrations includedUse the marketplace, installed bots, API access, and channel webhooks. | Bot ecosystems and webhook depth range from extensive to unavailable. | Communities can extend Shout without making extensions the core experience. |
| Welcome and onboarding | Guided arrivalWelcome configuration, join requests, and onboarding give new members a clear first step. | Onboarding depth varies by community eligibility and setup. | The first visit can explain the guild instead of exposing every room at once. |
05 / Stewardship
Give leaders tools they can understand
Permissions, prevention, and history live together as operational controls.
| Capability | Shout | Conventional platforms | Why it matters |
|---|---|---|---|
| Roles and permissions | Explicit access designRoles and room-level permissions define who can see, speak, post, and manage. | Granular role systems are common, with complexity varying by platform. | Leaders can delegate without handing over the entire guild. |
| AutoMod | Prevent before deliveryKeyword and mention-spam rules can reject a message with role and room exceptions. | Automated moderation may be native, bot-driven, or split between both. | Rules are predictable, visible, and scoped to the community. |
| Audit history | Actions remain inspectableGuild administration has a dedicated audit view. | Audit depth and retention vary by provider and plan. | Owners can understand what changed and who acted. |
| Safety controls | Part of guild settingsModeration, join requests, member blocking, and safety configuration have defined homes. | Safety tools are common but may be distributed across menus and help flows. | Members and leaders can find the right control under pressure. |
| Destructive actions | Separated into Danger ZoneHigh-impact server actions are isolated from routine settings. | Destructive controls are commonly available with varying separation and confirmation. | Routine administration is less likely to cause an irreversible mistake. |
06 / Personal command
Let each member shape their experience
Useful control without disconnecting personal preferences from the guild.
| Capability | Shout | Conventional platforms | Why it matters |
|---|---|---|---|
| Notification routing | Guild and channel controlDefault levels, overrides, alerts, inbox filters, and click-through destinations work together. | Notification layers are common, though alerts may lead to broad rather than exact locations. | Members can reduce noise without missing the reason they were called. |
| Appearance themes | Functional themesMembers can apply appearance choices across the application. | Most services offer a base light/dark choice; broader themes vary. | The client can feel personal while the guild retains its identity. |
| Voice and video setup | Centralized controlsDevices, sensitivity, camera, streaming, and privacy choices live in user settings. | Commonly available, with different levels of device and quality control. | Members can troubleshoot their setup without hunting through the room UI. |
| Keybinds + streamer mode | Dedicated settingsKeyboard actions and streaming-safe behavior are configurable. | Desktop clients commonly provide some form of keybind and streamer controls. | Fast actions and privacy fit the way players already operate. |
| Connections | Managed identity linksExternal connections have a dedicated account view. | Connection catalogs and display behavior vary by ecosystem. | Members decide which outside identities belong with their Shout profile. |
| Security + sessions | Visible account accessSecurity settings and active-session revocation are available to the account owner. | Security controls are standard, but session visibility and revocation depth vary. | A member can see and end access they no longer recognize. |
07 / Platform principles
Keep the business model out of the conversation
The product should serve the community using it—not an advertising profile.
| Capability | Shout | Conventional platforms | Why it matters |
|---|---|---|---|
| Advertising | No adsThe guild experience is not interrupted by advertising inventory. | Business models range from subscriptions to promotions, advertising, or a mix. | The community remains the center of the room. |
| Personal data sale | No sale of personal dataMessages, voice, files, and account activity are not packaged for sale. | Data practices differ by provider and should be checked in each privacy policy. | Communication is not treated as a lead-generation asset. |
| Homepage analytics | Consent before optional analyticsOptional first-party Beacon analytics stay off unless allowed, and Global Privacy Control is honored. | Consent models and analytics vendors vary by site and jurisdiction. | Visitors receive a real choice before optional measurement begins. |
| Free foundation | Core community tools stay freeText, voice, roles, moderation, events, polls, bots, 1080p streaming, and 25 MB uploads are included. | Free limits and feature gates vary across services. | A guild can function before anyone decides to upgrade. |
| Where it runs | Web, Windows, and LinuxUse a modern browser or install the dedicated desktop client. | Web and desktop availability is common; Linux support varies. | Members can join from the device that already fits their setup. |
| Paid path | Personal or guild-wideShout+ expands personal quality and capacity; Collective shares benefits with a server. | Upgrades may attach to an individual, a community, or both. | Support can follow one member or strengthen the whole hall. |
Reading the comparison: The conventional-platform column describes common interaction patterns based on category conventions. It does not claim that every provider behaves the same way. Product limits and availability can change; verify any purchasing decision against the provider’s current plan details.
Rally your guild. Own your world.
Do not settle for a familiar clone. Choose a better gathering place.
See the real interface, move through the guild, and decide whether Shout fits the way your people play.