Bot-to-Bot Autopilot
Doti doesn’t just answer questions. With Bot-to-Bot Autopilot, Doti becomes an autonomous agent that can be triggered by other bots or systems - executing complex, multi-step processes automatically.
This is where automation meets intelligence.
What Is Bot-to-Bot Autopilot?
Bot-to-Bot Autopilot allows external bots or automated Slack workflows to trigger Doti by tagging it in a message.
Doti will:
Recognize the message
Trigger Autopilot
Use its agentic capabilities to perform a series of steps
Reply automatically with a fully contextual response
Powered by Agents
What makes this powerful is Doti’s agent framework. Each Autopilot is tied to an agent that can include multi-step instructions.
This means Doti doesn't just answer - it can think, fetch, synthesize, and act.
Example Workflow: Support Ticket Investigation
Let’s say a Support Bot posts this:
@doti New Zendesk ticket: ID 123456 - Customer is having sync issues
If Doti is connected to the Support Agent with agentic logic, it could automatically:
Retrieve the ticket details using the provided ID
Analyze the ticket description to find similar historical cases
Search across Slack threads, Confluence docs, and support articles for context
Draft a resolution, tailored to the specific problem
🪄 All of this happens from a single tagged message - no human involved.
How to Enable Bot-to-Bot Autopilot
Select or create a new Autopilot
In the configuration panel:
✅ Enable “Allow Doti to respond to Bots”
Make sure:
The other bot tags
@doti
in its messageDoti is a member of the channel
The Autopilot is connected to an Agent or Collection
🔁 Use Cases
🎫 Support Tickets
Investigate, correlate, and respond to customer issues
📅 Weekly Summary Bot
Summarize conversations, extract metrics, identify trends
🔔 System Alerts
Cross-reference previous incidents, escalate or recommend fixes
⏱ Scheduled Reports
Run multi-step status checks and post AI-curated updates
Scope and Control
Bot-triggered Autopilot follows all agent and Autopilot configurations:
Agent instructions define multi-step workflows
Permissions can be enforced or bypassed
Invisible mode or Testbed can be used for moderation
Data scope is controlled via assigned collections or agents
You’re in complete control of what Doti does - and how confidently it does it.
Combine with Testbed for Safe Rollouts
Pair this with Testbed mode for maximum safety:
Let bots trigger Doti
Route the response to a moderator channel
Human reviewers can Publish or Dismiss the output
Perfect for sensitive domains or high-stakes channels.
Summary
Bot-to-Bot Trigger
Any bot tagging @doti
can trigger Autopilot
Agent-Powered Workflows
Doti runs multi-step, sequential actions
Use Cases
Support, operations, alerts, summaries, reports
Fully Configurable
Uses agent logic, collections, and permission models
Optional Moderation
Route responses through Testbed before publishing
AI in Motion
Doti not only replies — it executes
🤝 With Bot-to-Bot Autopilot, your bots don’t just inform - they activate. Doti becomes the AI backbone of every automated workflow in Slack.
Last updated
Was this helpful?