Missive

Missive is an email client built for teams, and the specific insight behind it is that the hard part of shared email is not routing or reporting but conversation. When three colleagues are responsible for one mailbox, the question that arises constantly is not which of us will answer but what should we say. The conventional answer is a separate chat tool: someone pastes the email into Slack, the discussion happens there, a decision is reached, and someone goes back to the mail client and writes the reply. That works, and it also fractures context, because the discussion and the message live in different systems, and six weeks later nobody can find why a particular answer was given. Missive puts the discussion inside the thread.

Chat attached to an email conversation is the signature feature. Any thread has an internal conversation channel where colleagues can message each other about it, and that channel is visible only to the team. You can ask a question about a customer's request, propose wording for a difficult reply, flag that an account is at risk, or hand a thread over with context, all without leaving the email and without the customer seeing any of it. The internal chat and the external reply are adjacent, so writing the response happens while the discussion is on screen. This is a genuinely better design than pasting into Slack for any team whose work involves deliberating over messages, and it is the reason people choose Missive over a conventional shared inbox.

Shared inboxes sit alongside personal mailboxes in the same interface. A team connects addresses such as support, sales, billing, careers or press, and everyone with access sees the same queue with the same history. Assignment marks who owns a conversation, labels organise threads, and collision detection shows when a colleague is already writing a reply, which prevents the classic failure of two people answering the same message. Statuses track whether a thread is open, pending or closed. Snoozing defers a conversation to a time or until the customer replies. These are the mechanics that turn a mailbox into a work queue, and Missive implements them without abandoning the feel of an email client.

Tasks extend the model beyond email. Any conversation can generate a task with an assignee and a due date, and tasks can exist independently as a lightweight to-do list for the team. Because a task carries its originating conversation, follow-up work retains context rather than becoming a bare line item. This covers a meaningful share of what a small team would otherwise buy a project management tool for, and it is one of the ways Missive consolidates spend.

Channels go beyond email. SMS and MMS, WhatsApp, Messenger, Instagram and live chat via a website widget can be connected, so conversations from those channels arrive in the same interface with the same assignment, chat and task behaviour. For a small business whose customers message on WhatsApp rather than email, this is more valuable than another email feature, and it means one tool covers the whole customer communication surface rather than three.

Native applications are a differentiator that is easy to underrate. Missive has real desktop clients for macOS and Windows and mobile applications for iOS and Android, rather than only a web application in a browser tab. Desktop clients deliver proper notification handling, keyboard shortcuts, offline access and multiple windows, and mobile applications allow a small team to stay responsive without a laptop open. Performance and keyboard-driven interaction are priorities in the design, and the result is an application that feels fast, which matters in a tool people inhabit for hours.

Mailbox connection is standard and non-proprietary: Gmail, Google Workspace, Microsoft 365, Outlook and any IMAP account can be connected, and email stays in the original mailbox rather than being migrated into a proprietary store. This reduces the risk of adoption considerably, because a team can trial Missive without moving anything, and can leave without losing data. Sending uses the connected account, so messages arrive from the real address with proper authentication rather than through a third-party relay that can harm deliverability.

Automation and integration are pragmatic rather than deep. Rules can assign, label, route and notify based on conditions, templates and canned responses handle repeated messages with personalisation tokens, and a public API plus webhooks allow custom integration. There is a directory of integrations, and Zapier covers the long tail. The automation capability is adequate for a small team and is not an attempt to compete with a rules engine like Front's or a workflow platform; a business needing sophisticated routing across many teams and channels should evaluate that specifically.

