Support tickets for your docs
Readers of your docs ask questions with Ask AI, leave a message on the site, give page feedback or send an email. Each conversation is a support ticket. The built-in support agent drafts replies from your docs, and a person sends them.
How a question arrives
| From | What happens |
|---|---|
| Ask AI on the docs site | A reader asks a question. AI answers from your docs and names the pages that it used. Each chat is kept as a ticket in AI chats, solved from the start. |
| Leave a message on the docs site | If AI cannot answer, the reader types a name, an email address and a message. The message opens the ticket of the chat for your team. After two questions without an answer, Ask AI opens the message form itself. |
| Page feedback | A reader clicks No on “Was this page helpful?” and adds a comment. The comment opens a ticket without a sender address. |
A person writes to the support address of the docs, for example support.k7x2@revdokumail.com. |
The docs site never shows the support address. A reader who leaves a message gets your reply by email.
Tickets
Each ticket has a number, for example #12. A ticket is open or solved. An open ticket waits for a person. Your replies and drafts join the ticket.
When you finish, click Solve #12. If the same person writes again, 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 the ticket for approval. 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. The Analytics page of the site lists them, with the searches that found nothing.
Safety of support tickets
- Revdoku scans each incoming email for viruses and spam.
- The AI filter checks each new message for phishing and prompt injection: email, messages left on the site and page feedback. It labels a suspected attack as Junk, and AI agents and apps get no content from Junk messages. The filter can miss an attack or label a message wrongly.
- Revdoku sends only replies. Each reply goes to the person who opened the ticket. Revdoku does not send newsletters, cold email or bulk email.
- AI agents and apps read messages 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 message of a ticket. See Ticket events.
- n8n and Zapier: start a workflow when a support ticket gets a message. See n8n and Zapier.
- API, MCP and CLI: list and read tickets, and reply to the person who opened a ticket. See the API guide, the MCP guide and the CLI.
A docs portal with Ask AI
and support tickets
Connect a repository, or describe your product to start. Each docs site has search, Ask AI, an API console, an MCP server and support tickets.
- 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 support tickets
- Analytics for people and AI agents