Moving to Google Chat?
Go from group mentions
to team shouts.

How team shouts work after the move

A team shout is useful when you need help from a department but don’t know which person to ask. In Shout!, the team’s Chat space determines who receives it.

If you used group mentions on another platform, Shout! gives you a way to keep that habit. In Google Chat, write !support-team from a project space and Shout! notifies the Support Team space with your message and a link back.

Shout! handles team notifications after your move. Your message history, files, and account migration stay with your migration process.

Map your teams to Chat spaces

Start with the teams people need to reach most often. Give each team a Chat space, make sure its membership is right, and add Shout! there. The space name becomes its shout name automatically.

Choose recognizable, distinct names. Paid plans let space managers set a custom alias in the space description, so a longer space name can have a short, memorable shout name. The alias guide explains the details.

Try it with one project and two teams

The Free plan covers 10 spaces per organization, so you can try it across several teams. Space limits include both source and destination spaces where Shout! is added.

1. Install Shout! An admin install gives your pilot the normal !name experience. An individual install works with @Shout! !name if your organization permits it.
2. Add it to the spaces you want to connect. For example: Project Launch, Design Team, and Support Team.
3. Send a real request. From Project Launch, write !design-team the launch page is ready for review.
4. Check both sides. The destination team should see the shout. Confirm that the people who need to reply can open the link back to Project Launch.
5. Show everyone the pattern. Share the team names and explain when to send a team shout. /shout spaces opens the directory in Chat.

Make it part of your Google Chat rollout

After the pilot, an administrator can install Shout! for the organization. Existing spaces keep working, the @Shout! prefix becomes optional, and messages from bots and webhooks can shout too.

Include the shout names in your team’s onboarding notes. Keep the spaces’ memberships current as people change roles. Shout! uses the members of each Chat space.

If you need more spaces, paid plans are priced per organization. They also add custom aliases and urgent shouts. Choose a plan based on how many spaces need Shout!, with no per-user fees.

Show the team when to use !!

Use !platform-team for a routine request. For an outage, !!platform-team checkout is down sends an urgent shout that bypasses Google Chat’s Do Not Disturb setting on paid plans. Agree on which situations need an urgent notification as part of your rollout. See how urgent shouts work.

Set expectations before the switch

• A team shout targets a space. Shout! doesn’t import groups or synchronize memberships from your previous platform.
• Both spaces need the app. Add Shout! where people send requests and where the target team receives them.
• The message is shared with the destination. Keep confidential content out of a shout unless it belongs with everyone in that space.
• Conversation access still applies. A link back doesn’t grant permission to open a private source conversation.
• Shouts stay in your organization. Direct messages are not shout sources or destinations.