Against competitors, Front is the closest and most direct rival, and the comparison is instructive. Front offers broader channel coverage, a deeper and more powerful rules engine, service level agreements with escalation, more mature analytics and reporting, a larger integration marketplace and artificial intelligence features for drafting and summarisation, at a higher per-seat price. Missive offers the internal chat in threads, native desktop and mobile clients, a faster and calmer interface, tasks, and a lower per-seat cost, with less automation depth and weaker governance. For a team of two to twenty that deliberates over messages and values speed and simplicity, Missive is usually the better fit; for a larger support operation that needs service levels, complex routing and detailed reporting, Front is stronger. Help Scout is an email-first shared inbox with a knowledge base and a well-regarded product, simpler and cheaper, without internal chat in threads and without the channel breadth. Hiver turns Gmail itself into a shared inbox with assignment, statuses and service level agreements for teams that refuse to leave the Gmail interface. Crisp, Tidio and tawk.to are chat-first platforms that add email and knowledge base rather than email-first platforms that add chat. Zendesk, Freshdesk and Intercom are ticketing and conversational support platforms, stronger on self-service, governance and artificial intelligence, and they impose a ticket abstraction that collaborative email does not suit. Superhuman is a fast individual email client with some shared features, aimed at personal productivity. Slack and Microsoft Teams are internal chat that many teams use for email discussion badly. Missive's position is the best collaborative email client for small and mid-sized teams, distinguished by chat-in-thread and native applications.

Pricing is freemium with per-user tiers. A free plan supports a small number of users with core shared inbox, chat and task functionality, which is genuinely usable for a very small team rather than being a token trial, and it is one of the more generous free tiers in the category. Paid plans are billed per user per month or per year at a discounted annual rate, and tiers add longer email retention and archive periods, larger attachment limits, more channels including SMS and WhatsApp, more automation and rules, additional integrations, administrative controls, single sign-on at higher levels, analytics and priority support. Because pricing is per user, cost scales with team size, which is predictable but means a company that wants many people to have read visibility pays for them. Retention period is a notable tier boundary: the free plan keeps a shorter history, and any team treating the inbox as a record needs a paid tier. Current figures are published on the vendor pricing page.

The limitations should be stated honestly. Automation and routing are shallower than Front's, so a complex multi-team distribution model with escalation is harder to express. Service level agreement management, breach escalation and operational reporting are weaker, which matters for a support organisation with contractual response commitments. There is no ticketing abstraction, so a workflow that requires strict lifecycle states, priorities and ownership handoffs across departments is not what Missive is built for. Analytics are basic compared with a dedicated support platform. Artificial intelligence drafting and summarisation are less developed than at the leaders. The knowledge base and self-service capability is limited, so ticket deflection requires another tool. Enterprise governance, audit logging and compliance certifications are less mature than at larger vendors. And a small independent vendor carries continuity risk relative to a category leader, though Missive has operated in this niche for many years.

Missive fits small and mid-sized teams working shared email addresses collaboratively, startups where everyone answers support and the discussion about how to answer matters, agencies and professional services firms managing client email with internal deliberation, e-commerce businesses handling customer questions across email, SMS and WhatsApp, recruiting teams coordinating on candidate correspondence, finance and operations teams working billing and vendor email, and any group for whom pasting emails into Slack has become the workflow. It does not fit large support organisations needing service levels, workforce management and deep reporting, companies requiring sophisticated rule-based routing across many departments, teams needing a knowledge base and self-service deflection, enterprises with governance and audit requirements, or organisations whose primary channel is live chat or social messaging rather than email.

In the closing comparison, choose Missive when internal discussion about customer messages is part of how your team works and you want a fast native client with shared inboxes, chat in threads and tasks at an affordable per-user price. Choose Front when you need rigorous routing, service level agreements, deep analytics and broad channel coverage and can fund a higher per-seat cost. Choose Help Scout when email-first support with a knowledge base and a simple humane product is the requirement. Choose Hiver when your team will not leave Gmail and needs shared inbox discipline inside it. Choose Zendesk, Freshdesk or Intercom when ticketing, self-service and artificial intelligence are the priorities. Choose Crisp when chat and bots matter more than email. The honest test for Missive is whether your team actually deliberates over messages; if it does, chat-in-thread removes a real friction that no other tool in this category handles as naturally, and if it does not, a cheaper shared inbox or a ticketing system may serve better.