Hey Imran. I'm Runbear — I work in Slack with you. Two ways to start:
Selected: Show me what's possible
👋 Hi Imran. I'm Runbear.
What's a question you wish someone on your team would just answer for you, instead of you having to dig?
Or type whatever you'd like to try.
Button choices prompt 39a6375e
What @-mentions did I miss?What happened in #all-boonsie today?selected
Selected: What happened in #all-boonsie today?
✅ Looks like it's been quiet in #all-boonsie today — no new messages yet.
Want me to run this every morning so you don't have to check manually?
- Every workday 9am
- Every workday 5pm
Not your rhythm? A couple of other things people commonly start with:
- "What @-mentions did I miss?"
- "Tell me everything about [customer email]"
onboarding steps: ✓ ask a question ☐ connect more tools ☐ create a trigger ☐ hire an AI teammate
✅ Set up — every weekday at 9am ET, I'll DM you a summary of #all-boonsie activity.
[View trigger](https://app.runbear.io/personal/event-triggers/scheduled-41bf043c-1cb3-4fd5-bff1-da9032c3bdc5)
You can run it right now to see what it looks like. Do you want to run it now?
onboarding steps: ✓ ask a question ☐ connect more tools ✓ create a trigger ☐ hire an AI teammate
btw, how do i invoke you in channels? are you in all channels right now?
Good question! I'm not in all channels automatically — you need to invite me first.
**To add me to a channel:**
1. Go to any channel
2. Type /invite @Runbear (or click the channel details and add me from there)
**To invoke me once I'm in a channel:**
- Just @mention me: @Runbear what happened here today?
- Or ask a question and tag me
I'm currently in this DM with you. Want me to join #all-boonsie so I can actually watch it and run that daily digest?
how do i invoke a different agent that i created?
To invoke a different agent you've created:
1. **Invite it to a channel** — Type /invite @[agent name] in the channel where you want to use it
2. **@mention it** — Once it's in the channel, just tag it: @[agent name] your question here
Each agent you create has its own Slack identity and works independently. You can have multiple agents in different channels — each with its own role, knowledge base, and tools.
**Quick check:** Have you already created other agents? If so, I can help you figure out which channels they're in or how to set them up. If not, that's the "hire an AI teammate" step we're about to hit — you'd build team agents at https://app.runbear.io/assistants.
Imran Sobh's Agent: Nice! Ollie works the same way:
1. **Invite Ollie to a channel** — /invite @Ollie in whichever channel you want to use them in
2. **@mention Ollie** — @Ollie [your question] and they'll respond
Each agent (me, Ollie, any others) operates independently with their own setup, tools, and knowledge.
Want help figuring out where Ollie is right now or what they're set up to do?
so you mention via usergroups or what?
Imran Sobh's Agent: Nope, not usergroups — agents are regular **@mentions**, just like tagging a person. Each agent appears as a bot user in your Slack workspace with its own profile. So you'd just type: • @Runbear (that's me) • @Ollie (your other agent) Slack will autocomplete it like any other user. Once the agent is in a channel, it'll respond when you @mention it or reply in a thread. Usergroups (like @engineering or @team-marketing) are different — those notify multiple people at once. Agents are 1:1 bot identities.
but how does it appear as its own profile that i can @mention by name?
Imran Sobh's Agent: Great question! When you create an agent and **deploy it to Slack**, Runbear registers it as a bot user in your workspace. That gives it its own profile, name, and @mention handle.
There are two ways this happens:
**1. Shared Runbear app (default)**
The agent uses the shared Runbear Slack app. Multiple agents can share this connection, but each has its own identity when you @mention it.
**2. Custom Slack bot (recommended for team agents)**
The agent gets its own dedicated Slack bot with a custom name, avatar, and profile. This is what you'd typically do for team agents like Ollie.
When you created Ollie, you either:
• Connected it via the shared app, OR
• Set up a custom Slack bot for it
Either way, once deployed, Ollie shows up as a bot user in your workspace member list, and you can @mention it by name.
**Want to check Ollie's setup?** I can pull up the details or help you deploy other agents to Slack if you're building more.
whats the benefit of this over using usergroups to route
Imran Sobh's Agent: Good question! Here's why individual agent @mentions beat usergroups for routing:
**1. Specialization**
Each agent can have different tools, knowledge, and capabilities. For example:
• @Ollie might be your customer support agent (connected to Zendesk, your docs)
• @Runbear (me) is your personal assistant (your calendar, email, tasks)
• @DevBot could handle engineering stuff (GitHub, Linear, logs)
With usergroups, everyone gets the same notification — no specialization.
**2. Clear routing**
@Ollie answer this customer question → Ollie knows it's for them, responds immediately.
With a usergroup, you'd notify multiple agents/people, and it's unclear who should respond.
**3. Different contexts**
Each agent maintains its own memory, conversation history, and context. Ollie remembers customer interactions; I remember your personal preferences. That doesn't work with a shared usergroup.
**4. No noise**
Only the relevant agent gets invoked. Usergroups would ping everyone in the group, even if only one should respond.
**5. Role-based access**
Different agents can have access to different tools and data. Your HR bot shouldn't see engineering repos, etc.
**TL;DR:** Individual agents = specialized roles with clear routing. Usergroups = broadcast notifications to multiple people/bots at once.
Make sense?