Support email for your docs
Each docs site has a support mailbox with its own email address. People write to that address, and readers of your docs send questions from the site. Each conversation is a ticket. The built-in support agent drafts replies from your docs, and a person sends them.
How a question arrives
| From | What happens |
|---|---|
A person writes to the support address of the docs, for example support.k7x2@revdokumail.com, or to an address on your own domain. |
|
| Ask AI on the docs site | A reader asks a question. Ask AI answers from your docs and names the pages that it used. |
| Leave a message on the docs site | If the answer does not help, the reader types a name, an email address and a message, and confirms the address with a code. The message arrives as an email from that address. |
The docs site never shows the support address. A reader who leaves a message gets your reply by email.
Tickets
Each conversation that someone starts is a ticket with a number, for example #12. A ticket is open or solved. Your replies and drafts join the ticket of the conversation.
When you finish, click Solve #12. If the same person writes again in that conversation, the ticket opens again.
Draft replies from your docs
The built-in support agent reads each new question. It finds up to five pages of your docs that match the question, and it writes a reply that links the page that it used.
- The draft waits in Drafts. The people who can reply get a notification.
- A person reads the draft and edits it if necessary.
- The person clicks Send, or declines the draft.
If no page of your docs answers the question, the email gets the Needs reply label. The support agent does not answer junk, automatic mail or forwarded email.
Use the questions that the docs do not answer to find the pages that you must write next.
Safety of the support mailbox
- Revdoku scans each incoming email for viruses and spam.
- The AI filter checks each received email for phishing and prompt injection. It labels a suspected attack as Junk, and AI agents and apps get no content from Junk email. The filter can miss an attack or label an email wrongly.
- Replies go only to people who wrote to the mailbox or left a message on the docs, to account members and to the other mailboxes of the account. Revdoku does not send newsletters, cold email or bulk email.
- AI agents and apps read email as data, not as instructions.
Connect your own tools
- Webhooks and live events: Revdoku sends a signed HTTPS request to your server for each new email. See Email events.
- n8n and Zapier: start a workflow when a support email arrives. See n8n and Zapier.
- API, MCP and CLI: list and read support email, and reply to the people who wrote. See the API guide, the MCP guide and the CLI.
Docs from GitHub,
for people and AI agents
Connect a repository. Revdoku publishes it as a docs site with search, Ask AI, an API console and an MCP server.
- Publishes from GitHub on every push
- Works with Mintlify repositories
- API console from your OpenAPI file
- MCP server and llms.txt for AI agents
- Ask AI and a support mailbox
- API, MCP and CLI access