A reader asks a question on your docs site
A developer reads your API docs at docs.example.com, clicks Ask and asks: “Why does a webhook retry after a timeout?” AI answers from your docs and names the pages that it used. Revdoku keeps the chat as a ticket.
If the answer does not help, the developer clicks Leave a message and types a name, an email address and the question. The message opens the ticket of the chat for your team, with the questions that the developer asked AI. The docs site never shows the support address.
People can also write to the support address directly, for example from a link in your app. A reader can also send a comment with page feedback. Each of these becomes a ticket too.
Set it up once
- Publish your docs site. See Publish API docs from a GitHub repository.
- Find the support address in the Email Settings of the bucket, for example
support.k7x2@revdokumail.com. - To receive email on your own domain, connect the domain in Account Settings → Domains. Then change the address in Email Settings.
- Make sure that the AI filter is on. The support agent works only on messages that the AI filter checked.
What happens to each question
| Step | What Revdoku does |
|---|---|
| 1. The message arrives | Scans email for viruses and spam. The AI filter labels suspected phishing and prompt injection as Junk. |
| 2. The ticket opens | The conversation gets a ticket number, for example #12. Your replies join the same ticket. |
| 3. The support agent drafts a reply | It reads up to five docs pages that match the question and writes a reply that links the page that it used. |
| 4. A person sends it | The draft waits in the ticket for approval. A person reads it, edits it if necessary, and clicks Send, or declines it. |
If no page of your docs answers the question, the email gets the Needs reply label, and the people who can reply get a notification. When the work is done, click Solve #12. A new email in the same conversation opens the ticket again.
The support agent does not answer Junk, automatic mail or forwarded email. AI agents and apps get no content from Junk messages. The AI filter can miss an attack or label a message wrongly, so a person reads each draft before it goes out.
Limits that protect your senders
| Guard | What it does |
|---|---|
| Replies only | Revdoku sends only replies. Each reply goes to the person who opened the ticket. A ticket without a sender address, for example page feedback, gets no reply: 403 EMAIL_RECIPIENT_NOT_ALLOWED. |
| Rate limits | Too many emails from the bucket, or to one recipient, in a minute, an hour or a day return 429 EMAIL_SEND_RATE_LIMITED. |
| Loop guard | When the bucket and one address each sent the other 20 emails in 24 hours, sending returns 429 EMAIL_LOOP_DETECTED. This stops two automatic responders from answering each other. |
Connect your own tools
- Signed webhook: Revdoku sends a
ticket.createdevent for the first message of a new ticket, and aticket.message_receivedevent for a later message. The event carries IDs only. Make sure that its HMAC signature is correct, then read the message with your API key. See Ticket events. - AI apps: the hosted MCP server at
https://mcp.revdoku.comhas the toolsbucket_ticket_list,bucket_ticket_getandbucket_ticket_reply. - Workflows: start an n8n or Zapier workflow when a support ticket gets a message.
People see every step
Analytics → Logs lists each read of a message, each draft and each reply, with the person or the connection that made it and the reason it gave.
Start
Start free. You do not need a card. See also Support tickets.