HEY Email Review (2026): Opinionated by Design

This HEY email review is written for a reader who has done the tour, likes the philosophy, and is trying to decide whether to actually move a mailbox. HEY is 37signals' bet that email should stop being a to-do list your correspondents write for you. The app enforces that bet through the UI — a Screener that asks whether each new sender may reach you, an Imbox that holds only real conversations, a Paper Trail for receipts, a Feed for newsletters, and no folders anywhere.

If those opinions match yours, HEY is a relief. If they do not, HEY is a fight — and it is not a fight you win by working around the app, because the app was designed to close those workarounds off. This piece walks the mechanics against HEY's own live product page as of August 2026 (pricing and packaging change; verify the current numbers at hey.com/pricing), and it says which reader should read something else instead.

The short answer#

HEY is a hosted email service that ships with strong opinions and enforces them through the interface. There is no folder tree to build. Instead there are named surfaces — Imbox, Feed, Paper Trail, Reply Later, Set Aside — and the app decides which one a message lives in, with a one-time yes/no on new senders in The Screener.

Search works. Classical rules and per-account filters do not, and that is deliberate. HEY suits owners of a single, quiet mailbox who want to spend less time steering it. It does not suit teams who need shared inboxes or delegation, users who need IMAP export or their own filter DSL, or anyone whose workflow depends on labelling one thread into three places at once. There is no permanent free tier — HEY runs on annual (or monthly, for the Domains tier) subscription after a 30-day no-credit-card trial.

Criteria that actually matter#

Most HEY reviews score it against a checklist that was written for a Gmail-shaped world — folders, filters, delegation, IMAP, per-message rules. HEY loses that checklist by design, and the score tells you nothing you did not already know from the marketing page. The criteria below are the ones on which HEY actually stands or falls in a real week of use.

• Screener signal quality — does the one-time yes/no on new senders reduce noise the way the marketing implies, or does it turn every legitimate first email from a client into a hunt through a secondary screen? This is the whole premise; if it is not right in week one, the rest does not save it.
• Surface routing accuracy — does the app put receipts in Paper Trail, newsletters in The Feed, and real replies in the Imbox without you correcting it? Misrouting a client thread into The Feed is the failure mode that ends the trial.
• Address portability — can you use your own domain, and what happens to inbound mail if you leave? HEY for Domains exists; there is still no IMAP, so an export is a mailbox dump rather than a live migration.
• Fit for business threads — how HEY behaves when a real thread has ten replies, three attachments, and a colleague who needs to see it. There is no shared inbox or delegation in the personal product; HEY for Domains is per-user, not a team console.
• Search and retrieval — HEY's search is genuinely fast on a full-text index, but it is the only way to find old mail because there are no folders to browse. If you think in folders, this is friction the app will not remove.
• AI features — as of August 2026, HEY does not ship an on-device drafting agent, an approval-before-send AI, or an autonomous triage layer. It ships human-designed surfaces that do the sorting. Read that as a feature or a gap depending on what you came for.
• Escape hatch — no IMAP, no POP, no third-party client, no bring-your-own-provider. Export exists, but the value that HEY adds (Screener state, Feed classification, Set Aside) does not travel with you if you leave.

Scoring table#

Below is HEY scored one to five on the seven criteria above, based on public product behaviour as of August 2026. A 5 is best-in-class; a 1 is a hard limitation the app will not fix. The 'what a 5 looks like' column tells you what HEY is being measured against, so you can decide whether the criterion matters to you at all.

A picture of what HEY optimises for#

HEY's design is a fork in the road: you either give the app authority over where mail lives, or you fight it every day. The illustration below is the mental model — one route where the user does the sorting with folders and filters, one where the app does it with named surfaces. HEY is emphatically the second route, and its 4-out-of-5 on routing accuracy is worth more than a 5 elsewhere because the whole product hinges on it landing.

A worked example — a week on HEY#

