Roll Out an Agent

Roll out in phases. Test the agent in a 1:1 chat first, add it to one shared Slack channel, then open it up.

​

Before you start

• The agent already works in a private chat.
• Slack (and any other tools it needs) are connected. See Give an agent a connector.
• You have decided whose connectors the agent should use. By default it uses each person’s own accounts.

​

Phase 1: Pilot in one channel

1. Add the agent to a single Slack channel. See Using Agents in Slack.
2. Start with a few people and real tasks.
3. Fix instructions and tools before you invite more people.

​

Phase 2: Expand

• Open the channel to the wider team once the agent behaves the way you want.
• If you want a custom name, avatar, and faster @mentions, connect a Custom Slack App.
• Add more channels as other teams ask for it.

​

Phase 3: DMs

Direct messages and group DMs need a Custom Slack App. The standard @Gumloop bot cannot be added to DMs.

​

How people reach the agent

Use a channel trigger when you want a whole channel to use the agent with no onboarding. If you do that, remove the @mention bot from the channel (/gummie remove) and keep Ignore Bot Messages on so the agent does not loop.

​

Whose connectors the agent uses

By default, a shared agent uses the invoker’s connectors. To make everyone share one inbox or CRM login, pin agent-owned credentials. For @mention rollouts:

• Turn on SSO or domain auto-join in organization settings so people are provisioned on first sign-in.
• Set the agent’s General Access to Organization so every member gets User access, and hide the parts of the setup they do not need with User Permissions.

​

Operating at scale

• Many people can message the same agent at once. You do not need extra triggers for parallelism.
• Attach subagents for specialized work instead of stuffing one agent with every tool.
• On Channels → Slack, set Thread Replies to Only on Mentions in busy channels.
• Usage comes from the org credit pool. See Who pays for a shared agent.

​

FAQ

​

Related