AI Documents

​

Overview

AI Documents live in Settings under AI Documents. This page is only shown when your agency has workflows access. Each document is Markdown text that your AI agent can read, and in some cases write, when it works on your account.

​

Document Types

Every document has one of three types. The type is chosen when you create the document and cannot be changed afterward. RevyOps Guides are locked outside of RevyOps’s own agency. A locked guide shows:

Locked. RevyOps keeps this up to date for you.

Guides are locked because every client reads the same version, which is what lets RevyOps improve a guide and have the change reach you the same day.

​

The Page

The AI Documents page shows:

• A New folder button and a New document button
• A search box (“Search documents and folders”)
• A client filter (“Any client”)
• A table with columns Document, Type (with a “What are these types?” tooltip), Assigned to, and Last updated

An empty folder shows “Empty folder. Add a document to it.”

​

Assigned To

Each document has an assignment:

​

Deleting a Document

Deleting a document warns you first:

Any AI agent step referencing this document will lose it. This cannot be undone.

​

Shared RevyOps Guides

RevyOps Guides are written and maintained by RevyOps in RevyOps’s own agency, and are shared out to every agency automatically. They only appear for other agencies when assigned to all clients. Other agencies see these guides’ folders as read-only in their own AI Documents list.

​

Client Starter Copies

When a new client is created, RevyOps can seed that client with a starting set of Shared Documents, copied from templates that live in a folder named Templates / Client Starter in RevyOps’s own agency. Each client gets its own copy, assigned to that client only, placed in a folder named Client Starter / [client name]. This seeding happens once per client, either when the client is created or the first time your AI agent reads AI Documents for that client.

​

Folders: How Your Agent Finds Things

Folders are how your AI agent finds its way around your documents. A full library is too large for an agent to read in one go, so it works the way a person would with a shared drive:

1. It lists the folders available to the client.
2. It opens the folder that matches what it needs, and lists the documents in it.
3. It reads one document at a time, or just the outline or one section of a long one.

That means the way you organise folders decides what your agent reads, and what it skips. What the agent sees

• Only folders that hold at least one document assigned to that client. A folder whose documents aren’t assigned to the client doesn’t appear for it at all.
• Folder names, document names and document types. These are all it has to decide where to look, so name them for what’s inside.
• Nested folders, written with ” / ” between levels, such as RevyOps Method / Templates / Client Starter.

Folders RevyOps sets up for you Tips for organising

• Keep one topic per document, so the agent can read exactly what it needs.
• Use clear folder names that say what’s inside, such as “Messaging” or “Objection Handling”, not “Misc” or “New folder”.
• Put a client’s working notes in that client’s own folder, so they stay separate from shared material.
• To move a whole library in at once, import a zip file. Each file’s folder path in the zip becomes its folder. See Agent Prompts and ICPs.
• Deleting a folder never deletes the documents in it. They move back to the top level.

​

How Your AI Agent Reads Documents

Your AI agent (through the MCP connection under Settings > Developer > MCP) can:

• List the folders and documents available to a client
• Read a document in full, by outline (headings only), or by a single section
• Search documents by name and content
• Create or update a Shared Document or Agent Prompt (an agent cannot create a RevyOps Guide)
• Delete a document, but only one that is assigned to that client alone

Your agent cannot edit or delete a RevyOps Guide, or a document shared with other clients. If it tries, it’s told to create its own Shared Document in its own folder instead. Document content is capped at 64,000 characters.