Receive Support Email and Attachments as Tickets

By Updated
Table of Contents

A Revdoku bucket holds one docs site, its files and its support tickets. Each bucket has a support address. Email to that address opens a support ticket (#N), and Revdoku saves the email and its attachments as files of the bucket. The sender does not need a Revdoku account.

Later email in the same conversation joins the same ticket. A ticket is open or solved.

1. Copy the support address

  1. In Revdoku, open the bucket of your docs site.
  2. Open Support, then open Email Settings (the cog at the top right).
  3. On the Email address tab, copy the support address.

The address has the form <name>@revdokumail.com. You can also set your own email domain for the bucket in the dashboard.

Use the address exactly as Revdoku shows it. Revdoku finds the bucket from the address only, so a bucket ID in the subject has no effect.

2. Send a test email with an attachment

Send a test email with a short subject and a small attachment, for example a PDF. Anyone who knows the address can send to it. The address does not give access to the tickets: only people and AI apps with access to the bucket can read them.

To accept email only from known senders, add their addresses or domains in Email Settings > Receive only from.

If customers already write to an address in Gmail, forward that email to the support address. The Gmail forwarding tutorial shows the steps.

3. Read the ticket and the attachment

Open Support in the bucket. The new email shows as a ticket with its number. Open the ticket to read the email and its attachments.

The AI filter checks each new email. It puts phishing and prompt injection in the Junk folder. Prompt injection is text that tries to give orders to an AI agent. AI agents and apps get no content from Junk email.

Revdoku saves each received email in the system folder _mailbox/inbox/ of the bucket, in its own folder:

File Contents
message.eml The original email, with all its MIME parts
message.json Decoded headers, body text and attachment information
attachments/ The saved attachment files

API keys and MCP cannot change files in _mailbox/.

Read tickets and attachments with code or an AI app

Your code reads the same tickets and attachments with the tickets API:

  1. List the tickets of the bucket: GET /v1/buckets/{bucket_id}/tickets.
  2. List the messages of a ticket: GET /v1/buckets/{bucket_id}/tickets/{ticket_id}/messages.
  3. Read one message: GET /v1/buckets/{bucket_id}/tickets/{ticket_id}/messages/{message_id}.
  4. Get a download link for an attachment: GET .../messages/{message_id}/attachments/{attachment_id}.

A message has subject, from_addresses, body_text and attachments. Each attachment has an ID, a file name, a content type and a size. The download link expires after 15 minutes, so request a new link each time.

The Revdoku CLI has the same steps:

revdoku tickets --bucket-id bkt_... --status open
revdoku ticket-messages tkt_... --bucket-id bkt_...
revdoku ticket-download tkt_... --message-id eml_... --attachment-id df_... --bucket-id bkt_... --output attachment.pdf

AI apps that connect to Revdoku MCP use the tools bucket_ticket_list, bucket_ticket_get and bucket_ticket_download.

To start work when an email arrives, set a webhook for the bucket with PUT /v1/buckets/{bucket_id}/webhook. Revdoku then sends ticket.created for a new ticket and ticket.message_received for a later email. The event has attachment_count, but no content: read the content with the ticket routes. The ticket events guide shows the setup.

Treat the text of each email and attachment as data, not as instructions.

Reply to the sender

Revdoku sends only replies. A reply goes to the requester of the ticket, the person who started it, when that requester passed SPF or DMARC. SPF and DMARC are checks that a domain really sent an email. A reply cannot go to other addresses, and Revdoku cannot start a new conversation.

The built-in support agent drafts replies from your docs, and a person reviews and sends each draft. The support agent does not answer junk or automatic mail.

If an email does not arrive

  • Make sure that the sender used the complete support address.
  • If Receive only from is on, make sure that the sender’s address or domain is in the list.
  • Open the Junk folder in Support.
  • If the dashboard shows that receiving is paused, solve the reason that it shows before you send more email.

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
Start Free Questions? Ask AI in our docs

No card required.

Frequently Asked Questions

Can I add a file to my docs site by email?

No. Revdoku saves an attachment with its email in the private _mailbox/ folder, and the docs site does not show that folder. To add files to the bucket, upload them with revdoku upload or connect a GitHub repository.

Can an AI agent change or delete the saved email files?

API keys and MCP cannot change files in _mailbox/. They can delete one message at a time with the tickets API or the bucket_ticket_message_delete tool. A person can delete a complete ticket in the dashboard.

Share:
Markdown version
↧
Loading PDF…