Bring @hivy into the conversation.Keep the work in Slack.
Assign an agent to a channel, then mention @hivy, add a chosen reaction, or let the agent watch for work. It reads the conversation, does the job with its tools and knowledge, and reports back in the same thread.
Work stays with the conversation
Stop carrying Slack requests into another app.
The request already has names, screenshots, decisions, and replies around it. Mention @hivy and the assigned agent gets that context, works with the same tools and knowledge it uses in Hivy, then posts the answer where everyone can find it.
# product-support
Customer reports, debugging, and handoffs
# product-support
Bring support problems here. Mention hivy when the agent should take over.
hivy is typing…
Always-on channel watch
Some work shouldn’t wait for a mention.
Give an agent a standing instruction for one channel. It can follow new messages, group repeated requests, take permitted actions, and post when the instruction calls for a response.
The channel keeps moving when nobody tags the bot.
The watch stays with the channel until an admin changes or stops it.
# customer-voice
Customer feedback and product requests
hivy is watching #customer-voice
Group repeated requests and post when product needs to decide.
hivy is typing…
# product-support
Customer reports, debugging, and handoffs
Reaction trigger
When someone adds 👀, run the Support agent on that message.
hivy is typing…
Reaction handoffs
Turn a reaction into a handoff.
Your team already uses reactions to say “I’m looking,” “please review,” or “take this.” Choose one emoji and tell Hivy which agent should run when that reaction appears.
No new command to teach the team.
Each reaction rule can have its own channel, agent, and job.
Channel ownership
Match each channel with an agent that knows the job.
Product questions should reach the Product agent; incidents should reach Reliability. You choose the route once, and an agent can cover more than one channel when the work overlaps.
After someone mentions @hivy
One mention carries the request into the assigned agent and brings the result back.
Spot the request
A teammate mentions @hivy in a channel you’ve connected.
Bring the context
Hivy reads the message, its parent post, and the replies around it.
Do the work
The assigned agent opens or resumes the session tied to that thread.
Answer the thread
The result comes back to Slack, right beside the original request.
Follow-up questions
Follow up without starting over.
The first mention connects the Slack thread to one Hivy session. Ask another question in that thread and the same agent continues with the conversation and work it already completed.
# product-support
Customer reports, debugging, and handoffs
hivy is typing…
What the agent remembers
Tomorrow’s answer remembers today’s work.
After a job, the agent can save the decisions, findings, conventions, and preferences worth keeping. Mention @hivy later and the next session can draw on those notes and the agent’s recent work.
Saved decision
Resolve every workspace before the import creates records.
Useful finding
Multi-workspace accounts return a list, not one record.
The agent can carry these notes into its next Slack request.
hivy is typing…
How teams use Hivy Tag
Hivy agents in Slack can return the work each team needs, right in the thread.
# support-escalations
Customer issues that need investigation
# support-escalations
Example conversation with the support agent assigned to this channel.
hivy is typing…
The regression starts in workspace_lookup.
- The July 18 deploy changed the response from one workspace to Workspace[].
- run_import still reads .id directly. Select the matched workspace before creating the import.
Find the failure while the report is still fresh.
A Support agent can read the report, inspect the connected systems, and return the cause with a fix your team can act on.
@hivy compare this import error with the last working deploy and tell me what changed.
Assigned in #support-escalations. The answer returns to the same Slack thread.
You choose the boundaries
@hivy only works where you’ve assigned it.
Your admins choose the Slack connection, channel, team, and agent. Mentions in public or private channels follow that route; without one, @hivy won’t start an agent run.
Routes set by channel
Agents picked by your team
Public and private channels
History attached to each thread
Your next handoff can stay in Slack.
Create a Hivy workspace, connect Slack, and assign the agent that should answer in each channel.