Sanaf AI
Start free
AI Chatbots

DocsBot AI, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your DocsBot AI account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • AI Chatbots
  • Connects with a key
  • 12 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What DocsBot AI is

DocsBot AI enables the creation of custom chatbots trained on your documentation, facilitating automated customer support and content generation.

You paste in a key from your own DocsBot AI account. It is kept encrypted, and you can withdraw it from inside DocsBot AI whenever you like.

How a run works

One message in, the work done in DocsBot AI.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in DocsBot AI. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own DocsBot AI account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

12 tools it already has

What it can do in DocsBot AI

These are the ready-made tools your AI employee already has in DocsBot AI. It is not limited to them, but it never has to be taught these.

  • Create BotTool to create a new bot within a team. use when you have a valid team id and want to provision a new bot.
  • Delete BotTool to delete a specific bot by its id. use after confirming the bot id is correct to permanently remove a bot from the system.
  • Generate Conversation TicketTool to generate a structured support ticket from a chat agent conversation. use when you need to convert an existing conversation into a ready-to-submit helpdesk ticket.
  • Get Bot DetailsTool to fetch details of a specific bot by id within a team. use after confirming valid team and bot ids.
  • Get Team DetailsTool to fetch details of a specific team by its id. use when you need full team info including members and settings after confirming the team id.
  • List Bot SourcesTool to list all sources for a specific bot. use when you need to retrieve paginated source lists after confirming the bot's identifier.
  • List QuestionsTool to list all questions asked of a specific bot. use after confirming the bot's identifier. example: "list questions for bot abc123 with status 'unanswered'."
  • List Team BotsTool to list all bots for a given team. use after confirming the team id to retrieve all associated bots for that team.
  • List TeamsTool to list all teams. use when you need to retrieve every team associated with the authenticated user.
  • Update BotTool to update specific fields for a bot (e.g., name, description, settings). use after confirming valid team and bot ids.
  • Update TeamTool to update specific fields for a team. use after confirming the team id when you need to change the team's name, description, or avatar url. returns the updated team record.
  • Upload File to Cloud StorageTool to upload a file to cloud storage via a presigned url. use after generating a presigned url for file upload.
Access, and who is in charge of it

You stay the boss of your DocsBot AI account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own DocsBot AI account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in DocsBot AI is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in DocsBot AI and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

See every app

Questions people ask about DocsBot AI

Can an AI employee really work inside DocsBot AI?
Yes. It signs in to your own DocsBot AI account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of DocsBot AI?
No. Nothing moves and nothing is replaced. Your records stay in DocsBot AI, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my DocsBot AI account?
You paste in a key from your own DocsBot AI account. It is kept encrypted, and you can withdraw it from inside DocsBot AI whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in DocsBot AI?
It has 12 ready-made tools in DocsBot AI today, among them Create Bot, Delete Bot and Generate Conversation Ticket. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use DocsBot AI and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in DocsBot AI and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in DocsBot AI?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in DocsBot AI is written down with what it did and when.