Take a solo consultant with a mailbox of about 120 messages a day: eight to twelve client threads, three or four vendor invoices, twenty newsletters they still read, and roughly ninety cold outreach messages they do not. On Monday morning the Screener queue has forty-one new senders. Thirty-eight are cold outreach and get one tap to reject; two are prospects the consultant has been expecting and get accepted into the Imbox; one is a vendor invoice that gets accepted straight into Paper Trail.

By Wednesday the Imbox contains only conversations the consultant chose to have. Newsletters are readable at leisure in The Feed. Reply Later has a stack of four threads to answer before Friday, and Set Aside holds two threads that need a document ready before they move. Nothing has been filed by hand; nothing needs a rule. Search finds the one thread from March in about a second.

The failure moment, when it comes, is a legitimate first email from a client's new project manager. It sits in the Screener for six hours before the consultant checks and admits it. That is the price HEY charges for the quiet Imbox, and it is the price the design refuses to negotiate. Whether that trade is worth six hours of latency on cold inbound is the whole decision.

Red flags — what HEY refuses to do#

The honest part of a review is the list of things HEY will not do, in the vendor's own words on their own live pages. None of these are secret; all of them break at least one common workflow.

• No third-party client access. HEY does not offer IMAP or POP for its own service, and it does not connect out to Gmail, Outlook or IMAP mailboxes you already own. It is the client and the mailbox at once, and it does not federate with either side of that.
• No folder tree, ever. If you rely on a nested folder structure for compliance or archival, the answer is not to negotiate with HEY — the answer is a different product. Search is the retrieval path.
• No rules or per-message filters in the classical sense. You can Reply Later, Set Aside, or move a sender's mail between the Feed, Imbox and Paper Trail, but you do not write conditional logic against subject lines or headers.
• No delegation, no shared inbox, no assignment. HEY for Domains is a per-seat product on a custom domain; it is not a team console. If two people need to see one thread and act on it, HEY is the wrong tool.
• Trackers blocked by default and cannot be re-enabled. Good if you are a recipient, meaningful if you also send from the same address and want open tracking on your own outbound.
• No autonomous AI agent, no approval-before-send drafting model, no audit log of an agent's actions — because there is no agent. HEY's answer to volume is the Screener and the surfaces, not automation on top of them.

What we'd pick and why (honest)#

Disclosure: we build AI Emaily. We are naming ourselves in the recommendation because a decision-guide that pretends the writer has no stake insults the reader, and because a page that never says who we are also earns no trust when it praises anybody else. Check the argument against a real trial rather than a claim.

HEY is the right choice for a specific reader. If you run a single mailbox, do not need a team to see your threads, are willing to commit to a @hey.com address (or pay for HEY for Domains), and actively want the app to enforce a way of working — HEY is genuinely a relief and there is nothing else quite like it. The Screener is the most disciplined answer to cold outreach any consumer email product ships, and the Imbox / Feed / Paper Trail split does route receipts and newsletters out of the way without you writing a rule. On the criteria HEY optimises for, HEY wins them.

HEY is the wrong choice for the workflow AI Emaily is built for. If you have a mixed set of accounts across Gmail, Microsoft 365 and IMAP under one identity; if you want an AI that drafts in your voice with an approval step before it sends, an autonomy toggle for the mail you would normally handle in three seconds, and an audit log a compliance reviewer can read; if you want your existing addresses to stay yours — HEY is not built for that shape and AI Emaily is. Packaging is a 7-day free trial on Pro/Autopilot (card required, no charge if cancelled before day seven), with pricing at aiemaily.com/pricing.

One concession by name: HEY's Screener is a better piece of design than any single feature we currently ship for first-time-sender control. Our cold-email filter operates on behaviour and domain rather than a per-sender allow list, and for high-volume mailboxes that is the right trade — but the psychological simplicity of one yes/no per new person is HEY's, and it is worth admitting.