Skip to content

Team inbox

Reply from the address they wrote to.

A shared inbox for support@, billing@ and sales@ that runs in your Cloudflare account. Threads update live, and nothing lives in a vendor's database.

The EmailFlare inbox with a thread list on the left and an open conversation on the right

How routing works

Cloudflare receives it. Your Worker files it.

There is no mail server to run. Cloudflare Email Routing delivers inbound mail straight to the Worker you deployed.

  1. Step 1

    A customer writes to support@

    From any mail client or provider, to an address on your domain.

  2. Step 2

    Cloudflare Email Routing

    A catch-all rule on your domain hands the message to your Worker. EmailFlare sets the rule up when you add a mailbox.

  3. Step 3

    Your Worker

    Parses the message, sets bounce and complaint reports aside, and finds or creates the thread and the contact.

  4. Step 4

    Your mailbox

    Messages go to D1, large bodies and attachments to R2. Browsers with the inbox open get a live push from a Durable Object.

When you reply, EmailFlare puts a token in the Reply-To address, so the customer's answer comes back to the same thread.

Mailboxes

One mailbox per address, one team behind each.

Create a mailbox for every address you answer: support@, billing@, sales@. Each one has its own members, and you can filter the whole inbox down to one.

  • Add a mailbox and EmailFlare configures Email Routing for its domain, if your API token allows it
  • Assign the people who should see it
  • Switch between All mailboxes and a single address in one click
The inbox sidebar with Compose, Starred, Archived and the mailbox picker, next to the thread list

Threads

Conversations, not a pile of messages.

Replies group into threads with the mail you sent, so a customer's whole history reads top to bottom. New mail appears as it arrives, without a refresh.

  • Live updates over a WebSocket, one Durable Object per signed-in user
  • Press / to search threads, or filter the list to unread
  • Attachments are listed on the message and stored in R2
A list of threads with sender, subject, preview and mailbox tags beside the open conversation

Reading mail

Open untrusted mail without trusting it.

HTML mail renders in a locked-down frame. Scripts do not run, and tracking pixels do not load until you say so.

  • Remote images are blocked, with a banner and a Load images button
  • Switch any message between rich, plain text and source
  • A shield summarises the SPF, DKIM and DMARC results for the sender
An open message with an Authenticated badge showing the sender passed SPF, DKIM and DMARC

Daily work

The small things that keep an inbox clear.

Each of these exists in the app today.

Star

Pin the threads you need to come back to. Starred is its own view, with a count.

Archive

Clear a thread without deleting it. A new reply brings it back to the inbox.

Mark as unread

Opening a thread marks it read. Mark it unread when you want it to stay on your list.

Canned replies

Insert a saved response from the reply box. They are created through the API for now, because the dashboard has no editor for them yet.

Contact history

Each sender becomes a contact scoped to the mailbox, so you see what you sent them and what they sent back in one place.

Test mailbox

Mail sent with a test API key lands here instead of a real inbox. Use it in development, staging and CI.

Keyboard shortcuts

Work the queue without the mouse.

The keys below are the ones the app listens for. Press ? inside the inbox to see them again.

Navigate

  • Next threadJ↓
  • Previous threadK↑
  • Search threads/
  • Close threadEsc
  • Show shortcuts?

Act

  • ComposeC
  • ReplyR
  • ArchiveE
  • StarS
  • Mark as unreadU
  • Send reply⌘↵

Go to

  • Command palette⌘K
  • InboxGI
  • Test mailboxGT
  • Activity logsGL
  • PlaygroundGP
  • TeamGU

Single-key shortcuts pause while you type in a field or have a dialog open. On Windows and Linux, use Ctrl in place of ⌘.

Roles and access

Give people only the mailboxes they need.

Mailbox membership is checked on the server for every thread, contact and reply, not just hidden in the interface.

Administrators

See every mailbox. Create mailboxes, assign people, manage domains, API keys and the rest of the workspace.

Members

See only the mailboxes they are assigned to, and can send only from those addresses. Everyone else's mail stays out of view.

Access types

Each member gets any of inbox for support, api for developers and tester for the test mailbox.

FAQ

Inbox questions.

Also sending mail from your app?Read about the email API

Give your support address a shared home.

Deploy EmailFlare, add a mailbox and send a test message to it. It takes a few minutes, and the mail stays in your account.