Searches an indexed documentation base for grounded answers, keeps its sources re-indexed, and escalates the questions it cannot close.
38actions available
Every action runs live through MCP. Nothing to build, nothing to maintain.
Ayro converts a DocsBot chat into a support ticket. Your team escalates complex conversations to humans.
Ayro retrieves analytics for a DocsBot over a time period. You see how many questions it answered and how well.
Ayro creates a new bot within a DocsBot team. Your support docs are now AI-searchable for customers.
Each card is one request a support team gets, and the Docsbot.ai actions Ayro runs to close it.
Ayro runs a semantic search over the bot's indexed content and pulls back the most relevant chunks, so a product question is answered from your own docs rather than from a general model.
Ayro requests a presigned upload URL, sends the file to storage, and registers it as a bot source, so a new policy or release note is answerable as soon as it finishes indexing.
Ayro lists what a bot has been trained on, re-indexes a source that failed, and removes the page that no longer exists, so the knowledge base matches what your docs actually say today.
When the docs do not cover the question, Ayro saves the lead's details and generates a ticket with a subject and body written from the customer's side, then hands the thread to a human agent.
How it works
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Ayro reads the Docsbot.ai actions it has and picks the ones a request needs.
Authorize the Docsbot.ai account your team already uses — one consent screen, no API keys, no mapping tables. Ayro can only do what you granted that account, and you can disconnect it at any time.
Describe the job the way you would hand it to a teammate. Ayro maps it to the Docsbot.ai actions that close it and chains as many as the request needs.
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started freeDocsbot.ai · Ayro
What can you do in Docsbot.ai without me setting anything up?
These, right away:
Great, let's start with the first one.
FAQ
Setup, permissions, and the limits of what Ayro can do inside Docsbot.ai.
Yes. Generate Conversation Ticket needs a Standard plan or higher, and the conversation has to have been created through the Chat Agent API rather than the legacy Chat API. The other DocsBot.ai actions Ayro uses, including Semantic Search Bot Content, carry no such requirement.
All 38 actions your agent can call on Docsbot.ai, straight from the live MCP connection.
Capture lead information by updating conversation metadata and saving the lead.
Create a new bot within a team.
Create a new source for a bot.
Create a new webhook subscription for a bot.
Delete a specific bot by its ID.
Delete a specific conversation by its ID.
Delete a specific lead by ID.
Delete a specific question from history.
Delete a specific source from a bot by its ID.
Delete a webhook (unsubscribe) by its ID.
Generates a structured support ticket from a Chat Agent conversation.
Fetch details of a specific bot by ID within a team.
Retrieve monthly statistical reports for a bot.
Retrieve comprehensive statistics and analytics for a bot over a time period or date range.
Retrieve detailed information about a specific source by its ID.
Fetch details of a specific team by its ID.
Get a presigned upload URL for uploading files as sources.
Retrieve details of a specific webhook by ID.
List all bots for a given team.
List conversation history for a bot with pagination.
List captured leads for a bot with pagination and date filtering.
List all questions asked of a specific bot.
List all deep research jobs for a bot with pagination support.
Retrieves a paginated list of all sources for a specific bot within a team.
List all members of a team including their roles.
List all teams.
List all registered webhooks for a bot.
Rate an answer from chat APIs as positive (1), neutral (0), or negative (-1).
Refresh a source to re-index its content.
Perform semantic search on a bot's indexed content.
Same connection, same setup. Pick the next one your team already uses.
Filters a requester's tickets and replies in thread, reuses approved canned responses, checks agent availability against SLA rules, and searches solution articles.
Reads conversations and their internal notes, handles thread attachments, keeps contact records matched and current, and subscribes to inbox events.
Matches chat visitors to their Plain record, checks tier before answering, opens and replies to threads, and updates group membership.
Creates contacts from a first-touch conversation, leaves internal notes for the next agent, and maintains the workspace tag list.
Lists the chatbots on an account, retrieves the leads they captured, and reads the smart prompts configured on a given bot.
Looks up ticket history, opens and replies to tickets, and keeps the queue tagged and deduplicated without an agent stepping in.

Authorize the account and your agent has all 38 actions from the first conversation.
