# InboxPilot: Full content
> The complete text of InboxPilot's blog and legal documents for LLM ingestion. See https://inboxpilot.co/llms.txt for a structured index of all pages.
# Blog
---
## Shared Mailbox Auto-Reply: Why Canned Responses Fail
Source: https://www.inboxpilot.co/blog/shared-mailbox-auto-reply
Published: 2026-07-30
Gmail replies once per sender per four days, and Microsoft 365 shared mailbox replies are text only. Here is what auto-replies solve and what they do not.
Every shared inbox reaches the same moment. Volume climbs, replies slip, and somebody suggests turning on an auto-reply so at least people know the message arrived. It is a reasonable instinct, and it buys you a little goodwill. It also quietly convinces the team that the problem is handled, when all that changed is that customers now receive two messages instead of one.
Auto-replies are worth setting up. They are just worth setting up with clear eyes about what they do, because the mechanics have specific limits that vendors document and most teams discover the hard way.
**Disclosure:** we make [InboxPilot](/), an AI email agent that drafts replies inside Gmail and Outlook. This guide is about the native tools first, including the cases where they are genuinely the right answer and no software purchase is needed. Our product shows up near the end, in the one situation it fits.
## TL;DR
- [What a shared mailbox auto-reply actually does](#what-a-shared-mailbox-auto-reply-actually-does): confirms receipt, sets a timeframe, nothing else.
- [How to set one up in Microsoft 365](#how-to-set-one-up-in-microsoft-365): admin center, Teams & groups, Shared mailboxes, Edit under Automatic replies. Text only, no images.
- [Why Gmail behaves differently](#why-gmail-behaves-differently): the vacation responder is per person, runs in whole days, and replies once per sender per four days.
- [The four failure modes](#the-four-failure-modes): silence after the acknowledgment, whole-day scheduling, the four-day gap, and invisible sent replies.
- [When a canned reply is the right call](#when-a-canned-reply-is-the-right-call): closures, holidays, genuinely unstaffed hours.
- [What actually replaces the canned reply](#what-actually-replaces-the-canned-reply): answering the question, not acknowledging it.
## What a shared mailbox auto-reply actually does
A shared mailbox auto-reply performs exactly one job: it tells the sender their message arrived and roughly when a human will get to it. That is real value. A customer who knows they will hear back by Tuesday does not send three follow-ups on Monday, and the follow-ups are usually what tips a busy inbox from behind into unmanageable.
What it does not do is reduce the work. The question still needs answering, by a person, from the same queue. If your inbox receives forty quote requests a week, an auto-reply turns forty unanswered emails into forty acknowledged unanswered emails.
That distinction matters most for the requests that repeat. A shared inbox at a supplier, a property manager, or a clinic tends to receive the same handful of questions in rotation: what does this cost, where is my order, what do you need from me, when can you come out. Those have knowable answers. Acknowledging them is not the same as answering them.
## How to set one up in Microsoft 365
Microsoft documents the admin path clearly. In the Microsoft 365 admin center, go to **Teams & groups**, then **Shared mailboxes**, select the mailbox, and select **Edit** under **Automatic replies**. You can then write separate messages for senders inside and outside your organization.
One constraint is worth knowing before you write the copy. Microsoft states plainly: "You can't add images, only text." If your brand guidelines assume a logo and a signature block, the shared mailbox auto-reply is not where that lives.
Two related settings surprise teams often enough to be worth checking at the same time.
The first is sent items. Microsoft documents that "by default, messages sent from the shared mailbox aren't saved to the Sent Items folder of the shared mailbox. Instead, they are saved to the Sent Items folder of the person who sent the message." That is the single most common cause of a team believing a customer was never answered when they were. You can change it in the admin center under the **Sent items** setting.
The second is licensing. Shared mailboxes "usually don't require a license," per Microsoft, but an Exchange Online Plan 2 license becomes necessary in three cases: the mailbox uses more than 50 GB of storage, it uses in-place archiving, or it is placed on litigation hold. Worth knowing before a mailbox that has run for six years quietly crosses a threshold.
## Why Gmail behaves differently
Google's equivalent is the vacation responder, and it is built around a different assumption: that a person is away, not that a queue is busy. Three documented behaviors follow from that, and all three matter for a shared address.
It runs in whole days. Google states that "your automatic reply starts at 12:00 AM on the start date and ends at 11:59 PM on the end date, unless you end it earlier." There is no native way to say "outside 9 to 5." An after-hours auto-reply on Gmail is a scheduling workaround, not a setting.
It does not reply every time. Google documents that "in most cases, your reply is only sent to people the first time they message you," and that it replies again if the same person contacts you after four days while the responder is still on. So a customer who emails on Monday and chases on Wednesday gets silence on the chase. From their side, the acknowledgment made a promise the second message did not honor.
It skips some mail entirely. Per Google, "emails sent to your spam folder or addressed to a mailing list you subscribe to don't get your reply."
Teams running a shared address through Google Groups sometimes expect Collaborative Inbox to cover the gap. It does not. Google documents it as a triage layer: assign a conversation to a member, mark it complete, needing no further action, or a duplicate, and organize with labels. Those are genuinely useful for ownership, which is the other half of the shared inbox problem. But there is no documented auto-reply or canned-response feature in Collaborative Inbox. Ownership and volume are separate problems, and Groups solves the first one.
## The four failure modes
Put the documented behavior together and the same four failures show up across almost every team.
**Silence after the acknowledgment.** The auto-reply promises a reply within one business day. The queue is three days deep. You have now converted a slow response into a broken promise, which is worse, because the customer has a timestamp.
**Whole-day scheduling.** The pattern most teams actually want is evenings and weekends. Gmail cannot express that natively, so people either leave the responder on permanently, which annoys regular correspondents, or toggle it manually and forget.
**The four-day gap.** Chasers get nothing. The customers most likely to chase are the ones already waiting longest, so the mechanic works against precisely the people you most need to reassure.
**Invisible sent replies.** With default Microsoft settings, replies live in the individual sender's Sent Items. Two colleagues answer the same email because neither can see the other's reply in the shared mailbox.
## When a canned reply is the right call
There is a real category where a canned reply is correct and sufficient, and it is worth being honest about it rather than selling past it.
If the inbox is genuinely unstaffed, a canned reply is the honest answer. Office closed for the holidays, a planned shutdown, a team offsite, a role that has moved to a different address. In all of those cases the message is not a placeholder for an answer, it *is* the answer: nobody is here, here is when we are back, here is who to contact if it cannot wait.
Same for a genuinely low-volume inbox. If your shared address receives five emails a week, an auto-reply plus a person checking it twice a day is a complete solution. Do not buy software for that.
The category where it stops working is the one in the middle: a staffed inbox, real volume, and questions that repeat. There the auto-reply is a bandage on a throughput problem.
## What actually replaces the canned reply
The alternative is not a better acknowledgment. It is answering the question in the first message.
Here is a request a supplier shared inbox receives constantly:
> **Subject:** Availability and pricing
>
> Hi, do you have the 40mm valve assemblies in stock, and what is the price for 250 units? We need delivery to Leeds before the 14th if possible.
A canned auto-reply says:
> Thanks for contacting us. A member of our team will respond within one business day.
Technically true, adds nothing. The customer already knew they had emailed you. Now compare a reply drafted against your actual price list and stock data:
> Hi Priya,
>
> Yes, the 40mm valve assemblies are in stock. For 250 units the price is £14.20 each, which is our 250-plus band, so £3,550 before VAT.
>
> Delivery to Leeds is 3 working days from order, so ordering by the 9th comfortably makes the 14th.
>
> Want me to raise a proforma invoice?
That reply took a person thirty seconds to check and send, because the drafting, the price band, and the lead-time arithmetic were already done. That is the actual saving. Not the acknowledgment, the answer.
This is the narrow case where a tool like [InboxPilot](/pricing) earns its place. It reads incoming mail in the Gmail or Outlook inbox the team already uses, drafts a reply grounded in your own documents and price lists, and waits for a person to approve the send. There is no migration and no new interface, which matters because the shared inbox is usually working fine as a place to collaborate. The bottleneck is typing the same answer repeatedly, and that is the part worth automating.
Two honest caveats. A draft is only as good as the documents behind it, so if your pricing lives in someone's head rather than a file, fix that first or the drafts will be confidently wrong. And approval genuinely matters early on: our default is that a person approves every send, and for anything involving a number you should keep it that way well past the point where it feels necessary.
If the answers change every time and no two emails in your inbox rhyme, none of this applies. Keep the auto-reply, staff the queue, and spend the budget somewhere it does more good.
## Related reading
- [RFQ and quote request automation](/use-cases/rfq-email-automation): how quote requests get read, priced, and answered from your own catalog.
- [Best shared inbox software](/blog/best-shared-inbox-software): the tools teams actually shortlist, and where each stops being enough.
- [Best shared inbox for Outlook](/blog/best-shared-inbox-for-outlook): shared mailbox alternatives for Microsoft 365 teams.
- [How to set up an automated response in Gmail](/blog/how-to-setup-an-automated-response-on-your-gmail-account): the vacation responder and the filter-plus-template method, step by step.
- [What an AI email agent does](/blog/ai-email-agent): the category explainer, including what it is not.
*Microsoft 365 shared mailbox behavior is quoted from Microsoft Learn, "Configure shared mailbox settings" and "Create a shared mailbox," both current as of their July 2026 revisions. Gmail vacation responder behavior is quoted from Google's Gmail Help article "Send automatic replies in Gmail." Google Groups Collaborative Inbox behavior is from Google Workspace Learning Center. Vendor documentation changes; check the current pages before relying on any specific limit. Pricing examples in the worked reply are illustrative, not quotes from a real customer. InboxPilot is the publisher of this article and competes with tools referenced elsewhere on this blog.*
---
## AI Email Agent for RFQs, Support, and Sales Email
Source: https://www.inboxpilot.co/blog/ai-email-agent
Published: 2026-07-27
Microsoft 365 telemetry: 117 emails a day per user. How an AI email agent handles RFQs, support, and sales email, with a person approving each send.
Look at the inbox your business actually runs on. Not your personal one, the shared one: sales@, info@, hello@, the address on the website footer. In the last hundred messages there's a request for a quote, a customer asking where their order is, someone asking whether you handle their region, an invoice, three newsletters, and a person who wants to buy something today.
Those first three need different answers from different parts of the business. They arrive in the same place, in the same format, at the same time, and one person has to sort them.
**Disclosure:** we make [InboxPilot](/), an AI email agent that drafts replies inside Gmail and Outlook. This post covers what an AI email agent can genuinely take over across quotes, support, and sales, with sourced numbers. It also says plainly where the agent should stop, which is before the send button.
## TL;DR
- In 2025, Microsoft's telemetry put the average Microsoft 365 worker at **117 emails received per day**, with most skimmed in under a minute. See [what an AI email agent actually is](#what-an-ai-email-agent-actually-is).
- One shared inbox runs [three different jobs](#why-one-inbox-ends-up-doing-three-jobs): quote requests, support questions, and inbound sales. Each needs a different playbook from the same agent.
- **Quote requests mostly do not arrive through portals.** Loopio's 2026 benchmark of 1,500+ response teams found only 45% of bids come through portals, down from 51% a year earlier.
- The strongest argument for [keeping a human on the send button](#where-the-agent-should-stop) is commercial, not philosophical. In Five9's 2026 research, trust in AI service roughly doubled when customers could see a clear route to a person.
- **[InboxPilot](#setting-one-up-without-breaking-anything), which is us,** is one of these agents: it works inside Gmail and Outlook, drafts from your own docs, and [keeps a human on the send button](#where-the-agent-should-stop) by default.
## What an AI email agent actually is
An AI email agent is software that reads incoming mail, classifies what each message wants, drafts a reply grounded in your own documents, and routes anything it should not answer to a human. In 2025, Microsoft's *Breaking down the infinite workday* report measured the average Microsoft 365 worker receiving 117 emails a day and skimming most of them in under 60 seconds ([Microsoft WorkLab](https://www.microsoft.com/en-us/worklab/work-trend-index/breaking-down-infinite-workday), 2025).
That report is worth sitting with. The same telemetry found workers interrupted every two minutes by a meeting, message, or notification, and found that 40% of the people already online at 6am are triaging email before the day starts. The inbox isn't one task among many. It's the surface everything else arrives through.
So why hasn't ordinary automation solved this already? Because filters and templates act on what a message looks like, not what it asks for.
Three words do the work in that definition, and they're what separate an agent from the automation you already tried:
- **Classifies.** It decides what a message *is* before deciding what to do with it. Keyword filters can't tell a quote request from a complaint that mentions price.
- **Grounded.** It writes from your rate sheet, your policies, your past replies. Not from what a general model believes about your industry.
- **Routes.** It knows which messages it shouldn't touch, and it hands those over cleanly instead of guessing.
Take any of those away and you have a template macro with a language model bolted on.
## Why one inbox ends up doing three jobs
Small and mid-size teams rarely have separate addresses for separate functions, so one queue absorbs work that larger companies split across three departments. In 2025, Zendesk's CX Trends 2026 research, built on responses from over 11,000 people across 22 countries, found 88% of customers now expect faster replies than a year ago and 74% expect availability around the clock ([Zendesk CX Trends 2026](https://cxtrends.zendesk.com/), 2025).
Here's what the three piles look like, and why they need different handling:
| Pile | What it looks like | What it needs | Cost of a slow reply |
|---|---|---|---|
| **Quote requests (RFQs)** | "Can you price this? Specs attached." | Requirements pulled out, missing info requested, estimator briefed | You're not on the shortlist |
| **Support questions** | "Where's my order?" "How do I cancel?" | An accurate answer from current policy, fast | Churn, and a public review |
| **Inbound sales** | "Do you work with companies our size?" | Speed above all, then qualification | The lead buys from whoever replied first |
They fail differently, too. A slow support reply annoys someone who already paid you. A slow sales reply loses someone who hasn't. A wrong quote is a contract problem. That's why one generic "reply to everything" setting doesn't work, and why the classification step matters more than the writing step. For most teams, the pile costing the most is the one nobody has measured.
## How an AI email agent handles a quote request
Quote requests are the highest-value thing in most shared inboxes and the slowest to move, because a human has to read an attachment before anyone can act. In 2026, Loopio's seventh annual benchmark, built with the Association of Proposal Management Professionals from 1,500+ teams and 250,000+ RFPs, found only 45% of bids are submitted through portals, down from 51% the year before ([Loopio](https://loopio.com/blog/rfp-statistics-win-rates/), 2026). The rest arrive some other way, mostly email.
So the agent's job on a quote request isn't to write the quote. It's to compress the gap between arrival and the estimator having what they need:
1. **Classify** the message as a quote request and label it, so it stops competing with newsletters for attention.
2. **Extract the requirements**: scope, quantity, location, deadline, and specifically what's missing.
3. **Draft the acknowledgement** that confirms fit, states a realistic turnaround, and asks for the drawing nobody attached.
4. **Escalate the pricing** to a person, always.
That last step isn't a limitation, it's the design. Loopio's 2026 data puts the current average win rate at 39%, with a 45% win rate as the 2019 to 2026 average. Nothing about an AI agent improves the number you quote. What it improves is whether you're still in the running when the buyer makes a shortlist.
> **Incoming, 7:12am:** "We need pricing on 400 units of the anodized bracket, delivered to Reno by mid-September. Drawing attached. Who should I send the PO to?"
> **Draft, 7:12am:** "Hi Dana, thanks for sending this over. 400 units at that spec is well within our range, and mid-September looks workable subject to a schedule check. The drawing came through, but I don't see a finish callout or a tolerance on the mounting holes. Send those and I'll have firm pricing to you within two business days. I'm copying Marcus, who'll own the quote, confirm the September slot against our schedule, and take the PO."
Notice what the draft withholds. No price. No promised unit cost, and no commitment the shop floor hasn't confirmed. Every factual claim in it traces either to a document or to a named human who will verify it, and a person reads the whole thing before it goes. If your quotes are formal 200-question proposal documents rather than emails, that's a [different category of tool](/blog/best-rfq-email-management-software) and worth knowing the difference.
## How an AI email agent handles a support question
Support is where grounding stops being a technical detail and starts being the entire product. In 2025, Zendesk's CX Trends 2026 research found 85% of CX leaders believe customers will leave over an issue that isn't resolved on first contact, and 86% of consumers said responsiveness and accurate resolution strongly influence what they buy ([Zendesk](https://cxtrends.zendesk.com/), 2025).
Accurate is the operative word. An AI agent that invents a 30-day return window when yours is 14 hasn't saved you time, it's created a dispute you'll honor anyway. This is why [knowledge base grounding](/product/knowledge-base) matters more than model quality for support email: the agent should write only from your help center, your macros, and your past replies, cite what it used, and escalate when the answer isn't there.
Adoption has already happened around you. In 2026, Five9's research with Hanover Research, covering 3,000 consumers and 600 CX decision-makers across the US, UK, and Germany, found 92% of organizations had implemented or piloted AI in customer service ([Five9](https://www.five9.com/news/news-releases/new-five9-research-ai-adoption-cx-hits-92-consumer-trust-still-depends-human), 2026). Implemented or piloted is a loose bar, though, and the gap between the two shows up further down this page.
What actually gets automated is not the hard tickets. It usually works by narrowing scope, which makes the support loop shorter than the quote loop:
1. **Classify and check** the question against your help center and past replies.
2. **Draft with the source attached**, so the approver can see which doc the answer came from without opening anything.
3. **Escalate on absence.** No matching source means no draft, and the thread goes to a person clean.
Teams running a [shared support inbox](/solutions/support-teams) see the time back on password resets, order status, hours, policy, and eligibility. The refund dispute still goes to a person, and should.
## How an AI email agent handles a sales email
For inbound sales, speed is close to the entire mechanism, and the canonical evidence is old enough that it deserves a date. In March 2011, Harvard Business Review published an audit of 2,241 US companies which found the average first response to a web lead took 42 hours, and 23% of companies never replied at all ([Harvard Business Review](https://hbr.org/2011/03/the-short-life-of-online-sales-leads), 2011).
A companion study in the same article, covering 1.25 million leads across 42 companies, found firms that responded within an hour were nearly seven times more likely to have a meaningful conversation with a decision maker than those that waited even an hour longer, and more than 60 times more likely than those that waited 24 hours.
One clarification, because these numbers get tangled constantly. You'll also see "100x" and "21x" attached to lead response time. Those come from a different piece of research: the 2007 MIT and InsideSales.com Lead Response Management study, which measured phone calls placed at 5 minutes versus 30 minutes ([Lead Response Management](https://www.leadresponsemanagement.org/lrm_study/), 2007). James Oldroyd led both that study and the HBR analysis, which is why the two get merged. They measure different channels at different intervals. If you're citing the hour-one figures, seven and sixty are the right numbers.
Fifteen years on, buyer patience has tightened rather than relaxed: in Zendesk's 2026 CX Trends research, 88% of customers said they expect faster replies than they did a year ago ([Zendesk](https://cxtrends.zendesk.com/), 2025). So the agent's job on a sales email is deliberately small:
1. **Acknowledge within minutes**, by name, referencing what they actually asked about.
2. **Ask the two questions** that decide whether this is a fit, and no more than two.
3. **Put a human in the thread** by name, before the lead has time to shop elsewhere.
> **Incoming, 4:48pm Friday:** "We're a 40-person insurance brokerage looking at AI for our shared inbox. Do you work with companies our size, and roughly what would this cost us?"
> **Draft, 4:51pm Friday:** "Hi Priya, yes, 40-person teams are squarely who we build for, and brokerages in particular run the kind of repetitive policy and claims-status email this handles well. Two quick things so I can give you a real number rather than a range: how many shared inboxes would you connect, and roughly how many customer emails land in them in a week? Sam on our team handles brokerage accounts and I've copied him here. Pricing starts at $29 per month and our Standard plan is $149."
What the draft doesn't do is qualify hard, pitch, or promise a discount. It buys the thing that matters on a Friday afternoon, which is being the reply that arrived before the weekend. For teams working [inbound leads out of a shared inbox](/solutions/sales-teams), that's most of the available upside, and it's the same problem covered in our post on [instant lead replies](/blog/sales-team-instant-lead-replies).
## Where the agent should stop
Every AI email agent needs a hard boundary, and the best case for one is commercial rather than philosophical. In 2026, Five9's research found 80% of consumers were willing to use AI-powered customer service when they knew a route to a live representative existed. Trust roughly doubled with that route visible, at 55% versus about a quarter without it, and 41% said they were less likely to use a company that uses AI for service at all, rising to 53% when no human option existed ([Five9](https://www.five9.com/news/news-releases/new-five9-research-ai-adoption-cx-hits-92-consumer-trust-still-depends-human), 2026; trust split reported by [CX Dive](https://www.customerexperiencedive.com/news/clear-path-to-live-agent-boosts-trust-ai-customer-service/825835/), 2026).
Practitioners have reached the same conclusion about their own work. In 2026, Microsoft's Work Trend Index, surveying 20,000 knowledge workers across 10 markets, found 86% of AI users treat AI output as a starting point rather than a final answer, and half named quality control of AI output as a top critical human skill ([Microsoft WorkLab](https://www.microsoft.com/en-us/worklab/work-trend-index/agents-human-agency-and-the-opportunity-for-every-organization), 2026).
There's also case law now. In February 2024, British Columbia's Civil Resolution Tribunal decided *Moffatt v. Air Canada* (2024 BCCRT 149), holding the airline liable for negligent misrepresentation after its website chatbot gave a customer wrong information about bereavement fares. The tribunal rejected the argument that the chatbot was a separate entity responsible for its own answers, reasoning that it should be obvious a company is responsible for all the information on its website, whether it comes from a static page or a chatbot ([McCarthy Tétrault](https://www.mccarthy.ca/en/insights/blogs/techlex/moffatt-v-air-canada-misrepresentation-ai-chatbot), 2024).
That was a real-time chatbot with no human review, not an email agent, so don't read it as a precedent about email. Read it as a clean statement of who owns the output: you do. Which points at a simple operating rule.
**Draft, don't send.** The agent writes, a person approves. On InboxPilot the AI draft is the unit every plan is metered by, and sending stays a human act. Two more guardrails are worth setting on day one:
- **Negative keywords.** Anything mentioning a refund dispute, legal threat, cancellation, complaint, or data request skips drafting entirely and goes to a person with no draft attached, so nobody can approve it on autopilot.
- **Escalate on absence.** When the answer isn't in your documents, the correct output is a handoff, not a confident guess. That behavior is a configuration choice, and it's the one worth checking before you buy anything.
In March 2025, Gartner predicted that by 2029, agentic AI will autonomously resolve 80% of common customer service issues without human intervention, cutting operational costs by 30% ([Gartner](https://www.gartner.com/en/newsroom/press-releases/2025-03-05-gartner-predicts-agentic-ai-will-autonomously-resolve-80-percent-of-common-customer-service-issues-without-human-intervention-by-20290), 2025). That's a forecast about 2029, about *common* issues, made by an analyst firm. It's a reasonable direction of travel. It isn't a description of 2026, and anyone selling it to you as one is selling.
## What to look for when you compare tools
Buying is where most of this goes wrong, because every tool demos well. In 2026, Intercom's survey of 2,400+ customer service professionals found 87% of senior leaders planned to invest in AI for customer service that year, while only 10% described their existing deployment as mature ([Intercom](https://www.intercom.com/blog/customer-service-transformation-report-2026/), 2026). Plenty of buying, not much working.
Drafting a plausible email is the easy part, and it's the part every demo shows you. These are the questions that separate the tools:
| Question | Why it matters | Good answer |
|---|---|---|
| Where do drafts get their facts? | Ungrounded models invent policies | Your docs, macros, and past replies, with sources cited |
| Does it send on its own by default? | This is a liability decision | Draft-and-approve is the default, autosend is opt-in |
| Where does it live? | Migration is where rollouts die | Inside Gmail and Outlook, not a new platform |
| What happens when it doesn't know? | Silent guessing is the failure mode | Escalates to a human with no draft |
| How is it priced? | Per-seat pricing suppresses adoption | Priced on volume, so the whole team can use it |
| What happens to your email data? | Legal and procurement will ask | SOC 2 Type II, and your data never trains models |
That last row is worth pushing on with any vendor. Ours is documented on our [security page](/security), including scoped OAuth access and the commitment that customer data never trains AI models.
## Setting one up without breaking anything
Rollouts fail on sequence, not software. That 87-to-10 gap above is mostly an ordering problem: guardrails go in before automations, and one inbox goes in before five.
Three steps, in this order:
1. **Connect the inbox that actually receives the work.** sales@, info@, support@, whichever address carries the volume. Gmail or Outlook, shared mailboxes included. Start with one.
2. **Feed it your documents.** Price list, policies, service area, standard terms, and twenty past replies you'd be happy to send again. This is [the grounding step](/product/knowledge-base), and draft quality is capped by what you put here.
3. **Set the guardrails before you set the automations.** Negative keywords first, approval on, autosend off. Then add [triage and routing rules](/product/smart-triage) once you've watched real drafts for a week.
Then run it in draft-only mode for two weeks and read every draft before approving. Why two weeks? Because that's long enough to see the messages that only show up on a Monday, and short enough that you'll still remember what you were testing. You'll learn more about which of your three piles is genuinely automatable than any vendor demo can tell you, and you'll find the gaps in your own documentation while you're at it.
On InboxPilot, that runs on any plan. Free covers 25 AI drafts, which is enough to test on real traffic. Hobby is $29 per month for 200 drafts. Standard is $149 per month for 1,500 drafts, unlimited inboxes, and knowledge base grounding, which is the feature doing the work in step 2. Annual billing takes roughly 20% off. Details on the [pricing page](/pricing).
**[See how InboxPilot drafts replies across quotes, support, and sales →](/)**
## Related reading
- [Best RFQ software for suppliers](/blog/best-rfq-email-management-software): proposal platforms compared, and why email intake is a separate purchase.
- [Instant lead replies for sales teams](/blog/sales-team-instant-lead-replies): the speed-to-respond problem in detail.
- [Best shared inbox software for Gmail and Outlook](/blog/best-shared-inbox-software): where sales@ and support@ actually live.
- [AI email assistant buyer's guide](/blog/ai-email-assistant-buyers-guide-2026): vendor questions, red flags, and how the tools compare.
- [Operations teams](/solutions/operations): the same three piles, framed for whoever owns the inbox.
- [RFQ and quote request automation](/use-cases/rfq-email-automation): how quote requests get read, priced, and answered from your own catalog.
---
*On sources. Microsoft's 117-emails-per-day figure comes from Microsoft 365 product telemetry, so it describes Microsoft 365 users rather than all workers, and excludes EU tenants. The Zendesk, Loopio, Five9, and Intercom figures all come from vendor-run research by companies selling into these conclusions, two of them through independent firms (Five9 via Hanover Research, Loopio in partnership with the APMP). Read them as directionally useful rather than neutral. Only the Harvard Business Review audit and the BCCRT decision are independent of the vendors involved. InboxPilot pricing was verified against the pricing page in July 2026. InboxPilot is the publisher of this article.*
---
## Best Intercom Alternatives in 2026: 9 Tools Compared
Source: https://www.inboxpilot.co/blog/intercom-alternatives
Published: 2026-07-27
Salesforce is buying Fin, formerly Intercom. Nine alternatives compared on the thing that actually decides your bill: how each one meters AI.
There is a specific reason "Intercom alternatives" is being searched more than usual this quarter, and it is not the pricing. It is that the company was acquired.
If you are running that evaluation now, most of the roundups you will find compare the same nine tools on the same seat prices. That comparison is close to useless in 2026, because the seat price is no longer where the bill comes from.
**Disclosure:** we make [InboxPilot](/solutions/support-teams), an AI email agent that drafts replies inside Gmail and Outlook with a person approving each send. We are one of the options below, and we are not the right one for most of the situations on this page. Every price here was read from the vendor's own pricing page on 27 July 2026 and is dated as such.
## TL;DR
- **Salesforce is acquiring Fin, formerly Intercom, for roughly $3.6 billion.** Signed 15 June 2026, not yet closed. See [what actually happened](#first-what-actually-happened-to-intercom).
- **The Intercom brand did not disappear**, despite what a lot of coverage implies. intercom.com still sells the helpdesk under that name.
- **Compare the metering, not the seat price.** Six of these nine tools bill AI separately, and they use three different units to do it. See [the split that decides your bill](#the-split-that-actually-decides-your-bill).
- Fin bills **$0.99 per outcome**, and defines a resolution as the customer not asking for more help. A frustrated customer who gives up bills the same as a happy one.
- [Nine alternatives compared](#the-nine-alternatives), with **InboxPilot**, which is us, as the pick for email-first teams, and an honest note on where each one beats us.
## First, what actually happened to Intercom
In May 2026 the company renamed itself **Fin**, after its AI agent, and moved that product to its own site at fin.ai. On **15 June 2026, Salesforce signed a definitive agreement to acquire Fin for approximately $3.6 billion**, subject to customary purchase price adjustments ([Salesforce Investor Relations](https://investor.salesforce.com/news/news-details/2026/Salesforce-Signs-Definitive-Agreement-to-Acquire-Fin/default.aspx), 2026). Salesforce cited more than 30,000 customer companies and an average 76% of support volume resolved end to end, which is a vendor-reported figure rather than an independent measurement.
Two corrections to what you will read elsewhere, both checkable in one click:
**The deal is signed, not closed.** Salesforce expects it to close in the fourth quarter of its fiscal year 2027, subject to regulatory approval. Nothing about your account changes today.
**The Intercom brand is still very much alive.** As of 27 July 2026, intercom.com resolves normally and describes itself as "the only helpdesk designed for the AI Agent era", with plans named Essential, Advanced, and Expert. Only intercom.com/fin redirects to fin.ai. So the company is Fin, the AI agent is Fin, and the helpdesk you may already be paying for is still Intercom.
What that means practically: this is a procurement question, not an emergency. Acquisitions can reshape roadmaps and renewal pricing, so if you are signing a multi-year contract before the close, get both in writing. That is the whole of it.
## The split that actually decides your bill
Here is what the seat-price roundups miss. The support software market has split into two camps, and which camp a vendor is in matters more than its list price.
**Camp one meters your AI.** Fin bills $0.99 per outcome. Help Scout bills $0.75 per AI Answers resolution. Front's Autopilot starts at $0.05 per conversation. Freshdesk includes 500 Freddy sessions then charges $49 per additional 100. Zendesk bills AI agents per automated resolution on top of seats. Gorgias charges when its AI Agent resolves a conversation.
**Camp two does not.** Missive has you bring your own API key. Zoho Desk bundles Zia into the plan. Crisp includes AI credits per workspace. Drag bundles credits into Plus and Pro.
Look at that chart again, because the point is not that one bar is longer. It is that the four bars measure **four different things**. Fin bills an outcome. Help Scout bills a resolution. Freshworks bills a session, which starts whether or not anything gets solved. Front bills a conversation. Gorgias bills a ticket, and its documentation says a ticket becomes billable when any message is sent from the helpdesk, "whether the message comes from a human agent, AI Agent, or an automatic reply from a Rule" ([Gorgias docs](https://docs.gorgias.com/en-US/subscription-plans-81852), 2026).
You cannot put those on a spreadsheet and compare them. That is the honest state of this market in 2026.
The Fin definition is the one worth reading closely, because it is the one you are most likely to be quoted. Fin counts a resolution when "no further help is requested after Fin's last answer" ([Fin pricing](https://fin.ai/pricing), retrieved 27 July 2026). A customer who got what they needed and a customer who gave up in frustration both stop replying. Both bill $0.99.
## How to choose one, in five questions
Before the list, the five questions that actually narrow it. Most people get stuck comparing feature grids when four of these five decide the outcome.
**1. Where do your customers actually write to you?** This is the first question and it eliminates most of the list immediately. If the majority of your support arrives as email to a shared address, a chat-widget-first tool is solving a problem you do not have. If most of it arrives through a widget on your site, an inbox tool is the wrong shape. Count last month's messages by channel before you shortlist anything.
**2. How does the AI bill, and in what unit?** Covered above, and it is the question most likely to produce a surprise invoice. Ask the vendor to define its billable unit in writing, then ask what happens when the AI answers badly and the customer walks away. On several of these tools, that still bills.
**3. Does your team have to move?** A helpdesk means your agents work inside a new platform, and that migration is where most rollouts die. Inbox-native tools avoid it entirely. Neither is better in the abstract, but the migration cost is real and rarely appears in a comparison table.
**4. What does the bill do when volume spikes?** Per-seat pricing is stable under a volume spike and expensive when you add people. Per-ticket and per-resolution pricing is the reverse. Flat pricing is stable under both and less efficient if your volume is genuinely tiny. Model your worst month, not your average one.
**5. Who approves what the AI sends?** Fully autonomous resolution and draft-and-approve are different products with different risk. If a wrong answer about pricing, policy, or eligibility creates a real liability for you, that difference matters more than any feature on the list.
Nothing on this page beats every option on all five. The point is to know which two you actually care about.
## The nine alternatives
### InboxPilot: AI drafting inside Gmail and Outlook
[InboxPilot](/solutions/support-teams) is for teams whose support arrives as email rather than chat. It reads each incoming message in the Gmail or Outlook inbox you already use, drafts a reply grounded in your own docs and policies, triages and labels the thread, and waits for a person to approve before sending. Pricing is flat: free for 25 AI drafts, $29 per month for 200, and $149 per month for 1,500 drafts with unlimited inboxes and up to 10 team members. No per-resolution meter.
**Where it does not fit:** we are not a helpdesk. There is no chat widget, no ticket queue, no customer-facing help center, no voice, no SMS. If you need any of those, something below is a better answer than we are.
### Help Scout: the shared inbox with a real help center
[Help Scout](https://www.helpscout.com/pricing/) pairs a shared inbox with a polished customer-facing knowledge base, which is the thing it does better than almost anyone. Free for 5 users on one inbox, then Standard at $25 per user per month, Plus at $45, and Pro at $75, with 16% off annual billing. AI Answers is metered separately at $0.75 per resolution, free for the first three months on new accounts.
**Best for:** small support teams that want a genuine help center out of the box, which InboxPilot does not provide at all.
### Front: collaboration-heavy shared inbox
[Front](https://front.com/pricing) layers assignment, internal comments, and SLA workflows over shared email, SMS, and WhatsApp. Starter is $25 per seat per month up to 10 seats, Professional $65 up to 50 seats, and Enterprise $105, all billed annually. Its AI is the most fragmented on this list: Autopilot from $0.05 per conversation, Copilot $20 per seat per month, Smart QA $20, Smart CSAT $10, all included only at Enterprise.
**Best for:** mid-market teams where several people work the same threads and internal collaboration matters more than draft automation. Worth noting Front marks the $105 Enterprise tier as its most popular, which tells you where real-world pricing lands.
### Missive: shared inbox with team chat, and no AI meter
[Missive](https://missiveapp.com/pricing) puts real-time team chat inside the email thread. Starter is $14 per user per month billed yearly up to 5 users, Productive $24 up to 50, Business $36 unlimited. There is a free plan and a 30-day trial. Its AI runs on your own API key or Missive credits rather than a per-resolution meter.
**Best for:** small teams who want collaborative inbox plus chat in one app and specifically do not want a metered AI bill. Missive is the cleanest counter-example to per-resolution pricing here.
### Drag: shared inboxes inside Gmail
[Drag](https://www.dragapp.com/pricing/) turns Gmail into shared boards without leaving Gmail, which makes it the closest structural comparison to InboxPilot on this page. Starter is $12 per user per month billed annually ($16 monthly), Plus $18 ($22), Pro $24 ($30). AI is included in Plus and Pro via bundled credits rather than a resolution meter, and the credits are currently free during early access, so treat today's effective price as provisional.
**Best for:** Gmail-only teams who want Trello-style shared inboxes and workflow structure rather than AI drafting as the main event.
### Gorgias: the ecommerce helpdesk priced by tickets
[Gorgias](https://www.gorgias.com/pricing) is built for ecommerce and integrates deeply with Shopify, with native order and refund actions inside the ticket that a general tool cannot match. Its pricing is unusual and deliberately so: it scales from 50 to 5,000 tickets a month and is, in its own words, "never priced per agent". Its AI Agent is on every plan and bills when it resolves a conversation.
**Best for:** Shopify stores with high ticket volume and lots of seasonal or part-time agents, where per-seat pricing punishes you for staffing up. One caution: Gorgias appears to have consolidated its AI pricing into base plans very recently, so confirm the current rate card directly rather than trusting any roundup, including this one. We have a longer [Gorgias alternative](/blog/gorgias-alternative) comparison if you are weighing it against staying in the inbox.
### Zendesk: the enterprise standard
[Zendesk](https://www.zendesk.com/pricing/) is the broadest platform here: omnichannel ticketing, voice, messaging, formal SLAs, deep reporting, and enterprise governance. Support Team is $19 per agent per month paid yearly, Suite Team $55, and Suite Professional $115, which Zendesk marks as most popular. Copilot is a further $50 per agent per month, and AI agents bill per automated resolution on top.
**Best for:** larger organisations that need channel breadth and compliance. Zendesk beats InboxPilot decisively on both. Do the arithmetic before you commit though: Suite Professional plus Copilot is $165 per agent per month before a single AI resolution is billed.
### Freshdesk: Zendesk-class ticketing at roughly half the seat price
[Freshdesk](https://www.freshworks.com/freshdesk/pricing/) offers similar ticketing breadth for less. Growth is $19 per agent per month billed annually, Pro $55, Enterprise $89. Freddy AI Agent includes the first 500 sessions on every plan and then charges $49 per additional 100 sessions, and Freddy Copilot is $29 per agent per month. It also sells day passes for occasional agents.
**Best for:** cost-sensitive teams that want full helpdesk features, and anyone with seasonal staffing where day passes beat full seats. Note the unit: Freshworks meters sessions, which bill whether or not the issue is solved.
### Zoho Desk: lowest seat cost, AI bundled
[Zoho Desk](https://www.zoho.com/desk/pricing.html) has a free edition for 3 agents and the lowest paid seat prices on this list, with Zia AI bundled into the higher plans rather than metered. It fits naturally if you already run Zoho CRM or Books.
**Best for:** teams already inside the Zoho ecosystem, and anyone who wants AI included with no per-resolution meter at the lowest entry cost. One practical note: Zoho serves regional pricing, so confirm your local rate on their site rather than relying on a US figure quoted in a roundup.
### Crisp: chat-first, flat per workspace
[Crisp](https://crisp.chat/en/pricing/) leads with a website chat widget and prices differently from everyone else here: a flat rate per workspace rather than per seat. Free forever for 2 seats, Mini $45 per month for 4 seats, Essentials $95 for 10, Plus $295 for 20 or more, with extra agents at $10 each. AI credits are bundled per plan.
**Best for:** small teams whose primary channel genuinely is a chat widget on the website, and who want predictable cost as the team grows. It is the only flat-per-workspace option on this list.
## The nine compared
| Tool | Entry price | Pricing model | AI billing | Best for |
|---|---|---|---|---|
| **InboxPilot** | Free (25 drafts) | Flat plan | **Included** | Email-first teams in Gmail/Outlook |
| **Help Scout** | Free (5 users) | Per seat | $0.75/resolution | Teams needing a real help center |
| **Front** | $25/seat/mo | Per seat | $0.05/conversation + add-ons | Collaboration-heavy mid-market |
| **Missive** | Free plan | Per seat | **BYOK, no meter** | Small teams refusing a metered bill |
| **Drag** | $12/user/mo | Per seat | **Bundled credits** | Gmail-only teams |
| **Gorgias** | Ticket-tiered | **By ticket volume** | Per AI resolution | Shopify stores, many agents |
| **Zendesk** | $19/agent/mo | Per seat | +$50/agent + per resolution | Enterprises needing breadth |
| **Freshdesk** | $19/agent/mo | Per seat | 500 free, then $49/100 sessions | Budget ticketing, seasonal staff |
| **Zoho Desk** | Free (3 agents) | Per seat | **Bundled** | Zoho-ecosystem teams |
| **Crisp** | Free (2 seats) | **Flat per workspace** | **Bundled credits** | Chat-first small teams |
All figures read from each vendor's own pricing page on 27 July 2026. Pricing in this category is changing fast, so confirm before you budget.
## Which one fits
Skip to the line that describes you.
- **Support arrives as email, in Gmail or Outlook.** InboxPilot, Missive, or Drag. All three keep you in the inbox and none of them meters AI per resolution.
- **You need a customer-facing help center.** Help Scout, comfortably.
- **Several people work the same threads and coordination is the pain.** Front or Missive.
- **You sell on Shopify and volume is spiky.** Gorgias, whose ticket-based model is genuinely better than per-seat when you staff up seasonally.
- **You need voice, SMS, social, and compliance in one platform.** Zendesk, or Freshdesk if budget is tighter.
- **Your main channel is a chat widget.** Crisp.
- **You already run Zoho.** Zoho Desk.
- **You want maximum autonomous deflection and accept a variable bill.** Honestly, staying on Fin is defensible. It is a strong product and the acquisition does not change it today.
The through-line: pick the tool that matches where your customers actually write to you, then check how it meters AI before you sign anything.
**[See how InboxPilot drafts replies inside Gmail and Outlook →](/solutions/support-teams)**
## Related reading
- [The best Intercom Fin alternative for email support](/blog/intercom-fin-alternative): the same question narrowed to Fin's per-outcome pricing and the email channel.
- [InboxPilot vs Intercom](/inboxpilot-vs-intercom): a straight two-way comparison.
- [Best shared inbox software for Gmail and Outlook](/blog/best-shared-inbox-software): if the shared inbox itself is what you are shopping for.
- [AI email agent for RFQs, support, and sales email](/blog/ai-email-agent): what an AI email agent does across all three, and where it should stop.
- [Order status email automation](/use-cases/order-status-email-automation): answering WISMO and shipping questions from your system of record.
---
*Every price above was read from the named vendor's own pricing page on 27 July 2026 and is stated with that date. Two entries carry extra uncertainty and are flagged in the text rather than quietly smoothed over: Gorgias renders its rate card in JavaScript and appears to have recently consolidated AI into base plans, and Zoho Desk serves regional pricing, so both should be confirmed directly. Salesforce's acquisition of Fin is described as a signed agreement rather than a completed deal because as of publication it has not closed. The 76% autonomous resolution figure is reported by Salesforce and Fin, not independently measured. InboxPilot competes with every tool on this list and is the publisher of this article, which is why each entry states plainly where that tool beats us.*
---
## How Accounting Firms Automate Client Emails with AI
Source: https://www.inboxpilot.co/blog/accounting-firm-email-automation
Published: 2026-07-23
Accounting firms lose tax season to document chasing and status emails. How AI drafts the repetitive client replies in Gmail and Outlook, grounded in your process, with a human approving every send.
Somewhere in your firm's inbox right now is a client asking, for the third time, what documents you still need from them. Next to it is another asking whether their return is done yet, and another attaching a W-2 to the wrong thread. None of these needs a CPA's judgment. All of them need answering, and during tax season there are hundreds.
That is the quiet tax on an accounting practice: not the returns themselves, but the endless, repetitive email around them.
**Disclosure:** we make [InboxPilot](/product/ai-email-writer), an AI email agent that drafts replies to client emails inside Gmail and Outlook. This post is explicit about the line: no AI should be answering a client's actual tax question. It handles the repetitive, non-advisory email so your people can do the work that requires them.
## TL;DR
- The bottleneck in tax season is not preparing returns, it is [the document chasing and status email around them](#the-real-tax-season-bottleneck-is-email).
- [Five repetitive email types](#the-five-emails-that-fill-an-accounting-inbox) fill the inbox: document requests, status questions, deadline reminders, onboarding, and where-do-I-send-this logistics.
- Across industries, the average business takes 42 hours to answer an inbound email and 23% never reply ([HBR](https://hbr.org/2011/03/the-short-life-of-online-sales-leads), 2011); for a prospective client shopping firms, slow is lost.
- **[InboxPilot](#the-workflow-from-client-email-to-approved-reply), which is us,** is an inbox-native AI agent that [drafts the repetitive, non-advisory replies](#what-ai-can-take-off-your-plate) inside Gmail and Outlook, grounded in your process, with [a preparer approving anything advisory](#keep-a-preparer-on-anything-advisory).
## The real tax season bottleneck is email
Ask any firm owner where the hours go between January and April and the honest answer is rarely "preparing returns." It is the surrounding email: chasing the documents you cannot start without, answering the same status question over and over, and reminding clients of deadlines they will miss anyway.
Document collection is the worst of it. A return cannot begin until the client sends the W-2, the 1099s, the brokerage statements, the mortgage interest, the childcare receipts. So your staff send the checklist, wait, send it again, receive half of it in a reply-all with no context, and chase the rest. Multiply that by every client, compressed into ten weeks, and the chasing alone can consume more time than the preparation.
The timing makes it worse. In a 2026 survey of 438 accountants, 58% said more than half their clients sent documents after February 15, and 70% admitted to errors or near-misses caught in the final 48 hours before the deadline ([CPA Practice Advisor](https://www.cpapracticeadvisor.com/2026/05/26/78-of-tax-pros-say-that-tax-season-negatively-impacts-personal-professional-life/183912/), 2026). The late documents and the last-minute scramble are two symptoms of the same untamed inbox.
The status questions pile on top. "Is my return done?" "Did you get my documents?" "When will I hear back?" Each is thirty seconds to answer and completely repetitive, and there are hundreds of them, arriving at exactly the moment your team has the least slack.
None of this is skilled work. It is the low-value layer wrapped around the high-value work, and it is precisely what software should absorb.
## The five emails that fill an accounting inbox
Ask a firm's admin what fills the inbox and it is some version of these five. Every one is repetitive and non-advisory, answerable from your own process.
| Email type | What it looks like | Why it drags |
|---|---|---|
| **Document requests & chasing** | "What do you still need?" "Here's my W-2" (wrong thread) | The return can't start until it's complete; someone chases every client |
| **Status questions** | "Is my return done yet?" | Thirty seconds each, hundreds of them, all at once |
| **Deadline reminders** | Extensions, estimated payments, filing dates | Same notices, re-sent to everyone |
| **Onboarding & engagement** | "How do I get started?" "What do you need to quote me?" | New-client logistics that pull time from filing |
| **Where-do-I-send-this** | Portal links, upload help, "which email?" | Pure logistics, endlessly repeated |
## What AI can take off your plate
In the client inboxes we help firms set up, one pattern holds: the same non-advisory questions, all day, every day of the season. An AI email assistant grounded in your own process absorbs that layer:
- **Triage on arrival.** Every email is sorted: document submission, status question, advisory question, new-client enquiry, deadline logistics. Advisory questions get flagged for a human immediately.
- **Drafts from your own process.** Point it at your document checklist, engagement steps, deadlines, and portal instructions, and it drafts grounded replies. A "what do you still need" question comes back with exactly the outstanding items from your checklist.
- **Instant acknowledgement.** A client who submits documents or asks a status question gets an immediate, on-brand reply, which cuts the follow-up emails that pile up when people are left wondering.
- **Advisory stays human.** Anything about a client's actual tax position is routed to a preparer, never auto-answered.
- **It runs where you work.** Inside the shared Gmail or Outlook inbox your firm already uses, no migration.
## The workflow: from client email to approved reply
Here is the shape of it. A status question comes in mid-season:
> **Incoming, 9:40am.** "Hi, just checking, is my return finished? And did you get the brokerage statement I sent last week? Trying to plan around the refund."
Seconds later a draft is waiting, grounded in your process:
> **AI draft, 9:40am.** "Hi Dana, thanks for checking in. Yes, we received your brokerage statement, that's logged. Your return is in preparation and on track; we'll reach out if we need anything else and let you know the moment it's ready for your review. One item still outstanding on our checklist is your 1098 mortgage interest, whenever that's handy."
One glance and one click. Under the hood, it takes seconds:
1. The email lands in the client inbox.
2. InboxPilot reads it, recognizes a non-advisory status-and-documents question, and checks the client's outstanding-items list against your checklist.
3. It drafts a reply confirming receipt, giving a status, and prompting for the one missing document, in your firm's tone.
4. It labels the thread "Status, needs approval" and surfaces it.
5. Your admin skims and sends, in seconds, not after the fifth follow-up.
## Keep a preparer on anything advisory
The guardrail is non-negotiable for this profession: anything touching a client's specific tax situation is routed to a person and never auto-sent. The AI handles the document chasing, status updates, reminders, and logistics, the repetitive layer that eats the season, and leaves every judgment call to a qualified preparer.
## Related reading
- [Document collection automation](/use-cases/document-collection-automation): how InboxPilot chases client documents politely, with a worked example.
- [How to automate email support](/blog/ai-email-agent): the general playbook for a repetitive inbox.
- [Best email management software for teams](/blog/ai-email-agent): the wider tool category, compared.
- [InboxPilot pricing](/pricing): plans, draft quotas, and what a firm actually pays.
---
*Response-time figures are cited from Harvard Business Review's cross-industry lead-response study; they are directional, not accounting-specific. InboxPilot is the publisher of this article; advisory questions are routed to a human and a preparer approves every send.*
See how firms set this up end to end on the [AI email automation for accounting and bookkeeping](/industries/accounting-bookkeeping) page.
---
## How Agencies Automate Client Emails with AI
Source: https://www.inboxpilot.co/blog/agency-email-automation
Published: 2026-07-23
For an agency, communication is the deliverable. How AI drafts client status, approval, and new-business emails in Gmail and Outlook, with a human approving every send.
An agency's product is not just the campaign, the design, or the code. It is the experience of being a client, and most of that experience is email. The status update that arrives before the client has to ask. The fast, clear answer to a question. The new-business inquiry that gets a warm reply within the hour instead of the next day. Get the email right and clients feel looked after; get it slow and even great work starts to feel neglected.
Which is why it is strange that client email is the least systematized thing most agencies do.
**Disclosure:** we make [InboxPilot](/product/ai-email-writer), an AI email agent that drafts replies to client and prospect emails inside Gmail and Outlook. This post walks through the workflow and is clear about the limit: no AI should be making strategic calls or handling a sensitive client conversation for you. It takes the repetitive email off your account team so they can spend their attention where it matters.
## TL;DR
- For an agency, [communication is part of the deliverable](#communication-is-the-deliverable), so slow email quietly erodes retainers and loses pitches.
- Across industries, the average business takes 42 hours to answer an inbound email and 23% never reply at all ([HBR](https://hbr.org/2011/03/the-short-life-of-online-sales-leads), 2011); for an inbound lead choosing an agency, first and clearest usually wins.
- [Five repetitive email types](#the-five-emails-that-fill-an-agency-inbox) fill the inbox: status updates, feedback and approvals, new-business inquiries, scheduling, and routine logistics.
- **[InboxPilot](#the-workflow-from-client-email-to-approved-reply), our inbox-native AI agent,** [drafts the repetitive client and prospect replies](#what-ai-can-take-off-your-plate) inside Gmail and Outlook, grounded in your projects and process, with [a human on anything strategic or sensitive](#keep-a-human-on-strategy-and-sensitive-threads).
## Communication is the deliverable
In Setup's 2024 Marketing Relationship Survey, the top reason clients ended an agency relationship was dissatisfaction with the value delivered, at 53%, up from 39% in 2022 ([Setup](https://setup.us/blog/why-clients-end-their-agency-relationships-why-agencies-think-they-do), 2024). And nothing makes good work feel like poor value faster than a client who has to chase you for an update.
Because when clients churn, it is rarely "the work was bad." Far more often it is "we felt out of the loop." Silence between milestones, a slow reply to a question, an approval request that sat for two days, each is small, and together they add up to a client who feels like a low priority and starts taking calls from other agencies.
The same dynamic runs on the new-business side. A prospect who emails your agency is emailing several. The pitch you win is often simply the one that replied first, sounded switched-on, and made the next step easy, while the prospect was still excited.
So the inbox is doing two of the most important jobs in the business, keeping current clients feeling looked after and converting new ones, and at most agencies it runs on whoever happens to have a spare moment between deliverables. That is the gap.
## The five emails that fill an agency inbox
Ask an account manager what fills the inbox and it is some version of these five. All are repetitive and answerable from your own project information and process.
| Email type | What it looks like | Why it drags |
|---|---|---|
| **Status updates & checks** | "Where are we on the launch?" | The client asks because you didn't tell them first; answerable from the plan |
| **Feedback & approvals** | "Sending notes." "Are we approved to proceed?" | Chasing sign-off and acknowledging feedback eats account time |
| **New-business inquiries** | A prospect who found you | High value, time-sensitive, and easy to answer slowly |
| **Scheduling** | Calls, reviews, kickoffs | Back-and-forth that pulls focus from the work |
| **Routine logistics** | Assets, access, invoices, links | Pure repetition, every client, every project |
## What AI can take off your plate
In the client inboxes we help agencies set up, the same updates and questions repeat across every account. An AI email assistant grounded in your own projects and process absorbs that layer:
- **Triage on arrival.** Every email is sorted: status question, feedback, approval, new business, logistics, strategic. Strategic and sensitive threads get flagged for the account lead.
- **Drafts from your own project info.** Point it at your project plans, process, scope docs, and timelines, and it drafts grounded replies. A "where are we" comes back with the actual status and next milestone; a new-business email comes back with a warm, on-brand first response and a prompt to book a call.
- **Proactive-feeling updates.** Because it can draft fast, the client hears back before frustration sets in, which is most of what "great communication" actually means.
- **Strategy stays human.** Anything creative, strategic, or touching scope, budget, or a delicate relationship is routed to the account lead, never auto-sent.
- **It runs where you work.** Inside the shared Gmail or Outlook inbox and per-client addresses your team already uses, no migration.
## The workflow: from client email to approved reply
Here is the shape of it. A status check comes in:
> **Incoming, 2:10pm.** "Hi, client's asking me where we are on the homepage redesign and when they'll see something. Can you give me an update I can pass on?"
Seconds later a draft is waiting, grounded in the project plan:
> **AI draft, 2:10pm.** "Hi Rachel, happy to. The homepage redesign is on track: wireframes are approved, visual design is in progress, and the first full mockup is scheduled to share with you this Thursday for review. After your feedback we'll move into build, targeting a staging link the following week. Want me to send a short written summary you can forward to the client directly?"
One glance and one click, and the client feels ahead of the question. Under the hood, it takes seconds:
1. The email lands in the account inbox.
2. InboxPilot reads it, recognizes a project-status request, and pulls the current status and next milestone from the plan.
3. It drafts a clear update with the next step and an offer to forward, in your agency's tone.
4. It labels the thread "Status, needs approval" and surfaces it.
5. Your account manager skims and sends in seconds, before the client had to chase.
## Keep a human on strategy and sensitive threads
The guardrail: status, logistics, and first responses can move fast, but anything strategic, creative, or touching scope, budget, or a difficult relationship stays draft-and-approve and routes to the account lead. The AI handles the repetitive, expectation-setting email, the layer that erodes when everyone is heads-down, and leaves the relationship judgment to your people.
## Related reading
- [How to automate email support](/blog/ai-email-agent): the general playbook for a repetitive inbox.
- [Best shared inbox software for Gmail and Outlook](/blog/best-shared-inbox-software): tools for a shared client inbox.
- [InboxPilot pricing](/pricing): plans, draft quotas, and what an agency actually pays.
---
*Response-time figures are cited from Harvard Business Review's cross-industry lead-response study; they are directional, not agency-specific. InboxPilot is the publisher of this article and drafts replies with a human approving every send.*
The [document collection automation](/use-cases/document-collection-automation) workflow covers the client intake and chasing patterns that apply to most agencies.
---
## How Chauffeur and Private-Driver Businesses Can Automate Booking Enquiry Emails
Source: https://www.inboxpilot.co/blog/chauffeur-booking-email-automation
Published: 2026-07-23
Chauffeur and private-driver businesses answer the same availability and quote enquiries all day. How AI reads booking emails, drafts a quote from your own rates, and routes the inbox, with a human approving every price.
A corporate PA emails at 7 a.m. asking for a quote on an airport transfer for three executives next Thursday, return trip, in an executive SUV. A regular client wants to change Friday's pickup time. A new enquiry asks whether you cover a town an hour outside your usual area.
Each of these is a small, answerable message. Together, across a day, they are the reason the phone-and-inbox juggling never stops, and the reason a booking enquiry sometimes sits long enough that the PA books the company down the road instead.
**Disclosure:** we make [InboxPilot](/product/ai-email-writer), an AI email agent that drafts replies to booking and quote enquiries inside Gmail and Outlook. This post walks through the workflow and is clear about the limit: no AI should be sending a customer a firm price for a custom job without a person checking it.
## TL;DR
- Booking enquiries are a speed game. Across industries, the average business takes 42 hours to answer an inbound lead and 23% never reply at all ([HBR](https://hbr.org/2011/03/the-short-life-of-online-sales-leads), 2011); for a high-value transfer, the quote that arrives first while the client is still deciding wins the work.
- The inbox is filled by [a few repetitive enquiry types](#the-emails-that-fill-a-chauffeur-inbox): availability questions, ride quotes, booking changes, and corporate account requests.
- Your booking software confirms jobs; [it does not answer the enquiries that come before a job exists](#your-booking-software-confirms-jobs-it-doesnt-answer-enquiries).
- **[InboxPilot](#the-workflow-from-new-enquiry-to-approved-quote), our inbox-native AI agent,** can [read the enquiry, draft a quote from your own rates, and route the inbox](#what-ai-can-take-off-your-plate) inside Gmail and Outlook, with [a person approving every price](#keep-a-person-on-pricing).
## The emails that fill a chauffeur inbox
Ask any private-driver or chauffeur operator what is in the enquiry inbox and it is some version of the same short list. Every one is repetitive and answerable from your own rate card and policies.
| Email type | What it looks like | Why it drags |
|---|---|---|
| **Availability & quote enquiries** | "How much for an airport transfer next Thursday, executive SUV, 3 passengers?" | The client is comparing operators; a fast, accurate quote wins the job |
| **Booking changes** | "Can we move Friday's pickup to 8am?" | Pure back-and-forth that interrupts whoever is coordinating |
| **Route & coverage questions** | "Do you cover this town?" "Can you do an hourly rate?" | Same answers, re-typed constantly |
| **Corporate & account requests** | Recurring transfers, invoicing, standing arrangements | Higher value, and exactly the enquiries you cannot afford to answer slowly |
None of this needs a person for the reading and the first draft. It needs a quick, correct, on-brand reply, which is what lets you win the enquiry instead of losing it to a slower rival.
## Your booking software confirms jobs, it doesn't answer enquiries
The chauffeur software market is built around dispatch: assign a driver, send a confirmation, remind the client, take the payment. That is genuinely useful, and it kicks in once a booking exists.
The problem is everything before the booking exists. The availability question, the custom quote, the "can you do this unusual run" enquiry, those arrive as plain emails, and they land in a Gmail or Outlook inbox that no dispatch system is watching. So operators end up with slick automation for confirmed jobs and a completely manual inbox for the enquiries that decide whether a job happens at all.
That is the gap InboxPilot fills. It does not replace your dispatch or booking software. It sits in the bookings@ or info@ inbox in front of it and answers the enquiry stage: reading each message, drafting a quote from your rates, flagging the ones that need you, and handing you the final click.
## What AI can take off your plate
An AI email assistant grounded in your own rates and policies can absorb the repetitive layer of the enquiry inbox:
- **Read the enquiry on arrival.** Route, date, time, vehicle class, and passenger count are pulled out of a free-text email into a clean summary.
- **Draft a quote from your own rates.** Point it at your rate card, coverage area, vehicle classes, and standard terms, and it drafts a grounded quote for standard jobs, in your voice, ready to approve.
- **Instant acknowledgement.** Even when an enquiry needs you, the client gets an immediate, professional reply instead of silence, which is what keeps them from booking a competitor while they wait.
- **Triage and routing.** Corporate accounts, custom routes, and anything unusual get flagged and routed to you rather than auto-quoted.
- **It runs where you already work.** No new platform. Inside the shared Gmail or Outlook inbox.
## The workflow: from new enquiry to approved quote
1. A booking enquiry lands in the bookings inbox.
2. InboxPilot reads it, recognizes a standard airport transfer, and checks your rate for that route and vehicle class.
3. It drafts a reply with the quote, availability, and a prompt to confirm, in your company's tone.
4. It labels the thread "Quote, needs approval" and surfaces it at the top.
5. You skim the draft, adjust if the job is unusual, and send, minutes after it arrived, while the client is still choosing.
## Keep a person on pricing
The guardrail: firm prices for custom jobs and corporate accounts stay draft-and-approve, and anything unusual routes to a person. Standard, repeatable quotes can be turned up to near-instant once you trust them. The AI does the reading and the first draft, the part that eats your evenings, and leaves the judgment calls to you.
## Related reading
- [Booking request automation](/use-cases/booking-request-automation): the workflow behind this post, with a worked airport-transfer example.
- [How to automate email support](/blog/ai-email-agent): the general playbook for a repetitive inbox.
- [InboxPilot pricing](/pricing): plans, draft quotas, and what a small operator actually pays.
---
*InboxPilot is the publisher of this article and drafts quotes with a person approving every price. It complements, and does not replace, your dispatch or booking software.*
---
## How Dental Practices Automate Patient Emails with AI
Source: https://www.inboxpilot.co/blog/dental-practice-email-automation
Published: 2026-07-23
New-patient emails that sit for a day go to the practice down the street. How AI triages and drafts patient email in Gmail and Outlook, with a human on anything clinical.
A prospective patient emails your practice on a Sunday evening: new to the area, needs a cleaning and thinks they might have a cavity, wants to know if you take their insurance and how soon you could see them. It is a new patient worth thousands over their lifetime, and it lands in an inbox nobody will open until Monday mid-morning, by which point they have emailed two other practices.
The front desk is a dental practice's growth engine. It is also, most days, completely underwater.
**Disclosure:** we make [InboxPilot](/product/ai-email-writer), an AI email agent that drafts replies to patient emails inside Gmail and Outlook. This post is explicit about the line: no AI should be answering a clinical question or handling protected health information unsupervised. It takes the repetitive, non-clinical email off the front desk so your team can care for the patients in front of them.
## TL;DR
- The front desk decides who becomes a patient, and [new-patient emails that sit get lost to a faster practice](#the-front-desk-is-the-bottleneck).
- Across industries, the average business takes 42 hours to answer an inbound email and 23% never reply at all ([HBR](https://hbr.org/2011/03/the-short-life-of-online-sales-leads), 2011); for a new-patient inquiry, slow is a lost patient.
- [Five repetitive email types](#the-five-emails-that-fill-a-dental-inbox) fill the inbox: new-patient inquiries, scheduling, insurance and fee questions, treatment questions, and reminders.
- **[InboxPilot](#the-workflow-from-patient-email-to-approved-reply), that's us,** is an inbox-native AI agent that can [triage and draft the non-clinical replies](#what-ai-can-take-off-your-plate) in Gmail and Outlook, grounded in your practice info, with [a person on anything clinical](#keep-a-person-on-anything-clinical).
## The front desk is the bottleneck
Every practice knows its front desk is where growth happens. A warm, fast response to a new-patient inquiry converts it; a slow or robotic one loses it. What practices underrate is how often that same front desk is physically unable to respond, because it is on the phone, checking someone in, chasing an insurance authorization, and calming a nervous patient, all at once.
The scale of the miss is measurable. In one analysis of 4,280 inbound calls across 26 dental practices, 38% went unanswered and new-patient conversion sat at just 25% ([Peerlogic](https://www.peerlogic.com/post/turning-missed-dental-phone-calls-into-profit), 2026). That is the phone; the overwhelmed front desk answering it is the same one your email waits behind.
So the emails wait. And the ones that wait longest are often the most valuable: the new-patient inquiries that come in after hours and on weekends, exactly when the office is closed and a prospective patient is finally sitting down to sort out their dental care.
The competitive reality is the same as any local service: a new patient choosing a dentist is rarely choosing just one. They send a few emails, and they tend to move forward with the practice that answered first, clearly, and kindly, while they were still thinking about it.
## The five emails that fill a dental inbox
Ask a practice's front-desk lead what fills the inbox and it is some version of these five. All are repetitive and, importantly, non-clinical, answerable from your own practice information.
| Email type | What it looks like | Why it drags |
|---|---|---|
| **New-patient inquiries** | "Taking new patients? Do you take my insurance?" | High-value, time-sensitive, and often arrives after hours |
| **Scheduling & rescheduling** | "Can you fit me in this week?" "Need to move Thursday." | Back-and-forth that ties up the front desk |
| **Insurance & fee questions** | "Do you take Delta Dental?" "How much is a crown roughly?" | Same answers, re-typed all day |
| **Treatment & pre-visit questions** | "What should I expect?" "Do I need to do anything first?" | Non-clinical ones are repetitive; clinical ones need a person |
| **Reminders & confirmations** | Appointment confirmations, forms, directions | Pure logistics, endlessly repeated |
## What AI can take off your plate
In the front-desk inboxes we help practices set up, the same non-clinical questions repeat all day. An AI email assistant grounded in your own practice information absorbs that layer:
- **Triage on arrival.** Every email is sorted: new-patient inquiry, scheduling, insurance, clinical question, logistics. Clinical questions get flagged for a person immediately.
- **Drafts from your own practice info.** Point it at your hours, new-patient process, accepted insurance, general fee ranges, and policies, and it drafts grounded replies. A "do you take my insurance and can you see me" email comes back with your answer and a prompt to book.
- **Instant acknowledgement, warmly.** A prospective patient who emails at 9 p.m. gets an immediate, friendly reply instead of silence until Monday, which is the difference between winning and losing them.
- **Clinical stays human.** Anything asking for advice, a diagnosis, or involving medical history is routed to a team member, never auto-answered.
- **It runs where you work.** Inside the shared Gmail or Outlook inbox your front desk already uses, no migration.
## The workflow: from patient email to approved reply
Here is the shape of it. A new-patient inquiry arrives on a Sunday night:
> **Incoming, 8:47pm.** "Hi, I just moved to the area and need to get set up with a dentist. I'm overdue for a cleaning and think I might have a small cavity. Do you take Delta Dental, and how soon could I get in?"
Seconds later a draft is waiting, grounded in your practice info:
> **AI draft, 8:47pm.** "Hi Jordan, welcome to the area, we'd be glad to get you in. Yes, we're in-network with Delta Dental, and we're currently welcoming new patients. We could typically schedule a new-patient exam and cleaning within the next week or so. If you reply with a couple of days that work, I'll get you booked, and our team can take a look at that tooth at the same visit."
One glance and one click first thing Monday, or that evening. Under the hood, it takes seconds:
1. The email lands in the front-desk inbox.
2. InboxPilot reads it, recognizes a non-clinical new-patient inquiry, and checks your accepted insurance and new-patient availability.
3. It drafts a warm reply confirming insurance and availability with a prompt to book, in your practice's voice, and flags the tooth mention for the team to address at the visit rather than diagnosing it.
4. It labels the thread "New patient, needs approval" and surfaces it at the top.
5. Your front desk skims and sends, fast, while the patient is still deciding.
## Keep a person on anything clinical
The guardrail is firm for healthcare: any clinical question, anything involving symptoms, diagnosis, or medical history, is routed to a team member and never auto-sent, and protected health information is handled inside your HIPAA safeguards. The AI handles the new-patient inquiries, scheduling, insurance questions, and logistics, the repetitive front-desk layer, and leaves care to your people.
## Related reading
- [Booking request automation](/use-cases/booking-request-automation): the generic appointment-enquiry workflow, before and after.
- [How to automate email support](/blog/ai-email-agent): the general playbook for a repetitive inbox.
- [Best shared inbox software for Gmail and Outlook](/blog/best-shared-inbox-software): tools for a shared front-desk inbox.
- [InboxPilot pricing](/pricing): plans, draft quotas, and what a practice actually pays.
---
*Response-time figures are cited from Harvard Business Review's cross-industry lead-response study; they are directional, not dental-specific. InboxPilot is the publisher of this article; clinical questions are routed to a person and a human approves every send.*
---
## How HVAC Companies Automate Service and Quote Emails with AI
Source: https://www.inboxpilot.co/blog/hvac-email-automation
Published: 2026-07-23
HVAC quote jobs go to whoever replies first. How AI triages service and quote email in Gmail and Outlook, with a human approving every send.
It is 88 degrees, your phones have not stopped, and there are nine emails in the service inbox nobody has opened. Two are new customers asking for a quote on a replacement system. One is a repeat customer who wants to move Thursday's maintenance visit. The rest are the usual: "do you service my area," "what's your call-out fee," "did you get my last message."
By the time someone at a desk works through that pile, the two quote requests have emailed three other contractors too. In HVAC, the job often goes to whoever replied first, not whoever is best.
**Disclosure:** we make [InboxPilot](/product/ai-email-writer), an AI email agent that drafts replies to service and quote emails inside Gmail and Outlook. This post walks through the workflow and says plainly where a tool like ours does not belong: no AI should be sending a customer a firm price or a firm appointment time without a person looking at it.
## TL;DR
- HVAC demand is spiky and time-sensitive, and [slow email replies lose the job](#why-hvac-companies-lose-the-job-in-the-inbox) to whichever contractor answered first.
- The inbox is filled by [five repetitive email types](#the-five-emails-that-fill-an-hvac-inbox): service requests, quote and estimate requests, scheduling, parts and warranty questions, and follow-ups.
- Here is the gap nobody talks about: [your phone already has an AI receptionist](#your-phone-has-an-ai-receptionist-your-inbox-does-not). Your inbox does not. The whole answering-service industry is built for calls, and email sits untouched.
- **[InboxPilot](#the-workflow-from-new-service-email-to-approved-reply), which is us,** can [triage, draft from your own pricing, and route](#what-ai-can-take-off-your-plate) service email inside Gmail and Outlook, with [a human approving every quote and booking](#keep-a-human-on-pricing-and-scheduling).
## Why HVAC companies lose the job in the inbox
Speed is the whole game for inbound service work, and the numbers on response time are brutal. Harvard Business Review's audit of 2,241 US companies found the average first response to an inbound lead took **42 hours**, and 23% of companies never responded at all ([HBR, "The Short Life of Online Sales Leads"](https://hbr.org/2011/03/the-short-life-of-online-sales-leads), 2011).
That study measured web leads across industries, not HVAC specifically, but the direction is exactly what every service owner already knows: a customer with a broken air conditioner is not waiting two days for you to email back.
Now layer on the two things that make HVAC harder than the average inbox. First, demand is seasonal and peaky: the first heat wave of summer and the first cold snap of winter dump a week's worth of requests into a single afternoon, precisely when your office is most swamped.
Second, the people who could answer are rarely at a desk. Technicians are in attics and crawl spaces; the owner is quoting a job across town. The email that would have won the sale sits unread not because anyone is lazy, but because everyone is busy doing the actual work.
The result is quiet and expensive: not a complaint, just a quote request that goes to a competitor because they replied in twenty minutes and you replied the next morning.
## The five emails that fill an HVAC inbox
Ask an HVAC office manager what is in the service inbox and you get some version of the same five piles. All five are repetitive, and all five are answerable from information you already have written down somewhere.
| Email type | What it looks like | Why it drags |
|---|---|---|
| **Service requests** | "My AC stopped cooling, can someone come out?" | Needs triage (emergency vs routine), a service-area check, and a next-step reply, fast |
| **Quote & estimate requests** | "How much for a new furnace / a mini-split in a 2-car garage?" | The customer is price-shopping several contractors at once; slow replies lose |
| **Scheduling & reschedules** | "Can we move Thursday's maintenance to next week?" | Pure back-and-forth that interrupts whoever is dispatching |
| **Parts & warranty questions** | "Is this covered?" "How long for the part?" | The answers rarely change but someone re-types them every time |
| **Follow-ups** | "Did you get my request?" "Any update on the quote?" | Tiny individually, constant in aggregate |
None of this is hard to answer. It is repetitive, and repetitive is exactly what software should absorb so your staff can handle the calls, the dispatch, and the customers who actually need a human.
## Your phone has an AI receptionist. Your inbox does not.
Here is the strange thing about the HVAC software market. Search for AI tools for HVAC companies and you will find a crowded field of **AI answering services**: they pick up your phone 24/7, book jobs, and route after-hours emergencies. That category is real and it is well funded.
Almost none of them touch email.
So the typical growing HVAC company ends up with an AI receptionist guarding the phone line and a completely manual inbox behind it, where quote requests and web-form submissions pile up exactly the same way they always did. The channel plenty of customers reach for first, type it once, send it, get a written answer, is the one channel nobody automated.
That is the gap InboxPilot fills. It is not an answering service and it does not replace one. It sits in the Gmail or Outlook inbox your office already runs and does for email what the answering service did for calls: reads every message, drafts a grounded reply, flags the urgent ones, and hands a person the easy final click.
## What AI can take off your plate
In the shared service inboxes we help HVAC teams set up, the same handful of questions repeat all day. An AI email assistant grounded in your own business absorbs that repetitive layer:
- **Triage on arrival.** Every incoming email is read and sorted: emergency no-cool/no-heat, routine service, new quote, existing-customer scheduling, supplier. The urgent ones get surfaced first instead of waiting their turn behind a newsletter.
- **Drafts from your own pricing and policies.** Point it at your price ranges, call-out fees, service-area list, maintenance-plan details, and standard warranty language, and it drafts replies grounded in your real answers, not generic AI text. A quote request comes back with your actual ballpark and a prompt to book a visit.
- **Instant acknowledgement, in your voice.** Even when a request needs a human, the customer gets an immediate, on-brand "we've got your request, here's what happens next" instead of silence, which is what keeps them from emailing your competitor while they wait.
- **Routing and escalation.** A suspected emergency, a warranty dispute, or a commercial-contract question gets flagged and routed to the right person instead of being auto-answered.
- **It works where your team already works.** No new platform, no migration. It runs inside the shared service@ or info@ inbox in Gmail or Outlook, so your office staff never leave the tool they know.
## The workflow: from new service email to approved reply
Here is the shape of it. A request comes in first thing:
> **Incoming, 7:12am.** "My AC stopped cooling overnight and the house is already warm. Can someone come out today? I'm in Westfield, and roughly what would a service call run?"
Seconds later a draft is waiting for approval, grounded in your service area, your call-out fee, and today's availability:
> **AI draft, 7:12am.** "Hi Sarah, sorry to hear the AC is down in this heat. Yes, we cover Westfield and can get a technician out today. Our diagnostic call is $89, credited toward any repair. I've pencilled in a 2 to 4pm window, reply to confirm and it's yours. If it turns into an emergency before then, call us at (555) 010-4477."
One glance and one click, at 7:12am instead of 9. Under the hood, it takes seconds:
1. A quote request lands in the service inbox.
2. InboxPilot reads it, recognizes it as a new-system quote, and checks the address against your service area.
3. It drafts a reply using your price range for that system type, a line about scheduling a free assessment, and your standard next-step, in your company's tone.
4. It labels the thread "Quote, needs approval" and surfaces it near the top of the inbox.
5. Your office manager reads the draft, tweaks the number if needed, and hits send, twenty minutes after it arrived, not the next morning.
The customer experiences a fast, professional, accurate reply. Your team experiences one glance and one click instead of reading, deciding, looking up pricing, and typing from scratch.
## Keep a human on pricing and scheduling
The honest guardrail: pricing and appointment commitments should stay draft-and-approve. A firm quote and a firm time slot both carry real consequences, so the sane default is that AI drafts and a person sends. Set sensitive topics, warranty disputes, commercial contracts, anything with a complaint in it, to route straight to a human and skip automation entirely.
Used that way, the AI is not answering for you. It is doing the reading, the sorting, and the first draft, which is where the hours actually go, and leaving the judgment calls to the people who should make them.
## Related reading
- [How construction companies automate RFQ and customer emails](/blog/construction-rfq-email-automation): the same workflow for a trade that lives on quote requests.
- [How to automate email support](/blog/ai-email-agent): the general playbook for putting a repetitive inbox on autopilot.
- [InboxPilot pricing](/pricing): plans, draft quotas, and what a service team actually pays.
---
*Response-time figures are cited from Harvard Business Review's cross-industry lead-response study; they are directional for HVAC, not HVAC-specific. InboxPilot is the publisher of this article and drafts replies with a human approving every send.*
The same pattern shows up in [booking request automation](/use-cases/booking-request-automation), alongside service calls and quote requests.
---
## How Manufacturers Can Automate RFQ Email Responses with AI
Source: https://www.inboxpilot.co/blog/manufacturer-rfq-email-automation
Published: 2026-07-23
Manufacturers and suppliers lose deals in the days between an RFQ email arriving and someone quoting it. How AI reads the request, drafts a quote from your own pricing and specs, and routes the inbox, with a human approving every number.
There is an RFQ sitting in your sales inbox right now. It came in as an email with a PDF drawing attached, asking for a price on 500 units with a delivery date four weeks out. Nobody has quoted it yet, because your estimator is finishing yesterday's batch and the owner is on the floor.
Meanwhile the buyer who sent it emailed two other shops the same morning. In manufacturing, when price and capability are close, the order often goes to whoever quoted first, not whoever was cheapest.
**Disclosure:** we make [InboxPilot](/product/ai-email-writer), an AI email agent that drafts replies to RFQs and customer emails inside Gmail and Outlook. This post explains the workflow and says plainly where a tool like ours does not belong: no AI should be sending a firm price, tolerance, or lead-time commitment without an estimator checking it.
## TL;DR
- Manufacturers rarely lose an RFQ because they can't do the work. They lose it in [the days between the email arriving and a person quoting it](#why-manufacturers-lose-rfqs-in-the-inbox).
- The estimating inbox is filled by [five repetitive email types](#the-five-emails-in-a-manufacturers-inbox): RFQs, availability and lead-time questions, spec clarifications, quote follow-ups, and reorders.
- Most RFQs do not arrive through a portal. [They arrive as email with a spec sheet attached](#most-rfqs-arrive-by-email-not-through-a-portal), which is why automation has to start in Gmail and Outlook.
- **[InboxPilot](#the-workflow-from-new-rfq-to-approved-quote), which is us,** can [read the RFQ, draft a quote from your own pricing and specs, and route the inbox](#what-ai-can-take-off-your-plate) inside Gmail and Outlook, with [an estimator approving every number](#keep-an-estimator-on-the-numbers).
## Why manufacturers lose RFQs in the inbox
The bottleneck in most shops is not capability or even price. It is the queue in front of the estimator. An RFQ lands, and before anyone can quote it, someone has to open the email, read the drawing or spec sheet, pull out the part number, quantity, material, tolerances, and required date, check availability and lead time, and only then start pricing. That reading-and-extracting step is pure overhead, and it happens for every request, winnable or not.
While that queue moves, the clock runs. The buyer who sent the RFQ is rarely sending it to one shop. When two suppliers can both do the job at a similar price, the faster quote wins a disproportionate share of the time, and the shop that took three days to respond never finds out how close it was.
This is not a hunch about buyer behavior. In a Thomas survey of more than 400 industrial buyers, respondents said they expect supplier responses within 24 hours and quietly drop the slow ones. One put it plainly: "There's nothing worse than no response or hearing back weeks later. If I have to follow up twice, I eliminate you from consideration." ([Thomas](https://blog.thomasnet.com/what-industrial-buyers-care-most-about-when-shortlisting-new-suppliers), 2021).
The frustrating part is that the slow step is the least skilled one. Your estimator's judgment on pricing and feasibility is valuable and hard to replace. The reading, sorting, and re-typing in front of it is not, and it is exactly what eats the hours.
## The five emails in a manufacturer's inbox
Ask a shop's sales desk what fills the inbox and you get some version of the same five piles. Every one is repetitive and answerable from information you already have on file.
| Email type | What it looks like | Why it drags |
|---|---|---|
| **RFQs** | "Price on 500 of part X, drawing attached, need by the 30th" | Specs are buried in PDFs; someone reads, extracts, and re-types before pricing starts |
| **Availability & lead time** | "Do you have this in stock? What's the lead time on 1,000?" | Same lookups, answered over and over |
| **Spec clarifications** | "Can you hold ±0.001?" "Do you do anodizing in-house?" | Capability questions whose answers rarely change |
| **Quote follow-ups** | "Did you get our RFQ?" "Any update on that number?" | Small individually, constant in aggregate, and often where deals are lost |
| **Reorders** | "Same as last time, another batch" | A quick win that still waits in the same undifferentiated queue |
None of this needs an estimator's judgment to acknowledge and start. It needs fast reading, accurate extraction, and a grounded first draft, which is what software should absorb so your estimator spends time pricing, not sorting.
## Most RFQs arrive by email, not through a portal
There is a persistent myth that RFQs live in procurement portals. Some do, at the largest GCs and OEMs and on public work. For most small and mid-size manufacturers and suppliers, the reality is an email inbox with spec sheets and drawings attached. Buyers reach for email because it is universal and low-friction: attach the drawing, hit send, get a number back.
That is why the wave of RFQ and CPQ software mostly misses this buyer. Those platforms are built around a portal and a structured configuration flow, and many target the enterprise or the buyer side of the transaction. They ask your customers to adopt a system, which most will not. The requests keep coming to the inbox, and the inbox stays manual.
That is the gap InboxPilot fills. It is not a CPQ platform and it does not ask your buyers to change anything. It sits in the estimating inbox in Gmail or Outlook and turns it into the front end of your quoting process: reading each RFQ, extracting the details, drafting a quote from your own data, and handing your estimator a number to check instead of a PDF to decode.
## What AI can take off your plate
An AI email assistant grounded in your own pricing and capability docs can absorb the repetitive layer of the estimating inbox:
- **Read and extract on arrival.** Every RFQ is read, including the attached spec sheet or drawing where possible, and the part, quantity, material, tolerances, and required date are pulled into a structured summary your estimator can scan in seconds.
- **Draft a quote from your own data.** Point it at your price lists, rate cards, capability statement, standard lead times, and past quotes, and it drafts a grounded reply with a ballpark or a firm number where your rules allow, in your company's tone.
- **Instant acknowledgement.** Even when a quote needs an estimator, the buyer gets an immediate, on-brand reply confirming receipt and next steps, which is what keeps them from awarding elsewhere while they wait.
- **Triage and routing.** Winnable RFQs, capability mismatches, and sensitive threads get sorted and routed, so nobody's request sits unseen and nothing risky gets auto-answered.
- **It runs where your team works.** No new platform, no migration, no portal for buyers. Inside the shared sales or estimating inbox in Gmail or Outlook.
## The workflow: from new RFQ to approved quote
1. An RFQ lands in the estimating inbox with a drawing attached.
2. InboxPilot reads the email and the drawing, extracts part, quantity, material, tolerance, and required date, and checks your standard lead time.
3. It drafts a reply with your ballpark pricing for that part type, your lead time, and standard terms, and attaches a structured summary of the request for the estimator.
4. It labels the thread "RFQ, needs approval" and surfaces it near the top of the inbox.
5. Your estimator checks the number, adjusts for anything the drawing implies, and sends, the same day, not three days later.
## Keep an estimator on the numbers
The honest guardrail: pricing, tolerances, and lead-time commitments stay draft-and-approve. A firm quote carries margin and contract risk, so AI drafts and an estimator sends. Route claims, change orders, disputes, and anything with a complaint in it straight to a person and skip automation entirely. Used this way, the AI does the reading and the first pass, where the hours go, and leaves the judgment to the person qualified to make it.
## Related reading
- [RFQ email automation, the full workflow](/use-cases/rfq-email-automation): the problem, the manual versions, and a before-and-after RFQ draft.
- [How construction companies automate RFQ and customer emails](/blog/construction-rfq-email-automation): the same workflow for the construction trades.
- [Best RFQ email management software](/blog/best-rfq-email-management-software): the wider tool category, compared.
- [InboxPilot pricing](/pricing): plans, draft quotas, and what an estimating team actually pays.
---
*Response-speed claims reflect the recurring finding in RFQ research that faster quotes win a disproportionate share of close decisions; specific figures should be confirmed against current sources. InboxPilot is the publisher of this article and drafts quotes with an estimator approving every number.*
InboxPilot has a deeper walkthrough of [RFQ email automation](/use-cases/rfq-email-automation) if quotes are your main bottleneck.
---
## How Plumbers Automate Quote and Service Emails with AI
Source: https://www.inboxpilot.co/blog/plumbing-email-automation
Published: 2026-07-23
Plumbing inboxes hold two opposite emails: panicked emergencies and considered quotes. How AI triages both and drafts replies in Gmail and Outlook, with a human approving every send.
Two very different emails land in a plumber's inbox, and they need opposite handling. One is a panic: "water is coming through the ceiling, can someone come now." The other is considered: "we're thinking about repiping the house, roughly what would that cost." Answer the panic slowly and you have an angry customer with a flood. Answer the quote slowly and the job goes to whoever replied first.
Most plumbing businesses handle both the same way: whenever someone at the desk gets to it. That is the gap this post is about.
**Disclosure:** we make [InboxPilot](/product/ai-email-writer), an AI email agent that drafts replies to service and quote emails inside Gmail and Outlook. This post walks through the workflow and is clear about the limit: no AI should be sending a firm price, or handling a genuine emergency, without a person in the loop.
## TL;DR
- A plumbing inbox holds two opposite jobs, [emergencies that need instant acknowledgement and quotes that need a fast, accurate number](#the-two-inboxes-hiding-in-one), and speed decides both.
- Across industries, the average business takes 42 hours to answer an inbound lead and 23% never reply at all ([HBR](https://hbr.org/2011/03/the-short-life-of-online-sales-leads), 2011). For a repipe quote, the one that arrives first while the homeowner is still deciding wins the work.
- [Five repetitive email types](#the-five-emails-that-fill-a-plumbing-inbox) fill the inbox, and every one is answerable from information you already have written down.
- **[InboxPilot](#the-workflow-from-new-email-to-approved-reply), which is us,** can [triage, draft from your own pricing, and route](#what-ai-can-take-off-your-plate) service and quote email in Gmail and Outlook, with [a human on pricing and every suspected emergency](#keep-a-human-on-pricing-and-emergencies).
## The two inboxes hiding in one
The reason a plumbing inbox is hard is that it is really two inboxes wearing one address.
The emergency inbox runs on trust and speed. A customer with water coming through the ceiling does not need a quote; they need to know a human saw the message and help is coming. A fast, calm acknowledgement with a realistic arrival window is the difference between a five-star review and a one-star one, and silence is what turns a burst pipe into a furious phone call.
The quote inbox runs on competition. A homeowner pricing a water heater, a repipe, or a bathroom is emailing several plumbers at once. The winning quote is rarely the cheapest; it is often just the first one that came back with a clear number and a next step, while the customer was still paying attention.
And most contractors are slow. In an analysis of 132,188 home-services speed-to-lead campaigns, only 12% of contractors answered a new lead within five minutes, and the single most common response time was a full day ([Hatch](https://www.usehatchapp.com/blog/hvac-speed-to-lead-response-rates), 2024). The bar to beat is low, and the reward for clearing it is the job.
Handled by hand, both suffer at the same time, because the moments the inbox is busiest, a heat wave, a freeze, a Monday morning, are exactly the moments your office staff are buried.
## The five emails that fill a plumbing inbox
Ask a plumbing office manager what is in the inbox and it is some version of these five. All are repetitive and answerable from your own pricing and policies.
| Email type | What it looks like | Why it drags |
|---|---|---|
| **Emergency service requests** | "Water everywhere, need someone now" | Needs instant acknowledgement, triage, and routing, not a queue |
| **Quote & estimate requests** | "How much to replace a water heater / repipe?" | The customer is price-shopping; the first clear quote wins |
| **Booking & scheduling** | "Can you come Thursday morning?" | Back-and-forth that interrupts whoever is dispatching |
| **Service-area & availability** | "Do you cover my town?" "What's your call-out fee?" | Same answers, re-typed all day |
| **Follow-ups** | "Did you get my request?" "Any update on the quote?" | Small individually, constant in aggregate |
None of this needs a plumber's judgment to acknowledge and start. It needs a fast, correct reply, which is what lets your team focus on the jobs and the calls that genuinely need a person.
## What AI can take off your plate
In the shared service inboxes we help trades teams set up, the same handful of questions repeat all day. An AI email assistant grounded in your own business absorbs that repetitive layer:
- **Triage on arrival.** Every email is read and sorted: suspected emergency, quote request, booking, service-area question. The panic emails float to the top and get flagged instead of waiting in line.
- **Drafts from your own pricing.** Point it at your price ranges, call-out fee, service area, and standard terms, and it drafts grounded replies. A repipe enquiry comes back with your ballpark and a prompt to book an on-site estimate.
- **Instant acknowledgement.** Even when a job needs a human, the customer gets an immediate, on-brand reply so an emergency does not sit in silence and a quote shopper does not drift to a competitor.
- **Routing and escalation.** Anything that reads like an emergency, or anything unusual, gets flagged and routed to a person rather than auto-answered.
- **It runs where you work.** No new platform. Inside the shared Gmail or Outlook inbox your office already uses.
## The workflow: from new email to approved reply
Here is the shape of it. A quote request comes in:
> **Incoming, 8:03am.** "Our water heater died over the weekend. It's a 3-bed house, gas. Roughly what would a replacement cost, and how soon could you do it?"
Seconds later a draft is waiting, grounded in your pricing and availability:
> **AI draft, 8:03am.** "Hi Mark, sorry about the water heater, no fun with a full house. For a gas replacement in a home your size we're typically in the $1,400 to $2,200 range depending on the unit, and we could usually fit it in within 2 to 3 days. If you reply with your address I'll book a quick on-site check to confirm the number. Need hot water sooner? Let me know and we'll prioritise it."
One glance and one click, at 8:03am instead of mid-morning. Under the hood, it takes seconds:
1. The email lands in the service inbox.
2. InboxPilot reads it, recognizes a water-heater quote, and checks your price range and availability.
3. It drafts a reply with your ballpark, your lead time, and a prompt to book an on-site estimate, in your company's tone.
4. It labels the thread "Quote, needs approval" and surfaces it at the top of the inbox.
5. Your office manager skims the draft and sends, minutes after it arrived.
## Keep a human on pricing and emergencies
The guardrail is simple: firm pricing stays draft-and-approve, and anything that reads like an emergency routes straight to a person, fast. AI does the reading, sorting, and first draft, the part that eats the hours, and leaves the water-through-the-ceiling calls and the final numbers to the people who should handle them.
## Related reading
- [How HVAC companies automate service and quote emails](/blog/hvac-email-automation): the same playbook for the sibling trade.
- [How to automate email support](/blog/ai-email-agent): the general approach to a repetitive inbox.
- [InboxPilot pricing](/pricing): plans, draft quotas, and what a service team actually pays.
---
*Response-time figures are cited from Harvard Business Review's cross-industry lead-response study; they are directional for the trades, not plumbing-specific. InboxPilot is the publisher of this article and drafts replies with a human approving every send.*
See [booking request automation](/use-cases/booking-request-automation) for how this extends to scheduling, quotes, and after-hours requests.
---
## How Property Managers Can Automate Tenant and Leasing Emails with AI
Source: https://www.inboxpilot.co/blog/property-management-email-automation
Published: 2026-07-23
Property managers answer the same maintenance, leasing, and rent emails all day. How AI triages tenant and prospect email, drafts replies from your own policies, and routes the inbox, with a human approving every send.
A prospect emailed at 9 p.m. asking if the two-bedroom on Elm is still available and whether you allow dogs. A tenant emailed at 6 a.m. because the heat is out. Somewhere in the same inbox is a renewal question, an application follow-up, and a vendor asking for a gate code.
By the time a property manager sits down to work through it, the prospect has toured two other buildings and the tenant has called twice. None of those emails were hard to answer. There were just too many of them, arriving at the wrong times, for one person to keep up with.
**Disclosure:** we make [InboxPilot](/product/ai-email-writer), an AI email agent that drafts replies to tenant and leasing emails inside Gmail and Outlook. This post walks through the workflow and is clear about the limit: no AI should be sending a tenant a lease commitment or a legal notice unsupervised.
## TL;DR
- Leasing is a speed game and maintenance is a trust game, and [slow email replies lose on both](#why-property-managers-lose-time-and-leases-in-the-inbox).
- The inbox is filled by [five repetitive email types](#the-five-emails-that-fill-a-property-management-inbox): maintenance requests, leasing inquiries, rent and renewal questions, applications, and vendor coordination.
- Your property management software does not answer these. [It runs the portal; the inbox is still manual.](#your-property-software-runs-the-portal-not-the-inbox)
- **[InboxPilot](#the-workflow-from-new-tenant-email-to-approved-reply), our inbox-native AI agent,** can [triage, draft from your own policies, and route](#what-ai-can-take-off-your-plate) tenant and prospect email inside Gmail and Outlook, with [a human on anything legal or financial](#keep-a-human-on-leases-money-and-notices).
## Why property managers lose time and leases in the inbox
Two different clocks run in a property management inbox, and both punish slowness. And both of them run over email: in the 2024 NMHC and Grace Hill Renter Preferences Survey of 172,703 renters across 4,220 communities, email was the channel renters most preferred for reaching their property, ahead of phone and text, even for scheduling tours and non-emergency maintenance ([NMHC/Grace Hill](https://www.nmhc.org/research-insight/research-report/nmhc-grace-hill-renter-preferences-survey-report/), 2024). Your prospects and tenants are choosing the channel most property managers are slowest on.
The leasing clock is about competition. A prospect emailing about a vacancy is almost always emailing about several. The unit does not go to the nicest building; it goes to the one that answered, sent the application, and booked the tour first. Every hour a leasing inquiry sits unread is an hour a competitor can close it.
The maintenance clock is about trust. A tenant whose heat is out does not need the problem fixed in the next ten minutes, but they need to know a human saw their message and something is happening. Silence is what turns a routine work order into an angry phone call, a bad review, and a renewal you lose next year.
The catch is that both clocks run hardest at exactly the times a property manager is not at a desk: evenings, early mornings, weekends, and the middle of a unit turn. The emails that decide a lease or a renewal are the ones most likely to sit unanswered.
## The five emails that fill a property management inbox
Ask any property manager what is in the inbox and you get some version of the same five piles. Every one of them is repetitive and answerable from information you already have documented.
| Email type | What it looks like | Why it drags |
|---|---|---|
| **Maintenance requests** | "The heat is out." "There's a leak under the sink." | Needs triage (emergency vs routine), acknowledgement, and routing to the right vendor or tech |
| **Leasing inquiries** | "Is the 2-bed still available? Do you allow pets?" | The prospect is shopping several buildings; slow replies lose the lease |
| **Rent & renewal questions** | "Can I pay on the 5th?" "What are my renewal options?" | Same handful of answers, re-typed constantly |
| **Applications & screening** | "Did you get my application?" "What documents do you need?" | Status and requirements questions that interrupt a manager mid-turn |
| **Vendor & owner coordination** | Gate codes, scheduling, approvals, updates | Logistics that pull attention away from tenants and prospects |
None of this needs judgment most of the time. It needs a fast, accurate, on-policy reply, which is exactly what software should handle so your team can focus on turns, showings, and the tenants who genuinely need a person.
## Your property software runs the portal, not the inbox
Here is the blind spot in the property management stack. AppFolio, Buildium, and their peers are excellent at what they do: accounting, listings syndication, online rent, and a tenant portal. Search for property management automation and you will find those platforms plus a layer of email-marketing tools for sending newsletters and nurture campaigns to owners and prospects.
Almost none of it answers the inbound email.
So the typical growing property manager has a polished portal for the tenants who use it and a completely manual Gmail or Outlook inbox for everyone who just emails, which is most people. Prospects and tenants overwhelmingly reach for email and web forms because they are easy: type it once, send it, get an answer. That is the channel the software stack forgot, and it is where the leasing and renewal decisions actually happen.
That is the gap InboxPilot fills. It does not replace your property management software. It sits in the leasing@ or maintenance@ inbox alongside it and does for inbound email what the portal never did: reads every message, drafts a grounded reply, flags the urgent ones, and hands a manager the final click.
## What AI can take off your plate
An AI email assistant grounded in your own policies can absorb the repetitive layer of that inbox:
- **Triage on arrival.** Every email is read and sorted: emergency maintenance, routine work order, new leasing inquiry, existing-tenant question, vendor, owner. No-heat and no-water float to the top instead of waiting behind a newsletter.
- **Drafts from your own policies.** Point it at your availability, pet and application rules, rent and late-fee policy, maintenance process, and renewal options, and it drafts replies grounded in your real answers. A leasing inquiry comes back with the actual availability, your pet policy, and a prompt to apply or book a tour.
- **Instant acknowledgement.** Even when a request needs a human, the tenant or prospect gets an immediate, on-brand reply so they are not left in silence, which is what keeps a prospect from signing elsewhere and a tenant from escalating.
- **Routing and escalation.** A suspected emergency, an eviction thread, or a legal question gets flagged and routed to the right person rather than auto-answered.
- **It runs where your team works.** No new platform. Inside the shared Gmail or Outlook inbox your leasing and maintenance staff already use.
## The workflow: from new tenant email to approved reply
1. A leasing inquiry lands in the leasing inbox at 9 p.m.
2. InboxPilot reads it, recognizes an availability-and-pets question, and checks your current availability and pet policy.
3. It drafts a reply confirming the unit is available, stating your pet policy, and linking the application and tour booking, in your company's tone.
4. It labels the thread "Leasing, needs approval" and surfaces it at the top of the inbox.
5. Your leasing agent skims the draft first thing in the morning, or that evening, and sends, hours before a slower competitor replies.
## Keep a human on leases, money, and notices
The guardrail is simple: anything that touches a lease commitment, a payment arrangement, or a legal notice stays draft-and-approve, and disputes, evictions, and legal questions route straight to a person and skip automation entirely. AI handles the reading, sorting, and first draft, the part that eats the hours, and leaves the decisions that carry consequences to the people who should make them.
## Related reading
- [Booking request automation](/use-cases/booking-request-automation): how showing and appointment enquiries get drafted the moment they arrive.
- [How real estate agents close more deals with a 60-second reply system](/blog/why-inboxpilot-real-estate-brokers-in-2026): the same speed-to-lead problem, agent side.
- [How to automate email support](/blog/ai-email-agent): the general playbook for a repetitive inbox.
- [InboxPilot pricing](/pricing): plans, draft quotas, and what a property team actually pays.
---
*InboxPilot is the publisher of this article and drafts replies with a human approving every send. It complements, and does not replace, your property management platform.*
For the full picture of how this works across maintenance, leasing, and owner communication, see [AI email automation for property management](/industries/property-management).
---
## How to Automate WISMO Order Status Emails on Shopify
Source: https://www.inboxpilot.co/blog/automate-order-status-emails-shopify
Published: 2026-07-22
WISMO is one of ecommerce's most common support requests. Here is how to auto-draft order status replies from your Shopify data, inside Gmail.
It is the email every store gets a hundred times a week. "Hi, just checking in, where is my order?" The customer bought three days ago, the package is in transit, and answering means opening the Shopify admin, finding the order, copying the tracking, and typing a friendly reply. Multiply that by every shipment that runs a day late during a sale, and a single question is eating a real share of your support hours.
That question has a name: WISMO, short for "where is my order." This guide walks through what WISMO is, why handling it by hand is so slow, and how to auto-draft accurate order status replies straight from your Shopify data without leaving Gmail or Outlook.
**Disclosure:** we make [InboxPilot](/industries/shopify-support), an AI email agent that drafts replies inside Gmail and Outlook, grounded in your own store data and policies, with a person approving each send. This post explains the general approach to WISMO automation and shows how InboxPilot does it.
## TL;DR
- **WISMO is the order status question**, and it is one of the most common emails an ecommerce store gets. See [what it is](#what-wismo-is-and-why-it-floods-your-inbox).
- **Handling it by hand is slow**, and slow replies cost sales, since customers now expect fast answers. See [why manual replies fall behind](#why-manual-order-status-replies-fall-behind).
- **You can automate it in your own inbox.** [InboxPilot](#how-to-automate-wismo-emails-in-gmail-and-outlook), which is us, connects Shopify, detects the WISMO email, pulls the order and tracking, and drafts the status update inside Gmail or Outlook. See [how to set it up](#how-to-automate-wismo-emails-in-gmail-and-outlook).
- **A human stays in control.** Drafts wait for review by default, and you decide which low-risk updates auto-send. See [what to keep a human on](#what-to-keep-a-human-on).
## What WISMO is and why it floods your inbox
WISMO is the "where is my order" email: the status check a customer sends after they buy. Has it shipped, where is it now, and when will it land. Shopify calls it [one of the most common types of customer inquiries for ecommerce merchants](https://www.shopify.com/blog/wismo-ecommerce), and it is easy to see why. Every order creates a window between purchase and delivery, and any friction in that window, a late scan, a quiet carrier, a missed notification, turns into an email.
Shipping visibility is not a nice-to-have to shoppers either. In the same guide, Shopify notes that [69% of consumers feel real-time order tracking is a top factor](https://www.shopify.com/blog/wismo-ecommerce) when they shop online. When they cannot see where their package is, they ask you. And the volume is not flat: it spikes exactly when you are busiest, during launches, promotions, and the holiday rush, when more orders and stretched carriers push more shipments past their promised date.
The frustrating part is that almost every WISMO answer already exists. The order, its status, and the tracking are sitting in your Shopify admin. The work is not deciding what to say. It is the lookup and the retype, over and over.
## Why manual order status replies fall behind
The manual loop looks harmless for one email and brutal at scale. An agent reads the message, switches to Shopify, searches the order by name or email, opens it, checks fulfillment status, copies the tracking link, switches back to the inbox, and writes a warm reply. Two or three minutes each, hundreds of times a week.
Speed is where it hurts. Customer patience for support email is thin, and most stores miss it. SuperOffice studied company response times and found that [62% of businesses never respond to customer emails at all](https://www.superoffice.com/blog/response-times/), with an average response time of over 12 hours, while nearly half of customers expect a reply within four hours. A slow or missing WISMO answer does not just annoy one shopper. Shopify reports that [44% of US consumers stopped shopping with a company after one poor customer service experience](https://www.shopify.com/blog/wismo-ecommerce), so a backed-up inbox during your busiest week is a direct hit to repeat revenue.
The usual fix is to install a separate helpdesk app, move your team into it, and pay by the ticket. That works for some stores, but it is a lot of platform to solve what is, at heart, an inbox and a data lookup. There is a lighter path.
## How to automate WISMO emails in Gmail and Outlook
The goal is to close the loop automatically: recognize the WISMO email, fetch the exact order and tracking from Shopify, and put a ready-to-send reply in the inbox you already use. With InboxPilot the setup is a plain-English rule rather than a rules engine you have to program.
You write something like this:
> When a customer emails asking where their order is, look up the order in Shopify, draft a friendly status update with the latest tracking and estimated delivery date, and send it for my review.
From then on, InboxPilot reads incoming mail, classifies the "where is my order" messages, matches each one to the [Shopify order](/integrations/shopify) behind it, and drafts a reply grounded in that order's real status. Because the draft is built from live data, it references the actual items, the current fulfillment status, and the latest tracking, not a generic template. You review and send, or let trusted cases go out on their own.
## A WISMO reply, drafted from the Shopify order
Here is what the loop looks like in practice. The customer sends this:
> Subject: Order #10432
>
> Hi, I ordered the merino crew (navy, medium) last Friday and I have not seen a shipping update. Can you tell me where it is? Hoping to have it before the weekend. Thanks, Dana
InboxPilot matches it to the order, reads the fulfillment status and tracking, and drafts this for the agent to approve:
> Hi Dana,
>
> Thanks for checking in, and good news: your merino crew (navy, medium) on order #10432 shipped Monday and is on its way. The carrier's latest scan has it in your regional facility, with delivery estimated for Thursday, so you should have it comfortably before the weekend.
>
> You can follow it live here: [tracking link]. If anything looks off with that estimate, just reply and I will jump back in.
>
> Best,
> The [Store] team
The agent scans it, sees it is right, and sends. What took two or three minutes of admin-hopping becomes a five-second review, and on the workflows you trust, it can skip the review entirely.
## Set it up in three steps
1. **Connect your store.** Authorize a scoped [Shopify connection](/integrations/shopify) so InboxPilot can look up orders, tracking, and customers behind each email.
2. **Add your policies.** Connect your shipping, returns, and refund policies so drafts follow your store's rules when a WISMO turns into a delay or a replacement.
3. **Describe the workflow.** Write the plain-English rule above. InboxPilot runs it on incoming mail and starts drafting order status replies in your inbox.
Most stores are connected and seeing their first order-grounded draft in [under two minutes](/industries/shopify-support).
## What to keep a human on
Automating WISMO does not mean sending on autopilot for everything. The clean cases, package in transit with good tracking, are perfect for a fast draft or an auto-send. The messy ones are not, and they should reach a person:
- A tracking number that has not scanned in days, or a package marked delivered that the customer says never arrived.
- An order past its promised delivery window, where the right answer may be a reship or a refund, not just a status.
- A customer who is clearly upset, or a high-value order where tone and judgment matter.
InboxPilot keeps every draft under review by default and lets you flag these exceptions for a human even after you turn on auto-send for the routine cases. You get speed on the 80% that is simple and keep judgment on the 20% that is not.
## Try it on your own inbox
WISMO is the easiest ecommerce email to automate well, because the answer already lives in your store. Connect Shopify, write one plain-English rule, and let the status updates draft themselves while you keep the inbox you already run on.
[Try InboxPilot free](https://www.inboxpilot.co/) with 25 AI drafts, no helpdesk migration required.
## Related resources
- [Order status email automation](/use-cases/order-status-email-automation): the platform-agnostic version of this workflow for any Gmail or Outlook inbox.
- [AI Customer Support for Your Shopify Store](/industries/shopify-support)
- [InboxPilot + Shopify: Order-Aware Support Replies](/integrations/shopify)
- [Returns and Refund Email Automation for Ecommerce](/blog/ecommerce-returns-refund-email-automation)
- [The Best Gorgias Alternative for Ecommerce Support](/blog/gorgias-alternative)
---
## Best Shared Inbox for Gmail in 2026: 8 Tools Ranked
Source: https://www.inboxpilot.co/blog/best-shared-inbox-for-gmail
Published: 2026-07-22
The best shared inbox for Gmail in 2026, ranked native vs connected: Hiver, Gmelius, Missive, Front, and Google's free option. Year one runs $0 to $3,900.
Search "best shared inbox for Gmail" and most articles lump together tools that live inside Gmail and tools that merely connect to it, as though those were the same purchase. They are not, and the difference is the single most important thing to get right if you are committed to staying in Gmail.
This roundup splits the field on exactly that line: does the tool run inside the Gmail window you already use, or does it pull your mail into a separate app? Where a limit exists, it is cited from Google's own documentation. Where a tool has a real weakness, we name it, including our own.
**Disclosure:** we make InboxPilot, and it is our top pick. It earns that spot for a specific reason rather than by default: most teams shopping this category are actually trying to fix volume, and InboxPilot is the only tool here that reduces how much email reaches humans instead of helping humans divide it faster. It works differently from a classic shared inbox, and its entry below states exactly what it does not do. If your problem is coordination, two teammates replying to the same customer, the classic Gmail-native pick is Hiver, and we say that plainly too.
## TL;DR
- **Best overall:** [InboxPilot](#1-inboxpilot). Native in Gmail (and Outlook too), it reduces email volume instead of dividing it, priced per workspace rather than per seat.
- **Best classic Gmail shared inbox:** [Hiver](#2-hiver). Runs inside Gmail, free tier, near-zero onboarding.
- **Best free option:** [Google's own native shared inbox](#3-googles-native-shared-inbox). Free on Workspace, in real Gmail, and almost nobody knows it shipped.
- **Cheapest Gmail-native paid tool:** [Gmelius](#4-gmelius) at $19, if nobody on your team touches Outlook.
- **Best for co-writing replies:** [Missive](#5-missive). Real-time collaborative drafting from $14 per user.
- **Best for support teams:** [Help Scout](#6-help-scout). Shared inbox plus knowledge base, free for 5 users.
- **Most complete classic product:** [Front](#7-front). Deep coordination and analytics, but it connects to Gmail rather than living in it, and the real plan is $65.
## First, the distinction that decides everything: native vs connected
Almost every regretted purchase in this category comes from missing one line.
| Type | What it means | Onboarding | Examples |
|---|---|---|---|
| **Native in Gmail** | Runs as a sidebar inside the Gmail window you already use | Near zero, no new app | Hiver, Gmelius, Google's native inbox, InboxPilot |
| **Connects to Gmail** | Pulls your Gmail into its own separate interface | Real, it is a new app | Front, Missive, Help Scout |
Neither is automatically better. Native wins on adoption because your team never leaves the tool they already know. Connected apps usually win on analytics depth and, crucially, on Outlook support, so a mixed Gmail and Outlook team should think hard before going native. If you are all-Gmail and want your team to actually adopt the thing, native is the safer bet.
## Rule out free before you buy anything
Two genuinely free options solve the "several of us need to see support@" problem without a purchase, and one of them is new enough that most competing articles have not caught up.
### Google now has a native shared inbox, and it is free
Google Workspace admins can create a shared email address directly from the Admin console (Users, then "Set up a shared email address"). Unlike the old Collaborative Inbox, it lives in **real Gmail**, not the Google Groups web interface, so it shows up in the Gmail mobile app too. It is included on Business Starter, Standard, and Plus with no paid add-on. ([Google Workspace admin docs](https://knowledge.workspace.google.com/admin/users/create-a-shared-inbox))
It gives you access and sending from the shared address. It gives you **no collision detection, no automation, and no SLA reporting.** It solves access, not coordination. But if that is your whole problem, it is free and it is enough.
### Gmail's concurrency ceiling is worth knowing
Google's native shared inbox is built on Gmail delegation, and delegation has documented limits: up to 1,000 delegates on paper, but **only around 40 can access the account simultaneously** under typical use, and Google notes that "above-average use by one or more delegates might reduce this number." Browser extensions that poll Gmail frequently reduce it further. ([Google Workspace admin docs](https://knowledge.workspace.google.com/admin/gmail/let-users-delegate-access-to-a-gmail-account))
That detail matters here, because Hiver and Gmelius are both Gmail extensions that poll the account.
**The honest summary:** a plain shared address is genuinely fine at two or three people and low volume. The real breaking point comes the first time two teammates answer the same thread without realizing the other already did. That is coordination, and free tools do not solve it.
## The comparison table
| Tool | Best for | Runs where | Free tier | Entry price | Outlook too? |
|---|---|---|---|---|---|
| **InboxPilot** | Best overall (AI email layer) | Inside Gmail | Yes | $29/mo flat | Native in both |
| **Hiver** | Gmail teams | Inside Gmail | Yes | $25/user/mo annual | Via separate Omni app only |
| **Google native shared inbox** | Free access | Inside Gmail | Free | $0 | No |
| **Gmelius** | Gmail-only budget | Inside Gmail | No | $19/user/mo annual | **No** |
| **Missive** | Co-writing replies | Separate app | Undocumented | $14/user/mo | Connects |
| **Help Scout** | Support teams | Separate app | Yes, 5 users | $25/user/mo | Connects |
| **Front** | Most complete classic tool | Separate app | No | From $25/seat/mo | Connects (sync caveats) |
Pricing verified against vendor pricing pages in July 2026.
## The best shared inbox tools for Gmail, ranked
### 1. InboxPilot
**Best for:** Gmail teams whose real problem is *volume*, and anyone who wants relief without leaving the Gmail they already use.
Read this section knowing we wrote it. InboxPilot takes the top spot for one reason: **every other tool on this list helps your team split the Gmail workload faster. InboxPilot cuts how much of it reaches a person in the first place.** It is an AI layer that triages, labels, and drafts replies inside the Gmail you already use, and in our experience most teams searching for a shared inbox are trying to fix volume, not coordination.
**Strengths**
- Native in Gmail, and in Outlook too, which no other Gmail-native tool here manages (Gmelius is Gmail-only, Hiver needs a separate product for Outlook).
- AI drafts grounded in your own docs, help center, and connected tools like Shopify, Notion, and Pipedrive.
- Smart triage, auto-labeling, and plain-English email workflows.
- Priced per workspace by AI draft volume, not per seat, so it does not get more expensive as your team grows.
- No migration. It layers onto the Gmail you already have, including Google's free native shared inbox.
**Tradeoffs, stated plainly**
- **It is not a classic shared inbox.** No teammate assignment, no collision detection, no internal notes, no SLA reporting. If your problem is two agents replying to the same customer, pair it with Hiver, Missive, or Help Scout, or pick one of those instead.
- **Cost scales with email volume, not headcount.** Cheaper for a big team with modest volume, more expensive for a small team drowning in mail. Do the math on your actual volume first.
- Newer, with a shorter public review record than the incumbents.
**Pricing:** Free (25 AI drafts, 1 inbox). Hobby $29/mo. Standard $149/mo (1,500 drafts, unlimited inboxes). Pro $499/mo. Enterprise custom. Annual billing is about 20% less, so Standard is $119/mo on a yearly plan. Per workspace, not per seat. ([inboxpilot.co/pricing](/pricing))
**When it makes the most sense:** you are on Google's plain shared inbox and want relief without a migration, or you run Hiver and want the repetitive volume deflected before it reaches a human. It pairs with any shared inbox below, and for a lot of teams it removes the reason to buy one.
### 2. Hiver
**Best for:** Google Workspace teams who will not leave Gmail, and should not have to. The classic Gmail-native shared inbox.
**Strengths**
- Genuinely native to Gmail, running as a sidebar. Onboarding is close to zero because there is no new app to learn.
- **Free forever tier** that includes a shared inbox, which is rare.
- Collision detection, assignment, and SLA basics.
- Clean pricing ladder with no surprises: Free, $25, $55, $85.
**Tradeoffs**
- **Performance is the recurring complaint.** Reviewers frequently report slow loading under volume and having to refresh the browser to bring Hiver back.
- Outlook is not supported in the Gmail product. Microsoft users need Hiver Omni, a separate standalone app rather than an Outlook add-in.
- Analytics are thinner than a full help desk.
**Pricing:** Free forever. Growth $25 per user per month annual ($35 monthly), Pro $55, Elite $85. ([hiverhq.com/pricing](https://hiverhq.com/pricing/hiver-in-gmail))
Full head-to-head: [Hiver vs InboxPilot](/blog/hiver-inboxpilot).
### 3. Google's native shared inbox
**Best for:** Google Workspace teams who want a shared address in real Gmail, for free, and do not yet need coordination features.
**Strengths**
- **Free** on Business Starter, Standard, and Plus, with no add-on.
- Lives in actual Gmail, unlike the old Collaborative Inbox, which lived in the Google Groups interface and never appeared in the Gmail mobile app.
- Sends from the shared address, with a "sent by" attribution you can hide.
**Tradeoffs**
- **No collision detection, no automation, no SLA reporting.** It solves access, not coordination.
- Inherits Gmail's delegation ceilings (roughly 40 concurrent delegates, reduced further by extensions).
- Rolling out in phases, so it may not be in your Admin console yet.
**Pricing:** $0, included with Workspace. ([Google Workspace admin docs](https://knowledge.workspace.google.com/admin/users/create-a-shared-inbox))
### 4. Gmelius
**Best for:** Small Google Workspace teams who want a shared inbox plus Kanban boards, at the lowest Gmail-native price.
**Strengths**
- Cheapest true Gmail-native entry at $19 per user per month.
- Kanban and Trello-style boards on top of email, an unusual and genuinely useful combination.
- Shared labels, internal notes, and sequences.
**Tradeoffs**
- **Gmail only. No Outlook, at all.** One Outlook user on your team disqualifies this tool entirely. Confirmed on Gmelius's own pricing page.
- **Speed complaints are persistent.** Users frequently report slow Gmail load times with the extension active, along with Chrome extension bugs.
- The mobile app is a frequently cited weak point.
- No free tier, and only a 7-day trial, which is not long enough to roll a shared inbox out to a team.
**Pricing:** Meli $19 per user per month annual ($21 monthly), Growth $25, Pro $40, Enterprise custom. ([gmelius.com/pricing](https://gmelius.com/pricing))
Also see: [Gmelius vs InboxPilot](/blog/gmelius-inboxpilot).
### 5. Missive
**Best for:** Teams that want to discuss and co-write replies inside the thread instead of copying them into Slack.
Missive connects to Gmail rather than living inside it, but it earns its place because nothing here matches its collaborative drafting.
**Strengths**
- **Cheapest serious entry point at $14 per user per month.**
- Real-time collaborative drafting is genuinely differentiated. Two people can write one reply together, live.
- Broad channel support: Gmail, Outlook, IMAP, WhatsApp, Messenger, Instagram, SMS via Twilio.
- Provider-agnostic, so it works the same whether you are on Google or Microsoft.
**Tradeoffs**
- Starter caps at 5 users. The realistic plan for a growing team is Productive at $24.
- **The learning curve is the most common complaint.** It is a genuinely new paradigm, and teams coming from plain Gmail need a few weeks to settle in.
- It is a separate app, so you lose the "never leave Gmail" advantage.
**Pricing:** Starter $14 per user per month (up to 5 users), Productive $24 (up to 50), Business $36 (unlimited). A free plan is referenced but its limits are not published, so confirm before relying on it. ([missiveapp.com/pricing](https://missiveapp.com/pricing))
Also see: [Missive vs InboxPilot](/blog/missive-inboxpilot).
### 6. Help Scout
**Best for:** Customer support teams that want a shared inbox plus a knowledge base, without Zendesk's weight.
**Strengths**
- **Free tier with 5 users**, one inbox, and one Docs site.
- The cleanest, easiest interface of any support tool here.
- Built-in knowledge base, so you are not buying a second product.
- AI Answers is priced per resolution ($0.75) rather than per seat, which is buyer-friendly.
**Tradeoffs**
- **Reporting is basic** compared to Zendesk or Freshdesk, and custom report history is gated to higher tiers.
- It connects to Gmail as a separate app, not a sidebar.
- Extra inboxes cost $10 per month each, and Pro requires a 10-user minimum.
**Pricing:** Free (5 users, 1 inbox). Standard $25 per user per month, Plus $45, Pro $75. ([helpscout.com/pricing](https://www.helpscout.com/pricing/))
Also see: [Help Scout vs InboxPilot](/blog/helpscout-vs-inboxpilot).
### 7. Front
**Best for:** Mid-market and larger teams that want the most complete product and can pay for it.
Front is the most complete classic shared inbox in this roundup. It ranks seventh *for Gmail teams specifically* only because it connects to Gmail as a separate app rather than living inside it, which undercuts the exact advantage a committed-Gmail team is optimizing for.
**Strengths**
- Mature collision detection and assignment, the two things you are actually buying.
- Deep integration catalog including Salesforce and HubSpot.
- Strong analytics, genuinely better than the rest of this list.
**Tradeoffs**
- **The advertised price is not the real price.** Starter at $25 per seat is limited to a single channel type. The plan most teams actually need is Professional at **$65 per seat per month**, and Enterprise is $105.
- Separate app, so no native-Gmail adoption advantage.
- AI is an add-on: Copilot at $20 per seat per month, Autopilot from $0.05 per conversation.
**Pricing:** Starter $25 per seat per month annual (up to 10 seats), Professional $65, Enterprise $105. No free tier, 14-day trial. ([front.com/pricing](https://front.com/pricing))
Full head-to-head: [InboxPilot vs Front](/inboxpilot-vs-front).
### 8. Other Gmail-native options worth a look
Two lighter Gmail-native tools come up often and are worth a trial if the above feel too heavy:
- **Drag** turns Gmail into a shared Kanban board and is one of the lightest-weight options. Gmail-only, no free plan (7-day trial). Starter $12, Plus $18, Pro $24 per user per month billed annually ($16, $22, $30 monthly). ([dragapp.com/pricing](https://www.dragapp.com/pricing/))
- **Keeping** adds help-desk-style shared inbox and ticketing inside Gmail, aimed at small support teams. Gmail-only, 2-user minimum, no free plan (14-day trial). Essentials $14, Advanced $24, HIPAA $49 per user per month billed annually. ([keeping.com/pricing](https://www.keeping.com/pricing/))
Both are Gmail-only, so cross them off immediately if anyone on your team is on Outlook.
## What a 5-person Gmail team actually pays in year one
Advertised entry prices mislead, so here is the real number for a five-person team, at list price, billed annually.
| Tool | Plan needed for 5 people | Monthly | Year one |
|---|---|---|---|
| Google native shared inbox | Included with Workspace | $0 | **$0** |
| Hiver | Free tier, or Growth at $25 | $0 to $125 | **$0 to $1,500** |
| Help Scout | Free (5 users), or Standard $25 | $0 to $125 | **$0 to $1,500** |
| Missive | Starter $14 (caps at exactly 5) | $70 | **$840** |
| Gmelius | Meli $19 | $95 | **$1,140** |
| InboxPilot | Standard $119 flat | $119 | **$1,428** |
| Front | Starter $25, single channel | $125 | **$1,500** |
| Front (Professional, realistic) | $65 | $325 | **$3,900** |
Front's real cost is closer to $3,900 than the $1,500 its entry tier implies. And several genuinely capable options here cost nothing at five people, which is the point: rule out free before you spend.
## How to choose a shared inbox for Gmail
### 1. Rule out free first
If you are two or three people, Google's native shared inbox or Hiver's free tier may genuinely be enough. Paying $1,500 a year to solve a problem you do not have yet is the most common mistake in this category.
### 2. Decide how much you care about staying inside Gmail
If adoption is your risk, go native (Hiver, Gmelius) so nobody has to learn a new app. If analytics depth matters more, a connected app (Front, Help Scout) is worth the context switch.
### 3. Check whether anyone touches Outlook
Gmelius has no Outlook support at all, and Hiver's Gmail product does not either. If even one teammate is on Microsoft, that removes options before you compare a single feature. See the companion guide: [best shared inbox for Outlook](/blog/best-shared-inbox-for-outlook).
### 4. Separate the volume problem from the coordination problem
These are two different problems. Assignment and collision detection solve coordination and do nothing for sheer volume. AI drafting solves volume and does nothing for coordination. Work out which one is actually hurting before you shop.
## How to choose, in one paragraph
Start with the diagnosis, not the tool. If the honest answer is that nobody is stepping on anyone's toes, there is just too much email, that is a volume problem and [InboxPilot](/pricing) is our pick, on its own or alongside whichever shared inbox you land on. If you are two or three people on Workspace, turn on **Google's native shared inbox** and spend nothing. If you are a Gmail team that wants real coordination with the least friction, **Hiver** is the lowest-effort upgrade and has a free tier. If you want Kanban boards on top and nobody uses Outlook, **Gmelius**. If you want to co-write replies live, **Missive**. If you want a support tool with a knowledge base, **Help Scout**. And if you want the most complete classic shared inbox and can accept a separate app, **Front** at its real price.
## Related reading
- [Best shared inbox software for Gmail and Outlook](/blog/best-shared-inbox-software): the full category, both platforms, including help desks.
- [Best shared inbox for Outlook](/blog/best-shared-inbox-for-outlook): the Microsoft-side companion to this guide.
- [Hiver vs InboxPilot](/blog/hiver-inboxpilot), [Gmelius vs InboxPilot](/blog/gmelius-inboxpilot), [Missive vs InboxPilot](/blog/missive-inboxpilot): the direct comparisons.
- [How to automate email support](/blog/ai-email-agent): what to automate once your inbox is organized.
- [RFQ and quote request automation](/use-cases/rfq-email-automation): how quote requests get read, priced, and answered from your own catalog.
---
*Pricing verified against vendor pricing pages in July 2026 and stated per user per month unless noted. Platform limits are cited from Google's own administrator documentation. Vendors change pricing frequently, so confirm current rates before purchasing. InboxPilot is the publisher of this article and is one of the tools discussed.*
---
## Best Shared Inbox for Outlook in 2026: What Works with M365
Source: https://www.inboxpilot.co/blog/best-shared-inbox-for-outlook
Published: 2026-07-22
Best shared inbox for Outlook in 2026: most tools are Gmail-first and treat Outlook as an afterthought. What actually works with M365, past its 25-user cap.
Here is the thing nobody tells you when you search "best shared inbox for Outlook": most of the tools that dominate these lists were built for Gmail first. Some added Outlook years later. One of the most popular, Gmelius, still does not support Outlook at all. Another, Hiver, runs inside Gmail and pushes Outlook users to a separate product entirely. Even the best all-rounder documents that its Outlook read-status sync is conditional.
So this guide is organized around the question a Microsoft team actually needs answered: what genuinely works with Outlook, and where are the caveats hiding? Where a limit exists, it is cited from Microsoft's own documentation.
**Disclosure:** we make InboxPilot, and it is our top pick. It earns that spot for a specific reason rather than by default: most Microsoft teams shopping this category are actually trying to fix volume, and InboxPilot is the only tool here that reduces how much email reaches humans instead of helping humans divide it faster, natively inside Outlook, which several better-known tools cannot claim. It works differently from a classic shared inbox, and its entry below states exactly what it does not do. If your problem is coordination, two agents replying to the same customer, the classic shared inbox to beat is Front, with the sync caveat noted, and we say that plainly too.
## TL;DR
- **Best overall:** [InboxPilot](#1-inboxpilot). The only tool here that reduces email volume instead of dividing it, native inside Outlook, priced per workspace rather than per seat.
- **Best free option:** [the Microsoft 365 shared mailbox](#2-microsoft-365-shared-mailbox). Native in Outlook, free, with documented ceilings.
- **Best classic shared inbox:** [Front](#3-front). The most complete coordination product, but read its Outlook sync caveat first, and the real plan is $65.
- **Cheapest provider-agnostic option:** [Missive](#4-missive) at $14 per user, treats Outlook and Gmail equally.
- **Best for support teams:** [Help Scout](#5-help-scout). Shared inbox plus knowledge base, free for 5 users.
- **When you have outgrown a shared inbox:** [Zendesk](#6-zendesk) or [Freshdesk](#7-freshdesk), real help desks.
- **Cross these off if you are on Outlook:** Gmelius (Gmail only) and Hiver's main Gmail product.
## Read this first: the Outlook support map
The single most useful thing on this page is knowing, before you compare features, which tools actually treat Outlook as a first-class citizen.
| Tool | Outlook support | Reality |
|---|---|---|
| **Microsoft 365 shared mailbox** | Native | Built into Outlook, free, documented ceilings |
| **Missive** | Full | Provider-agnostic, Outlook and Gmail treated equally |
| **Front** | Yes, with caveats | Read-status sync is conditional, Front documents this |
| **Help Scout** | Connects | Separate app, works the same for any provider |
| **Zendesk / Freshdesk** | Connects | Help desks, provider-agnostic by design |
| **Hiver** | Omni only | Main product is Gmail-only; Outlook needs a separate app |
| **Gmelius** | **None** | Gmail only, confirmed on its own pricing page |
| **InboxPilot** | Native | Runs inside Outlook and Gmail both |
If a tool is not on this list, assume it started life as a Gmail extension and verify Outlook support directly with the vendor before you get attached.
## Start with free: the Microsoft 365 shared mailbox
Every listicle skips straight to paid tools. On Microsoft, you should rule out the free native option first, because for a low-volume address it is genuinely enough, and it is already included in your subscription.
### Where the M365 shared mailbox breaks, in Microsoft's own words
This is the best-sourced fact on this page, straight from Microsoft's admin documentation:
> "A shared mailbox supports a maximum of 25 users. If too many users access the mailbox at the same time, they might experience connection failures or duplicated messages."
> ([Microsoft Learn, About shared mailboxes](https://learn.microsoft.com/en-us/microsoft-365/admin/email/about-shared-mailboxes))
Duplicated messages means two agents answering the same customer. That is the platform vendor naming the failure mode in its own docs, which is far more credible than a shared inbox company telling you shared mailboxes are bad.
The other documented limits are worth knowing before you rely on one:
- **50 GB cap** without an Exchange Online Plan 2 license. On hitting it, the mailbox stops sending, then stops receiving.
- **No encryption.** Mail from a shared mailbox cannot be encrypted, because the mailbox has no security context of its own.
- **You cannot prevent users from deleting messages.**
- **No external access.** A contractor on an outside domain cannot be given access.
**The honest summary:** the M365 shared mailbox is fine for a handful of people on a low-volume info@ or reception@ address, and it is free. The real breaking point arrives well before the 25-user ceiling, the first time two people answer the same message because Outlook gave neither of them any signal the other was already on it. That is coordination, and the free mailbox does not do coordination.
## The comparison table
| Tool | Best for | Outlook support | Free tier | Entry price |
|---|---|---|---|---|
| **InboxPilot** | Best overall (AI email layer) | Native | Yes | $29/mo flat |
| **M365 shared mailbox** | Free, low volume | Native | Free | $0 |
| **Front** | Classic shared inbox | Yes (sync caveats) | No | From $25/seat/mo |
| **Missive** | Provider-agnostic | Full | Undocumented | $14/user/mo |
| **Help Scout** | Support teams | Connects | Yes, 5 users | $25/user/mo |
| **Zendesk** | Outgrown the category | Connects | No | $19 Support, $55 Suite |
| **Freshdesk** | Budget ticketing | Connects | 6 months only | $19/agent/mo annual |
| **Hiver Omni** | Hiver users on Outlook | Separate web workspace | Yes | Free / from $25/user/mo |
Pricing verified against vendor pricing pages in July 2026.
## The best shared inbox tools for Outlook, ranked
### 1. InboxPilot
**Best for:** Outlook teams whose real problem is *volume*, and anyone who wants relief without leaving Outlook.
Read this section knowing we wrote it. InboxPilot takes the top spot for one reason: **every other tool here helps a team share the Outlook workload. InboxPilot shrinks the workload itself, before it reaches anyone.** It is an AI layer that triages, labels, and drafts replies inside the Outlook you already use, and in our experience most Microsoft teams searching for a shared inbox are trying to fix volume, not coordination.
**Strengths**
- **Native in Outlook** and in Gmail both, which several better-known tools here cannot claim (Gmelius has no Outlook at all, Hiver needs the separate Omni app).
- AI drafts grounded in your own docs, help center, and connected tools like Shopify, Notion, and Pipedrive.
- Smart triage, auto-labeling, and plain-English email workflows.
- Priced per workspace by AI draft volume, not per seat, so it does not get more expensive as your team grows.
- No migration. It layers onto the mailbox you already have, including the free M365 shared mailbox.
**Tradeoffs, stated plainly**
- **It is not a classic shared inbox.** No teammate assignment, no collision detection, no internal notes, no SLA reporting. If your problem is two agents replying to the same customer, pair it with Front, Missive, or Help Scout, or pick one of those instead.
- **Cost scales with email volume, not headcount.** Cheaper for a big team with modest volume, more expensive for a small team drowning in mail. Do the math on your actual volume first.
- Newer, with a shorter public review record than the incumbents.
**Pricing:** Free (25 AI drafts, 1 inbox). Hobby $29/mo. Standard $149/mo (1,500 drafts, unlimited inboxes). Pro $499/mo. Enterprise custom. Annual billing is about 20% less, so Standard is $119/mo on a yearly plan. Per workspace, not per seat. ([inboxpilot.co/pricing](/pricing))
**When it makes the most sense:** you are on a plain M365 shared mailbox and want relief without a migration, or you already run Front and want the repetitive volume deflected before it reaches a human. It pairs with any shared inbox below, and for a lot of Outlook teams it removes the reason to buy one.
### 2. Microsoft 365 shared mailbox
**Best for:** Microsoft shops with a low-volume info@ or reception@ address and a handful of people on it.
**Strengths**
- **Free.** No license required on the mailbox itself.
- Native in Outlook desktop, web, and mobile. Automapping means it simply appears.
- Includes a shared calendar.
**Tradeoffs**
- **25-user maximum, with "connection failures or duplicated messages" beyond it,** per Microsoft's own docs.
- 50 GB hard stop without an Exchange Online Plan 2 license.
- No encryption, no way to prevent deletion, no external users.
- No assignment, no collision detection, no reporting.
**Pricing:** $0. ([Microsoft Learn](https://learn.microsoft.com/en-us/microsoft-365/admin/email/about-shared-mailboxes))
### 3. Front
**Best for:** Mid-market and larger teams that want shared inbox ergonomics with serious integrations and analytics.
Front is the most complete classic shared inbox that connects to Outlook. If your diagnosis is coordination rather than volume, this is the tool to beat, with one caveat every Microsoft team should read before buying.
**Strengths**
- Mature collision detection and assignment, the two things you are actually buying.
- Deep integration catalog including Salesforce and HubSpot.
- Strong analytics, genuinely better than the rest of this list.
**Tradeoffs**
- **Outlook sync is conditional, and Front documents this itself.** Read status syncs only for personal channels, and for shared conversations only once the assignee reads it. In-place archive mailboxes do not sync at all. Mixed Front and Outlook teams get confused by this. ([Front help docs](https://help.front.com/en/articles/205376))
- **The advertised price is not the real price.** Starter at $25 per seat is single-channel. The plan most teams need is Professional at **$65 per seat per month**, and Enterprise is $105.
- AI is an add-on: Copilot at $20 per seat per month, Autopilot from $0.05 per conversation.
**Pricing:** Starter $25 per seat per month annual (up to 10 seats), Professional $65, Enterprise $105. No free tier, 14-day trial. ([front.com/pricing](https://front.com/pricing))
Full head-to-head: [InboxPilot vs Front](/inboxpilot-vs-front).
### 4. Missive
**Best for:** Teams that want a shared inbox that treats Outlook and Gmail as genuine equals, at the lowest paid entry price.
Missive is the strongest answer to this list's core problem, because it is provider-agnostic by design. It does not care whether you are on Microsoft or Google, so Outlook is not a bolt-on.
**Strengths**
- **The lowest paid entry point here, $14 per user per month.**
- Provider-agnostic, so Outlook gets the same treatment as Gmail.
- Real-time collaborative drafting: two people can write one reply together, live.
- Broad channel support: Outlook, Gmail, IMAP, WhatsApp, Messenger, Instagram, SMS via Twilio.
**Tradeoffs**
- Starter caps at 5 users. The realistic plan for a growing team is Productive at $24.
- **The learning curve is the most common complaint.** It is a new paradigm and takes a few weeks to settle in.
- Some users report occasional duplicate-thread and snooze confusion.
**Pricing:** Starter $14 per user per month (up to 5 users), Productive $24 (up to 50), Business $36 (unlimited). A free plan is referenced but its limits are not published, so confirm before relying on it. ([missiveapp.com/pricing](https://missiveapp.com/pricing))
Also see: [Missive vs InboxPilot](/blog/missive-inboxpilot).
### 5. Help Scout
**Best for:** Customer support teams that want a shared inbox plus a knowledge base, without Zendesk's weight.
**Strengths**
- **A free tier covering 5 users**, one inbox, and one Docs site.
- The cleanest, easiest interface of any support tool here.
- Built-in knowledge base, so you are not buying a second product.
- Provider-agnostic, so Outlook works the same as any other mailbox.
**Tradeoffs**
- **Reporting is basic** compared to Zendesk or Freshdesk, and custom report history is gated to higher tiers.
- Workflow customization feels restrictive once your needs get complex.
- Extra inboxes cost $10 per month each, and Pro requires a 10-user minimum.
**Pricing:** Free (5 users, 1 inbox). Standard $25 per user per month, Plus $45, Pro $75. ([helpscout.com/pricing](https://www.helpscout.com/pricing/))
Also see: [Help Scout vs InboxPilot](/blog/helpscout-vs-inboxpilot).
### 6. Zendesk
**Best for:** Teams that have outgrown the shared inbox category entirely and need a real help desk.
Zendesk is on this list so you can rule it in or out honestly. It is not a shared inbox. It is a ticketing suite, and that is a different purchase. It connects to Outlook without issue because it is provider-agnostic.
**Strengths**
- The deepest routing, reporting, and automation available anywhere here.
- Enormous app ecosystem.
- Scales to genuine enterprise volume.
**Tradeoffs**
- **The $19 Support Team tier is a trap for this buyer.** Anything resembling the suite starts at **$55 per agent (Suite Team)**, and Professional is $115.
- Complexity and admin burden are its most common criticisms.
- Email stops feeling like email and becomes tickets. That is the point, and also the cost.
**Pricing:** Support Team $19 per agent per month annual. Suite Team $55, Suite Professional $115. No free tier. ([zendesk.com/pricing](https://www.zendesk.com/pricing/))
More on running the two together: [InboxPilot and Zendesk](/blog/inboxpilot-and-zendesk-integration).
### 7. Freshdesk
**Best for:** Budget-conscious Microsoft teams that want real ticketing and can live with rough edges.
**Strengths**
- Aggressive pricing at $19 per agent per month.
- Freddy AI included rather than bolted on.
- Solid knowledge base and customer portal, provider-agnostic.
**Tradeoffs**
- **The free plan is not free forever.** It is currently $0 for 1-2 agents for 6 months. Most roundups still describe an old perpetual free plan.
- **Duplicate and child ticket handling** is a recurring complaint.
- Reporting is limited on lower tiers.
**Pricing:** Free for 1-2 agents for 6 months. Growth $19 per agent per month annual, Pro $55, Enterprise $89. ([freshworks.com/freshdesk/pricing](https://www.freshworks.com/freshdesk/pricing/))
### 8. Hiver Omni (the Outlook workaround)
**Best for:** Teams already sold on Hiver who happen to be on Outlook.
Hiver's well-known product runs natively inside Gmail as a Chrome extension. For Outlook, Hiver offers a separate standalone app called Omni rather than an in-Outlook add-in. Outlook users work in Hiver's own web workspace, so they do not get a Hiver panel inside Outlook the way Gmail users get one inside Gmail.
**Strengths**
- Brings Hiver's shared-inbox coordination, assignment, collision detection, and SLA basics, to Outlook, which the Gmail extension never covered.
- Multichannel on higher tiers: live chat, WhatsApp, voice, and social alongside email.
- No Outlook premium: the same price ladder as Hiver's Gmail product.
**Tradeoffs**
- **It is a separate web workspace, not the native-in-Outlook experience Microsoft teams usually want.** "Hiver supports Outlook" is true, but not in the inside-your-mailbox way it works on Gmail.
- The reason to choose it is prior commitment to Hiver, not Outlook fit specifically.
**Pricing:** Omni uses the **same ladder as Hiver's Gmail product**, with no separate Omni pricing: Free, Growth $25, Pro $55, Elite $85 per user per month billed annually ($35, $65, $95 monthly). Higher tiers unlock more channels. ([hiverhq.com/pricing/hiver-omni](https://hiverhq.com/pricing/hiver-omni))
## What a 5-person Outlook team actually pays in year one
Advertised entry prices mislead, so here is the real number for a five-person support team, at list price, billed annually.
| Tool | Plan needed for 5 people | Monthly | Year one |
|---|---|---|---|
| M365 shared mailbox | Included with Microsoft 365 | $0 | **$0** |
| Help Scout | Free (5 users), or Standard $25 | $0 to $125 | **$0 to $1,500** |
| Missive | Starter $14 (caps at exactly 5) | $70 | **$840** |
| Freshdesk | Growth $19 | $95 | **$1,140** |
| InboxPilot | Standard $119 flat | $119 | **$1,428** |
| Front | Starter $25, single channel | $125 | **$1,500** |
| Front (Professional, realistic) | $65 | $325 | **$3,900** |
| Zendesk Suite Team | $55 | $275 | **$3,300** |
Front's real cost is closer to $3,900 than the $1,500 its entry tier implies. And the free M365 shared mailbox covers a surprising number of Microsoft teams that never actually needed to buy anything.
## How to choose a shared inbox for Outlook
### 1. Rule out the free M365 shared mailbox first
For a low-volume address on a few people, it is native, free, and often enough. Spending $1,500 a year to solve a problem you do not have yet is the most common mistake in this category.
### 2. Verify Outlook support before comparing any feature
Gmelius has none. Hiver's main product has none, only the separate Omni app. Even Front's Outlook read-status sync is conditional. Confirm the tool treats Outlook as first-class before you fall for its feature list.
### 3. Price the plan you will actually need
Front's $25 Starter is single-channel; the realistic plan is $65. Zendesk's $19 is not the Suite; that starts at $55. Build the number from the plan you will really be on.
### 4. Separate the volume problem from the coordination problem
Two different problems, two different fixes. Coordination is solved by assignment and collision detection. Volume is solved by AI drafting. Neither touches the other, so diagnose which one is actually hurting before you shop.
## How to choose, in one paragraph
Start with the diagnosis, not the tool. If the honest answer is that nobody is stepping on anyone's toes, there is just too much email, that is a volume problem and [InboxPilot](/pricing) is our pick, natively inside Outlook, on its own or alongside whichever shared inbox you land on. If you are a few people on a low-volume Microsoft address, use the **M365 shared mailbox** and spend nothing. If you need real coordination and want the most complete classic shared inbox, **Front**, at its real price and with the Outlook sync caveat understood. If you want Outlook treated as a true equal at the lowest price, **Missive**. If you want a support tool with a knowledge base, **Help Scout**. And if you have outgrown shared inboxes entirely, **Zendesk** or **Freshdesk**.
## Related reading
- [Best shared inbox software for Gmail and Outlook](/blog/best-shared-inbox-software): the full category, both platforms, including help desks.
- [Best shared inbox for Gmail](/blog/best-shared-inbox-for-gmail): the Google-side companion to this guide.
- [Missive vs InboxPilot](/blog/missive-inboxpilot), [Help Scout vs InboxPilot](/blog/helpscout-vs-inboxpilot): the direct comparisons.
- [How to automate email support](/blog/ai-email-agent): what to automate once your inbox is organized.
- [RFQ and quote request automation](/use-cases/rfq-email-automation): how quote requests get read, priced, and answered from your own catalog.
- [Shared mailbox auto-reply](/blog/shared-mailbox-auto-reply): setting automatic replies on a Microsoft 365 shared mailbox, and what they cannot do.
---
*Pricing verified against vendor pricing pages in July 2026 and stated per user per month unless noted. Platform limits are cited from Microsoft's own administrator documentation. Vendors change pricing frequently, so confirm current rates before purchasing. InboxPilot is the publisher of this article and is one of the tools discussed.*
---
## The Best Shopify Customer Support Apps in 2026
Source: https://www.inboxpilot.co/blog/best-shopify-customer-support-apps-2026
Published: 2026-07-22
A practical 2026 guide to the best Shopify customer support apps, from full helpdesks like Gorgias and Zendesk to inbox-native AI in Gmail.
Search "Shopify customer support app" and you get a wall of options: full helpdesks, chat widgets, order-tracking tools, returns portals, and AI add-ons, all promising to fix the same inbox. The right choice depends less on features and more on one question: do you want to run your support inside a separate platform, or keep it in the inbox your team already uses.
This guide sorts the main Shopify support tools for 2026 by what they actually are, so you can match one to how your store works. It covers full ecommerce helpdesks, a general-purpose platform, and the inbox-native approach, with honest notes on where each fits.
**Disclosure:** we make [InboxPilot](/industries/shopify-support), an AI email agent that drafts replies inside Gmail and Outlook, grounded in your Shopify orders and policies. This post includes InboxPilot and compares it fairly with tools built by other companies. We are not affiliated with those companies, and the descriptions below are based on their public information. Check each vendor's site for current details.
## TL;DR
- **Pick a helpdesk** (Gorgias, Richpanel, Re:amaze, Zendesk) when you want a full multichannel platform your team runs inside. See [how to choose](#how-to-choose-a-shopify-support-app).
- **Pick inbox-native AI** (InboxPilot) when you run support from Gmail or Outlook and want grounded drafting without a migration or a ticket meter. See [the list](#the-best-shopify-customer-support-apps-in-2026).
- **Match the pricing model to your volume.** Ticket-tiered and per-agent pricing climb with growth and busy seasons; flat pricing does not. See [the comparison](#shopify-support-apps-compared).
## How to choose a Shopify support app
Before the feature checklist, weigh four things that actually drive the decision:
- **Where your team works.** A helpdesk asks you to move out of Gmail or Outlook and into its inbox. An inbox-native tool keeps your team where it is. Migration has a real cost in time and training.
- **Channels you truly need.** If most of your support is email, a heavy multichannel platform may be more than you use. If you live on chat, SMS, and social too, that breadth matters.
- **Pricing model, not just price.** Ticket-tiered pricing penalizes your busiest season. Per-agent pricing grows with headcount. Flat pricing stays predictable. Read the model, then the number.
- **How the AI is grounded.** The useful question is whether replies are grounded in your real Shopify orders and your live policies, not whether a tool says "AI." Grounding is what makes a draft safe to send.
## The best Shopify customer support apps in 2026
### InboxPilot: inbox-native AI for Gmail and Outlook
[InboxPilot](/industries/shopify-support) is the option for stores whose support lives in email and who would rather not run a separate helpdesk. It stays in the Gmail or Outlook inbox you already use, connects to [Shopify](/integrations/shopify) to read the exact order behind each email, and drafts order status, returns, and refund replies grounded in your store data and policies. A person approves each send by default, and you can auto-send the low-risk cases.
It prices flat, from $149 per month for 1,500 AI drafts with unlimited inboxes and up to 10 team members, with a free tier of 25 drafts to test. Best for stores that want AI drafting and triage without migrating to a helpdesk or paying by the ticket. It is email-first, so if you need deep native chat, SMS, and social ticketing in one platform, a full helpdesk below may fit better.
### Gorgias: the ecommerce-native helpdesk
[Gorgias](https://www.gorgias.com/) is a helpdesk built specifically for ecommerce. It centralizes email, chat, social, and SMS into one ticketing platform, integrates tightly with Shopify, and layers automation and AI on top. It is a strong choice for a growing store that wants a dedicated multichannel desk and is happy to run the team inside it. Its pricing is tiered by monthly ticket volume, so the bill tracks how much you resolve. We wrote a fuller [Gorgias alternative](/blog/gorgias-alternative) comparison if you are weighing it against staying in your inbox.
### Richpanel: helpdesk with heavy self-service
[Richpanel](https://www.richpanel.com/) is an ecommerce-focused customer service platform that pairs a multichannel helpdesk with a customer self-service portal and AI, aiming to deflect common questions before they become tickets. It integrates with Shopify and suits stores that want a branded self-service experience alongside agent support. Like other helpdesks, it is a separate platform your team works inside. See our [Richpanel alternative](/blog/richpanel-alternative) piece for a closer look.
### Re:amaze: multichannel helpdesk for SMBs
[Re:amaze](https://www.reamaze.com/) is a multichannel helpdesk covering email, live chat, social, SMS, and FAQ pages, with Shopify integration and automation. It is popular with small and mid-sized stores that want breadth across channels in one shared inbox. It typically prices per agent seat, so cost scales with team size. A fit when chat and social are core channels for you, not just email.
### Zendesk: the general-purpose CX platform
[Zendesk](https://www.zendesk.com/) is a large, general-purpose customer service platform used well beyond ecommerce. It is powerful and highly configurable, with a deep ticketing system, extensive integrations including Shopify, and enterprise features. That power comes with weight: it is more platform to configure and run than many small stores need, and it prices per agent. A fit for larger teams that need enterprise-grade workflows and are ready to invest in setup.
### Gladly: people-centered service for premium brands
[Gladly](https://www.gladly.com/) is a customer service platform organized around the customer rather than the ticket, aimed at brands that treat service as a core part of their experience. It is a premium, higher-end option better suited to established brands with dedicated support teams than to early-stage stores. Worth a look if a lifelong-customer, conversation-centric model matches how you want to run support.
## Shopify support apps compared
| Tool | What it is | Where your team works | Typical pricing model | Best for |
|------|------------|----------------------|-----------------------|----------|
| InboxPilot | Inbox-native AI assistant | Your Gmail & Outlook inbox | Flat, from $149/mo | Email-first stores that want AI drafting without a migration |
| Gorgias | Ecommerce helpdesk | Separate platform | Tiered by ticket volume | Multichannel stores wanting a dedicated ecommerce desk |
| Richpanel | Helpdesk + self-service | Separate platform | Per agent / tiered | Stores wanting heavy customer self-service |
| Re:amaze | Multichannel helpdesk | Separate platform | Per agent | SMBs where chat and social are core channels |
| Zendesk | General-purpose CX platform | Separate platform | Per agent | Larger teams needing enterprise workflows |
| Gladly | People-centered service platform | Separate platform | Premium / custom | Established brands with dedicated support teams |
Pricing models change, so treat this as a starting point and confirm the current numbers on each vendor's site.
The two pricing shapes behave very differently as your support volume grows:
## Which one is right for your store
The honest answer is that the best Shopify support app depends on your team, not a ranking. Two clear paths:
- **If you want a full, multichannel helpdesk** and are ready to run your team inside a dedicated platform, start with **Gorgias** for ecommerce depth, **Re:amaze** for multichannel breadth at SMB scale, **Zendesk** for enterprise power, or **Richpanel** if self-service is central. **Gladly** fits premium brands.
- **If you run support from a shared Gmail or Outlook inbox** and want AI that drafts order status, returns, and refund replies grounded in Shopify, without a migration or a ticket meter, an inbox-native assistant like **InboxPilot** is the closer fit.
Plenty of stores never needed the full platform. They needed their WISMO, returns, and refund email handled well, in the inbox they already use, at a cost they can predict.
## Try the inbox-native approach
If your Shopify support is mostly email and you would rather not run another platform, start where your team already works. InboxPilot drafts grounded order, returns, and refund replies inside Gmail and Outlook, reads your Shopify orders, and prices flat.
[Try InboxPilot free](https://www.inboxpilot.co/) with 25 AI drafts, no helpdesk migration required.
## Related resources
- [AI Customer Support for Your Shopify Store](/industries/shopify-support)
- [The Best Gorgias Alternative for Ecommerce Support](/blog/gorgias-alternative)
- [The Best Richpanel Alternative for Ecommerce Support](/blog/richpanel-alternative)
- [How to Automate Order Status (WISMO) Emails for Your Shopify Store](/blog/automate-order-status-emails-shopify)
- [Order status email automation](/use-cases/order-status-email-automation): answering WISMO and shipping questions from your system of record.
*InboxPilot is not affiliated with Gorgias, Richpanel, Re:amaze, Zendesk, or Gladly. Product names and trademarks belong to their respective owners, and the descriptions above reflect publicly available information as of July 2026. Verify current features and pricing on each vendor's website.*
---
## Returns and Refund Email Automation for Ecommerce
Source: https://www.inboxpilot.co/blog/ecommerce-returns-refund-email-automation
Published: 2026-07-22
US retail returns hit $890 billion in 2024. Here is how to automate returns and refund emails, grounded in your policy and Shopify orders.
Returns are not a niche part of ecommerce. They are a season all their own, and most of the workload lands in your inbox as email: can I return this, how do I return this, and where is my refund. Each one means checking the order, the policy window, the item condition, and the payment method before anyone can even start typing. Do that a few hundred times a week and returns quietly become one of your biggest support costs.
This guide covers why returns are a support problem and not just a logistics one, what actually slows a returns reply down, and how to auto-draft accurate, on-policy return and refund emails from your Shopify data without moving your team into a separate helpdesk.
**Disclosure:** we make [InboxPilot](/industries/shopify-support), an AI email agent that drafts replies inside Gmail and Outlook, grounded in your own store data and policies, with a person approving each send. This post explains the general approach and shows how InboxPilot handles returns and refunds.
## TL;DR
- **Returns are huge and growing.** US retail returns reached $890 billion in 2024, and the experience shapes whether people buy again. See [why it is a support problem](#why-returns-are-a-support-problem-not-just-a-logistics-one).
- **The reply is slow because it needs context**, the order, the policy window, the item, and the payment method. See [what slows it down](#what-slows-a-returns-reply-down).
- **You can automate the email in your own inbox.** [InboxPilot](#how-to-automate-returns-and-refund-emails), which is us, reads the request, checks it against your policy and the Shopify order, and drafts the next steps inside Gmail or Outlook. See [how to do it](#how-to-automate-returns-and-refund-emails).
- **A human keeps control of approvals.** Drafts wait for review, refunds are a deliberate action, and exceptions get flagged. See [where a human stays in the loop](#where-a-human-should-stay-in-the-loop).
## Why returns are a support problem, not just a logistics one
Returns are enormous. The National Retail Federation and Happy Returns reported that [US retail returns totaled $890 billion in 2024, about 16.9% of annual sales](https://nrf.com/media-center/press-releases/nrf-and-happy-returns-report-2024-retail-returns-total-890-billion). For an online store, a meaningful slice of every month's orders comes back, and almost every one starts or ends with an email exchange.
More importantly, the return experience decides whether a customer comes back. In the same 2024 report, the NRF found that [76% of consumers consider free returns a key factor](https://nrf.com/media-center/press-releases/nrf-and-happy-returns-report-2024-retail-returns-total-890-billion) in deciding where to shop, and [67% say a negative return experience would discourage them from shopping with a retailer again](https://nrf.com/media-center/press-releases/nrf-and-happy-returns-report-2024-retail-returns-total-890-billion). A slow, confusing, or off-policy return reply is not a minor annoyance. It is one of the fastest ways to lose a repeat customer.
That is why returns belong in the support conversation, not just the warehouse one. The label, the restock, and the refund are logistics. The reply that tells the customer what happens next, and how quickly, is support, and it is the part they judge you on.
## What slows a returns reply down
A returns email is harder to answer than a WISMO email because it depends on more context. Before an agent can reply, they usually need to confirm:
- **The order**, so they know what was bought, when, and for how much.
- **The return window**, measured from purchase or delivery, to see whether the item still qualifies.
- **The item and its condition rules**, since some categories are final sale or have their own conditions.
- **The payment method**, because the refund timeline and destination depend on it.
Only after all of that can they write a reply that is both correct and clear. Get the window wrong and you either lose money on a return you should have declined or anger a customer you should have helped. That is a lot of careful lookup for an email that, in most cases, follows one of a few predictable shapes.
The NRF also found that [84% of consumers are more likely to shop with a retailer that offers no box, no label returns and immediate refunds](https://nrf.com/media-center/press-releases/nrf-and-happy-returns-report-2024-retail-returns-total-890-billion). Speed and clarity in that reply are not just efficiency for you. They are a reason customers choose you.
## How to automate returns and refund emails
The pattern mirrors WISMO, with one addition: the policy check. You want the assistant to read the request, pull the real order, check it against your live return policy, and draft the correct next steps, all inside the inbox you already use.
With InboxPilot you connect your [Shopify store](/integrations/shopify) and your returns, refund, and shipping policies, then write a plain-English rule:
> When a customer asks to return or refund an item, look up the order in Shopify, check it against our return policy, and draft a reply with the return steps or the refund timeline. Flag anything outside the return window for me.
From then on, return and refund emails get a grounded draft that references the real order and follows your policy.
## A refund reply, grounded in your policy
Here is the loop with a refund request. The customer writes:
> Subject: Return request, order #10188
>
> Hi, the boots I ordered are lovely but they run small. I would like to return them for a refund. I bought them about two weeks ago. What do I need to do? Thanks, Marco
InboxPilot matches the order, checks the purchase date against the return window, confirms the category is eligible, and drafts this for review:
> Hi Marco,
>
> Thanks for reaching out, and sorry the boots did not fit. Good news: your order #10188 is well within our 30-day return window, so a refund is no problem.
>
> Here is how it works. Use this prepaid label to send the boots back in their original condition: [return label link]. As soon as our warehouse scans them in, we will refund the full amount to your original payment method, which typically lands within 5 to 7 business days.
>
> If you would rather exchange them for the next size up, just reply and I will set that up instead.
>
> Best,
> The [Store] team
The agent confirms the window and the label are right and sends. The judgment, that this order qualifies and the timeline is correct, was done by the draft from your policy. The person just approves.
## Where a human should stay in the loop
Automation should speed up the routine and protect the exceptions. Return and refund workflows are exactly where you want a person on the edge cases:
- **Issuing the actual refund.** InboxPilot drafts the reply and the next steps, but approving the return and issuing the money should stay a deliberate action a person controls.
- **Outside-policy requests.** A return past the window, a final-sale item, or a partial-refund negotiation needs human judgment, not an automatic yes.
- **High-value or repeat cases.** Expensive orders and customers with a pattern of returns deserve a look before anything goes out.
InboxPilot keeps every draft under review by default, lets you auto-send only the confirmations you trust, and flags the exceptions above for a person even after the routine cases run on their own. You clear the predictable returns fast and keep control of the money and the edge cases.
## Clear the returns queue without a new platform
Returns are too big and too visible to leave to slow, manual replies. Ground the answers in your policy and your Shopify orders, keep approvals in human hands, and let the routine return and refund emails draft themselves in the inbox you already run on.
[Try InboxPilot free](https://www.inboxpilot.co/) with 25 AI drafts, no helpdesk migration required.
## Related resources
- [Order status email automation](/use-cases/order-status-email-automation): the sibling WISMO workflow, automated the same way.
- [AI Customer Support for Your Shopify Store](/industries/shopify-support)
- [How to Automate Order Status (WISMO) Emails for Your Shopify Store](/blog/automate-order-status-emails-shopify)
- [AI Customer Support for E-commerce & Retail](/industries/ecommerce-retail)
---
## The Best Richpanel Alternative for Ecommerce Support (2026)
Source: https://www.inboxpilot.co/blog/richpanel-alternative
Published: 2026-07-22
Richpanel is a separate ecommerce helpdesk. Here is the best Richpanel alternative for stores that want AI support inside Gmail and Outlook.
A store evaluates Richpanel, likes the self-service portal in the demo, and then pictures the rollout: migrate the inbox, stand up the help center, retrain the team, and manage another platform, all to answer the same "where is my order" emails the store already handles in Gmail. The tool is capable. The question is whether the store wants a whole customer service platform to do it.
That tension is behind a lot of "Richpanel alternative" searches. Richpanel is a strong, ecommerce-native customer service platform. Not every store wants a separate helpdesk with a self-service portal, or a bill that climbs with volume.
**Disclosure:** we make [InboxPilot](/industries/shopify-support), an AI email agent that drafts replies inside Gmail and Outlook, grounded in your own store data and policies, with a person approving each send. This post compares it fairly with Richpanel, including where Richpanel is the better pick. We are not affiliated with Richpanel, and the descriptions here reflect its public information as of July 2026.
## TL;DR
- **Richpanel is a separate ecommerce helpdesk**, with a multichannel inbox, AI, and a customer self-service portal. It is capable and Shopify-native. See [where it fits](#what-richpanel-is-and-where-it-fits).
- **InboxPilot works in the inbox you already use.** It drafts WISMO, returns, and refund replies inside Gmail and Outlook, grounded in Shopify, with no migration. See [how it fits ecommerce](#inboxpilot-as-a-richpanel-alternative).
- **Flat pricing, not a plan-tier climb.** From $149 per month for 1,500 AI drafts, unlimited inboxes, and up to 10 agents, so [busy seasons do not spike the bill](#the-pricing-difference).
- **Pick Richpanel** when you want a full platform with a branded self-service portal. **Pick InboxPilot** when you run support from a shared inbox and want AI drafting with a predictable cost. See [how to choose](#how-to-choose).
## What Richpanel is, and where it fits
Richpanel is a customer service platform built for ecommerce. It brings email, chat, social, and other channels into one helpdesk, adds AI to draft and deflect common questions, and pairs the agent side with a customer-facing self-service portal where shoppers can track orders and start returns on their own. It integrates with Shopify and is designed to reduce ticket volume by answering routine questions before they reach an agent.
For a store that wants a dedicated, multichannel support desk with a strong self-service layer and is happy to run the team inside it, Richpanel is a well-designed choice. Two traits define the model, and neither is a flaw, they are fit questions:
- **It is a separate platform.** Your team moves out of Gmail or Outlook and works inside the Richpanel helpdesk, and you set up and maintain the self-service portal.
- **It is a full customer service suite.** That breadth is valuable if you need it, and more than some stores want if most of their support is email.
## The core tradeoff: a new platform vs your inbox
Before the price question, there is a platform question. A great deal of ecommerce support is email: where is my order, can I return this, where is my refund, is this in stock. Many stores already handle all of it in a shared Gmail or Outlook inbox that a small team works together.
A helpdesk asks you to move that work into a new system: migrate history, build and maintain a portal, retrain the team, and manage another platform. That is worth it for some stores and overkill for others. An inbox-native assistant takes the opposite approach: it brings the AI to the inbox you already run support from, instead of moving your team to the AI.
## Feature comparison: InboxPilot vs Richpanel
| Feature | InboxPilot | Richpanel |
|---------|------------|-----------|
| Where your team works | Your Gmail & Outlook inbox | Separate Richpanel helpdesk |
| Migration required | No | Yes (move into the platform) |
| Pricing model | Flat, usage-based plans | Plan tiers, scales with volume |
| Predictable in a busy season | Yes | Scales with volume |
| Shopify order context in replies | Yes | Yes |
| WISMO, returns, refunds drafting | Yes, grounded in your policy | Yes |
| Smart triage & labeling | Yes | Yes |
| Human approval before send | Yes, by default | Configurable |
| Customer self-service portal | No (inbox-first) | Yes |
| Multichannel (SMS, social, chat) | Email-first | Yes, full multichannel |
| Free tier | Yes (25 AI drafts) | Check current plans |
| Setup | Connect inbox, under 2 min | Platform onboarding + portal setup |
## InboxPilot as a Richpanel alternative
InboxPilot is built for stores whose support lives in email and who would rather not run a separate helpdesk. It handles the same ecommerce load Richpanel targets, from inside Gmail and Outlook.
It connects to [Shopify](/integrations/shopify) and reads the exact order behind each email, then drafts a grounded reply:
- **WISMO ("where is my order")** emails get a status update with live tracking, drafted the moment they land. See our [WISMO automation guide](/blog/automate-order-status-emails-shopify).
- **Returns and refunds** follow your live policy, checked against the real order, so agents never quote the wrong window. See our [returns automation guide](/blog/ecommerce-returns-refund-email-automation).
- **Product, stock, and sizing** questions are answered from your catalog and help docs.
Every draft waits for a person by default, and you can auto-send the low-risk cases. There is no separate inbox to learn and no portal to build. Your customers keep emailing the same address, and your team keeps the Gmail or Outlook inbox it already uses.
The one honest tradeoff: Richpanel gives you a branded customer self-service portal and full multichannel ticketing in one suite. InboxPilot is email-first and does not replace a self-service portal. If a portal is central to your plan, that is a point for Richpanel. If your support is mostly email and you want it handled well without a new platform, that is the case for InboxPilot.
## The pricing difference
Helpdesk platforms generally price so that cost grows with your volume, your channels, or your team, whether through plan tiers or per-agent seats. That means your bill tends to climb exactly when a launch or holiday season spikes your ticket count. Check [Richpanel's pricing](https://www.richpanel.com/pricing) for its current plans and tiers.
InboxPilot prices flat. Plans start at $149 per month for 1,500 AI drafts, unlimited inboxes, and up to 10 team members, with a free tier of 25 drafts to test. A busy season does not push you into a higher bracket, and adding an inbox does not add a line item. See the full [pricing](/pricing) for details.
A Richpanel plan and an InboxPilot plan are different units, so compare the shape, not a line-for-line quote. One bill tends to track volume; the other holds steady.
Those two shapes diverge as your support volume grows:
## How to choose
Choose **Richpanel** when:
- You want a full ecommerce customer service platform with a branded self-service portal
- You are ready to run your team inside a dedicated helpdesk
- Deep multichannel ticketing and heavy self-service deflection are worth the platform weight
Choose **InboxPilot** when:
- You run support from a shared Gmail or Outlook inbox and want to keep it
- You want AI drafting grounded in Shopify without migrating to a helpdesk
- You want a flat, predictable bill instead of pricing that climbs with volume
- Email is your main support channel
- You want a free tier to test before committing
## Conclusion
Richpanel is a capable, ecommerce-native customer service platform, and for stores that want a full suite with a self-service portal it earns its place. But plenty of stores do not want another platform, or a bill that climbs with volume. They want their WISMO, returns, and refund email handled well, in the inbox they already use, at a cost they can predict.
That is what InboxPilot is built for. It drafts grounded ecommerce replies inside Gmail and Outlook, reads your Shopify orders, and prices flat. Start free with 25 AI drafts, no helpdesk migration required.
[Try InboxPilot free](https://www.inboxpilot.co/)
## Related resources
- [AI Customer Support for Your Shopify Store](/industries/shopify-support)
- [The Best Shopify Customer Support Apps in 2026](/blog/best-shopify-customer-support-apps-2026)
- [The Best Gorgias Alternative for Ecommerce Support](/blog/gorgias-alternative)
- [How to Automate Order Status (WISMO) Emails for Your Shopify Store](/blog/automate-order-status-emails-shopify)
- [Order status email automation](/use-cases/order-status-email-automation): answering WISMO and shipping questions from your system of record.
*InboxPilot is not affiliated with Richpanel. Product names and trademarks belong to their respective owners, and the descriptions above reflect publicly available information as of July 2026. Verify current features and pricing on Richpanel's website.*
---
## The Best Gorgias Alternative for Ecommerce Support (2026)
Source: https://www.inboxpilot.co/blog/gorgias-alternative
Published: 2026-07-20
Gorgias is a separate ecommerce helpdesk priced by ticket volume. Here's the best Gorgias alternative for stores that want AI support inside Gmail and Outlook, grounded in Shopify.
A store owner opens the Gorgias plan page mid-migration and does the math on next quarter. The helpdesk is genuinely good at ecommerce. But the bill scales with tickets, the busy season is exactly when tickets spike, and the team is being asked to move out of the Gmail inbox they have used for years into a whole new platform to answer the same "where is my order" emails.
That tension is behind a lot of "Gorgias alternative" searches. Gorgias is a strong, ecommerce-native helpdesk. Not every store wants a separate helpdesk, or a bill that climbs with every ticket.
**Disclosure:** we make [InboxPilot](/industries/ecommerce-retail), an AI email agent that drafts replies inside Gmail and Outlook, grounded in your own store data and policies, with a person approving each send. This post compares it fairly with Gorgias, including where Gorgias is the better pick.
## TL;DR
- **Gorgias is a separate helpdesk, priced by tickets.** It is ecommerce-native and capable, billed in tiers by monthly ticket volume, so cost climbs with volume ([Gorgias pricing](https://www.gorgias.com/pricing)). See [the tradeoff](#the-core-tradeoff-a-new-helpdesk-vs-your-inbox).
- **InboxPilot works in the inbox you already use.** It drafts WISMO, returns, and refund replies inside Gmail and Outlook, grounded in Shopify, with no migration. See [how it fits ecommerce](#inboxpilot-as-a-gorgias-alternative).
- **Flat pricing, not a ticket meter.** From $149/month for 1,500 AI drafts, unlimited inboxes, and up to 10 agents, so [busy seasons do not spike the bill](#the-pricing-difference-tickets-vs-flat).
- **Pick Gorgias** when you want a full multichannel ecommerce helpdesk. **Pick InboxPilot** when you run support from a shared inbox and want AI drafting with a predictable cost. See [how to choose](#how-to-choose).
## What Gorgias is, and where it fits
Gorgias is a helpdesk built specifically for ecommerce. It centralizes email, chat, social, and SMS into one ticketing platform, integrates tightly with Shopify, and layers automation and AI on top to deflect and resolve common store questions. For a growing store that wants a dedicated, multichannel support desk and is happy to run the team inside it, Gorgias is a well-designed choice.
Two traits define the model, and neither is a flaw, they are fit questions:
- **It is a separate platform.** Your team moves out of Gmail or Outlook and works inside the Gorgias helpdesk.
- **It is priced by ticket volume.** Plans are tiered on monthly billable tickets, with higher tiers and overage as you grow, so the bill tracks volume.
## The core tradeoff: a new helpdesk vs your inbox
Before the price question, there is a platform question. A great deal of ecommerce support is email: where is my order, can I return this, where is my refund, is this in stock. Many stores already handle all of it in a shared Gmail or Outlook inbox that a small team works together.
A helpdesk asks you to move that work into a new system: migrate history, retrain the team, and manage another platform. That is worth it for some stores and overkill for others. An inbox-native assistant takes the opposite approach: it brings the AI to the inbox you already run support from, instead of moving your team to the AI.
## Feature comparison: InboxPilot vs Gorgias
| Feature | InboxPilot | Gorgias |
|---------|------------|---------|
| Where your team works | Your Gmail & Outlook inbox | Separate Gorgias helpdesk |
| Migration required | No | Yes (move into the helpdesk) |
| Pricing model | Flat, usage-based plans | Tiered by monthly ticket volume |
| Predictable in a busy season | Yes | Scales with tickets |
| Shopify order context in replies | Yes | Yes |
| WISMO, returns, refunds drafting | Yes, grounded in your policy | Yes |
| Smart triage & labeling | Yes | Yes |
| Human approval before send | Yes, by default | Configurable |
| Multichannel (SMS, social, chat) | Email-first | Yes, full multichannel |
| Free tier | Yes (25 AI drafts) | No |
| Setup | Connect inbox, under 2 min | Helpdesk onboarding |
## InboxPilot as a Gorgias alternative
InboxPilot is built for stores whose support lives in email and who would rather not run a separate helpdesk. It handles the same ecommerce load Gorgias targets, from inside Gmail and Outlook.
### It works in the inbox you already use
Connect Gmail or Outlook with OAuth in under two minutes. There is no helpdesk to migrate to and no history to move. Customers keep emailing the same address, and your team keeps the shared inbox they already know, with a grounded draft waiting on every ticket.
### Grounded in your store data and policy
InboxPilot reads order context and drafts from your own material:
- WISMO replies with tracking and order status
- Returns and exchanges that follow your live policy
- Refund confirmations with the right window and timeline
- Product, sizing, and availability answers from your catalog and help docs
Every reply reflects your store's actual orders, policy, and voice, not a generic template.
### Triage and workflows, not just replies
Beyond drafting, InboxPilot triages and labels each ticket the moment it lands, routes threads to the right agent, and runs multi-step email workflows you describe in plain English, check the order, draft an apology with the refund policy, follow up in three days. It keeps the shared inbox organized, with a person approving sends by default.
## The pricing difference: tickets vs flat
Ticket-tiered pricing feels fair and often is, until a launch or a holiday triples your volume and the bill climbs with it. That is the exact moment a store least wants a cost spike.
InboxPilot prices flat instead. The Standard plan is $149/month for 1,500 AI drafts, unlimited inboxes, and up to 10 agents. When volume surges, the plan holds. The value is not only the number, it is the predictability: you can forecast support cost even in your busiest month.
These are different units, a Gorgias ticket is not identical to an InboxPilot draft, so compare the shape, not a line-for-line quote. One bill tracks volume; the other holds steady.
## How to choose
Choose **Gorgias** when:
- You want a full, multichannel ecommerce helpdesk (email, chat, SMS, social)
- You are ready to run your team inside a dedicated platform
- Deep, native ticketing and helpdesk workflows are worth the platform weight
Choose **InboxPilot** when:
- You run support from a shared Gmail or Outlook inbox and want to keep it
- You want AI drafting grounded in Shopify without migrating to a helpdesk
- You want a flat, predictable bill instead of a ticket meter
- Email is your main support channel
- You want a free tier to test before committing
## Conclusion
Gorgias is a capable, ecommerce-native helpdesk, and for stores that want a full multichannel platform it earns its place. But plenty of stores do not want another platform or a bill that climbs with every ticket. They want their WISMO, returns, and refund email handled well, in the inbox they already use, at a cost they can predict.
That is what InboxPilot is built for. It drafts grounded ecommerce replies inside Gmail and Outlook, reads your Shopify orders, and prices flat. Start free with 25 AI drafts, no helpdesk migration required.
[Try InboxPilot free](https://www.inboxpilot.co/)
## Related resources
- [AI Customer Support for E-commerce & Retail](/industries/ecommerce-retail)
- [AI Email Assistant Buyer's Guide 2026](/blog/ai-email-assistant-buyers-guide-2026)
- [InboxPilot vs Intercom: Full Comparison](/inboxpilot-vs-intercom)
- [Order status email automation](/use-cases/order-status-email-automation): answering WISMO and shipping questions from your system of record.
---
## The Best Intercom Fin Alternative for Email Support (2026)
Source: https://www.inboxpilot.co/blog/intercom-fin-alternative
Published: 2026-07-20
Salesforce is acquiring Fin, formerly Intercom, for $3.6B. What it changes, and the best Fin alternative if your team runs support from email.
A support lead adds up last month's Intercom invoice and stops on one line: the Fin resolution charges. Fin did real work, but the number moves every month, and it climbs exactly when volume spikes and budgets are tightest. Meanwhile, most of the team's actual conversations never touched the chat widget at all. They came in by email.
That is the quiet mismatch behind a lot of "Intercom Fin alternative" searches. Fin is a strong AI agent for a chat-and-helpdesk world. Plenty of support teams do not live in that world. They live in a shared Gmail or Outlook inbox.
**Disclosure:** we make [InboxPilot](/solutions/support-teams), an AI email agent that drafts replies inside Gmail and Outlook, grounded in your own documents, with a person approving each send. This post compares it fairly with Intercom Fin, including where Fin is the better pick. For a side-by-side on the full platform, see [InboxPilot vs Intercom](/inboxpilot-vs-intercom).
## TL;DR
- **Salesforce is buying Fin.** On 15 June 2026, Salesforce signed a definitive agreement to acquire Fin, the company that was Intercom until about a month earlier, for roughly $3.6 billion. It is signed, not closed. See [what the acquisition changes](#what-the-salesforce-acquisition-changes-and-what-it-does-not).
- **Fin is priced on outcomes.** As of July 2026, Fin lists $0.99 per outcome with a 50-outcome monthly minimum, plus $29 per helpdesk seat ([Fin](https://fin.ai/pricing)). The bill scales with volume, so it is hard to forecast. See [the pricing math](#the-pricing-math-per-outcome-vs-flat).
- **Fin lives in a chat widget and helpdesk.** If your team answers customers from a shared email inbox instead, that is a channel mismatch, not just a price one. See [the bigger mismatch](#the-bigger-mismatch-chat-widget-vs-your-inbox).
- **InboxPilot is inbox-native and flat-priced.** It drafts grounded replies inside Gmail and Outlook, from $149/month for 1,500 AI drafts, with [a person approving every send](#inboxpilot-as-an-intercom-fin-alternative).
- **Pick Fin** when support is chat-first and already deep in Intercom. **Pick InboxPilot** when support is email-first and you want a predictable bill. See [how to choose](#how-to-choose).
## What the Salesforce acquisition changes, and what it does not
If you are evaluating Fin in the second half of 2026, this is the context you need before anything else.
Two things happened in quick succession. In May 2026 the company renamed itself Fin, after its AI agent, and moved that product to its own site at fin.ai. Worth being precise here, because a lot of coverage overstates it: the Intercom brand did not disappear. As of July 2026 intercom.com still resolves and still sells the helpdesk under the Intercom name, describing itself as "the only helpdesk designed for the AI Agent era". What changed is the company name and where the AI agent lives, not the product you may already be paying for. Then on 15 June 2026, Salesforce announced a definitive agreement to acquire Fin for approximately $3.6 billion, subject to customary purchase price adjustments ([Salesforce Investor Relations](https://investor.salesforce.com/news/news-details/2026/Salesforce-Signs-Definitive-Agreement-to-Acquire-Fin/default.aspx), 2026; also reported by [MarTech](https://martech.org/salesforce-acquires-fin-formerly-known-as-intercom/), 2026). Salesforce cited more than 30,000 customer companies and said Fin's AI agents resolve on average 76% of support volume end to end, a vendor-reported figure rather than an independent measurement.
Now the part most coverage skips. **The deal is signed, not closed.** Salesforce expects it to close in the fourth quarter of its fiscal year 2027, and it remains subject to the usual regulatory conditions. Nothing about your Fin account changes today.
What Salesforce has said about the roadmap is also reassuring rather than alarming: Fin's technology is intended to sit alongside Agentforce, with Fin positioned as the faster-to-deploy option for SMB and commercial teams while Agentforce serves enterprises wanting deep customization. Read plainly, that is a plan to keep Fin, not retire it.
So the honest read is not "Fin is going away." It is narrower, and it is a procurement question rather than a product one:
- **Roadmap direction can shift after a close.** Priorities that served an independent company do not always survive integration into a platform strategy.
- **Renewal pricing is worth pinning down.** Outcome-based pricing is unusually sensitive to repackaging, because the unit itself can be redefined.
- **Multi-year contracts carry more uncertainty than usual right now.** If you are signing one before the close, ask about both of the above in writing.
None of that makes Fin a bad product. It is a strong AI agent and it was strong before the announcement. It does mean that if you were already weighing a switch for other reasons, the timing now favors doing that evaluation deliberately rather than renewing on autopilot. For a lot of teams reading this, the other reason came first anyway, and it is about channel.
## What Fin is, and where it fits
Fin is Intercom's AI agent. It answers customer questions inside Intercom's Messenger and helpdesk, trained on your help center and past conversations, and it resolves a large share of routine tickets without a human. For teams that already run support through Intercom's chat widget on a website or in-app, Fin is a natural, capable add-on.
The model has two defining traits worth being clear-eyed about:
- **It is chat-and-helpdesk shaped.** Fin is designed around the Messenger and the helpdesk inbox, not the Gmail or Outlook inbox your team may actually work in.
- **It is priced per outcome.** You pay per billable outcome, so cost tracks volume rather than a fixed monthly line. Fin defines a resolution as no further help being requested after its last answer, and bills one outcome per conversation even when it takes several actions.
Neither is a flaw. They are design choices that fit some teams and not others.
## The bigger mismatch: chat widget vs your inbox
Before the price question, there is a channel question, and it matters more than most comparison posts admit.
A great deal of real customer support still happens over email. Orders, refunds, account issues, B2B back-and-forth, and vendor threads land in a shared Gmail or Outlook inbox that a small team works together. Fin is built to deflect chat conversations and helpdesk tickets. Pointing it at an email-first workflow means changing how your team works, or bolting a chat product onto a job that is fundamentally about email.
An inbox-native assistant inverts that. Instead of asking customers to come to a widget and asking agents to move into a new helpdesk, it works where both already are: the email thread. That is the core of why teams running support from Gmail and Outlook look past the chatbot category entirely.
## Feature comparison: InboxPilot vs Intercom Fin
| Feature | InboxPilot | Intercom Fin |
|---------|------------|--------------|
| Primary channel | Gmail & Outlook inbox | Chat widget & Intercom helpdesk |
| Works in your existing email | Yes | No (Intercom inbox) |
| Pricing model | Flat, usage-based plans | Per outcome ($0.99) plus seats |
| Predictable monthly bill | Yes | Scales with volume |
| Human approval before send | Yes, by default | Autonomous resolutions |
| Grounded in your docs | Yes (docs, FAQs, policies, CRM) | Yes (help center, content) |
| Smart triage & labeling in email | Yes | N/A for email |
| Email workflows (route, escalate, follow up) | Yes | Chat/helpdesk automations |
| Free tier | Yes (25 AI drafts) | No |
| Setup | Connect Gmail/Outlook, under 2 min | Requires Intercom setup |
| Security | SOC 2 Type II, HIPAA eligible (Enterprise) | SOC 2 |
## The pricing math: per-outcome vs flat
Outcome-based pricing sounds fair and often is, until volume climbs. Because you pay per outcome, the monthly bill is a moving target that peaks in your busiest months.
As of July 2026, Fin publishes $0.99 per outcome with a 50-outcome monthly minimum, $29 per helpdesk seat per month alongside Intercom, and a higher $9.99 rate for qualifications ([Fin pricing](https://fin.ai/pricing), retrieved 27 July 2026).
Here is the directional math. These are different units, a Fin outcome is not identical to an InboxPilot draft, so treat this as a shape comparison, not a like-for-like quote:
**Fin at 1,500 outcomes in a month:**
- 1,500 outcomes x $0.99 = **about $1,485 in outcome fees**, before helpdesk seat costs.
**InboxPilot at 1,500 AI drafts in a month:**
- Standard plan: **$149/month flat**, for 1,500 AI drafts, unlimited inboxes, and up to 10 team members.
The point is not that one number is small and one is large. It is that one is fixed and one is not. When a product launch or a billing issue triples your volume, the flat plan holds and the per-outcome bill spikes. For a team that needs to forecast support costs, predictability is the feature.
## InboxPilot as an Intercom Fin alternative
InboxPilot is built for teams whose support lives in email. It handles the same routine load Fin targets, from inside Gmail and Outlook.
### It works in the inbox you already use
Connect Gmail or Outlook with OAuth in under two minutes. There is no new helpdesk to migrate to and no widget to install. Customers keep emailing the address they already use, and your team keeps working in the inbox they already know.
### Grounded drafts, in your voice
InboxPilot reads each incoming email and drafts a reply grounded in your own material:
- Help docs, FAQs, and policies
- Product and pricing information
- CRM and customer history
- Past email conversations
Answers reflect how your business actually works, not a generic model guess.
### A person approves every send
This is the deliberate difference from an autonomous chatbot. By default, InboxPilot drafts and a human reviews before anything goes out. Routine, high-confidence replies can be set to auto-send once you trust them, and sensitive threads can be excluded entirely so a person always handles them. You choose how much autonomy to grant, rather than starting fully hands-off.
### Triage and workflows, not just replies
Beyond drafting, InboxPilot triages and labels every thread the moment it lands, routes messages to the right person, and runs multi-step email workflows you describe in plain English, escalate this, follow up in three days, tag that. It organizes the inbox, not just the answer.
## How to choose
Choose **Intercom Fin** when:
- Your support is chat-first, on a website or in-app Messenger
- You are already invested in the Intercom helpdesk and content
- You want fully autonomous resolution and per-outcome billing fits your model
- A future move into the Salesforce ecosystem is a plus for you rather than a risk
Choose **InboxPilot** when:
- Your team runs support from a shared Gmail or Outlook inbox
- You want a flat, predictable bill instead of a per-outcome meter
- You want a human approving replies by default, with autonomy you grant over time
- You want triage, labeling, and email workflows in the same tool
- You want a free tier to test before committing
## Conclusion
Intercom Fin is a capable AI agent for chat-first teams already living in Intercom, and its outcome-based pricing suits some models well. But a lot of support does not happen in a chat widget. It happens in email. For teams that run their day from Gmail and Outlook, the better Intercom Fin alternative is not another chatbot, it is an assistant that works inside the inbox, on a flat and predictable plan, with a person in the loop.
That is what InboxPilot is built to do. Start free with 25 AI drafts, no chat widget required.
[Try InboxPilot free](https://www.inboxpilot.co/)
## Related resources
- [InboxPilot vs Intercom: Full Comparison](/inboxpilot-vs-intercom)
- [AI email agent for RFQs, support, and sales email](/blog/ai-email-agent)
- [AI Email Assistant Buyer's Guide 2026](/blog/ai-email-assistant-buyers-guide-2026)
- [AI Customer Support for Support Teams](/solutions/support-teams)
- [Order status email automation](/use-cases/order-status-email-automation): answering WISMO and shipping questions from your system of record.
---
*Acquisition details are from Salesforce's own investor relations announcement dated 15 June 2026 and are described here as a signed agreement rather than a completed deal, because as of publication it has not closed. The 76% autonomous resolution figure is reported by Salesforce and Fin, not independently measured, and is labeled as such above. Fin pricing was read from fin.ai/pricing on 27 July 2026 and may change; check the current page before budgeting. InboxPilot pricing was verified against our pricing page in July 2026. InboxPilot competes with Fin and is the publisher of this article, which is why the acquisition section states plainly what the deal does not change.*
---
## How Construction Companies Can Automate RFQ and Customer Emails with AI
Source: https://www.inboxpilot.co/blog/construction-rfq-email-automation
Published: 2026-07-16
Construction teams lose a third of the week to admin. How AI classifies RFQs, drafts doc-grounded replies, and routes email, with a human approving every send.
There is a quote request sitting in your estimating inbox right now. It came in as an email with a PDF attached, from a GC you'd like more work from, and nobody has opened it because your estimator is walking a site and the office manager is chasing a permit.
That gap is what this post is about. Construction companies rarely lose bids because they can't do the work. They lose them in the days between an email arriving and a person getting to it.
**Disclosure:** we make [InboxPilot](/), an AI email agent that drafts replies to RFQs and customer emails inside Gmail and Outlook. This post explains the workflow with sourced numbers, and it says plainly where a tool like ours does not belong: no AI should be sending your final pricing unsupervised.
## TL;DR
- In 2018, FMI and PlanGrid's *Construction Disconnected* study found construction professionals spend **35% of their working hours on non-optimal activities**, including 5.5 hours a week just hunting for project data. See [why teams lose hours to email](#why-construction-teams-lose-hours-to-email).
- **Most quote requests still move outside bid portals.** Loopio's 2026 cross-industry benchmark of 1,500+ response teams found only 45% of submissions go through portals; for subs and suppliers, what fills the gap is email. See [the five workflows](#the-five-email-workflows-that-eat-the-day).
- You probably can't hire your way out. In the AGC's 2025 workforce survey, **roughly four in five construction firms had unfilled salaried positions**, the office roles that answer email.
- **[InboxPilot](#setting-up-rfq-email-automation-without-risking-a-bad-quote), which is us,** is an inbox-native AI agent that can [classify, extract, draft, and route](#what-ai-can-actually-take-off-your-plate) RFQ email inside Gmail and Outlook, grounded in your own rate sheets and capability docs, with [a human approving every send](#the-workflow-from-new-rfq-to-approved-reply).
## Why construction teams lose hours to email
In 2018, FMI and PlanGrid surveyed 599 construction leaders for their report *Construction Disconnected* and found that 35% of a construction professional's working hours, about 14 hours a week, went to non-optimal activities: 5.5 hours looking for project data, 4.7 hours on conflict resolution, and 3.9 hours dealing with mistakes and rework ([FMI/PlanGrid, Construction Disconnected](https://pg.plangrid.com/rs/572-JSV-775/images/Construction_Disconnected.pdf), 2018). The same report put the cost of that lost time at $177.5 billion in US labor for the year.
That study is old enough that we're stating its date, which is more than most articles quoting it do. The newer data suggests the problem grew. In 2021, Autodesk and FMI's follow-up study, *Harnessing the Data Advantage in Construction*, surveyed more than 3,900 industry professionals and estimated that bad data may have cost the global construction industry $1.85 trillion in 2020 ([Autodesk + FMI](https://www.prnewswire.com/news-releases/study-from-autodesk-and-fmi-finds-better-data-strategies-could-save-the-global-construction-industry-1-85-trillion-301376278.html), 2021).
And where does project information actually sit? A lot of it sits in email. In 2025, Microsoft's Work Trend Index measured the average worker receiving 117 emails a day and getting interrupted every two minutes during core hours ([Microsoft WorkLab, Breaking Down the Infinite Workday](https://www.microsoft.com/en-us/worklab/work-trend-index/breaking-down-infinite-workday), 2025). That's all industries, not just construction. Now add the construction-specific twist: the people receiving those emails are often in a truck, on a scaffold, or mid-pour.
So the inbox is where RFQs, bid invitations, sub questions, and document requests all land, and it's staffed by whoever happens to be at a desk.
## The five email workflows that eat the day
Ask a construction office manager what's in the inbox and you'll get some version of the same five piles:
| Workflow | What it looks like | Why it drags |
|---|---|---|
| **RFQ and quote requests** | "Can you give us a number on the Oakdale sitework?" with plans attached | Requirements are buried in PDFs; someone has to read, qualify, and re-type them for the estimator |
| **Bid invitations (ITBs)** | A GC invites you to bid a trade package by a deadline | Every invite needs a bid/no-bid decision and a reply either way; many never get one |
| **Subcontractor questions** | Rates, insurance limits, crew availability, scope boundaries | The answers rarely change, but somebody re-types them every week |
| **Document requests** | COIs, W-9s, licenses, lien waivers, safety docs | Pure fetch-and-attach work that still interrupts someone's day |
| **Follow-ups** | "Did you get our quote?" "Any word on the award?" | Small individually, constant in aggregate |
Here's the part most software guides skip: this traffic mostly does not run through bid portals. Loopio's 2026 RFP benchmark, built on data from more than 1,500 response teams across industries, found only 45% of submissions go through online portals, down from 51% the year before ([Loopio](https://loopio.com/blog/portal-response/), 2026). Public work and the biggest GCs use portals. Nearly everyone else works out of the inbox. That's why construction email automation has to start inside Gmail and Outlook, not inside another platform your customers won't adopt.
## What AI can actually take off your plate
The useful question isn't whether AI works on email. It's which parts of the pile an AI assistant for construction companies can genuinely own. The adoption data says teams have already decided: in the same 2026 Loopio benchmark, nearly 80% of response teams had brought generative AI into their process, and in Autodesk's 2025 *State of Design and Make* survey of 5,594 industry leaders, 69% said AI will enhance their industry, a 12-point drop from the year before, so the enthusiasm is real but no longer naive ([Autodesk](https://adsknews.autodesk.com/en/news/2025-state-of-design-and-make/), 2025).
### 1. Classify what just arrived
The AI reads each incoming email and tags it: RFQ, bid invitation, sub question, document request, follow-up, or none of the above. That sounds minor. It isn't. Triage is the step that currently requires a person to open and read everything, and it's the reason time-sensitive quote requests sit unread next to newsletters.
### 2. Extract the requirements
For a quote request, the assistant pulls out what the estimator needs to see in ten seconds: scope, site, dates, deadline, and what's missing. If the sender never attached the grading spec, the draft reply asks for it, which is exactly what your best office manager would do.
### 3. Draft the reply from your own documents
This is where generic AI tools fall down. The 2018 FMI study found 52% of rework globally traces back to poor project data and miscommunication, and an AI reply that invents an insurance limit or quotes last year's rates is a liability, not automation. Grounded drafting means the assistant writes only from documents you gave it: your rate sheet, capability statement, service area, insurance and licensing, standard exclusions, past quotes. When the answer isn't in those sources, it escalates instead of guessing.
### 4. Answer the questions you've answered a hundred times
"What are your insurance limits?" "Do you cover the north county?" "What's your lead time on formwork?" These have fixed answers that live in documents. They're the highest-volume, lowest-risk place to automate quote requests and routine questions, and they're where teams see time savings first.
### 5. Route the rest to the right person
Not everything should get a draft. Keyword rules send RFQs to the estimator, invoices to accounting, and scheduling to the super. Negative keywords do the opposite job: anything mentioning a claim, dispute, back charge, or change order skips automation entirely and lands in front of a human with no draft attached.
## The workflow: from new RFQ to approved reply
Here's the whole loop for RFQ response automation, end to end:
1. **An RFQ lands** in estimating@ at 6:40am while the crew is loading out.
2. **The AI reads and classifies it** as a quote request, labels it, and flags the bid deadline it found in the body.
3. **It checks your documents**: services and capabilities, service area, rate sheet, insurance and licensing, and the last three quotes you sent this GC.
4. **It drafts a response** that confirms fit, states availability, asks for the missing plans, and commits to a proposal date.
5. **A person approves**, edits if needed, and sends. Total elapsed time: minutes, and none of them the estimator's.
What that looks like in practice:
> **Incoming, 6:40am:** "We're bidding the Ridgeline distribution center and need a number for site concrete: footings, slab-on-grade, and dock aprons. Bid is due the 28th. Can you turn this around, and are you available to start in October?"
> **AI draft, 6:41am:** "Hi Mark, thanks for the invite on Ridgeline. Site concrete is squarely in our wheelhouse and we have crews opening up in October. To get you a solid number before the 28th, can you send the structural drawings and the slab spec? We carry $2M general liability and can name you as additional insured before mobilization. You'll have our proposal at least two days ahead of the deadline."
Notice what the draft doesn't do. It doesn't invent a price, promise a start date the schedule can't support, or paste in boilerplate. Every claim in it traces to a document, and a person still reads it before it leaves the building. If your bids are 200-question proposal documents rather than emails, that's a different problem with [a different toolset](/blog/best-rfq-email-management-software).
## What changes when replies go out the same day
**Faster response times.** The classic data here is old, so we'll date it honestly. In March 2011, Harvard Business Review published an audit of 2,241 US companies ("The Short Life of Online Sales Leads") that found the average first response to an inbound lead took 42 hours, 23% of companies never responded at all, and firms replying within an hour were roughly seven times more likely to qualify the lead ([HBR](https://hbr.org/2011/03/the-short-life-of-online-sales-leads), 2011). That study measured web leads, not RFQs, so treat it as directional. The direction isn't controversial: the first credible answer shapes the shortlist.
**Fewer missed opportunities.** Sit with that 23%-never-replied figure for a second. GCs behave as if they know it: standard practice is to invite several subs per trade precisely because many invitations go unanswered. Being the sub that always answers, even when the answer is a fast and polite no-bid, is a cheap reputation to buy, and it's the one that gets you invited back.
**Less admin work, which you couldn't hire for anyway.** In 2025, the AGC of America and NCCER's workforce survey of nearly 1,400 firms found 92% of firms trying to hire had difficulty finding qualified workers, and roughly four in five had openings for salaried positions, the office and professional roles that answer email ([AGC/NCCER 2025 Workforce Survey](https://www.agc.org/news/2025/08/28/construction-workforce-shortages-are-leading-cause-project-delays-immigration-enforcement-affects), 2025). Deloitte's 2026 Engineering and Construction Outlook projects the industry needs about 499,000 additional workers in 2026 and puts nearly $124 billion of output at risk from labor gaps ([Deloitte](https://www.deloitte.com/us/en/insights/industry/engineering-and-construction/engineering-and-construction-industry-outlook.html), 2025). Automating the inbox isn't about replacing your office manager. It's about the second office hire you can't make.
## Setting up RFQ email automation without risking a bad quote
Three steps, and the guardrails matter more than the features:
1. **Connect the inbox.** Whatever address the quote requests hit: estimating@, bids@, info@. Gmail or Outlook, and a shared mailbox works fine.
2. **Feed it your documents.** Rate sheet, capability statement, service area, insurance and licensing, standard exclusions, and a handful of past quotes you were proud of. This is the grounding step; the drafts are only as good as what you give them.
3. **Set the guardrails.** Trigger keywords like *RFQ*, *quote*, *bid*, and *proposal* route into drafting. Negative keywords like *claim*, *dispute*, *back charge*, and *change order* route straight to a person, no draft. Leave draft-and-approve on. The AI writes, you send.
That last guardrail isn't a setting we invented for this post. Drafts-with-approval is how InboxPilot works by default: the AI draft is the unit we meter every plan by, and sending stays a human act.
On InboxPilot, that setup runs on any plan: Free covers 25 AI drafts to test it on real traffic, Hobby is $29 per month, and Standard at $149 per month covers 1,500 drafts, unlimited inboxes, and knowledge base grounding, which is the feature doing the heavy lifting in step 2. Annual billing takes roughly 20% off. Full details on the [pricing page](/pricing).
**[See how InboxPilot helps construction teams respond to RFQs faster →](/use-cases/rfq-email-automation)**
The construction page includes real draft examples for RFQs, subcontractor emails, vendor pricing, and scheduling requests.
## Related reading
- [RFQ email automation, the full workflow](/use-cases/rfq-email-automation): how InboxPilot answers quote requests from your catalog, with a worked example.
- [Best RFQ software for suppliers](/blog/best-rfq-email-management-software): response platforms compared, and why the email intake layer is a separate purchase.
- [Best shared inbox software for Gmail and Outlook](/blog/best-shared-inbox-software): where estimating@ actually lives, and how teams coordinate on it.
- [Instant lead replies for sales teams](/blog/sales-team-instant-lead-replies): the same speed-to-respond problem, framed for inbound leads.
---
*Statistics are attributed to their original source with the year of publication stated, including where that year is older than the article. The FMI/PlanGrid figures are from 2018 and the HBR response-time audit is from 2011; both are labeled as such above rather than passed off as current research. InboxPilot pricing was verified against the pricing page in July 2026. InboxPilot is the publisher of this article.*
---
## How Visa Agencies Can Automate Client Emails with AI
Source: https://www.inboxpilot.co/blog/visa-agency-email-automation
Published: 2026-07-16
Schengen applications hit 11.7 million in 2024, and 64 countries now offer digital nomad visas. How visa agencies automate client email with AI, human-approved.
At 11:04pm, a freelance developer in Austin sends the same email to three relocation agencies: "I want to move to Spain next spring. Do I qualify for the digital nomad visa, and what would it cost?" One of those agencies answers before breakfast in Texas. Guess which one gets the consultation.
Visa and relocation work is casework, but the business is won and lost in the inbox. Prospects shop several firms at once, applications live or die on complete documents, and clients mid-move ask "where are we?" in four languages across nine time zones.
**Disclosure:** we make [InboxPilot](/), an AI email agent that drafts replies inside Gmail and Outlook, grounded in your own documents. This post explains the workflow with sourced numbers, and it's upfront about the line no tool should cross: an AI can draft from your eligibility guides, but it should never promise an outcome or give case-specific immigration advice.
## TL;DR
- In 2024, Schengen states received **11.7 million short-stay visa applications, up 13.6% in one year** (European Commission, May 2025). Demand is growing faster than agency headcount. See [the demand numbers](#the-demand-side-more-applicants-same-inboxes).
- **64 countries now run formal digital nomad visa programs, and 91% of them launched since 2020** (Global Citizen Solutions data via Forbes, Sept 2025). Spain tops the ranking; Italy joined in April 2024.
- Speed wins retainers. In Harvard Business Review's 2011 audit, **23% of companies never answered an inbound lead at all**. See [what changes](#what-changes-when-every-inquiry-gets-a-same-day-reply).
- **[InboxPilot](#setting-up-visa-agency-email-automation-without-risking-bad-advice), which is us,** can draft eligibility, checklist, document, and status replies from your own guides, in the sender's language, with [a consultant approving every send](#the-workflow-from-eligibility-question-to-approved-reply).
## The demand side: more applicants, same inboxes
In 2025, the European Commission reported that Schengen countries received 11.7 million short-stay visa applications in 2024, up 13.6% from 2023 and 56% from 2022, with 9.7 million visas issued and a 14.8% refusal rate ([European Commission, DG Migration and Home Affairs](https://home-affairs.ec.europa.eu/news/visa-applications-reach-117-million-eu-and-schengen-associated-countries-2025-05-20_en), 2025). Behind almost every one of those applications sits an email thread: requirements, documents, fees, status.
The longer-stay market is growing too. The UN counted 304 million people living outside their birth country in 2024 ([UN DESA, International Migrant Stock 2024](https://www.un.org/development/desa/pd/sites/www.un.org.development.desa.pd/files/undesa_pd_2025_intlmigstock_2024_key_facts_and_figures_advance-unedited.pdf), 2025). Spain, the market our two examples below serve, passed 10 million foreign-born residents for the first time on 1 January 2026 ([INE](https://www.ine.es/dyngs/Prensa/en/ECP4T25.htm), 2026), and in 2024 it granted a record 15,638 first residence permits to Americans, more than any other EU country ([The Local, citing Eurostat](https://www.thelocal.es/20250924/revealed-record-number-of-americans-move-to-spain), 2025).
Then there's the product that created a whole new client type. As of September 2025, 64 countries offered formal digital nomad visa (DNV) programs, and 91% of them launched since 2020 ([Global Citizen Solutions ranking, via Forbes](https://www.forbes.com/sites/alexledsom/2025/09/10/heres-how-digital-nomad-visas-compare-based-on-new-2025-data/), 2025). Spain ranks first on that index. Italy opened its own program in April 2024 with a minimum income around 28,000 euros a year ([K&L Gates](https://www.klgates.com/Digital-Nomad-Visa-5-30-2024), 2024).
Grand View Research valued the immigration services category at roughly $14.2 billion in 2022, projecting 5.8% annual growth through 2030 ([Grand View Research](https://www.grandviewresearch.com/pipeline/immigration-services-industry-procurement-intelligence-report), 2023). More applicants, more visa types, more competing agencies. The inbox is where all of it lands first.
## The five email workflows that fill the inbox
Every visa and relocation agency we've looked at runs some version of the same five piles:
| Workflow | What it looks like | Why it drags |
|---|---|---|
| **Eligibility questions** | "I'm a US freelancer earning $95k. Do I qualify?" | Each one needs passport, income, and work situation checked against a moving target of rules |
| **Requirement checklists** | "What documents do I need for the Spain DNV with a spouse?" | The answer exists in your guides; someone still re-types it for every passport and family shape |
| **Document collection** | Scans arrive incomplete, mislabeled, one attachment at a time | Chasing the missing apostille eats hours and stalls the case |
| **Status checks** | "Any news from the consulate?" | Zero-value to answer, costly to ignore; clients mid-move are anxious |
| **Follow-ups and cross-sell** | Tax questions after the visa, healthcare, housing, renewals | High-value threads that go cold because nobody follows up on time |
None of this is unique to immigration work, but the volume multiplier is. In 2025, Microsoft's Work Trend Index measured the average worker receiving 117 emails a day, interrupted every two minutes during core hours ([Microsoft WorkLab](https://www.microsoft.com/en-us/worklab/work-trend-index/breaking-down-infinite-workday), 2025). Now add clients writing from every time zone their passports come from, in their own languages, all pointed at a consultancy of five people.
## What two real agencies tell you about the problem
Look at two well-run firms in this space and you can see the email load written into their business models.
**[MoveWise](https://movewise.net)** sells digital nomad visa and tax packages for Spain and Italy as fixed modules, listed between 295 and 995+ euros per person, with a money-back guarantee if an application is rejected. It operates fully remote: email, WhatsApp, video calls. Think about what that guarantee does to the inbox. When a rejection costs you the fee back, the first eligibility email isn't admin, it's underwriting. Mis-qualify a prospect in that reply and you either lose the sale or take on refund risk. And fixed modules mean pre-sales email has one more job: routing each prospect to the right package before a competitor answers at all.
**[Moving to Spain](https://movingtospain.com)** has guided expats from Barcelona since 2015 and reports having helped more than 20,000 of them. Its menu runs from visas and taxes to healthcare, insurance, housing, banking, and school search. Breadth creates a different problem: one inquiry can touch three specialisms, so the inbox is a routing switchboard, and every live client generates status threads across several workstreams at once. A free-roadmap funnel like theirs also produces exactly the kind of high-volume, top-of-funnel questions that are too repetitive for consultants and too valuable to ignore.
To be clear about what this section is: neither company is an InboxPilot customer, we haven't spoken with either, and everything above comes from their public websites as of July 2026. They're here because they cleanly illustrate the two dominant shapes of this business, productized packages and full-service guidance, and both shapes tend to bury teams in exactly the email that's automatable.
## What AI can handle for a visa agency
Here's what an AI email assistant for immigration consultants and visa agencies can genuinely own, and where it has to stop.
### 1. Qualify the eligibility question
The AI reads the inquiry, pulls out nationality, income, work situation, and family members, and drafts a reply against your eligibility guide. Clear fits get a confident draft plus a consultation link. Edge cases get flagged to a consultant instead of guessed at. Either way, the prospect hears back while they're still deciding which agency to talk to.
### 2. Send the right checklist
"What documents do I need?" has a precise answer for every passport, destination, and visa type, and it already lives in your requirement guides. The AI drafts the exact checklist with processing time and fees, instead of someone copy-pasting from a PDF for the fourth time that morning.
### 3. Chase the documents
When a submission arrives incomplete, the draft asks for the specific missing items: the apostilled background check, the second bank statement, the passport photo at the right size. Cases arrive at your caseworkers complete instead of in fragments.
### 4. Reply in the sender's language
This is the quiet revenue lever. In CSA Research's 2020 survey of 8,709 consumers in 29 countries, 76% preferred buying with information in their own language, and about 75% said they're more likely to buy again when customer care comes in their language ([CSA Research, Can't Read, Won't Buy](https://csa-research.com/l/media/Consumers-Prefer-their-Own-Language), 2020). An assistant that reads Portuguese and drafts Portuguese means every market gets a native-speed reply without hiring for it.
### 5. Route and escalate the rest
Status checks get answered from your tracking notes. Tax questions route to the tax specialist. And negative keywords pull the sensitive traffic out of automation entirely: anything mentioning a rejection, appeal, refund, or complaint reaches a person untouched, with no draft attached. Immigration outcomes affect people's lives; those threads deserve a human from the first word.
## The workflow: from eligibility question to approved reply
Here's the loop end to end, using the inquiry from the top of this post:
1. **The email lands** at 11:04pm, addressed to info@ like everything else.
2. **The AI classifies it** as a pre-sales eligibility question: Spain, digital nomad visa, family of three.
3. **It checks your documents**: the eligibility guide, the family-member income rules, the Spain package sheet, your consultation booking link.
4. **It drafts a reply**, in the sender's language, ready two minutes later.
5. **A consultant approves it** first thing in the morning, edits if needed, and sends. The prospect in Texas wakes up to an answer that sounds like it came from someone who read their email carefully. Someone did; the AI just went first.
What that looks like:
> **Incoming, 11:04pm:** "Hi, I'm a US citizen working remotely as a freelance developer, making around $95k. I want to move to Valencia next spring with my wife and daughter. Do we qualify for the digital nomad visa, and what do your services cost?"
> **AI draft, 11:06pm:** "Hi Jordan, thanks for reaching out. Based on what you've described, freelance income near $95k with clients outside Spain, you're well positioned for Spain's digital nomad visa, and it extends to spouses and children with a higher income threshold your figures appear to meet. To confirm, we'd want to see your last three months of invoices and evidence of your ongoing client relationships. Our Spain family package covers the full application; pricing is on the attached sheet. Would a 20-minute call this week help? Booking link below."
Notice the hedges: "appear to meet," "to confirm." The draft works from the agency's own guide, asks for evidence, and promises nothing. It doesn't quote legal thresholds from memory and it doesn't give case-specific advice. That's the design, not a limitation.
## What changes when every inquiry gets a same-day reply
**You win the shopped prospect.** The classic data is old, so we'll date it plainly: Harvard Business Review's March 2011 audit of 2,241 US companies found the average first response to an inbound lead took 42 hours, 23% never responded at all, and firms replying within an hour were about seven times likelier to qualify the lead ([HBR](https://hbr.org/2011/03/the-short-life-of-online-sales-leads), 2011). It measured web leads, not visa inquiries, so treat it as directional. But your prospect emailed three agencies tonight. Somebody's reply arrives first.
**Every market gets covered.** Time zones and languages stop being a staffing problem. The 11pm inquiry from Austin, the Portuguese question at dawn, the German one during your lunch: all drafted on arrival, all waiting for a human yes.
**Consultants do casework again.** The checklist re-typing, the status replies, the document chasing all move off the desks of the people you hired for judgment. In a category growing 5.8% a year on Grand View's projection, capacity is the constraint, and this is the cheapest capacity you can add.
## Setting up visa agency email automation without risking bad advice
Three steps. The guardrails matter more than anything on the feature list:
1. **Connect the inbox.** Whatever address the inquiries hit: info@, hello@, applications@. Gmail or Outlook, shared mailboxes included.
2. **Feed it your documents.** Eligibility guides, requirement checklists per visa type, fee tables, package sheets, your booking link, and a handful of past replies you were proud of. Keep them current; the drafts inherit whatever the documents say.
3. **Set the guardrails.** Trigger keywords like *visa*, *eligibility*, *requirements*, *documents*, and *status* route into drafting. Negative keywords like *rejection*, *appeal*, *refund*, *complaint*, and *lawyer* route straight to a person, no draft. Leave draft-and-approve on for everything.
That approval step isn't a setting we invented for this article. Drafts-with-approval is how InboxPilot works by design: the AI draft is the unit every plan meters, and a person still presses send. Client documents aren't used to train public models. Free covers 25 AI drafts to test on real traffic, Hobby is $29 per month, and Standard at $149 per month covers 1,500 drafts, unlimited inboxes, and knowledge base grounding, the feature carrying step 2. Annual billing takes roughly 20% off. Details on the [pricing page](/pricing).
**[See how InboxPilot automates document collection and chasing →](/use-cases/document-collection-automation)**
## Related reading
- [Document collection automation](/use-cases/document-collection-automation): the checklist, acknowledgment, and reminder workflow in full.
- [How construction companies automate RFQ and customer emails](/blog/construction-rfq-email-automation): the same drafts-with-approval playbook, applied to quote requests.
- [Best shared inbox software for Gmail and Outlook](/blog/best-shared-inbox-software): where info@ actually lives, and how teams coordinate on it.
- [Instant lead replies for sales teams](/blog/sales-team-instant-lead-replies): the speed-to-lead problem on its own.
---
*Statistics are attributed to their original source with the year of publication stated, including where that year is older than the article; the HBR audit is from 2011 and the CSA Research survey is from 2020, and both are labeled as such. Facts about MoveWise and Moving to Spain come from their public websites, retrieved July 2026; neither company is affiliated with InboxPilot or was interviewed for this article. InboxPilot pricing was verified against the pricing page in July 2026. InboxPilot is the publisher of this article.*
---
## Best RFQ Software for Suppliers: 8 Tools (2026)
Source: https://www.inboxpilot.co/blog/best-rfq-email-management-software
Published: 2026-07-13
Most RFQs arrive by email, not through a portal. Compare RFQ response platforms and the email intake layer where quote requests actually land.
Every guide to RFQ software makes the same assumption: that the RFQ is already a document sitting on your desk. They compare content libraries, answer automation, and proposal assembly. All useful. All downstream of the part where suppliers actually lose the deal.
Because for most suppliers, the RFQ does not arrive as a document. It arrives as an email, into `sales@` or `quotes@` or `info@`, where it sits alongside 200 other messages until somebody notices it.
**Disclosure:** we make InboxPilot, which solves the email intake problem and does not solve the proposal problem. It is not the top pick in the response-platform category below, because it does not belong in that category. If your RFQ is a 200-question document, you need Responsive or Loopio. If your RFQ is an unopened email, that is a different problem, and it is the one we cover here.
## TL;DR
- **Best overall for RFQ email management:** [InboxPilot](#category-two-the-email-layer-where-rfqs-actually-arrive), which is us. Most RFQs arrive as email, not portal submissions, and InboxPilot is the tool built for that intake layer: triage, routing, and grounded draft replies inside Gmail or Outlook.
- **Only 45% of RFP submissions go through online portals**, according to [Loopio's 2026 benchmark](https://loopio.com/blog/portal-response/) of 1,500+ companies and 250,000+ RFPs. The majority arrive by other channels, mostly email.
- **88% of manufacturers and distributors have lost deals** to inefficiencies in how quotes get generated and approved ([TrendCandy for Aleran](https://www.aleran.com/press-article/b2b-manufacturing-survey-manual-quoting-processes-leading-to-lost-revenue-driving-investments-in-ai-powered-commerce-and-cpq/), July 2025, n=200, margin of error ±4.6%).
- **Best RFQ response platform:** [Responsive](#1-responsive-formerly-rfpio) for enterprise teams, [Loopio](#2-loopio) for high-volume repeatable responses, [AutoRFP.ai](#4-autorfp-ai) if you want published pricing.
- **Not for you:** SAP Ariba, Coupa, Jaggaer, Zycus. Those are your *customer's* tools. See [why](#first-rfq-software-means-two-opposite-things).
## First: "RFQ software" means two opposite things
Search "RFQ software" and you will be shown SAP Ariba next to Loopio, as if a supplier could use either. They sit on opposite sides of the transaction.
| Side | What the tool does | Who uses it | Examples |
|---|---|---|---|
| **Buyer-side** (sourcing, procurement) | Issue RFQs, invite vendors, run auctions, score incoming bids | Your customer's procurement team | SAP Ariba, Coupa, Jaggaer, Zycus, Procurify |
| **Supplier-side** (response management) | Build and submit the response, reuse past answers, manage approvals | You, the vendor being asked to quote | Responsive, Loopio, Arphie, AutoRFP, Tribble, SiftHub, Qvidian, Ombud |
If you are reading this because quote requests keep landing in your inbox, **you are on the supplier side.** Buyer-side platforms are how those requests reach you. Buying one will not help you answer them. Skip every listicle that mixes the two, which is most of them.
## The thing nobody in this category writes about
Here is a statistic that appears in nearly every RFQ software article, quoted approvingly, with nobody noticing what it means.
Loopio's 2026 RFP benchmark, built from more than 1,500 global companies and over 250,000 RFPs, reports that **only 45% of submissions go through online portals.** ([Loopio](https://loopio.com/blog/portal-response/))
Turn that around. **The majority of RFPs and RFQs do not arrive through a portal.** They arrive through email, forwarded PDFs, spreadsheets attached to a message from a buyer you have never met, and requests dropped into a shared address that three people half-watch.
Every RFQ platform in this post is excellent at the second half of the job. Not one of them touches the first half. They assume you already have the document. They do not triage a shared mailbox, they do not route an inbound quote request to the right engineer, and they do not draft the acknowledgement that keeps you in the running while you work up the real numbers.
That gap is where deals die, and the data says so.
## What slow intake actually costs
In July 2025 the research firm TrendCandy surveyed 200 decision-makers at US manufacturers, wholesalers, and distributors with 100+ employees on behalf of Aleran (margin of error ±4.6% at 95% confidence). The findings:
- **88% have lost deals** because of inefficiencies in how quotes are generated and approved.
- **71% take at least a full day** to produce a quote.
- **Only 37%** have fully automated quoting.
- Manual workflows leak roughly **5% of annual revenue.**
([Aleran press release](https://www.aleran.com/press-article/b2b-manufacturing-survey-manual-quoting-processes-leading-to-lost-revenue-driving-investments-in-ai-powered-commerce-and-cpq/), corroborated by [Digital Commerce 360](https://www.digitalcommerce360.com/2025/10/21/survey-manufacturers-lose-revenue-to-manual-quoting/))
Note what that first number is not saying. It is not "88% lost deals because their proposal was weak." It is inefficiency in generating and approving quotes. Much of that is upstream of the proposal entirely.
### A note on the speed-to-lead statistics everyone quotes
You will see two famous numbers in every article on this subject: that responding in 5 minutes rather than 30 makes you 100 times more likely to make contact, and that responding within an hour makes you 7 times more likely to qualify a lead.
Both are real. Both are also **from 2007 and 2011**, and both measured phone calls to inbound web leads, not RFQs to suppliers. The 100x figure comes from Dr. James Oldroyd's Lead Response Management study ([MIT/InsideSales, 2007](https://25649.fs1.hubspotusercontent-na2.net/hub/25649/file-13535879-pdf/docs/mit_study.pdf)). The 7x figure and the finding that **23% of audited companies never responded at all**, with an average response time of 42 hours, come from the Harvard Business Review audit of 2,241 US companies ([Oldroyd, McElheran and Elkington, HBR, March 2011](https://hbr.org/2011/03/the-short-life-of-online-sales-leads)).
We are citing them with their dates attached because most articles in this category do not, and quietly implying that 19-year-old phone-call data is fresh 2026 RFQ research is exactly the kind of thing that should make you distrust an article. Treat them as directional. The direction is not in dispute.
## Category one: RFQ and RFP response platforms
These build the response. All of them assume you already have the document. **Pricing in this category is almost universally quote-only**, and we have not invented a single number below.
| Tool | Best for | Email intake? | Pricing |
|---|---|---|---|
| **Responsive** | Enterprise proposal teams with a mature content library | No | Quote-only. Vendr observes $7K to $28K/yr |
| **Loopio** | High-volume, repeatable responses | No | Quote-only |
| **Arphie** | Mid-size teams wanting fast onboarding | No | Quote-only, per-project |
| **AutoRFP.ai** | Teams doing 10+ requests a month | No | **Published: $899 to $1,299/mo** |
| **Tribble** | Grounding answers in Gong, Slack, and CRM | No | Quote-only, credit-based |
| **SiftHub** | Teams needing bid/no-bid and SME coordination | No | Quote-only |
| **Upland Qvidian** | Regulated industries needing compliance trails | No | Quote-only |
| **Ombud** | Mid-market response teams | No | Quote-only |
### 1. Responsive (formerly RFPIO)
**Best for:** Enterprise proposal teams with a real content library and the headcount to maintain it.
**Strengths:** The largest install base in the category. Deep workflow automation. Strong real-time extraction from knowledge documents.
**Tradeoffs:** TechTarget explicitly cites a **steep learning curve**. Cost is opaque, and implementation is a project rather than a purchase.
**Pricing:** Quote-only. The procurement aggregator Vendr reports observed contracts between roughly **$7,000 and $28,000 per year, averaging about $13,955**. That figure is Vendr's observation, not Responsive's published price. ([Vendr](https://www.vendr.com/marketplace/responsive))
### 2. Loopio
**Best for:** Teams responding to a high volume of repeatable RFPs, RFIs, and security questionnaires.
**Strengths:** Intuitive interface. Strong content library reuse. Publishes the best benchmark data in the category, which is genuinely useful whether or not you buy the product.
**Tradeoffs:** TechTarget notes a longer implementation than competitors. Foundations starts at a 10-seat baseline, so it is not built for the one-person quoting desk.
**Pricing:** Quote-only, confirmed on Loopio's own pricing page ("book a call to build a custom quote"). ([loopio.com/pricing](https://loopio.com/pricing/))
### 3. Arphie
**Best for:** Mid-size teams that want AI-native drafting and fast onboarding.
**Strengths:** Priced per project with unlimited users rather than per seat, which is unusual and buyer-friendly. Source citations on generated answers. Will explicitly say "I don't know" rather than hallucinate, which matters more than it sounds.
**Tradeoffs:** Newer and smaller vendor. Reported gaps in reporting depth, mobile, and export. Its marketed "84% AI acceptance rate" is a vendor claim, not an audited figure.
**Pricing:** Quote-only, concurrent-project model.
### 4. AutoRFP.ai
**Best for:** Teams handling 10 or more requests a month who want to know the price before booking a call.
**Strengths:** **The only tool in this category with published pricing**, which in a market this opaque is worth something on its own. Ingests messy Excel and Word formats. Browser extension for working inside procurement portals.
**Tradeoffs:** The vendor is also a prolific content marketer that publishes comparisons of its own competitors, so discount its self-assessments accordingly.
**Pricing:** Scale **$899 per month**, Accelerate **$1,299 per month** billed annually, Enterprise on request.
### 5. Tribble
**Best for:** Teams that want answers grounded in the systems they already use.
**Strengths:** Retrieval across Gong, Slack, and CRM. Fast implementation. Native Google Docs and Sheets. Win/loss analytics.
**Tradeoffs:** **Credit-based usage pricing makes cost genuinely hard to forecast.** It is an asynchronous document tool, so it has nothing to offer during a live procurement call.
**Pricing:** Quote-only, monthly credit packs.
### 6. SiftHub
**Best for:** Teams that need bid/no-bid qualification and structured SME coordination, not just drafting.
**Strengths:** Covers the full lifecycle including the go/no-go decision, which most tools skip. Governance and review routing.
**Tradeoffs:** TechTarget notes a longer implementation. Smaller vendor.
**Pricing:** Quote-only.
### 7. Upland Qvidian
**Best for:** Regulated industries (financial services, insurance) that need compliance trails and access control more than they need a modern interface.
**Strengths:** Mature content library. Strong governance. G2 rating of 4.3 out of 5 across roughly 150 reviews.
**Tradeoffs:** Widely criticized for a **dated interface, slow search, and complex implementation.** You will see a "$15,000 to $25,000" price floated online. It originates from a direct competitor's blog, so we are not repeating it as fact.
**Pricing:** Quote-only. ([uplandsoftware.com/qvidian](https://uplandsoftware.com/qvidian/))
### 8. Ombud
**Best for:** Mid-market response teams focused on content reuse.
**Strengths:** Ease of use. OmMatch autofill. Structured collaboration.
**Tradeoffs:** Content-freshness management is a chore. Collaborative editing gets awkward on long documents. Import and export are rigid.
**Pricing:** Quote-only, fully custom.
## Category two: the email layer, where RFQs actually arrive
These are not substitutes for the platforms above. **If an RFQ is a 200-question document, you need a response platform. If it is an email you have not opened yet, that is a different problem.** Most suppliers have both, and only buy for one.
Unlike the response platforms, everything here publishes its price.
| Tool | Triages inbound? | Auto-routes? | Drafts first reply? | Entry price | Outlook? |
|---|---|---|---|---|---|
| **InboxPilot** | Yes | Yes | Yes, grounded in your docs | $29/mo flat | Yes |
| **Front** | Yes (AI Topics) | Yes, rules | Yes, Copilot is a paid add-on | $25/seat/mo | Yes |
| **Hiver** | Yes | Yes, rules + round-robin | Yes, from Growth tier | $25/user/mo | Via Omni only |
| **Missive** | Partial | Yes, up to 1,000 rules | AI on Productive and above | $14/user/mo | Yes |
| **Gmelius** | Yes | Yes | Yes | $19/user/mo | **No** |
### InboxPilot
**Best for:** Suppliers whose quote requests land in a shared Gmail or Outlook mailbox and sit there too long.
This is our product, and this is the one category in this post where we will claim the top spot, because it is a narrow claim: **triage and first response on inbound RFQ email**, inside the inbox you already use.
**What it does here:** watches `sales@` or `quotes@`, recognizes a quote request when one arrives, labels and prioritizes it, routes it to the right rep or engineer, and drafts a first reply grounded in your product docs, pricing, and past responses. The buyer gets an acknowledgement with real content in minutes instead of a silence that lasts two days.
**Tradeoffs, plainly:**
- **It is not an RFP response platform.** No content library, no proposal document assembly, no compliance matrix, no bid/no-bid workflow. It does nothing about the 33 hours Loopio says a full RFP response takes. If that is your bottleneck, buy Loopio and do not buy us.
- Pricing is metered by AI draft, not per seat. That is cheaper than per-seat tools for a small quoting desk and worth doing the math on if you run high volume.
- Newer than the incumbents, with a shorter public track record.
**Pricing:** Free (25 AI drafts). Hobby $29/mo. Standard $149/mo (1,500 drafts, unlimited inboxes, knowledge base grounding). Pro $499/mo (12,000 drafts, advanced routing, SSO). Enterprise custom. Annual billing is about 20% less (Standard $119/mo). ([inboxpilot.co/pricing](/pricing))
### Front
**Best for:** Larger sales teams that want a full customer operations platform around the shared mailbox.
**Strengths:** Mature rules engine, strong analytics, omnichannel.
**Tradeoffs:** The AI that does the drafting is a paid add-on ($20 per seat per month for Copilot, Autopilot from $0.05 per conversation), so the real cost sits well above the $25 headline. Starter caps you to a single channel type.
**Pricing:** Starter $25 per seat per month, Professional $65, Enterprise $105. ([front.com/pricing](https://front.com/pricing))
### Hiver
**Best for:** Google Workspace quoting desks that will not leave Gmail.
**Strengths:** Native in Gmail, free tier, AI copilot from the entry paid tier, round-robin routing that maps well to assigning quotes to reps.
**Tradeoffs:** Gmail-first. Outlook requires the separate Omni product, which matters here because most manufacturers run on Microsoft 365. Reviewers report performance lag at volume.
**Pricing:** Free. Growth $25 per user per month annual, Pro $55, Elite $85. ([hiverhq.com/pricing](https://hiverhq.com/pricing))
### Missive
**Best for:** Small quoting teams on a budget who want to discuss a quote in the thread.
**Strengths:** Cheapest entry at $14. A powerful rules engine (up to 1,000 rules on Productive and above). Provider-agnostic.
**Tradeoffs:** The $14 Starter tier has **no AI and no integrations**, and AI requires buying credits separately, so the useful plan is Productive at $24.
**Pricing:** Starter $14, Productive $24, Business $36 per user per month. ([missiveapp.com/pricing](https://missiveapp.com/pricing))
### Gmelius
**Best for:** Gmail-only teams that want shared inbox plus Kanban.
**Tradeoffs:** **Gmail only. No Outlook.** For a manufacturer or distributor, that is usually disqualifying on its own.
**Pricing:** Meli $19, Growth $25, Pro $40 per user per month annual. ([gmelius.com/pricing](https://gmelius.com/pricing))
## What to look for
### 1. Work out which half of the problem is actually costing you
Two very different failures look the same from the outside:
- **You are losing bids you responded to.** Your response is too slow to assemble, or not good enough. Buy a response platform.
- **You are losing bids you never responded to.** The RFQ sat in a shared mailbox for three days, or went to the wrong person, or nobody realized it was time-sensitive. No response platform will help you. Fix intake.
Most suppliers have both problems and only buy for the first, because that is the only one the market sells against.
### 2. Confirm you are being sold a supplier-side tool
If the demo shows you inviting vendors and scoring bids, you are looking at a buyer-side procurement suite. Politely leave.
### 3. Insist on a real price
Almost this whole category is quote-only. That is a choice, not a necessity: AutoRFP publishes $899 and $1,299, and every email-layer tool publishes per-seat pricing. If a vendor will not give you a number before a discovery call, that tells you something about the sales cycle you are about to enter.
### 4. Check Outlook support before the feature list
Most manufacturers and distributors run on Microsoft 365. Gmelius does not support Outlook at all, and Hiver's Gmail product does not either. That fact eliminates tools faster than any feature comparison.
### 5. Ask what happens to the RFQ before it becomes a document
This is the question the entire category is built to avoid. Ask it on every call: *how does the quote request get from my customer's email to your platform?* The answer, in every case, is that someone on your team does it manually.
## How to choose, in one paragraph
If you run a proposal team responding to structured, document-heavy RFPs, buy a response platform: **Responsive** if you are enterprise, **Loopio** if volume is high and repeatable, **AutoRFP** if you want to know the price today. If you are a supplier whose quote requests arrive as email into a shared mailbox and the real problem is that they sit there, no response platform will help you, and that is the narrow case where [InboxPilot](/pricing) is built to help. Most growing suppliers eventually want both, and the intake layer is the cheaper of the two to fix first.
## Related reading
- [RFQ email automation](/use-cases/rfq-email-automation): what automating quote-request email actually looks like, before and after.
- [Instant lead replies for sales teams](/blog/sales-team-instant-lead-replies): the same intake problem, framed for inbound leads.
- [Best shared inbox software for Gmail and Outlook](/blog/best-shared-inbox-software): where quote requests land, and how teams coordinate on them.
- [Best email management software](/blog/ai-email-agent): the wider category.
---
*Pricing was verified against vendor pricing pages in July 2026 where published. Where a vendor does not publish pricing, this article says so rather than estimating. Statistics are attributed to their original source with the year of publication stated, including where that year is older than the article. InboxPilot is the publisher of this article and is one of the tools discussed.*
---
## Best Shared Inbox Software for Gmail and Outlook in 2026
Source: https://www.inboxpilot.co/blog/best-shared-inbox-software
Published: 2026-07-13
Compare shared inbox software for Gmail and Outlook: InboxPilot, Front, Hiver, Missive, Gmelius and Help Scout, plus Google's new native shared inbox. 2026 pricing.
Most comparisons of shared inbox software have a curious feature in common: they do not cite a single source. They assert that shared mailboxes "break down at scale" without telling you where that number comes from, and they blend help desks in with shared inboxes as if they were the same purchase.
This one is sourced. Where a limit exists, we cite Microsoft's or Google's own documentation. Where a tool has a real weakness, we name it, including our own.
**Disclosure:** we make InboxPilot, and it is our top pick. It earns that spot for a specific reason rather than by default: most teams shopping this category are actually trying to fix volume, and InboxPilot is the only tool here that reduces how much email reaches humans instead of helping humans divide it faster. It works differently from a classic shared inbox, and its entry below states exactly what it does not do. If your problem is coordination, two agents replying to the same customer, the classic shared inbox to beat is Front, and we say that plainly too.
## TL;DR
- **Best overall:** [InboxPilot](#1-inboxpilot). The only tool here that reduces email volume instead of dividing it, native in both Gmail and Outlook, priced per workspace rather than per seat.
- **Best classic shared inbox:** [Front](#2-front). The most complete coordination product, with the pricing to match.
- **Best for Gmail teams:** [Hiver](#3-hiver). Lives inside Gmail, free tier, near-zero onboarding.
- **Best for collaboration:** [Missive](#4-missive). Real-time co-drafting and chat in the thread, from $14 per user.
- **Best for support teams:** [Help Scout](#5-help-scout). Shared inbox plus knowledge base, free for 5 users.
- **Best free option, Google:** [Google's new native shared inbox](#9-googles-native-shared-inbox-new-in-2026). Free, in real Gmail, and almost nobody knows it exists.
- **Best free option, Microsoft:** [the M365 shared mailbox](#10-microsoft-365-shared-mailbox). Free, native in Outlook, with documented ceilings.
- **Cheapest Gmail-native paid option:** [Gmelius](#6-gmelius) at $19, if nobody on your team uses Outlook.
## Start here: which of the three are you actually buying?
Almost every bad purchase in this category comes from confusing three different products.
| Class | What it gives you | What it does not | Examples |
|---|---|---|---|
| **Plain shared mailbox** | Several people can open one mailbox. Free. | No assignment, no collision detection, no reporting | M365 shared mailbox, Google's native shared inbox, Google Groups Collaborative Inbox |
| **Shared inbox tool** | Assignment, collision detection, internal notes, light reporting. Still feels like email. | Deep ticketing, CSAT, portals | Front, Hiver, Gmelius, Missive |
| **Help desk** | Tickets, queues, macros, SLAs, CSAT, deep analytics | The feeling that you are still using email | Zendesk, Freshdesk (Help Scout straddles) |
Work out which class you are in before you compare a single feature. A three-person team does not need Zendesk. A 30-agent org cannot run on a Google Group.
## The free options first, because you may not need to buy anything
Every listicle in this category skips straight to the paid tools. Two free options are worth ruling out first, and one of them is new enough that the competing articles have not noticed it.
### Google's native shared inbox is new, free, and undocumented in every comparison we found
Google Workspace admins can now create a shared email address directly from the Admin console (Users, then "Set up a shared email address"). Unlike the old Collaborative Inbox, it lives in **real Gmail**, not the Google Groups web interface. It is included on Business Starter, Standard, and Plus with no paid add-on. ([Google Workspace admin docs](https://knowledge.workspace.google.com/admin/users/create-a-shared-inbox))
It gives you access and sending from the shared address. It gives you **no collision detection, no automation, and no SLA reporting.** It solves access, not coordination. But if your problem is "three of us need to see support@," it is free and it is enough.
### Microsoft tells you exactly where its shared mailbox breaks
This is the best-sourced fact in this entire post, and it comes from Microsoft's own admin documentation:
> "A shared mailbox supports a maximum of 25 users. If too many users access the mailbox at the same time, they might experience connection failures or duplicated messages."
> ([Microsoft Learn, About shared mailboxes](https://learn.microsoft.com/en-us/microsoft-365/admin/email/about-shared-mailboxes))
Duplicated messages. Two agents answering the same customer. That is the platform vendor naming the failure mode in its own docs, which is considerably more persuasive than a shared inbox company telling you that shared mailboxes are bad.
The other documented M365 limits are worth knowing before you rely on one:
- **50 GB cap** without an Exchange Online Plan 2 license. On hitting it, the mailbox stops sending, then stops receiving.
- **No encryption.** Mail from a shared mailbox cannot be encrypted, because the mailbox has no security context of its own.
- **You cannot prevent users from deleting messages.**
- **No external access.** A contractor on an outside domain cannot be given access.
### Gmail has a concurrency ceiling too
Google's native shared inbox is built on Gmail delegation, and delegation has documented limits: up to 1,000 delegates on paper, but **only around 40 can access the account simultaneously** under typical use, and Google notes that "above-average use by one or more delegates might reduce this number." Browser extensions and APIs that poll Gmail frequently reduce it further. ([Google Workspace admin docs](https://knowledge.workspace.google.com/admin/gmail/let-users-delegate-access-to-a-gmail-account))
That last detail is worth sitting with, because Hiver and Gmelius are both Gmail extensions.
**The honest summary:** a plain shared mailbox is genuinely fine at two or three people and low volume. The vendor-documented ceilings are 25 users (Microsoft) and roughly 40 concurrent delegates (Google). But the real breaking point arrives much earlier, the first time two people reply to the same customer and neither knows it happened.
## The comparison table
| Tool | Best for | Where it lives | Gmail | Outlook | Entry price | Free tier |
|---|---|---|---|---|---|---|
| **InboxPilot** | Best overall (AI email layer) | Inside both | Native | Native | $29/mo flat | Yes |
| **Front** | Classic shared inbox | Separate app | Connects | Connects (sync caveats) | From $25/seat/mo | No |
| **Hiver** | Gmail teams | Inside Gmail | Native | Via Omni only | $25/user/mo annual | Yes |
| **Missive** | Collaboration | Separate app | Connects | Connects | $14/user/mo | Undocumented |
| **Help Scout** | Support teams | Separate app | Connects | Connects | $25/user/mo | Yes, 5 users |
| **Gmelius** | Gmail-only budget | Inside Gmail | Native | **No** | $19/user/mo annual | No |
| **Zendesk** | Outgrown the category | Separate app | Connects | Connects | $19/agent (Support), $55 (Suite) | No |
| **Freshdesk** | Budget ticketing | Separate app | Connects | Connects | $19/agent/mo annual | 6 months only |
| **Google native shared inbox** | Free, Workspace | Inside Gmail | Native | No | $0 | Free |
| **M365 shared mailbox** | Free, Microsoft | Inside Outlook | No | Native | $0 | Free |
Pricing verified against vendor pricing pages in July 2026.
## The best shared inbox tools, ranked
### 1. InboxPilot
**Best for:** Teams whose real problem is *volume*, and anyone who wants relief without leaving Gmail or Outlook.
Read this section knowing we wrote it. InboxPilot takes the top spot for one reason: **every other tool on this list helps humans divide the work faster. InboxPilot reduces how much work reaches humans at all.** It is an AI layer that triages, labels, and drafts replies inside the Gmail or Outlook you already have, and in our experience most teams googling "shared inbox software" are trying to fix volume, not coordination.
**Strengths**
- Native in **both Gmail and Outlook**, which no other Gmail-native tool here manages (Gmelius is Gmail-only, Hiver needs a separate product for Outlook).
- AI drafts grounded in your own docs, help center, and connected tools like Shopify, Notion, and Pipedrive.
- Smart triage, auto-labeling, and plain-English email workflows.
- Priced per workspace by AI draft volume, not per seat, so it does not get more expensive as your team grows.
- No migration. It layers onto the mailbox you already have, including a plain M365 or Google shared mailbox.
**Tradeoffs, stated plainly**
- **It is not a classic shared inbox.** No teammate assignment, no collision detection, no internal notes, no SLA reporting. If your problem is two agents replying to the same customer, pair it with Front, Hiver, Missive, or Help Scout, or pick one of those instead.
- **Cost scales with email volume, not headcount.** That is cheaper for a big team with modest volume and more expensive for a small team drowning in mail. Do the math on your actual volume before assuming it is the cheap option.
- Newer, with a shorter public review record than the incumbents.
**Pricing:** Free (25 AI drafts, 1 inbox). Hobby $29/mo. Standard $149/mo (1,500 drafts, unlimited inboxes). Pro $499/mo. Enterprise custom. Annual billing is about 20% less, so Standard is $119/mo on a yearly plan. Per workspace, not per seat. ([inboxpilot.co/pricing](/pricing))
**When it makes the most sense:** you are on a plain M365 or Google shared mailbox and want relief without a migration, or you run Front or Hiver and want the repetitive volume deflected before it reaches a human. It pairs with any shared inbox below, and for a lot of teams it removes the reason to buy one.
### 2. Front
**Best for:** Mid-market and larger teams that want shared inbox ergonomics with serious integrations, analytics, and omnichannel.
Front is the most complete classic shared inbox in this category. If your diagnosis is coordination rather than volume, this is the tool to beat.
**Strengths**
- Mature collision detection and assignment, the two things you are actually buying.
- Deep integration catalog including Salesforce and HubSpot.
- Strong analytics, genuinely better than the rest of this list.
- Omnichannel on Professional and above.
**Tradeoffs**
- **The advertised price is not the real price.** Starter at $25 per seat is limited to a single channel type. The plan most teams actually need is Professional at **$65 per seat per month**, and Enterprise is $105.
- **Outlook sync is conditional, and Front documents this itself.** Read status syncs only for personal channels, and for shared conversations only once the assignee reads it. In-place archive mailboxes do not sync at all. Mixed Front and Outlook teams get confused by this. ([Front help docs](https://help.front.com/en/articles/205376))
- AI is an add-on: Copilot at $20 per seat per month, Autopilot from $0.05 per conversation.
**Pricing:** Starter $25 per seat per month annual (up to 10 seats), Professional $65, Enterprise $105. No free tier, 14-day trial. ([front.com/pricing](https://front.com/pricing))
Full head-to-head: [InboxPilot vs Front](/inboxpilot-vs-front).
### 3. Hiver
**Best for:** Google Workspace teams who will not leave Gmail, and should not have to.
**Strengths**
- Genuinely native to Gmail, running as a sidebar. Onboarding is close to zero because there is no new app to learn.
- **Free forever tier** that includes a shared inbox, which is rare.
- Collision detection, assignment, and SLA basics.
- Clean pricing ladder with no surprises: Free, $25, $55, $85.
**Tradeoffs**
- **Performance is the recurring complaint.** Reviewers on G2 and Capterra consistently report slow loading under volume and needing to refresh the browser to bring Hiver back.
- Outlook is not supported in the Gmail product. Microsoft teams have to use Hiver Omni, which is a separate standalone app, not an Outlook add-in.
- Analytics are thinner than a full help desk.
**Pricing:** Free forever. Growth $25 per user per month annual ($35 monthly), Pro $55, Elite $85. ([hiverhq.com/pricing](https://hiverhq.com/pricing/hiver-in-gmail))
Also see: [Hiver vs InboxPilot](/blog/hiver-inboxpilot).
### 4. Missive
**Best for:** Teams that want to discuss and co-write replies inside the thread instead of copying them into Slack.
**Strengths**
- **Cheapest serious entry point at $14 per user per month.**
- Real-time collaborative drafting is genuinely differentiated. Two people can write one reply together, live.
- Broad channel support: Gmail, Outlook, IMAP, WhatsApp, Messenger, Instagram, SMS via Twilio.
- Provider-agnostic, so it does not care whether you are on Google or Microsoft.
**Tradeoffs**
- Starter caps at 5 users. The realistic plan for a growing team is Productive at $24.
- **The learning curve is the dominant reviewer complaint.** It is a genuinely new paradigm, and teams coming from plain Gmail need a few weeks to settle in.
- Occasional duplicate-thread and snooze confusion reported by reviewers.
**Pricing:** Starter $14 per user per month (up to 5 users), Productive $24 (up to 50), Business $36 (unlimited). A free plan is referenced but its limits are not published, so confirm before relying on it. ([missiveapp.com/pricing](https://missiveapp.com/pricing))
Also see: [Missive vs InboxPilot](/blog/missive-inboxpilot).
### 5. Help Scout
**Best for:** Customer support teams that want a shared inbox plus a knowledge base, without Zendesk's weight.
**Strengths**
- **Free tier with 5 users**, one inbox, and one Docs site.
- The cleanest, easiest interface of any support tool here.
- Built-in knowledge base, so you are not buying a second product.
- AI Answers is priced per resolution ($0.75) rather than per seat, which is buyer-friendly.
**Tradeoffs**
- **Reporting is basic** compared to Zendesk or Freshdesk, and custom report history is gated to higher tiers. This is the most consistent reviewer theme.
- Workflow customization feels restrictive once your needs get complex.
- Extra inboxes cost $10 per month each, and Pro requires a 10-user minimum.
- No native voice or WhatsApp.
**Pricing:** Free (5 users, 1 inbox). Standard $25 per user per month, Plus $45, Pro $75. ([helpscout.com/pricing](https://www.helpscout.com/pricing/))
Also see: [Help Scout vs InboxPilot](/blog/helpscout-vs-inboxpilot).
### 6. Gmelius
**Best for:** Small Google Workspace teams who want a shared inbox plus Kanban boards, at the lowest Gmail-native price.
**Strengths**
- Cheapest true Gmail-native entry at $19 per user per month.
- Kanban and Trello-style boards on top of email, which is an unusual and genuinely useful combination.
- Shared labels, internal notes, and sequences.
**Tradeoffs**
- **Gmail only. No Outlook, at all.** One Outlook user on your team disqualifies this tool entirely. Confirmed on Gmelius's own pricing page.
- **Speed complaints are persistent.** Reviewers repeatedly report slow Gmail load times with the extension active, and Chrome extension bugs.
- The mobile app is the most-cited weak point.
- No free tier, and only a 7-day trial, which is not long enough to roll a shared inbox out to a team.
**Pricing:** Meli $19 per user per month annual ($21 monthly), Growth $25, Pro $40, Enterprise custom. ([gmelius.com/pricing](https://gmelius.com/pricing))
Also see: [Gmelius vs InboxPilot](/blog/gmelius-inboxpilot).
### 7. Zendesk
**Best for:** Teams that have outgrown this category entirely and need a real help desk.
Zendesk is on this list so you can rule it in or out honestly. It is not a shared inbox. It is a ticketing suite, and that is a different purchase.
**Strengths**
- The deepest routing, reporting, and automation available anywhere here.
- Enormous app ecosystem.
- Scales to genuine enterprise volume.
**Tradeoffs**
- **The $19 Support Team tier is a trap for this buyer.** Anything resembling the suite starts at **$55 per agent (Suite Team)**, and Professional is $115.
- Complexity and admin burden are the dominant reviewer criticisms. Setup takes real planning.
- Email stops feeling like email and becomes tickets. That is the entire point, and also the entire cost.
**Pricing:** Support Team $19 per agent per month annual. Suite Team $55, Suite Professional $115. No free tier. ([zendesk.com/pricing](https://www.zendesk.com/pricing/))
More on running the two together: [InboxPilot and Zendesk](/blog/inboxpilot-and-zendesk-integration).
### 8. Freshdesk
**Best for:** Budget-conscious teams that want real ticketing and can live with rough edges.
**Strengths**
- Aggressive pricing at $19 per agent per month.
- Freddy AI included rather than bolted on.
- Solid knowledge base and customer portal.
**Tradeoffs**
- **The free plan is not free forever.** It is currently $0 for 1-2 agents for 6 months. Most roundups still describe an old perpetual free plan. Check before you plan around it.
- **Duplicate and child ticket handling** is a specific, recurring reviewer complaint: child tickets get treated as new tickets, and agents end up creating duplicates.
- Reporting is limited on lower tiers.
**Pricing:** Free for 1-2 agents for 6 months. Growth $19 per agent per month annual, Pro $55, Enterprise $89. ([freshworks.com/freshdesk/pricing](https://www.freshworks.com/freshdesk/pricing/))
### 9. Google's native shared inbox (new in 2026)
**Best for:** Google Workspace teams who want a shared address in real Gmail, for free, and do not yet need coordination features.
**Strengths**
- **Free** on Business Starter, Standard, and Plus, with no add-on.
- Lives in actual Gmail, unlike the old Collaborative Inbox, which lived in the Google Groups interface and never appeared in the Gmail mobile app.
- Sends from the shared address, with a "sent by" attribution you can hide.
**Tradeoffs**
- **No collision detection, no automation, no SLA reporting.** It solves access, not coordination.
- Inherits Gmail's delegation ceilings (roughly 40 concurrent delegates, reduced further by extensions).
- Rolling out in phases, so it may not be in your Admin console yet.
**Pricing:** $0, included with Workspace. ([Google Workspace admin docs](https://knowledge.workspace.google.com/admin/users/create-a-shared-inbox))
### 10. Microsoft 365 shared mailbox
**Best for:** Microsoft shops with a low-volume info@ or reception@ address and a handful of people on it.
**Strengths**
- **Free.** No license required on the mailbox itself.
- Native in Outlook desktop, web, and mobile. Automapping means it simply appears.
- Includes a shared calendar.
**Tradeoffs**
- **25-user maximum, with "connection failures or duplicated messages" beyond it,** per Microsoft's own docs.
- 50 GB hard stop without an Exchange Online Plan 2 license.
- No encryption, no way to prevent deletion, no external users.
- No assignment, no collision detection, no reporting.
**Pricing:** $0. ([Microsoft Learn](https://learn.microsoft.com/en-us/microsoft-365/admin/email/about-shared-mailboxes))
## What a 5-person team actually pays in year one
Advertised entry prices are misleading, so here is the real number for a five-person support team, at list price, billed annually. No competitor publishes this.
| Tool | Plan needed for 5 people | Monthly | Year one |
|---|---|---|---|
| Google native shared inbox | Included with Workspace | $0 | **$0** |
| M365 shared mailbox | Included | $0 | **$0** |
| Hiver | Free tier, or Growth at $25 | $0 to $125 | **$0 to $1,500** |
| Missive | Starter $14 (caps at exactly 5) | $70 | **$840** |
| Gmelius | Meli $19 | $95 | **$1,140** |
| Help Scout | Free (5 users), or Standard $25 | $0 to $125 | **$0 to $1,500** |
| InboxPilot | Standard $119 flat | $119 | **$1,428** |
| Front | Starter $25, single channel | $125 | **$1,500** |
| Front (Professional, realistic) | $65 | $325 | **$3,900** |
| Zendesk Suite Team | $55 | $275 | **$3,300** |
Two things stand out. Front's real cost is closer to $3,900 than the $1,500 its entry tier implies. And InboxPilot's flat pricing looks unremarkable at five people, which is the honest picture: it gets more interesting at 15 people and less interesting at very high volume.
## What to look for in shared inbox software
### 1. Rule out free first
If you are two or three people, Google's native shared inbox or the M365 shared mailbox may genuinely be enough. Spending $1,500 a year to solve a problem you do not have yet is the most common mistake in this category.
### 2. Check Outlook support before anything else
Gmelius does not support Outlook. Hiver's Gmail product does not either. If any meaningful part of your team is on Microsoft, that removes options before you compare a single feature.
### 3. Price the plan you will actually need
Front's $25 Starter is single-channel. Zendesk's $19 is not the Suite. Missive's $14 Starter caps at five users. Build the number from the plan you will really be on, at the headcount you will really have.
### 4. Ask what breaks at 3x volume
Every tool here works at low volume. Ask each vendor what fails first when volume triples: rule caps, load times, reporting depth, or the AI meter.
### 5. Separate the volume problem from the coordination problem
These are different problems with different solutions. Collision detection fixes coordination. It does nothing about volume. AI drafting fixes volume. It does nothing about coordination. Diagnose which one is actually hurting before you shop.
## How to choose, in one paragraph
Start with the diagnosis, not the tool. If the honest answer is that nobody is stepping on anyone's toes, there is just too much email, that is a volume problem and [InboxPilot](/pricing) is our pick, on its own or alongside whichever shared inbox you land on. If you are two or three people on Workspace, try **Google's native shared inbox** and spend nothing. If you are a Gmail team who wants real coordination, **Hiver** is the lowest-friction upgrade and has a free tier. If you want the most complete classic shared inbox and can pay for it, it is **Front**, at its real price rather than its advertised one. If you want a support-shaped tool with a knowledge base, **Help Scout**. And if your team is on Microsoft, quietly cross Gmelius off the list.
## Related reading
- [Best shared inbox for Gmail](/blog/best-shared-inbox-for-gmail) and [best shared inbox for Outlook](/blog/best-shared-inbox-for-outlook): the platform-specific versions of this guide.
- [Best email management software: 11 tools for support teams](/blog/ai-email-agent): the wider category, including help desks.
- [Hiver vs InboxPilot](/blog/hiver-inboxpilot), [Gmelius vs InboxPilot](/blog/gmelius-inboxpilot), [Missive vs InboxPilot](/blog/missive-inboxpilot): the direct comparisons.
- [How to automate email support](/blog/ai-email-agent): what to automate once your inbox is organized.
- [RFQ and quote request automation](/use-cases/rfq-email-automation): how quote requests get read, priced, and answered from your own catalog.
- [Shared mailbox auto-reply](/blog/shared-mailbox-auto-reply): the documented limits of native auto-replies on a shared address.
---
*Pricing verified against vendor pricing pages in July 2026 and stated per user per month unless noted. Platform limits are cited from Microsoft and Google's own administrator documentation. Vendors change pricing frequently, so confirm current rates before purchasing. InboxPilot is the publisher of this article and is one of the tools discussed.*
---
## How to Generate Emails Using Your Documents (Step by Step)
Source: https://www.inboxpilot.co/blog/how-to-generate-emails-using-your-documents
Published: 2026-05-27
Upload policies and product docs, connect Gmail or Outlook, and get email drafts grounded in your own files. Setup steps, guardrails, and honest limits.
Most AI writing tools sound confident and wrong. Ask a generic assistant to reply to a refund request and it will invent a policy. Ask it to quote your enterprise pricing and it will guess. The problem is not the model. It is the missing context.
Generating emails from your documents means something specific: when a message lands in your inbox, the AI reads it, searches your uploaded policies, product sheets, and SOPs, and drafts a reply that uses your facts in your voice. No copy-pasting from a PDF, no tab-switching to Notion, no hoping a chatbot remembered what you pasted last Tuesday.
This guide walks through the full setup: which documents to gather, how to upload and configure them, how to test before anything reaches a customer, and the limits to plan around.
**Disclosure:** we make [InboxPilot](/product/knowledge-base), an inbox-native AI email agent, and the walkthrough below uses it because document-grounded drafting is its core workflow. If your repetitive email is a handful of identical replies, Gmail's free [native templates](/blog/automate-your-gmail) cover it and you can skip this setup entirely.
## TL;DR
- **Document-grounded generation means retrieval, not memory.** The AI searches your uploaded files on every email and drafts from what it finds. See [what it means](#what-generating-emails-from-your-documents-means).
- **Setup is five steps**: connect the inbox, upload files, layer FAQ and website sources, set guardrails, test in Playground. See [the setup](#set-it-up-in-five-steps).
- **Start with three to five core documents**, not the whole company wiki. Refund policy, pricing sheet, and product specs cover most inbound questions. See [what to gather](#what-to-gather-before-you-start).
- **Draft mode first, automation later.** Every reply waits for human review until you opt specific workflows into auto-send. See [the rollout](#set-it-up-in-five-steps).
- **[InboxPilot](#where-inboxpilot-fits)**, which is us, keeps the documents attached to Gmail and Outlook so the knowledge lives where the conversations happen. See [where it fits](#where-inboxpilot-fits), including the cases where it is the wrong tool.
## What generating emails from your documents means
In practice, your documents become a searchable knowledge base the AI consults on every incoming email. Technically this is often called retrieval-augmented generation (RAG). From your side it feels simpler: the assistant knows your refund window because you uploaded `Refund-Policy-2026.pdf`, not because it read the whole internet.
When InboxPilot generates an email, it runs a four-part loop:
1. **Reads** the incoming message and works out the intent: refund, pricing, shipping, scheduling.
2. **Retrieves** the most relevant sections from your uploaded files, FAQ pairs, website crawl, and templates.
3. **Drafts** a reply in your configured tone, with facts pulled from those sources rather than invented.
4. **Delivers** the result as a Gmail or Outlook draft for review, or an automatic send if you have opted that workflow in.
That is fundamentally different from pasting an email into a chat window. The knowledge stays attached to your inbox, updates when you update your files, and applies consistently across your team. For the full picture of grounding Gmail on business data beyond files, see [how to train Gmail on your own data](/blog/how-to-train-gmail-on-your-own-data).
## Why documents beat pasting into a chatbot
Teams that live in email already have the answers written down. They sit in PDFs, Word files, onboarding decks, and internal wikis. The win is connecting that library directly to the inbox instead of rewriting it into prompts every morning.
| Approach | What you get | Main risk |
| --- | --- | --- |
| Generic AI chat | Fast drafts | Invented policies, wrong pricing, off-brand tone |
| Autocomplete-style suggestions | Phrasing that matches you | No access to your help docs or SOPs |
| Static templates | Consistent wording | Breaks when the question does not match the template |
| Document-grounded AI | Accurate, contextual replies from your own corpus | Quality depends on what you upload, which is fixable in minutes |
The shift is not just speed. It is trust: you are not hoping the model remembered your policy. You uploaded it.
## What to gather before you start
You need three things:
- A **Gmail or Microsoft 365 / Outlook** inbox you want to assist or automate.
- An **[InboxPilot account](https://www.inboxpilot.co/auth/signup)**. The Free plan includes 25 AI drafts a month, enough to validate on real mail.
- **Three to five core documents.** Common starting points: refund and returns policies, pricing sheets and plan comparisons, product specs, onboarding guides, SLAs and support playbooks.
The Knowledge Center **Files** tab accepts PDF, DOC/DOCX, spreadsheets, and other common business formats. InboxPilot extracts the text, indexes it, and consults it when drafting. Resist uploading the entire company wiki on day one: a refund policy plus a handful of FAQ pairs is enough to judge quality on real threads, and you expand from there.
## Set it up in five steps
### Step 1: Connect your inbox
Sign up at [app.inboxpilot.co/auth/signup](https://www.inboxpilot.co/auth/signup), open **Connect account**, and choose **Gmail** or **Outlook**. The OAuth flow requests scoped access to read and draft in the inbox you select, and nothing else.
You can connect multiple inboxes on paid plans, and each inbox can later get its own document set. That matters when `support@` and `billing@` should not share the same policy PDFs.
### Step 2: Upload your documents
Open **Knowledge Center** in the left sidebar and go to the **Files** tab. Click **Upload File** or drag and drop, wait for processing to finish, and confirm each file appears in your library.
One habit pays off immediately: clear filenames. `Refund-Policy-2026.pdf` and `Enterprise-Pricing-Q2.docx` make it obvious which source produced which answer when you test later, and which file to replace when a policy changes.
If you manage several connected addresses, you can attach documents per inbox, so billing policies stay with `billing@` and sales playbooks with `sales@`. Organization-wide uploads remain available to every inbox when that is what you want.
### Step 3: Layer the sources files cannot cover
Documents carry narrative policy well, but most teams get the best results by combining sources in the Knowledge Center:
| Source | Best for |
| --- | --- |
| Files | Policies, manuals, long-form PDFs, internal SOPs |
| FAQ | Exact answers for high-stakes questions ("What is your refund window?") |
| Website | Public help center and docs, kept fresh by crawl |
| Raw text | Short facts: pricing tiers, hours, escalation rules |
| Email templates | Reusable reply structures the AI selects by intent |
| Learn from email | Tone and phrasing from your historical sent mail |
Use documents for depth and FAQ pairs for precision. If a question must be answered identically every time, write it as an FAQ pair rather than trusting retrieval to land on the right paragraph of a 30-page handbook. Templates add the third layer, structure, which we cover in the [custom email templates guide](/blog/automate-your-gmail).
### Step 4: Set the guardrails in Configuration
Open **Configuration** for the connected inbox. Documents supply the facts; this screen supplies the rules for how they show up:
- **Persona prompt.** Who is writing. For example: "You are a support agent for Acme SaaS. Be concise and friendly, and never promise features not listed in the product docs."
- **Trigger keywords.** Topics safe for document-backed replies: `refund`, `pricing`, `hours`, `shipping`.
- **Negative keywords.** Topics that must always reach a human: `legal`, `lawsuit`, `executive complaint`.
- **Send mode.** Start in **draft mode**, where every generated reply lands in your inbox for review. Autonomous send is a per-workflow decision for later, covered in our [automated response guide](/blog/how-to-setup-an-automated-response-on-your-gmail-account).
### Step 5: Test in Playground, then go live
Before any customer sees an AI reply, open **Playground** and paste the sample emails you actually get every week. Check whether each draft cites the right policy in the right tone. When an answer is wrong or thin, add a targeted FAQ pair or upload the missing document, then test again. Playground is an isolated sandbox: nothing sends and no live threads change.
When the answers look right, enable the agent. New mail is processed against your documents, FAQ, and templates, and drafts appear in Gmail or Outlook and in **Logs**. Correct any draft you disagree with; the agent learns from edits, so similar replies improve.
A rollout that works for most teams: week one, one inbox and three to five documents in draft-only mode. Week two, FAQ pairs for the top ten question types. Week three, auto-send for two or three safe, well-documented topics, with everything else still drafting or escalating.
## What happens when a new email arrives
The end-to-end flow, once your documents are in place:
```text
Incoming email -> intent detection -> search Knowledge Center
(files, FAQ, website, templates) -> draft reply in your voice
-> draft in inbox OR auto-send OR escalate to a human
```
Say a customer writes: "I ordered last Tuesday, can I still return this?" InboxPilot matches the intent to returns, pulls the relevant section from your uploaded refund policy, checks whether an FAQ pair defines a canonical answer, and drafts a reply with the correct window and steps. Depending on your configuration, that draft waits for review or goes out on its own.
When a question is not covered by any source, the agent escalates or flags uncertainty instead of guessing, and Memory Suggestions can propose new Q&A pairs where the model was unsure. Adding the missing doc or FAQ closes the gap for every future email on that topic. That loop is how the system stays accurate without anyone retraining a model by hand.
## Best practices that decide draft quality
**Write documents for retrieval, not for print.** Use descriptive headings like "Refund eligibility" and "Enterprise pricing," keep one topic per section, and do not bury the refund window on page 12 of a general handbook. Retrieval finds well-labeled sections; it struggles with sprawl.
**Keep the index current.** When a policy changes, replace the file in the Files tab the same day. A grounded draft from a stale document is wrong with confidence, which is the exact failure you set this up to avoid.
**Pair documents with templates for structure.** If you often send the same shape of reply (demo follow-up, onboarding checklist, quote response), save an email template with a short "when to use" description. The AI blends the template structure with facts from your files.
**Start narrow, then expand.** Train on what actually hits the inbox. The fastest teams validate one inbox and one topic cluster before adding the next, rather than uploading everything and auditing nothing.
## The limits worth planning for
Document-grounded generation is the most reliable way to get accurate AI email, and it still has edges worth stating plainly:
- **Quality tracks your uploads.** Thin, outdated, or contradictory documents produce thin, outdated, or contradictory drafts. The fix is fast, but it is on you.
- **Files do not update themselves.** Uploaded documents are snapshots. Website crawls stay fresher automatically; internal PDFs need a re-upload when policy moves.
- **Some topics should never auto-send.** Refunds outside policy, legal threats, and angry escalations belong with a human, which is what negative keywords and draft mode are for.
- **Sensitive material needs judgment.** If a document contains data you would not want quoted in an outbound email (full customer lists, unreleased financials), keep it out of the knowledge base or restrict those threads to draft-only with mandatory review.
None of these are reasons to skip the setup. They are reasons to start in draft mode and expand automation only where the drafts have earned it.
## Where InboxPilot fits
InboxPilot is an inbox-native AI email agent: it works inside Gmail and Outlook, including shared inboxes, with no migration and no new interface. Documents in the Knowledge Center are one grounding source among several, alongside your website, FAQ pairs, templates, and past email, and every draft waits for human approval by default with auto-send opt-in per workflow.
Your documents ground replies for your organization's agent only; customer data never trains AI models, and InboxPilot is SOC 2 Type II and GDPR compliant. Details are on the [security page](https://www.inboxpilot.co/security), and our [data privacy guide](/blog/ai-email-tools-data-privacy-guide) covers what to ask before connecting documents to any AI tool. Pricing is flat by draft volume with unlimited seats on paid plans: Free covers 25 drafts a month, Hobby is $29/month for 200, Standard is $149/month for 1,500 with unlimited inboxes, and Pro is $499/month for 12,000.
To be honest about fit: this workflow is built for repetitive operational email, quotes, order status, returns, document collection, routine support. InboxPilot is not a chat widget, not a ticket queue, and not a personal productivity coach for an executive inbox. And if your questions are few and identical, free Gmail templates answer them without any of this machinery.
## Related reading
- [How to train Gmail on your own data](/blog/how-to-train-gmail-on-your-own-data)
- [How to create custom email templates in Gmail](/blog/automate-your-gmail)
- [How to automate your Gmail inbox: 7 setups that work](/blog/automate-your-gmail)
- [How to set up an automated response in Gmail](/blog/how-to-setup-an-automated-response-on-your-gmail-account)
- [AI email tools data privacy guide](/blog/ai-email-tools-data-privacy-guide)
- [Document collection automation](/use-cases/document-collection-automation): chasing missing documents without writing the reminders yourself.
Your policies and product docs already contain the answers your inbox needs every day. If retyping them is the piece of your week you want back, [try InboxPilot free](https://www.inboxpilot.co/), upload your first three documents, and run five real questions through Playground against your own mail.
---
## How to Train Gmail on Your Own Data (2 Methods)
Source: https://www.inboxpilot.co/blog/how-to-train-gmail-on-your-own-data
Published: 2026-05-19
Gmail cannot read your refund policy or help docs out of the box. Two no-code ways to ground Gmail replies in your own data, and which one scales.
A customer emails asking whether your 30-day refund window covers sale items. Gmail has been reading email for two decades, but it has never read your refund policy. Smart Compose can finish your sentence. It cannot tell you what your own returns page says.
That gap is the whole problem with AI in the inbox. Out of the box, Gmail's AI is trained on the open internet, not on your help center, your SOPs, your pricing, or the five hundred replies your best support person has already written. "Training Gmail on your own data" means closing that gap: giving the AI that drafts from your inbox the same context a new hire would get in week one.
There are two practical, no-code ways to do it. One stays inside Google's ecosystem. One connects a purpose-built agent to your Gmail. This guide walks through both, step by step, including the limits nobody mentions.
**Disclosure:** we make [InboxPilot](/integrations/gmail), the second method in this guide. It is an inbox-native AI email agent for teams handling operational email at volume. If you just want help phrasing the occasional personal email, Google's free native tools are enough and you do not need us.
## TL;DR
- You cannot retrain Google's models, but you can ground the AI in your inbox with your own documents. See [what training actually means](#what-training-gmail-actually-means).
- **The Google native route** (Smart Compose personalization plus Gemini for Workspace) helps you write faster, one email and one document at a time. See [method 1](#method-1-the-google-native-route).
- The native route only works while you are typing. It cannot read incoming mail, answer overnight, or share knowledge across a team. See [where it tops out](#where-the-native-route-tops-out).
- **[InboxPilot](#method-2-train-an-ai-agent-with-inboxpilot)**, which is us, trains an agent on your files, website, Notion, Q&A pairs, and past email, then drafts replies inside Gmail with a human approving sends. See [method 2](#method-2-train-an-ai-agent-with-inboxpilot).
- Costs differ in shape: Gemini for Workspace is priced per seat, InboxPilot is flat by draft volume with a free tier. See [what it costs](#what-it-costs).
## What training Gmail actually means
Be precise about the word "training." You cannot retrain Google's underlying Gemini or Gmail models on your private data. That is not how consumer AI products work, and you would not want it to be.
What you can do is give the AI that reads and writes from your account a curated knowledge base it retrieves from on every reply. The technique is called retrieval-augmented generation, or grounding. From the outside it feels exactly like the AI knows your business: ask about the refund window and it answers from your policy doc, not from a guess.
The two methods in this guide differ in who does the work afterward. Google's native tools assist you while you write each email yourself. An agent like InboxPilot handles whole categories of email, drafting replies to refund questions, lead intake, and routine support before you open the thread. That distinction, assistant versus agent, decides which method fits you.
## Method 1: the Google native route
Google has been quietly learning your writing patterns for years. Smart Compose personalization, the "Help me write" feature, and, for Workspace customers with the Gemini add-on, grounding on your Drive files together form Google's answer to "train Gmail on my data." Think of it as turning Gmail into a smarter version of you: it picks up your phrasing and, with Gemini, pulls facts from Drive when you ask.
You will want a Google Workspace account with Gemini enabled for the full stack. Personal accounts get a limited version.
In Gmail, open the gear icon, then **See all settings**. On the **General** tab, set **Smart Compose personalization** to on, and confirm **Smart Compose** itself is set to writing suggestions on. This uploads nothing new. It tells Gmail it may learn from the emails you already send.
With Gemini for Workspace, click **Compose**, then the **Help me write** icon in the compose window. Describe the reply you want, and use an `@` mention to reference a Google Doc (for example `@Refund Policy 2026`) so Gemini grounds the draft in that file. Review, refine, insert.
Treat one Drive folder as the knowledge base: FAQs, refund policy, SLAs, product one-pagers, all as Google Docs with descriptive names so they are easy to `@`-mention. Gemini reads the live doc, so policy updates propagate the moment you save.
Gmail's non-AI automation still matters. Use the vacation responder for holding messages and filters to route known senders and subjects to labels, so whatever handles your mail next gets clean inputs.
## Where the native route tops out
For individual drafting help, the native route is genuinely good and mostly free. For a business inbox, it has hard ceilings:
- **It only works while you type.** Smart Compose, Help me write, and Gemini all activate in the compose window. Nothing reads incoming mail for you, nothing replies overnight, nothing deflects the hundredth copy of the same question.
- **Grounding is one document at a time.** The `@` mention is great when you know which doc holds the answer. There is no retrieval across your whole corpus when the answer spans five policies.
- **Learning is per person, not per team.** Personalization is tied to your account. The knowledge in your best teammate's sent folder does not transfer to a new hire, and a shared support@ cannot have its own voice separate from sales@.
- **It costs per seat.** Gemini for Workspace runs roughly $20-30 per user per month on top of your Workspace plan, and personal Gmail misses most of it.
- **There is no automation surface.** Native Gmail cannot read an email, recognize it as a shipping question, check the order, and draft the answer. That is the gap purpose-built tools exist to fill.
None of this is a flaw. Gmail is a personal inbox, not an automation platform. If your goal is a team inbox that answers itself, you need the second method.
## Method 2: train an AI agent with InboxPilot
[InboxPilot](/integrations/gmail) is an inbox-native AI email agent. It connects to Gmail (and Outlook) through OAuth, ingests your data, and drafts replies grounded in that data directly in your inbox. There is no migration and no new interface: your team keeps working in Gmail, and drafts wait for human approval by default. Auto-send is opt-in per workflow, and the agent escalates when it is unsure instead of guessing.
Here is the setup end to end.
Create a free account and connect Gmail through Google's standard OAuth consent screen, granting scoped access to the inbox you want to train. Shared inboxes work, and you can connect several accounts and train each one differently: one agent for support@, another for sales@.
Open the Knowledge Center and add what Gmail does not know. Drag in files (PDFs, Word docs, CSVs), paste your website URL for a full crawl of your help center, connect Notion pages that stay in sync, or add Q&A pairs where you dictate the exact answer to a high-stakes question. Shopify and Pipedrive connections let replies reference this customer's actual order or deal, and you can opt in to learning tone from your past sent email. Click train and the agent indexes everything, usually in minutes.
Give each connected inbox its own persona prompt, tone setting, and rules in plain English. Trigger keywords route topics like pricing, hours, and order status into drafting. Negative keywords do the opposite: anything mentioning legal, cancellation, or a dispute skips automation and lands in front of a human with no draft. Then pick the send mode, with draft-for-review as the default and auto-send reserved for intents you trust.
Ask the agent your real inbox questions in the Playground before going live. Where it misses, add the missing doc or a Q&A pair and re-test. Once live, run draft mode for the first week, review what it writes, then loosen the reins on the categories it nails. Logs and escalations show every reply and every hand-off, so trust is earned on evidence.
One honest boundary: InboxPilot automates email. It is not a chat widget for your website, not a ticket queue, not a phone system, and it is the wrong tool for an executive who wants help with a personal inbox. If your repetitive work lives in email, it fits. If it lives in chat or calls, look elsewhere.
## Every way to feed Gmail your data
Whichever method you pick, the inputs come down to a short list. The tradeoff running through all of them is control versus effort: crawling a website is fast but broad, Q&A pairs are slow but exact.
| Input | Available in | Best for |
|---|---|---|
| File uploads (PDF, DOCX, TXT, CSV) | Both | Policies, manuals, SOPs that already exist as documents |
| Drive doc `@` mentions | Google native | Grounding a single draft in a single doc |
| Website crawl | InboxPilot | Help centers and docs sites already on the public web |
| Pasted text | InboxPilot | Positioning, escalation rules, do-not-answer topics |
| Q&A pairs | InboxPilot | High-stakes questions where the wording must be exact |
| Notion sync | InboxPilot | Team wikis that change weekly |
| Shopify and Pipedrive data | InboxPilot | Replies that cite this customer's order or deal |
| Past sent email | InboxPilot | Matching your actual voice from day one |
Most teams end up combining three or four: a website crawl for coverage, files for policies, and a dozen Q&A pairs to lock down the answers that must never drift.
## What it costs
**The Google native route.** Smart Compose personalization is free on any account. The meaningful business features need Gemini for Google Workspace, roughly $20-30 per user per month on top of your Workspace plan, so the bill grows with headcount.
**InboxPilot.** Pricing is flat by AI draft volume, with unlimited seats on paid plans: Free covers 25 drafts a month to test on real traffic, Hobby is $29 per month for 200, Standard is $149 per month for 1,500 drafts with unlimited inboxes, and Pro is $499 per month for 12,000. Never per-seat, and no separate AI subscription required. Details on the [pricing page](/pricing).
The comparison worth making is not tool against tool, it is shape against shape. Per-seat pricing suits assistants, because the value lands on each writer. Volume pricing suits agents, because the value is email handled, whoever is on shift.
## Related reading
- [7 ways to automate your Gmail inbox](/blog/automate-your-gmail): the broader automation menu, from filters to full AI drafting.
- [Gemini for Gmail alternatives](/blog/alternative-gemini-for-gmail): how the native assistant compares when you need more than drafting help.
- [Custom email templates in Gmail](/blog/automate-your-gmail): the manual version of grounded replies, and when templates are enough.
- [What an AI email agent actually does](/blog/ai-email-agent): the agent category explained end to end.
- [Document collection automation](/use-cases/document-collection-automation): chasing missing documents without writing the reminders yourself.
If the ceiling you keep hitting is "Gmail writes well but knows nothing about my business," grounding is the fix, and you can test it without a migration. Connect an inbox to [InboxPilot](https://www.inboxpilot.co/), feed it your real docs, and judge the first 25 drafts yourself.
---
## Email Admin Burden Statistics 2026: What Inbox Time Costs
Source: https://www.inboxpilot.co/blog/admin-burden-email-statistics-2026
Published: 2026-02-28
The average worker spends 2.6 hours a day on email, 28% of the workweek. The full numbers on what inbox admin costs per employee and where the time goes.
Most companies can quote their software spend to the dollar. Almost none can tell you what email costs them, even though for a typical knowledge-work team it is a bigger number than the entire software budget.
The data behind that claim has been consistent for years: email takes over a quarter of the average worker's week, the biggest slice of that time goes to composing replies, and the interruptions add a second cost that never shows up in any audit.
This post collects the admin burden statistics worth knowing in 2026, converts them into dollar figures you can sanity-check against your own payroll, and looks at what companies are actually doing to get the time back.
**Disclosure:** we make [InboxPilot](/), an AI email agent that drafts replies to repetitive email inside Gmail and Outlook. This is a statistics roundup, not a pitch: every figure is attributed to its source, our own arithmetic is labeled as arithmetic, and InboxPilot appears once, in the section on automation, where it belongs.
## TL;DR
- The average worker spends **2.6 hours per day on email, 28% of the workweek** (McKinsey Global Institute), and receives 121 emails a day (Radicati Group). See [the core numbers](#the-core-numbers).
- Over a 2,080-hour year that is **582 hours per employee, about $20,370 at a $35 hourly rate**. See [what a year of email costs](#what-a-year-of-email-costs).
- Composing replies is the largest slice, roughly 40% of email time. See [where the time actually goes](#where-the-time-actually-goes).
- Each interruption takes about **23 minutes of refocusing** (UC Irvine), which is how 2.6 direct hours becomes an estimated 4-5 hours of real impact. See [the hidden cost of interruptions](#the-hidden-cost-of-interruptions).
- Slow replies leak revenue too: **35-50% of sales go to the vendor who responds first** (InsideSales). See [slow replies cost more than time](#slow-replies-cost-more-than-time).
- **[InboxPilot](#what-companies-are-doing-about-it)**, which is us, is the automation approach in the final section: AI drafts the repetitive replies, a human approves them.
## The core numbers
Seven statistics do most of the work in any conversation about email load:
| Metric | Statistic | Source |
|--------|-----------|--------|
| Time spent on email per day (average worker) | 2.6 hours | McKinsey Global Institute |
| Share of workweek spent on email | 28% | McKinsey Global Institute |
| Emails received per day (average professional) | 121 | Radicati Group |
| Emails sent per day (average professional) | 40 | Radicati Group |
| Time to refocus after an email interruption | 23 minutes | UC Irvine |
| Workers who check email outside work hours | 81% | Adobe Email Usage Study |
| Email volume growth year-over-year | 4.3% | Statista |
Two of these deserve a second look. The 4.3% annual growth figure means the burden compounds rather than leveling off: whatever email costs you this year, it costs more next year at the same headcount. And the 81% of workers checking email outside work hours means the 2.6 daily hours are not all landing inside the workday.
## What a year of email costs
Here is the 28% figure made concrete:
- 2,080 working hours per year (40 hours per week, 52 weeks)
- 28% of that time on email = **582 hours per year**
- At $35 per hour average knowledge worker cost = **$20,370 per employee per year**
For a 10-person team, that is **$203,700 per year** in time spent managing email. For a 50-person team, **$1,018,500 per year**.
The formula, if you want to run your own numbers:
**Annual email cost = employees x working hours per year x % of time on email x average hourly rate**
A 25-person team at the averages above: 25 x 2,080 x 28% x $35 = **$509,600 per year**.
These figures count only direct time. They exclude the productivity loss from context switching, the stress cost, the communication errors caused by delayed responses, and the revenue impact of slow customer replies. Those show up below.
## Where the time actually goes
Not all email time is equal. Research puts the breakdown roughly here:
**Reading and triaging, about 35% of email time.** Sorting what matters, what is junk, what requires action, and what can wait. For someone receiving 121 emails per day, even a 30-second triage decision per email takes an hour.
**Composing replies, about 40% of email time.** Writing is the most time-intensive part. Professionals spend roughly 1-1.5 hours per day deciding what to say, drafting the message, editing for tone and length, and reviewing before sending.
**Administrative tasks, about 25% of email time.** Forwarding, tagging, filing, archiving, following up, setting reminders. All the organizational work around email that involves no actual communicating.
The composing slice is the one worth staring at. It is the largest share of the time, and in operational inboxes (order status, quote requests, routine questions) most of those replies are close variants of replies someone on the team has already written.
## The hidden cost of interruptions
The 2.6 hours of direct email time understates the total impact, because email is an interruption engine.
The UC Irvine finding, that it takes an average of 23 minutes to fully refocus on a complex task after an email interruption, compounds quickly. A professional who checks email 15 times per day and gets interrupted 8 times by notifications can lose several additional hours to re-engagement time that never appears in any email audit.
Including context switching, the estimated total productivity impact for high-volume email users is **4-5 hours per day**, not the 2.6 hours typically cited. Treat that as an estimate rather than a measurement. The honest version: nobody has instrumented the full cost, and the pieces that have been measured already look bad.
## How the burden varies by industry
Email load is not uniform across sectors. The ranges below are directional compilations rather than a single study's output, but the ordering is stable:
| Industry | Daily Emails Received | % of Work on Email |
|----------|----------------------|-------------------|
| Financial Services | 180+ | 35-40% |
| Legal | 150+ | 30-38% |
| Consulting | 140+ | 28-35% |
| Technology | 120+ | 25-30% |
| Healthcare (admin) | 100+ | 20-28% |
| Retail/E-commerce | 80-120 | 20-25% |
Customer-facing roles carry additional weight: support, sales, and account management professionals often handle 200+ emails per day, with response quality directly tied to revenue.
## Slow replies cost more than time
Admin burden statistics usually focus on the time side. The revenue side gets less attention and matters at least as much:
- Leads contacted within 5 minutes of inquiry are 100x more likely to qualify than those contacted after 30 minutes (Harvard Business Review)
- 35-50% of sales go to the vendor who responds first (InsideSales)
- 90% of customers expect a response to a customer service email within 24 hours, and 45% expect it within 4 hours
For a business with sales or support email, a slow inbox is a revenue leak layered on top of a productivity cost.
## What companies are doing about it
Three approaches show up repeatedly, in rough order of ambition.
### Email reduction policies
Email-free Fridays, mandatory response windows, and moving internal chatter to Slack or Teams. These help at the margins, but they do nothing about incoming external email, which is where most operational load lives.
### Shared inbox management
Tools like Help Scout and Fin (formerly Intercom) route and assign email so two people stop answering the same message. That cuts duplication and coordination overhead. A human still composes every reply, so the 40% composing slice barely moves.
### AI email automation
The newest approach, and the one aimed directly at the composing slice. AI email agents like InboxPilot, which we make, connect to Gmail or Outlook, read incoming email, and draft replies grounded in the company's own docs and past email, with a human approving sends by default.
The arithmetic from earlier runs in reverse here. For a customer support team receiving 500 emails per week, 70% of which are repetitive questions, AI automation can handle 350 of those without human involvement. At $35 per hour, that recovers approximately 58 hours and $2,030 per week for a single team.
Against those numbers the tooling is cheap: InboxPilot's Standard plan is $149 per month for 1,500 AI drafts and unlimited inboxes, with a free plan of 25 drafts to test on real traffic. Recovering even 10% of a 25-person team's $509,600 annual email cost pays for it many times over. Details on the [pricing page](/pricing).
## Related reading
- [The psychology of email anxiety](/blog/email-anxiety-psychology-inbox-overwhelm): what this volume does to attention and stress, and why willpower fixes fail.
- [AI email assistant buyers guide 2026](/blog/ai-email-assistant-buyers-guide-2026): how to evaluate the automation category before buying anything.
- [AI email assistants for teams](/blog/ai-email-assistant-for-teams): the shared-inbox version of the same problem.
- [Best shared inbox software for Gmail and Outlook](/blog/best-shared-inbox-software): if routing and assignment is the gap, start here.
- [Instant lead replies for sales teams](/blog/sales-team-instant-lead-replies): the response-speed numbers applied to inbound leads.
- [RFQ and quote request automation](/use-cases/rfq-email-automation): how quote requests get read, priced, and answered from your own catalog.
If the composing slice is the piece you want back first, that is the part InboxPilot automates: the AI drafts, you approve, and the repetitive 70% stops costing an hour and a half a day per person.
---
*Statistics above are attributed to their named sources (McKinsey Global Institute, Radicati Group, UC Irvine, Adobe, Statista, Harvard Business Review, InsideSales). Dollar figures are our own arithmetic from those sources at the stated assumptions. InboxPilot is the publisher of this article.*
---
## AI Email Assistant Buyer's Guide 2026: What to Look For
Source: https://www.inboxpilot.co/blog/ai-email-assistant-buyers-guide-2026
Published: 2026-02-28
AI email assistant now means four different products. A buying framework: the category table, six vendor questions, and where InboxPilot does not fit.
Every AI email assistant demo looks the same. An inbox fills, the AI drafts something plausible, everyone saves five hours a week. What the demo never shows you is whose inbox it was, and that detail decides whether the tool works for you at all.
"AI email assistant" now covers at least four products that have almost nothing in common. A tool built to get a founder's personal inbox to zero will do nothing for the support@ address that three people share. A drafting copilot will not route a quote request to the right rep. Buying across categories is the most common mistake in this market, and it costs you the setup weeks, not just the subscription.
**Disclosure:** we make [InboxPilot](/product), an inbox-native AI email agent for a company's operational email: the shared inboxes where RFQs, order questions, and routine support land. It is our pick below for team and operational email. It is the wrong buy if the problem is your own personal inbox, which is Superhuman and Fyxer territory, and we say so.
## TL;DR
- **Diagnose before you demo.** Volume, cognitive overhead, and slow writing are [three different problems](#first-decide-which-problem-you-are-buying-for) that lead to three different purchases.
- The market splits into [four categories](#the-four-kinds-of-ai-email-assistant): personal email clients, drafting copilots, shared inbox collaboration tools, and AI email agents.
- Six [vendor questions](#what-to-look-for-before-you-sign) expose most bad fits: grounding, approval flow, data handling, control, pricing model, and onboarding.
- **[InboxPilot](#where-inboxpilot-leads-and-where-it-does-not), which is us,** leads for team and operational email: grounded drafts inside Gmail and Outlook, flat pricing by draft volume, unlimited seats on paid plans. It is not a personal-productivity tool.
- Walk away from vendors showing [these red flags](#red-flags-worth-walking-away-from): no answer on model training, no exclusion controls, per-seat pricing with no team story.
## First decide which problem you are buying for
Most buyers have one of three problems, and each maps to a different product.
**Too much volume.** The inbox receives hundreds of messages, many of them the same questions, and replies go out too slowly. You need automation: something that drafts or handles the repeatable mail so people only touch exceptions.
**Too much overhead.** You can keep up, but opening the inbox is a cognitive tax. You need triage: sorting, prioritizing, and surfacing what matters.
**Writing is too slow.** You know what to say; typing it is the drag. You need drafting help in your own voice.
Volume problems belong to teams and shared addresses. Overhead and drafting problems belong to individuals. Almost no tool solves both sides well, whatever the landing page says.
## The four kinds of AI email assistant
| Category | What it actually does | Examples | Pricing model | Buy it when |
|---|---|---|---|---|
| **Personal email client** | Speed and triage for one person's inbox | Superhuman | Per seat, around $30/user/mo | Your own inbox is the bottleneck |
| **Drafting copilot** | Writing help inside your existing suite | Gemini for Gmail, Microsoft Copilot | Bundled with the office suite | You want a writing aid, not automation |
| **Shared inbox collaboration tool** | Assignment, internal comments, and rules on support@ or sales@ | Front, Hiver, Missive | Per seat, entry tiers $14-$25/user/mo | Coordination between people is the problem |
| **AI email agent** | Reads incoming mail, drafts grounded replies, routes and escalates | InboxPilot | Flat, by AI draft volume | The same questions arrive daily and eat the day |
The first two rows make an individual faster. The last two work on company email. Fyxer, at around $30 per user per month, sits between the first two: personal inbox organization plus drafting, per seat.
If you want the deeper comparisons, we keep dedicated pages for [InboxPilot vs Fyxer](/blog/alternative-fyxer) and [InboxPilot vs Superhuman](/blog/alternative-superhuman-ai).
## What to look for before you sign
Six questions filter this market faster than any feature matrix.
### 1. Does it learn from your content or from templates
Template libraries don't scale; you end up maintaining them forever. Tools that read your docs, website, and past email produce answers that stay current as your business changes. **Ask:** how does the AI know what to say, and can I feed it my own documents?
### 2. Does it draft, send, or both, and who decides
There is a wide gap between a tool that prepares drafts for approval and one that sends on its own. The pattern to look for is human approval by default with auto-send as an opt-in per workflow, not a global switch. **Ask:** can I keep approval mandatory for some workflows and automate others?
### 3. What happens to your email data
Is your content used to train models, where is it stored, and can they show a SOC 2 report? This deserves its own checklist, and we wrote one: [the data privacy guide for AI email tools](/blog/ai-email-tools-data-privacy-guide). **Ask:** is my email ever used to train your models?
### 4. What can it be told never to touch
You need sender-level and topic-level exclusions: legal threads, angry escalations, anything with a keyword you specify. A tool without exclusion controls will eventually answer something it shouldn't have opened. **Ask:** how do I stop it from ever replying to a specific sender or topic?
### 5. What does it cost at your real size
Per-seat pricing looks cheap solo and compounds with every hire. Volume pricing looks bigger up front and flattens as the team grows. **Ask:** if I add three teammates and two inboxes in six months, what changes on the invoice?
### 6. How long until it answers accurately
Some tools are useful the first afternoon; others want a rollout project. Neither is wrong, but you should know which one you are buying. **Ask:** what does week one look like, and what do I have to prepare?
## Where InboxPilot leads, and where it does not
InboxPilot is an inbox-native AI email agent. It connects to Gmail or Outlook, including shared inboxes, with no migration and no new interface. It reads what arrives, drafts replies grounded in your docs, website, and past email, routes threads with plain-English rules, and escalates when it is unsure. Humans approve every send by default; auto-send is opt-in per workflow.
That design targets one problem: repetitive operational email. RFQs and quotes, order status, returns, document collection, bookings, purchase orders, COI requests, routine support. If those are the piles in your inbox, this is the category we lead and the tool we would tell you to trial first.
**Fit and facts:**
- Best for teams whose shared inbox answers the same questions daily
- Pricing is flat by draft volume, never per seat: Free (25 drafts/mo), Hobby $29/mo (200), Standard $149/mo (1,500, unlimited inboxes), Pro $499/mo (12,000), Enterprise custom ([pricing](/pricing))
- SOC 2 Type II, GDPR compliant, customer data never trains AI models
- Integrations include Slack, Zendesk, Shopify, Pipedrive, Notion, and custom APIs
**Tradeoffs, plainly:** InboxPilot is not a personal-productivity tool. It won't reorganize an executive's private inbox or shave seconds off keyboard shortcuts; Superhuman is better at that, and Fyxer is built for exactly that job. It's also not a chat widget, a ticket queue, or a phone system. Email in, email out.
## Red flags worth walking away from
**No straight answer on training data.** If a vendor can't say "we do not train on your email" in one sentence, assume the opposite.
**No exclusion controls.** Automation you cannot scope is automation you will eventually apologize for.
**Per-seat pricing with no team tier.** For anything beyond solo use, the math breaks quickly. Look for inbox-based or volume-based pricing.
**Accuracy claims with no trial.** "Accurate replies" means nothing until it's seen your mail. Any serious vendor lets you test on real traffic before you pay.
## Which one fits
**Your own inbox is the problem:** buy a personal tool. Superhuman for speed and triage, Fyxer for organization plus drafting. Honest win for both; we don't compete there.
**You mostly need writing help:** try the copilot already bundled in your suite before paying for anything else.
**Your team argues about who owns which thread:** a shared inbox collaboration tool like Front, Hiver, or Missive fixes assignment and visibility.
**Your team answers the same operational questions every day:** that is the case [InboxPilot](/pricing) is built for, and the free plan is enough to test it on real traffic.
Run a two-week trial with your actual senders before committing to any of them. Watch what the tool drafted, what it should never have touched, and what your customers said back.
## Related reading
- [AI email assistant for teams](/blog/ai-email-assistant-for-teams): the shared inbox version of this decision, with the pricing math.
- [AI email assistant for executives](/blog/ai-email-assistant-for-executives): why the executive inbox is usually two problems wearing one label.
- [AI email tools and data privacy](/blog/ai-email-tools-data-privacy-guide): the vendor questions that matter before you connect anything.
- [Best AI assistants compared](/blog/best-ai-assistants-comparison-2026): the wider tool-by-tool comparison.
- [RFQ and quote request automation](/use-cases/rfq-email-automation): how quote requests get read, priced, and answered from your own catalog.
If the pile in your inbox is operational, repetitive, and shared, that is the specific gap [InboxPilot](/pricing) was built to close. Start on the free plan and let your real email decide.
---
## AI Email Assistant for Executives: A 2026 Reality Check
Source: https://www.inboxpilot.co/blog/ai-email-assistant-for-executives
Published: 2026-02-28
Workers now average 117 emails a day. Executive inbox pain is usually two problems: personal triage, and the company's operational email leaking upward.
The executive inbox works like a smoke detector. Much of what lands in it is not the executive's job, exactly. It is everything downstream that smoldered long enough to climb: the quote nobody sent, the refund nobody approved, the customer who CCed the CEO because support@ went quiet for three days.
Most "AI email assistant for executives" articles skip that detail. They assume the executive inbox is one problem, personal triage, and recommend one tool. In practice it is two problems wearing one label, and they have different fixes with different price tags.
**Disclosure:** we make [InboxPilot](/product), an AI email agent for a company's operational email. It is not a personal-inbox productivity tool, and if personal triage is your whole problem, tools like Superhuman are the honest recommendation, not us. This post separates the two problems so you buy for the one you actually have.
## TL;DR
- Executive inbox pain is [two problems, not one](#two-different-problems-hide-behind-executive-email): your own triage, and the company's operational email leaking upward.
- Microsoft's 2025 Work Trend Index measured the average worker at **117 emails a day, interrupted every two minutes** during core hours. See [what actually reaches you](#the-operational-inbox-is-what-actually-reaches-you).
- For personal triage, [a personal email client is the right buy](#when-a-personal-email-client-is-the-right-buy). Superhuman and Fyxer own that category, and we do not compete in it.
- **[InboxPilot](#what-fixing-the-operational-layer-looks-like), which is us,** is the fix when the real problem is the operational layer: grounded drafts in the shared inboxes whose silence becomes your escalations, with human approval on every send by default.
- Before approving either purchase, ask [the same three questions](#questions-to-ask-before-you-approve-either-purchase) about grounding, control, and data handling.
## Two different problems hide behind executive email
**Problem one is personal.** Your named inbox gets more than you can process: board threads, investor updates, intros, internal decisions. The volume is high and the judgment required is higher. No AI should be answering most of it, but better triage, faster keyboard-driven processing, and good drafts make the hours shorter.
**Problem two is organizational.** The company's shared inboxes, sales@, support@, quotes@, are slow or inconsistent, and the failures escalate to you. The customer CCs the CEO. The GC calls because the quote request sat unopened. You didn't receive this email because it needs your judgment. You received it because a process broke two levels down.
The tooling mistake is treating problem two with a problem-one tool. A faster personal email client helps you process the escalation beautifully. It does nothing about why the escalation exists.
## When a personal email client is the right buy
If your pain is genuinely personal, buy in the personal category and don't overthink it.
Superhuman built its reputation on speed and triage for exactly this user, and Fyxer positions itself as an organizer and drafter for busy individuals; both have charged around $30 per user per month. They live in your own inbox, learn your patterns, and make the daily grind of processing measurably faster.
What they won't do is answer the company's email. They are single-player tools by design. That's not a criticism; it's the category boundary, and it is the reason we wrote comparison pages for [Fyxer](/blog/alternative-fyxer) and [Superhuman](/blog/alternative-superhuman-ai) instead of pretending we replace them.
## The operational inbox is what actually reaches you
The baseline load is real for everyone. In 2025, Microsoft's Work Trend Index measured the average worker receiving 117 emails a day and getting interrupted every two minutes during core hours ([Microsoft WorkLab, Breaking Down the Infinite Workday](https://www.microsoft.com/en-us/worklab/work-trend-index/breaking-down-infinite-workday), 2025). Executives generally sit above that average, but the more useful observation is about composition: a meaningful share of what reaches an executive is operational mail that escaped its lane.
And operational mail escapes its lane through slowness. The classic evidence is old, so we date it: Harvard Business Review's 2011 audit of 2,241 US companies found the average first response to an inbound lead took 42 hours and 23% of companies never replied at all ([HBR, March 2011](https://hbr.org/2011/03/the-short-life-of-online-sales-leads)). That study measured web leads, not shared inboxes, so treat it as directional. The direction matches what every executive already knows: unanswered email doesn't disappear, it climbs.
| | Personal triage problem | Operational email problem |
|---|---|---|
| **Where it lives** | Your named inbox | sales@, support@, quotes@, billing@ |
| **What it looks like** | Too many threads needing your judgment | The same questions, answered slowly or inconsistently |
| **Right category** | Personal email client (Superhuman, Fyxer) | Inbox-native AI email agent (InboxPilot) |
| **Who benefits** | You | The team, and you, via fewer escalations |
| **Pricing shape** | Per seat | Flat, by AI draft volume |
## What fixing the operational layer looks like
This is the half where InboxPilot leads, so weigh the source. It connects to the shared inboxes in Gmail or Outlook that your team already uses, with no migration. It reads incoming mail, drafts replies grounded in your docs, website, and past email, applies plain-English routing rules, and escalates when unsure. A person approves every send by default; auto-send is opt-in per workflow, which matters when the mail carries pricing or commitments.
The categories it takes over are exactly the ones that otherwise leak upward: RFQs and quotes, order status, returns and refunds, document collection, bookings, purchase orders, COI requests, routine support.
For an executive evaluating it, three facts do most of the work:
- **Pricing is flat and never per seat:** Free (25 AI drafts/mo), Hobby $29/mo (200), Standard $149/mo (1,500 drafts, unlimited inboxes), Pro $499/mo (12,000), Enterprise custom ([pricing](/pricing)). Unlimited users on paid plans, so it's not a per-head budget line.
- **Security posture:** SOC 2 Type II, GDPR compliant, and customer email never trains AI models.
- **Honest limits:** it is not a chat widget, not a ticket queue, not a phone tool, and, again, not a personal-inbox product. Email in, grounded draft out, human approves.
The effect on the executive inbox is indirect but real. When quotes@ answers the same day, the GC doesn't call you. When support@ handles the refund, the customer doesn't CC you. The escalation channel quiets because the layer below it works.
## Questions to ask before you approve either purchase
Whichever category you are buying, the same three questions filter vendors quickly.
**Where do the answers come from?** Templates rot. Tools grounded in your own documents and past email stay current. This matters double for operational mail, where a wrong answer is a commitment.
**Who controls what it touches?** You need topic and sender exclusions, and approval by default. Anything touching legal threads, personnel, or disputes should never see automation.
**What happens to the data?** Training policy, storage, certifications. We wrote the full checklist in the [data privacy guide for AI email tools](/blog/ai-email-tools-data-privacy-guide); it applies to us and to every personal tool equally.
## Which problem to fix first
Fix the one generating the other. If your inbox is heavy but the escalations are rare, buy the personal tool and enjoy it. If a noticeable share of your inbox exists because sales@ or support@ was slow, fixing your personal triage just helps you process failure faster, and the operational layer is the cheaper, higher-leverage fix.
Plenty of executives eventually run both: Superhuman on their own inbox, an agent on the company's. They don't compete, and any vendor who says one replaces the other is selling past the category line.
## Related reading
- [AI email assistant buyers guide 2026](/blog/ai-email-assistant-buyers-guide-2026): the full category map and vendor questions.
- [AI email assistant for teams](/blog/ai-email-assistant-for-teams): the operational problem from the team side, with pricing math.
- [InboxPilot vs Superhuman](/blog/alternative-superhuman-ai): the category boundary, tool by tool.
- [Instant lead replies for sales teams](/blog/sales-team-instant-lead-replies): why slow shared inboxes cost revenue before they cost your attention.
- [Document collection automation](/use-cases/document-collection-automation): chasing missing documents without writing the reminders yourself.
If the emails reaching you are mostly things somebody else should have answered two days ago, that operational layer is the piece [InboxPilot](/pricing) fixes. The free plan is enough to point it at one shared inbox and watch what stops climbing.
---
## Best AI Email Assistant for Teams in 2026
Source: https://www.inboxpilot.co/blog/ai-email-assistant-for-teams
Published: 2026-02-28
Team email lives in shared inboxes, not seats. AI email agents vs collaboration tools like Front and Hiver, and why the pricing math flips at 10 users.
Watch a five-person team run sales@ for a week and you will see the same email answered three different ways, one thread claimed by two people, and one claimed by nobody for two days. The volume isn't the hard part. The hard part is that a shared inbox has no owner, so consistency and speed both depend on who happened to open it.
Tools attack that problem from two directions. Collaboration tools organize the people: assignments, internal comments, statuses. AI email agents work on the mail itself: reading, drafting, routing. Most buying guides blur the two categories, which is how teams end up with the wrong one.
**Disclosure:** we make [InboxPilot](/product), an AI email agent for exactly this situation, and it is our pick below for teams drowning in repetitive operational email. It's not a collaboration platform, and if thread ownership and internal discussion are your bigger problem, Front or Hiver will serve you better. We say where.
## TL;DR
- Team email means [shared inbox email](#team-email-is-shared-inbox-email): support@, sales@, quotes@. Tools built for personal inboxes do not transfer.
- Two tool families compete for the budget: see [the at a glance table](#two-tool-families-at-a-glance) comparing InboxPilot, Front, Hiver, Missive, and Fyxer.
- **[InboxPilot](#inboxpilot-for-teams-which-is-us), which is us,** leads when the problem is repetitive operational mail: grounded drafts inside Gmail and Outlook, human approval by default, flat pricing with unlimited seats on paid plans.
- [Per-seat pricing fights team adoption](#why-per-seat-pricing-fights-team-adoption): at 15 users, $22.50 per seat is $337.50 a month against a flat $149.
- Collaboration tools [win honestly](#where-a-collaboration-tool-beats-us) on assignment, internal comments, and analytics. Some teams need both layers.
## Team email is shared inbox email
A team's email problem almost never lives in personal inboxes. It lives in the addresses everyone shares and nobody owns: support@, sales@, billing@, quotes@. Those inboxes have three properties personal tools aren't built for.
**Volume concentrates there.** The repetitive questions, order status, pricing, availability, returns, all land in one place, in bulk.
**Consistency matters more than speed.** Five people answering the same question five ways is how a team quietly contradicts its own policies.
**Nobody is accountable by default.** A thread everyone can see is a thread everyone can assume someone else took.
Any tool you evaluate should be judged against those three, not against a demo of a founder clearing their personal inbox.
## Two tool families, at a glance
| Tool | Category | AI drafting | Pricing model | Entry price | Main tradeoff |
|---|---|---|---|---|---|
| **InboxPilot** | AI email agent | Yes, grounded in your docs and past email | Flat, by draft volume, unlimited seats | Free, then $29/mo | Not a collaboration or ticketing layer |
| **Front** | Shared inbox collaboration | Copilot is a paid add-on | Per seat | $25/seat/mo | Real cost sits above the headline price |
| **Hiver** | Shared inbox collaboration | From Growth tier | Per seat | $25/user/mo | Gmail-first; Outlook needs the separate Omni product |
| **Missive** | Shared inbox collaboration | On Productive tier and above | Per seat | $14/user/mo | Cheapest tier has no AI |
| **Fyxer** | Personal AI assistant | Yes, for individual inboxes | Per seat | $22.50/user/mo annual | Built for individuals, not shared addresses |
Per-seat figures are the vendors' published entry tiers as verified in July 2026; the [shared inbox comparison](/blog/best-shared-inbox-software) covers that category tool by tool.
The split to internalize: collaboration tools make humans faster at answering. An agent answers, and humans approve. Which one you need depends on where the hours actually go.
## Why per-seat pricing fights team adoption
Per-seat pricing made sense when software's cost scaled with the humans using it. For AI email, the cost driver is volume: a five-person team handling 1,500 emails a month needs the same AI work as a fifteen-person team handling 1,500 emails a month.
Here is the arithmetic with Fyxer's $22.50 per user per month annual rate against InboxPilot's flat Standard plan:
| Team size | Per seat at $22.50/user/mo | InboxPilot Standard, flat |
|---|---|---|
| 5 users | $112.50 | $149 |
| 10 users | $225 | $149 |
| 15 users | $337.50 | $149 |
| 25 users | $562.50 | $149 |
Below ten users, per-seat is cheaper and that's worth saying plainly. At ten the lines cross, and past it the gap compounds with every hire. The quieter cost of per-seat models is behavioral: teams start rationing licenses, and the person covering the inbox on a Saturday turns out not to have one.
## InboxPilot for teams, which is us
InboxPilot is an inbox-native AI email agent. It connects to the shared inboxes your team already runs in Gmail or Outlook, no migration, no new interface to train people on. It reads incoming mail, drafts replies grounded in your docs, website, and past email, triages and labels, routes threads with plain-English rules, and escalates when unsure. Approval is human by default; auto-send is opt-in per workflow.
For the three shared inbox properties above: it absorbs the concentrated volume by drafting the repetitive replies, it enforces consistency because every draft comes from the same grounded sources, and it narrows the accountability gap because routing rules put each thread in front of a named person with a draft attached.
The operational categories it handles are the usual suspects: RFQs and quotes, order status (with a Shopify integration), returns and refunds, document collection, bookings, purchase orders, COI requests, routine support. Integrations include Slack, Zendesk, Shopify, Pipedrive, Notion, and custom APIs.
**Fit and facts:**
- Best for teams whose shared inbox answers the same questions daily
- Pricing, flat and never per seat: Free (25 drafts/mo), Hobby $29/mo (200), Standard $149/mo (1,500 drafts, unlimited inboxes), Pro $499/mo (12,000), Enterprise custom ([pricing](/pricing))
- Unlimited users on paid plans, so weekend cover and new hires cost nothing
- SOC 2 Type II, GDPR compliant, customer email never trains AI models
**Tradeoffs, plainly:** InboxPilot doesn't give you assignment workflows, internal comment threads, SLA timers, or team analytics dashboards. It's not a ticket queue, a chat widget, or a phone tool. If your inbox problem is coordination rather than composition, we're the wrong first purchase.
## Where a collaboration tool beats us
Give the other category its wins, because they are real.
**Front** is the mature choice for larger teams that want a full customer operations platform around the mailbox: strong rules, analytics, omnichannel. Its AI drafting is a paid add-on, so price the real configuration, not the $25 headline.
**Hiver** keeps Google Workspace teams inside Gmail with assignment and round-robin routing that maps naturally to "whose turn is it." The catch for mixed environments: Outlook support requires its separate Omni product.
**Missive** is the budget pick with a genuinely deep rules engine, though the $14 tier ships without AI, so the practical plan is Productive.
Teams with heavy internal discussion per thread, formal SLAs, or multi-channel support (chat, social, phone) should start in this category. Some teams eventually run both layers: a collaboration tool for ownership, an agent for the answering.
## What to check on any team trial
Two weeks on real traffic answers more than any comparison table. Watch four things: whether drafts were accurate for your actual questions, whether anything got touched that should have been excluded, whether the team actually used it or quietly reverted, and what the invoice looks like at the headcount you expect next year, not this one.
## Which one fits
**Repetitive operational email is eating the week:** trial [InboxPilot](/pricing) first; the free plan covers 25 drafts on real traffic.
**Threads fall through the cracks between teammates:** Front or Hiver, depending on whether you live in a platform or in Gmail.
**Small team, tight budget, rules-heavy workflow:** Missive.
**The problem is actually one person's inbox:** that's the personal category; see the [buyers guide](/blog/ai-email-assistant-buyers-guide-2026).
## Related reading
- [Best shared inbox software for Gmail and Outlook](/blog/best-shared-inbox-software): the collaboration category in full, tool by tool.
- [AI email assistant buyers guide 2026](/blog/ai-email-assistant-buyers-guide-2026): the four-category map this post sits inside.
- [Instant lead replies for sales teams](/blog/sales-team-instant-lead-replies): what faster first replies are worth on inbound leads.
- [Best RFQ email management software](/blog/best-rfq-email-management-software): the same shared inbox problem, framed for quote requests.
- [RFQ and quote request automation](/use-cases/rfq-email-automation): how quote requests get read, priced, and answered from your own catalog.
If your team's shared inbox answers the same questions every day and the drafting is the bottleneck, that is the piece [InboxPilot](/pricing) was built to remove. Point it at one inbox on the free plan and let two weeks of real email make the case either way.
---
## AI Email Tools and Data Privacy: What to Ask Vendors
Source: https://www.inboxpilot.co/blog/ai-email-tools-data-privacy-guide
Published: 2026-02-28
Five questions to ask any AI email vendor before granting inbox access: training, storage, SOC 2, retention, control. Plus InboxPilot's own answers.
The OAuth consent screen takes about four seconds to click through. Read it slowly once: you are handing a third party the ability to read, and often send, everything in an inbox that contains client communications, financials, HR matters, and every candid sentence anyone ever wrote to you.
Most teams grant that access in under five minutes, without reading the privacy policy. That's not carelessness; the policies are long and written to be skimmed. But there is a short list of questions that cuts through them, and any vendor worth connecting can answer every one in plain language.
**Disclosure:** we make [InboxPilot](/product), an AI email agent, so we are a vendor in the category this guide teaches you to interrogate. The questions below apply to us as much as anyone. Where we state InboxPilot's own posture, we state only what we can back, and we do not make claims about competitors' certifications, because we haven't audited them.
## TL;DR
- An OAuth grant can mean read-only or [full send-and-modify access](#what-you-are-actually-granting-an-ai-email-tool) to your entire mail history. Know which one you clicked.
- [Five questions](#five-questions-that-separate-serious-vendors-from-the-rest) separate serious vendors from the rest: model training, storage location, SOC 2, retention on cancellation, and exclusion controls.
- Regulated work raises the bar: [legal, healthcare, finance, and HR](#where-the-bar-sits-higher-by-industry) each add a requirement, and HIPAA in particular needs a signed BAA.
- Run the [five-minute checklist](#a-checklist-you-can-run-in-five-minutes) before connecting anything. Three unanswered items means walk.
- **[InboxPilot](#how-inboxpilot-answers-these-questions), which is us:** SOC 2 Type II, GDPR compliant, customer data never trains AI models, and human approval on every send by default, with auto-send opt-in per workflow.
## What you are actually granting an AI email tool
The "Sign in with Google" or "Sign in with Microsoft" button hides a scope decision that vendors make and users inherit.
**Read-only access** lets the tool read mail but not send, modify, or delete. **Full mailbox access** lets it do all of those, across your entire history, not just new mail. Many tools also request calendar and contacts in the same grant.
Neither scope is wrong by itself; an assistant that sends replies needs send permission to exist. The point is to know which grant you made and to match it against what the tool claims to do. A tool that only drafts shouldn't need delete rights.
The scope tells you what the vendor can touch. The five questions below tell you what they do with it, which is the part the consent screen never shows.
## Five questions that separate serious vendors from the rest
| Question | Good answer looks like | Walk away when |
|---|---|---|
| Is my email used to train models? | A flat written no, backed by a DPA | "We may use data to improve our services" |
| Where is data stored and processed? | Named regions, named sub-processors | The sales rep has to go find out |
| Can you show a SOC 2 report? | Type II report available under NDA | No audit, no named framework |
| What happens when I cancel? | Defined deletion timeline, GDPR deletion honored | Silence, or indefinite retention |
| What can I exclude from automation? | Sender, topic, and workflow-level controls | An all-or-nothing switch |
### 1. Is my email used to train your models
This is the question with the widest gap between vendors and the one most evaded. AI had to learn from something; the issue is whether it keeps learning from you. If customer content feeds model training, your client emails and confidential threads may be improving a system that serves other customers.
Look for an explicit sentence, "we do not use your data to train our models," and a Data Processing Agreement that says the same thing in binding language. Treat "improve our services" phrasing as a yes until proven otherwise.
### 2. Where is my data stored and processed
For EU businesses, or anyone with EU customers, processing location is a compliance question, not a preference. GDPR requires lawful transfer mechanisms for personal data leaving the EU, such as Standard Contractual Clauses. Ask for server regions, the sub-processor list, and the transfer mechanism by name. A vendor that can't answer is either non-compliant or does not know its own infrastructure, and both are disqualifying.
### 3. Can you show a SOC 2 report
SOC 2 is an independent audit of security controls. Type I is a snapshot; **Type II verifies the controls operated over a sustained period**, which makes it the report worth asking for. It's not a guarantee, but it is the difference between "trust us" and "a third party checked."
No SOC 2 isn't automatically fatal for a young vendor, but they should name the framework they follow (ISO 27001, NIST) and offer something auditable in its place.
### 4. What happens to my data when I cancel
Retention after cancellation is where good intentions go unexamined. You want a defined deletion timeline in writing and confirmation that GDPR or CCPA deletion requests are honored. Data kept indefinitely after you leave is risk you carry for a product you no longer use.
### 5. What can I stop the AI from touching
The most practical privacy control is scoping. You should be able to exclude specific senders, specific topics, and whole categories of thread from automation, and to keep human approval mandatory on everything else. Legal matters, disputes, and personnel threads should never be a model's problem. A tool that can't be told "never touch this" cannot be trusted with an inbox that contains everything.
## Where the bar sits higher by industry
**Legal.** Attorney-client privilege extends to email. Confirm privileged matters can be excluded from automation entirely and that nothing privileged can end up in training data.
**Healthcare.** If your mail contains Protected Health Information, HIPAA applies and the vendor must sign a Business Associate Agreement. Many AI email tools won't. No BAA, no connection, regardless of features.
**Finance and accounting.** Client financial data brings its own regulatory load. Confirm encryption in transit and at rest, and ask who among the sub-processors can see client data.
**HR and recruiting.** The personal data here belongs to employees and candidates, not just the company, which makes training-data policies and deletion rights weigh heavier than usual.
## A checklist you can run in five minutes
Before connecting any AI tool to your inbox, confirm in writing:
- No-training policy stated explicitly
- DPA available and signed
- Storage locations and sub-processors named
- Deletion timeline on cancellation defined
- SOC 2 (ideally Type II) or a named framework with third-party audit
- GDPR or CCPA position stated, if either applies to you
- Sender and topic exclusion controls exist
- Human approval available as the default, not a workaround
- Industry-specific requirement met (BAA for HIPAA, privilege handling for legal)
If the first three cannot be satisfied, stop there. Features can't compensate for a vendor that will not commit on paper.
## How InboxPilot answers these questions
Since we wrote the exam, here is our own answer sheet, limited to what we can actually back:
- **Training:** customer data never trains AI models.
- **Certification:** SOC 2 Type II.
- **Regulation:** GDPR compliant.
- **Control:** human approval on every send by default. Auto-send is opt-in per workflow, drafting is grounded in your own docs and past email, and the agent escalates when unsure rather than guessing. Plain-English rules govern what gets triaged, labeled, routed, or left alone.
For anything this list does not cover, retention timelines, sub-processors, DPAs for your jurisdiction, ask us the same way you would ask anyone else; the [security page](/security) is the starting point. A vendor that resents due diligence is answering a question you didn't ask.
## Related reading
- [AI email assistant buyers guide 2026](/blog/ai-email-assistant-buyers-guide-2026): the full evaluation framework, of which privacy is one gate.
- [AI for law firms](/blog/ai-for-law-firms): the privilege and confidentiality questions in depth.
- [AI email assistant for teams](/blog/ai-email-assistant-for-teams): where shared inboxes change the risk picture.
- [What an AI email agent actually is](/blog/ai-email-agent): the category this guide keeps referring to.
- [Document collection automation](/use-cases/document-collection-automation): chasing missing documents without writing the reminders yourself.
Fifteen minutes of vendor questions is cheap insurance against connecting your inbox to a training pipeline. If you want to see how a vendor answers when the questions are pointed at it, [InboxPilot](/security) will sit for the exam.
---
## Microsoft Copilot Email Alternative for Teams (2026)
Source: https://www.inboxpilot.co/blog/alternative-microsoft-copilot-email
Published: 2026-02-28
Copilot for Outlook is a $30/user/month drafting layer on M365. Compare it with InboxPilot, which automates shared-inbox email on flat pricing.
Microsoft Copilot in Outlook does what it says: it summarizes long threads, suggests reply drafts, and coaches your tone. If your organization already lives in Microsoft 365, it is a genuine upgrade for the person reading and writing the mail.
The cost of entry is specific. Copilot is a $30 per user per month add-on, on top of a qualifying M365 business plan such as Business Standard at $12.50 per user per month or higher. And what you get for it is assistance, not automation: every reply Copilot drafts still waits for a human to review and send.
That leaves two groups searching for an alternative: teams not on the right Microsoft plan (or on Gmail entirely), and teams whose problem is not drafting speed but a shared inbox full of repetitive email that nobody has answered yet.
**Disclosure:** we make [InboxPilot](/), the email automation side of this comparison, so read our take on Copilot accordingly. Copilot is a suite-wide assistant and a reasonable buy for committed M365 shops; we are a narrower tool aimed at a different layer, and this post is about that difference.
## TL;DR
- **[InboxPilot](#inboxpilot-the-pick-for-team-and-support-email-automation)** is the pick for automating repetitive team email, which is us: grounded drafts, triage, routing, and opt-in auto-send inside shared Gmail and Outlook inboxes.
- [Microsoft Copilot](#microsoft-copilot-the-assistant-layer-across-m365) is the pick for individuals inside a committed M365 organization, where it assists across Outlook, Word, Excel, and Teams.
- The choice comes down to [which layer is broken](#what-are-you-actually-replacing): people drafting too slowly, or an inbox nobody is keeping up with.
- Pricing models differ sharply: Copilot is $30 per user per month on top of M365; InboxPilot is flat by AI draft volume with unlimited seats on paid plans.
- The [which one fits](#which-one-fits) section maps situations to picks, including running both.
## InboxPilot and Copilot at a glance
| Tool | Best for | Pricing model | Main tradeoff |
|---|---|---|---|
| **InboxPilot** | Teams automating repetitive email in shared Gmail or Outlook inboxes | Flat, by AI draft volume, unlimited seats on paid plans | Email only: no chat widget, ticket queue, or suite-wide assistant features |
| **Microsoft Copilot** | Individuals in M365 organizations wanting AI across Outlook and Office apps | $30 per user per month add-on, plus qualifying M365 plan | Drafts only, Outlook only, grounded in SharePoint and Teams content, costs scale with headcount |
## What are you actually replacing
Copilot and InboxPilot are both "AI for email" and yet barely compete, because they attack different bottlenecks.
**Copilot speeds up the human.** Summaries mean less reading, drafts mean less typing, tone coaching means fewer rewrites. If your team's email volume is manageable and the complaint is that composing takes too long, that is the bottleneck Copilot addresses, and it addresses it across the whole Office suite, not just mail.
**InboxPilot reduces what reaches the human.** A shared inbox receiving order-status questions, quote requests, and returns does not primarily suffer from slow typing. It suffers from volume and latency: messages sit unclaimed, answers vary by who replies, and the same question is answered from scratch daily. That needs recognition, routing, and grounded replies, produced whether or not anyone is at the keyboard.
Decide which sentence describes your team before comparing features. Per-user assistant pricing also reads very differently depending on the answer: it is fair for a tool that makes each person faster, and expensive for a team that mostly needs one inbox handled.
## The two tools, honestly
### InboxPilot: the pick for team and support email automation
InboxPilot is an inbox-native AI email agent, and it is our product, so weigh this section with that in mind. It connects to Gmail and Outlook, including shared inboxes, with no M365 Business requirement, no migration, and no new interface. It reads incoming email and drafts replies grounded in your company's docs, website, and past email, rather than in whatever a general model can guess.
Human approval is the default. Auto-send is opt-in per workflow: teams typically let the agent draft everything for review at first, then switch on auto-send for the routine categories it handles reliably, with escalation to a human whenever confidence is low. Plain-English rules cover triage, labels, and routing across multiple inboxes, and integrations include Slack, Zendesk, Shopify, Pipedrive, and Notion alongside Gmail and Outlook.
The core use cases are repetitive operational email: RFQs and quotes, order status, returns and refunds, document collection, bookings, purchase orders, and routine support. On security, InboxPilot is SOC 2 Type II and GDPR compliant, and customer data never trains AI models.
- **Best fit:** teams whose shared inboxes answer the same questions on repeat and want consistent, grounded replies without composing each one.
- **Pricing:** flat, by AI draft volume, never per seat. Free (25 drafts a month), Hobby $29, Standard $149 (1,500 drafts, unlimited inboxes), Pro $499 (12,000 drafts), Enterprise custom. ([Pricing](/pricing))
- **Tradeoff:** email only and deliberately narrow. It will not summarize your Word docs, sit in your Teams meetings, or assist across the Office suite, and it is not a personal productivity tool for an executive's own mailbox.
Against Copilot specifically: InboxPilot is the tool when the expensive problem is the shared inbox itself, not the speed of the people writing in it.
### Microsoft Copilot: the assistant layer across M365
Copilot's honest win is breadth inside one ecosystem. In Outlook it condenses long chains into bullet points, generates reply drafts from thread context, coaches tone and formality, helps schedule meetings, and searches your mailbox in natural language. The same subscription assists in Word, Excel, PowerPoint, and Teams, which no email-only tool matches.
For an organization already standardized on M365 Business Standard or higher, with knowledge in SharePoint and Teams, Copilot compounds an existing investment. IT manages it through familiar admin tooling, and users get AI where they already work rather than in another tab.
The limits are structural. Copilot drafts; it does not send, so high-volume inboxes still spend human time approving every reply. It is Outlook-only, which excludes Gmail teams entirely (Google's equivalent layer is Gemini for Gmail). Its grounding is the Microsoft graph, so knowledge living in Google Drive, Notion, a CRM, or the public web is out of reach for reply drafting. And per-user pricing compounds: at $30 per user per month, a 20-person rollout is $600 a month before the underlying M365 licenses.
- **Best fit:** committed M365 organizations that want individuals faster across the whole suite, email included.
- **Pricing:** $30 per user per month add-on, on top of M365 Business Standard ($12.50 per user per month) or higher.
- **Tradeoff:** a general assistant layer, not an automation system. The shared inbox still depends on a human opening, deciding, and sending.
Against InboxPilot specifically: Copilot is the tool for making M365 users faster everywhere, not for taking categories of email off the team.
## Which one fits
- **You are all-in on M365 and the complaint is individual productivity.** Buy Copilot. Suite-wide assistance is its home turf and InboxPilot does not play there.
- **Your team uses Gmail, or mixes Gmail and Outlook.** Copilot is out of scope; InboxPilot connects to both.
- **A shared inbox is where email goes to wait.** InboxPilot. Drafting assistance does not triage, route, or answer unattended mail.
- **Your knowledge base lives outside SharePoint and Teams.** InboxPilot grounds replies in your docs, website, and past email regardless of where they live.
- **Headcount is growing and per-user AI licensing stings.** InboxPilot's flat draft-volume pricing does not change when you add people.
- **You want both faster individuals and a handled inbox.** Run both; they do not overlap.
If the layer you are missing is the one that answers repetitive email instead of drafting it faster, [try InboxPilot free](/pricing), no M365 subscription required.
## Related reading
- [InboxPilot vs Gemini for Gmail](/blog/alternative-gemini-for-gmail): the same layer question on the Google side.
- [Best shared inbox for Outlook](/blog/best-shared-inbox-for-outlook): where operational email lives in Microsoft shops.
- [AI email assistant for teams](/blog/ai-email-assistant-for-teams): what team-grade email AI requires.
- [AI email assistant buyers guide](/blog/ai-email-assistant-buyers-guide-2026): the full evaluation checklist.
- [AI email tools and data privacy](/blog/ai-email-tools-data-privacy-guide): the security questions to ask any vendor in this category.
- [RFQ and quote request automation](/use-cases/rfq-email-automation): how quote requests get read, priced, and answered from your own catalog.
---
## Perplexity Email Assistant vs InboxPilot: Which Fits
Source: https://www.inboxpilot.co/blog/alternative-perplexity-email
Published: 2026-02-28
Perplexity's email assistant triages and drafts for one person. Compare it with InboxPilot, a flat-rate AI email agent for shared team inboxes.
People land on "Perplexity email assistant" from two directions. Some already pay for Perplexity, like its cited answers, and want to know whether its assistant can take over their inbox too. Others just want AI answering their email, and Perplexity is the AI brand they trust.
Both groups are asking the same underlying question: which inbox is the assistant supposed to fix? Perplexity's email assistant is built for one person's mail. If the inbox that hurts is `sales@` or `support@`, where quote requests and order questions wait for whoever notices them, a personal assistant is the wrong shape for the problem, however good the model behind it is.
**Disclosure:** we make [InboxPilot](/), so this comparison is written by one of the two vendors in it. We have kept it to checkable facts and we are upfront about the split: Perplexity's assistant is a personal tool on top of a research engine, InboxPilot is a team automation tool, and buying the wrong one wastes money in either direction.
## TL;DR
- **[InboxPilot](#inboxpilot-the-pick-for-company-email-which-is-us)** is the better pick when the email you want automated is company email: RFQs, order status, returns, and routine support answered in a shared Gmail or Outlook inbox, with flat pricing and unlimited seats.
- **[Perplexity's email assistant](#perplexity-email-assistant-a-personal-layer-on-a-research-engine)** wins for individuals: triage and drafts for your own mailbox, backed by the best cited research engine on the market.
- The real decision is [which inbox you are fixing](#what-are-you-actually-replacing): your own, or the one your whole team answers from.
- The [pricing shapes differ](#pricing-per-user-vs-flat-rate): Perplexity charges per user, InboxPilot charges a flat rate by AI draft volume with unlimited seats.
- They are not substitutes for each other. The [decision map](#which-one-fits) at the end gives honest picks by situation, including running both.
## Perplexity email assistant vs InboxPilot at a glance
| Tool | Best for | Pricing model | Main tradeoff |
|---|---|---|---|
| **InboxPilot** | Teams automating repetitive operational email in shared inboxes | Flat tiers by AI draft volume, unlimited seats, from $29/mo (free plan: 25 drafts) | Email only: no research engine, no meeting notes, no chat widget or ticket queue |
| **Perplexity email assistant** | Individuals who want their own inbox triaged and drafted, plus first-class research | Per user subscription (the research product, Perplexity Pro, has been $20/user/mo) | Personal by design: one mailbox, no company knowledge base, no team routing |
## What are you actually replacing
Before comparing features, name the job. People arrive at this comparison from two very different situations.
**Situation one: your own inbox is the problem.** You personally get too much mail, half of it needs your judgment, and you want triage plus drafts that save you the first pass. You probably also want research on tap while you write. That is the job Perplexity's email assistant was built for, and its research engine is a genuine advantage no email tool matches.
**Situation two: the company inbox is the problem.** Quote requests sit in `sales@` until someone notices. The same order-status question gets retyped by whoever happens to look. The answers already live in your docs, your website, and your past email. That is workflow automation, not personal productivity, and it is the job InboxPilot was built for.
The two products both "draft email with AI," which is why comparison tables blur them together. What they draft from, for whom, and what happens after the draft are entirely different.
### InboxPilot: the pick for company email (which is us)
InboxPilot is an inbox-native AI email agent. It works inside Gmail and Outlook, including shared inboxes, with no migration and no new interface for the team to learn. It reads incoming mail, works out what each message is asking, and drafts a reply grounded in your website, docs, and past email rather than generic model output.
Human approval is the default: drafts wait for a person to review. Auto-send is opt-in per workflow, so the fifth identical order-status question can go out on its own while quote requests still get human eyes. When the AI is not confident, it escalates instead of guessing. Triage, labels, and routing run on plain-English rules across multiple inboxes.
The sweet spot is repetitive operational email: RFQs and quotes, order status (there is a Shopify integration), returns and refunds, document collection, bookings, purchase orders, and routine support.
- **Best fit:** teams answering the same operational questions in a shared inbox every day.
- **Pricing:** flat, by AI draft volume, unlimited seats on paid plans. Free 25 drafts/mo, Hobby $29/mo (200 drafts), Standard $149/mo (1,500 drafts, unlimited inboxes), Pro $499/mo (12,000 drafts), Enterprise custom. ([Pricing](/pricing))
- **Security:** SOC 2 Type II, GDPR compliant, and customer data never trains AI models.
- **The honest tradeoff:** it is email only, and it is not a research tool. There is no answer engine, no web search, no meeting notes, no chat widget, no ticket queue. If what you actually want is Perplexity-grade research with light inbox help on the side, InboxPilot is the wrong buy.
### Perplexity email assistant: a personal layer on a research engine
Perplexity built its name on research: ask a question, get a synthesized answer with citations from the live web. For understanding a topic, checking a claim, or reading up before a difficult reply, it is hard to beat, and none of that changes here.
The email assistant extends that into your mailbox. It connects to Gmail and Outlook and helps you triage what came in and draft responses, so the AI you already use for answers also takes the first pass at your mail. For an individual who lives in Perplexity anyway, that is a real convenience: one subscription, one assistant, research and inbox in the same place.
The limits show up when you point it at company email. It is built around one person and their account. There is no shared-inbox model, no routing of a message to the right teammate, no plain-English workflow rules, and no grounding of replies in a company knowledge base. It drafts from your context, for you to send. Ask it about your return policy and it can reason impressively, but it is not reading your policy doc, your pricing table, or the last hundred replies your team sent.
- **Best fit:** individuals who want research and personal inbox help from one subscription.
- **Pricing:** per user. Perplexity Pro, the research subscription, has been $20 per user per month; which tier currently includes the email assistant is worth confirming on Perplexity's own pricing page before you commit.
- **The honest tradeoff:** personal by design. It helps you handle your mail; it does not take a category of company email off the team.
Back to the anchor problem: if the mailbox that hurts is the shared one, a personal assistant, even one with the best research engine behind it, does not fix that, and Perplexity does not claim it does.
## Pricing: per user vs flat rate
The shapes diverge with headcount. Perplexity charges per user, which is the natural model for a personal assistant: each person who wants the research engine and the inbox help pays for a seat.
InboxPilot charges by AI draft volume with unlimited seats. Standard at a flat $149 a month covers 1,500 drafts across as many teammates and inboxes as you have, and the price does not move when you hire.
Neither model is wrong. For one person, a $20 research subscription is a small line item and InboxPilot Hobby at $29 covers a single light workflow. For eight people sharing three inboxes, per-user pricing is simply the wrong shape, because the work being automated belongs to the mailbox, not to any one seat.
## Which one fits
- **You are an individual who wants research and inbox help in one place.** Perplexity. The email assistant plus the answer engine is a combination nothing in the team-email category offers.
- **Your team answers the same operational questions daily in a shared inbox.** InboxPilot. Grounded drafts plus triage and routing is the actual fix, and flat pricing covers the whole team.
- **You need replies grounded in your docs and policies, with auto-send for the safe cases.** InboxPilot. Perplexity drafts from the web and your personal context, not from a company knowledge base.
- **You mostly need to research topics, verify claims, and summarize documents.** Perplexity, and it is not close. InboxPilot does none of that.
- **You want both jobs done.** Run both. They barely overlap: plenty of people research in Perplexity all day while an email agent works the shared inboxes. There is no integration between them to configure, because they never touch the same message.
## Related reading
- [AI email assistant for teams](/blog/ai-email-assistant-for-teams): what changes when the inbox is shared.
- [AI email assistant for executives](/blog/ai-email-assistant-for-executives): the personal side of this split, covered properly.
- [Best Fyxer AI alternatives](/blog/alternative-fyxer): another personal assistant compared against team automation.
- [What an AI email agent actually does](/blog/ai-email-agent): the product category underneath this comparison.
- [Best shared inbox software](/blog/best-shared-inbox-software): the wider category for team email.
- [Document collection automation](/use-cases/document-collection-automation): chasing missing documents without writing the reminders yourself.
If the inbox you keep thinking about is your own and you value research on tap, Perplexity's assistant is worth a look. If it is the shared one your team answers all day, that is the gap [InboxPilot](/pricing) was built for, and the free plan's 25 drafts a month are enough to test it on real email.
*InboxPilot is the publisher of this article and one of the two tools discussed.*
---
## Saner AI vs InboxPilot: Personal Assistant or Email Agent
Source: https://www.inboxpilot.co/blog/alternative-saner-ai
Published: 2026-02-28
Saner.AI is a personal AI assistant for notes, tasks, and email triage. Compare it with InboxPilot, a flat-rate AI email agent for shared team inboxes.
Saner.AI starts from an honest observation: for a lot of people, the problem is not any single app but the scatter. Notes in one place, tasks in another, email piling up in a third, and the connective work of moving between them eating the day. Its answer is one personal assistant that sits across all three.
That is a real product doing a real job. But many people searching for a Saner.AI alternative are not trying to organize their own work. They are trying to fix `sales@` or `support@`: the shared mailbox where quote requests and order questions wait, because they belong to everyone and therefore to no one.
**Disclosure:** we make [InboxPilot](/), so this comparison is written by one of the two vendors in it. We have kept it to checkable facts and we are upfront about the split: Saner.AI is a personal productivity assistant, InboxPilot is a team email automation tool, and buying the wrong one wastes money in either direction.
## TL;DR
- **[InboxPilot](#inboxpilot-the-pick-for-shared-team-email-which-is-us)** is the better pick when the email you want off your plate is company email: RFQs, order status, returns, and routine support answered in a shared Gmail or Outlook inbox, with flat pricing and unlimited seats.
- **[Saner.AI](#saner-ai-one-assistant-for-notes-tasks-and-your-own-inbox)** wins on personal organization: your own inbox triaged, threads summarized, and the follow-ups captured as notes and tasks in the same place.
- The real decision is [which problem you are hiring for](#what-are-you-actually-replacing): one persons scattered work, or the companys unanswered mail.
- The [pricing shapes differ](#pricing-per-person-vs-per-team): Saner.AI prices per user like most personal tools, InboxPilot charges a flat rate by AI draft volume with unlimited seats.
- Neither replaces the other. The [decision map](#which-one-fits) at the end gives honest picks by situation.
## Saner AI vs InboxPilot at a glance
| Tool | Best for | Pricing model | Main tradeoff |
|---|---|---|---|
| **InboxPilot** | Teams automating repetitive operational email in shared inboxes | Flat tiers by AI draft volume, unlimited seats, from $29/mo (free plan: 25 drafts) | Email only: no notes, no tasks, no personal productivity layer |
| **Saner.AI** | Individuals who want notes, tasks, and their own inbox handled in one place | Per user subscription (see their pricing page for current tiers) | Personal by design: one persons workspace, no shared-inbox model, no company knowledge base |
## What are you actually replacing
Before comparing features, name the job. People arrive at this comparison from two very different situations.
**Situation one: your own work is scattered.** You personally juggle notes, tasks, and a full inbox, and things fall through the cracks between them. You want one assistant that triages your mail, summarizes the long threads, and turns what matters into tasks you will actually see again. That is the job Saner.AI was built for, and it aims squarely at knowledge workers who feel that scatter most, including people with ADHD.
**Situation two: the company inbox is the problem.** Quote requests sit in `sales@` until someone notices. The same order-status question gets retyped by whoever happens to look. The answers already live in your docs, your website, and your past email, and producing them again by hand is a real chunk of someones week. That is workflow automation, not personal productivity, and it is the job InboxPilot was built for.
Both products can be described as "AI that helps with email," which is why they end up in the same search results. Who they help, what they draft from, and what happens after the draft are entirely different.
### InboxPilot: the pick for shared team email (which is us)
InboxPilot is an inbox-native AI email agent. It works inside Gmail and Outlook, including shared inboxes, with no migration and no new interface for the team to learn. It reads incoming mail, works out what each message is asking, and drafts a reply grounded in your website, docs, and past email rather than generic model output.
Human approval is the default: drafts wait for a person to review. Auto-send is opt-in per workflow, so the fifth identical order-status question can go out on its own while quote requests still get human eyes. When the AI is not confident, it escalates instead of guessing. Triage, labels, and routing run on plain-English rules across multiple inboxes.
The sweet spot is repetitive operational email: RFQs and quotes, order status (there is a Shopify integration), returns and refunds, document collection, bookings, purchase orders, and routine support.
- **Best fit:** teams answering the same operational questions in a shared inbox every day.
- **Pricing:** flat, by AI draft volume, unlimited seats on paid plans. Free 25 drafts/mo, Hobby $29/mo (200 drafts), Standard $149/mo (1,500 drafts, unlimited inboxes), Pro $499/mo (12,000 drafts), Enterprise custom. ([Pricing](/pricing))
- **Security:** SOC 2 Type II, GDPR compliant, and customer data never trains AI models.
- **The honest tradeoff:** it is email only, and it is not a personal organizer. There are no notes, no task manager, no summaries of your reading backlog, no calendar features. If the problem is your own scattered work rather than the companys unanswered mail, InboxPilot is the wrong buy.
### Saner AI: one assistant for notes, tasks, and your own inbox
Saner.AI is a personal AI assistant built around a simple bet: the tools you already use are fine, the switching between them is what kills you. So it puts notes, tasks, and email in one workspace and lets an assistant work across them. Your inbox gets triaged, long threads get summarized into the context you actually need, and the follow-up becomes a task instead of a mental note you will lose by lunch.
For an individual, that combination is the honest win here. A team email agent does nothing for the article you meant to read, the idea you jotted down last week, or the task hiding in paragraph four of a thread. Saner.AI treats those as one connected problem, and its focus on scattered-brain workflows is a deliberate design choice, not a gap.
The limits show up when you point it at company email. It is built around one person and their workspace. There is no shared-inbox model, no routing of a message to the right teammate, and no grounding of replies in a company knowledge base. It helps you decide and draft; it does not take a category of company email off the team entirely, and the deciding stays with you.
- **Best fit:** solo professionals and knowledge workers whose real problem is scatter across notes, tasks, and their own inbox.
- **Pricing:** per user, like most personal productivity tools. We are not quoting current numbers here; check their pricing page.
- **The honest tradeoff:** personal by design. It organizes how one person handles their work; it was never meant to answer a shared mailbox.
Back to the anchor problem: if `sales@` is where email goes to die, a personal workspace does not fix that, and Saner.AI does not claim it does.
## Pricing: per person vs per team
The shapes diverge with headcount. Saner.AI prices per user, which is the natural model for a personal assistant: each person who wants their own workspace pays for a seat, and the cost tracks headcount.
InboxPilot charges by AI draft volume with unlimited seats. Standard at a flat $149 a month covers 1,500 drafts across as many teammates and inboxes as you have, and the price does not move when you hire.
Neither model is wrong. For one person, a single Saner.AI seat is a small line item, and InboxPilot Hobby at $29 covers 200 drafts for a single light workflow. For eight people sharing three inboxes, per-user pricing is simply the wrong shape, because the work being automated belongs to the mailbox, not to any one seat.
## Which one fits
- **You are a solo professional drowning in notes, tasks, and your own email.** Saner.AI. Bringing the three into one assistant is its whole point, and no team email tool attempts it.
- **Your team answers the same operational questions daily in a shared inbox.** InboxPilot. Grounded drafts plus triage and routing is the actual fix, and flat pricing covers the whole team.
- **You need replies grounded in your docs and policies, with auto-send for the safe cases.** InboxPilot. Saner.AI drafts from your personal context, not from a company knowledge base.
- **You want your inbox summarized and your follow-ups captured, not automated away.** Saner.AI. If you read every email personally, an automation layer is more than you need.
- **You want both jobs done.** They barely overlap. Run a personal assistant for the individuals who need one and an email agent on the shared inboxes; just do the per-user math honestly before rolling either out company-wide.
## Related reading
- [Best Fyxer AI alternatives](/blog/alternative-fyxer): another personal assistant compared against team automation.
- [AI email assistant for teams](/blog/ai-email-assistant-for-teams): what changes when the inbox is shared.
- [AI email assistant buyers guide 2026](/blog/ai-email-assistant-buyers-guide-2026): how to scope the purchase before comparing vendors.
- [Best AI email assistants compared](/blog/best-ai-assistants-comparison-2026): the wider field, personal and team tools side by side.
- [What an AI email agent actually does](/blog/ai-email-agent): the product category underneath this comparison.
- [Booking request automation](/use-cases/booking-request-automation): turning booking and appointment enquiries into confirmed slots.
If the work you keep losing track of is your own, Saner.AI is worth a look, and the notes-tasks-email combination is genuinely uncommon. If the mail that hurts is the shared inbox your team answers all day, that is the gap [InboxPilot](/pricing) was built for, and the free plan's 25 drafts a month are enough to test it on real email.
*InboxPilot is the publisher of this article and one of the two tools discussed.*
---
## The Psychology of Email Anxiety (and How to Fix It)
Source: https://www.inboxpilot.co/blog/email-anxiety-psychology-inbox-overwhelm
Published: 2026-02-28
Checking email three times a day measurably lowered stress in a UBC study. The psychology of inbox overwhelm, and fixes that do not rely on willpower.
You sit down to start the day and open the inbox first. Forty-seven new emails. Most are probably fine, but you do not know which ones yet, so you read all of them. Half need replies you do not have time to write. You close the tab, and the unanswered ones follow you into your next meeting. An hour later you check again, mostly to make sure nothing new is on fire.
That loop is not a time management failure. It is a psychological one, it is reasonably well documented, and it responds better to changing the environment than to discipline.
**Disclosure:** we make [InboxPilot](/), an AI email agent that drafts replies to repetitive email inside Gmail and Outlook. This post is a psychology explainer, not a pitch. InboxPilot appears once, as one of five mitigations, and it only helps with one of them: volume. If your inbox dread comes from a difficult boss or a job you hate, no software fixes that.
## TL;DR
- Email pairs **variable rewards with open loops**, the same pairing that makes slot machines hard to walk away from. See [email is built like a slot machine](#email-is-built-like-a-slot-machine).
- In a 2015 University of British Columbia experiment, people limited to **checking email three times a day reported significantly lower daily stress**, with no change in how much email they got.
- The checking is only half the cost. UC Irvine research from 2008 measured **about 23 minutes to fully refocus** after an interruption. See [the cost is cognitive](#the-cost-is-cognitive-not-just-hours).
- Willpower rules ("only check twice a day") fail because they leave the uncertainty in place. See [why willpower fixes keep failing](#why-willpower-fixes-keep-failing).
- The changes that stick are environmental: separation, triage, automation, a done state, and naming the feeling. **[InboxPilot](#3-automate-the-questions-you-have-already-answered)**, which we make, is one practical option for the automation piece. See [five changes that actually reduce the load](#five-changes-that-actually-reduce-the-load).
## Email is built like a slot machine
Nobody designed email to produce anxiety. It just happens to line up almost perfectly with the conditions that create compulsive checking.
**Variable rewards.** Most messages are noise. Occasionally one is important, exciting, or scary. Your brain cannot tell which in advance, so it learns to check constantly in hope of the payoff. This is a variable reward schedule, the same reinforcement pattern that keeps people at slot machines.
**Open loops.** Psychologists call it the Zeigarnik effect: unfinished tasks stay active in working memory and keep claiming attention even when you are doing something else. Every unanswered email is an open loop. Forty open loops is a background process that never quits.
**Ambient urgency.** An inbox has no built-in priority signal. A message from your biggest client renders identically to a newsletter. So your brain assesses every message as potentially urgent, which keeps the stress response quietly elevated even on days when nothing urgent arrives.
The best evidence that the relationship, not the volume, drives the stress comes from a randomized experiment at the University of British Columbia. Kushlev and Dunn assigned adults to a week of checking email only three times a day and a week of unlimited checking. During the limited week, participants reported significantly lower daily stress, even though the amount of email they received did not change ([Kushlev and Dunn, Computers in Human Behavior](https://doi.org/10.1016/j.chb.2014.11.005), 2015).
Same inbox. Different relationship. Less stress.
## The cost is cognitive, not just hours
Most people tally email cost in time spent. The larger cost is what the checking does to everything around it.
**Context switching.** When you break from focused work to glance at email, your brain does not snap back to where it was. Gloria Mark's research group at UC Irvine measured the recovery: on average, about 23 minutes to fully re-engage with a complex task after an interruption ([Mark et al., The Cost of Interrupted Work](https://www.ics.uci.edu/~gmark/chi08-mark.pdf), 2008). Check email ten times across a workday and the switching cost alone can plausibly eat a couple of hours of deep work capacity. That figure is arithmetic, not a study result, but the mechanism it rests on is measured.
**Decision fatigue.** Every message demands a micro-decision: read now, reply now, reply later, archive, ignore. Hundreds of those per day draw on the same cognitive resource as your real decisions, which is one reason judgment and inbox hygiene tend to degrade together in a bad week.
**Anticipatory anxiety.** Many professionals describe a low-grade unease that persists all day, not about any specific message but about the fact that the inbox exists and might contain something requiring action. It is hard to measure and easy to recognize.
And the raw load keeps the whole system primed. In 2025, Microsoft's Work Trend Index measured the average worker receiving 117 emails a day and getting interrupted every two minutes during core hours ([Microsoft WorkLab, Breaking Down the Infinite Workday](https://www.microsoft.com/en-us/worklab/work-trend-index/breaking-down-infinite-workday), 2025). At that cadence, the question is not whether the mechanics above kick in. It is how hard.
## Why willpower fixes keep failing
Most email advice is willpower dressed up as a system: check only twice a day, close the tab, use a timer, set an auto-responder.
These fail for a consistent reason. If you check email eleven times a day, it is because your brain has learned that checking resolves uncertainty. A rule against checking does not remove the uncertainty. It just asks you to sit with it until you give in, and the giving in usually arrives around the third notification.
The interventions that hold up share a different logic: **reduce what is unhandled, so there is less uncertainty to resolve.** If a meaningful share of your email is questions you have answered before, and something else handles them, you do not need discipline to ignore them. They are already done. The reward schedule collapses because checking stops paying out. The open loops close without you.
## Five changes that actually reduce the load
None of these require you to become a different person, which is the point.
### 1. Separate email from your work environment
Do not keep the inbox open in a tab beside your actual work. Open it deliberately, in its own window or its own time slot. The spatial boundary becomes a psychological one: scheduled email is engagement, an always-open tab is a slot machine on your desk.
### 2. Triage, do not process
When you open the inbox, your only job is sorting: flag the two or three things that genuinely need you, and close everything else unread or archived. This caps the open loops your brain has to carry at a handful instead of forty. Replying happens later, in a block you chose.
### 3. Automate the questions you have already answered
The messages that feed the anxiety loop are often ones that never needed you personally: the same product question, the same status request, the same scheduling back-and-forth. Your brain treats them all as open loops anyway. Moving that category out of your conscious processing entirely is the highest-leverage volume cut available.
This is the piece InboxPilot addresses, and the only place it belongs in this post. It reads incoming email, drafts replies grounded in your own docs and past email, and by default a human approves every send. The repetitive messages still get answered. They just stop being your open loops. If your volume is low or mostly one-off conversations, this mitigation will not do much for you; the other four still will. The numbers on how much of a typical inbox is repetitive are in our [email admin burden statistics roundup](/blog/admin-burden-email-statistics-2026).
### 4. Create a done state
Part of why email feels endless is that it literally is. So define an artificial ending: a short close-of-day pass where everything is either handled, scheduled, or consciously deferred. The goal is not inbox zero as a badge. It is a closure signal that reduces overnight rumination, because your brain has been told the loops are parked, not open.
### 5. Name the feeling when it shows up
When you feel the pull to check outside your chosen times, label it: "that is inbox anxiety." Research on mindfulness and compulsive behavior finds that labeling an impulse reduces its intensity. You are not suppressing the urge, you are observing it, and observation buys you enough distance to choose.
## What a calmer inbox feels like
People who get this under control describe the same shift: email becomes something you do instead of something that happens to you.
The distinction is mechanical, not motivational. When most of the repetitive volume is handled before you arrive, opening the inbox stops being a gamble and becomes a review. The variable reward schedule has nothing left to pay out. You answer the messages that need you and leave.
Anxiety needs uncertainty to attach to. Remove the uncertainty, by shrinking what sits unhandled, and there is simply less for it to grab.
## Related reading
- [Email admin burden statistics 2026](/blog/admin-burden-email-statistics-2026): what the volume costs in hours and dollars, with sources.
- [AI email assistant buyers guide 2026](/blog/ai-email-assistant-buyers-guide-2026): how to evaluate automation tools if you decide volume is your problem.
- [How to set up an automated response in Gmail](/blog/how-to-setup-an-automated-response-on-your-gmail-account): the simplest version of mitigation number three.
- [Why your inbox deserves a purpose-built AI email assistant](/blog/why-inbox-deserves-purpose-built-ai-email-assistant): the case for tools that work inside the inbox instead of beside it.
- [Booking request automation](/use-cases/booking-request-automation): turning booking and appointment enquiries into confirmed slots.
The honest sequence is environment first, habits second. Fix the separation and the triage this week; if the repetitive volume is the piece still weighing on you after that, that is the part [InboxPilot](/) automates.
---
*Studies are cited with their publication year, including where that year is older than this article: the UBC checking experiment is from 2015 and the UC Irvine interruption research is from 2008. The two-hours-lost figure is our arithmetic from the UC Irvine finding, labeled as such above. InboxPilot is the publisher of this article.*
---
## Best AI Assistants 2026: ChatGPT vs Gemini vs Copilot
Source: https://www.inboxpilot.co/blog/best-ai-assistants-comparison-2026
Published: 2026-01-15
ChatGPT, Gemini, Copilot, Claude, Perplexity, and Grok compared for 2026, plus where a purpose-built email agent beats all six on inbox work.
Most teams do not have an AI assistant problem. They have a routing problem: they bought one general assistant, and now it gets asked to do everything from summarizing a contract to answering the fortieth order-status email of the day.
The first job it does well. The second it does badly, because answering support email is not a chat task. It is a workflow that starts when a message arrives, not when a person opens a chat window and pastes something in.
This guide compares the six general assistants worth considering in 2026, then draws the line where a generalist stops being the right tool.
**Disclosure:** we make [InboxPilot](/product/ai-email-writer), an AI email agent that drafts replies inside Gmail and Outlook. We do not sell any of the six assistants below, and we are not claiming to replace them: for research, coding, and long-document work they beat us outright, because we do not do those things at all.
## TL;DR
- **ChatGPT is still the best generalist**, Gemini wins in Google shops, Copilot wins in Microsoft shops, Claude wins on long documents, Perplexity wins on cited research, and Grok wins on fast informal chat. See [the six at a glance](#the-six-general-assistants-at-a-glance).
- **All six are tools you go to.** They wait for a prompt. None of them watches a shared inbox or acts when mail arrives. See [where a generalist stops](#where-a-general-assistant-stops-and-an-email-agent-starts).
- **Per-seat pricing is the hidden cost.** Most land around $20 to $30 per user per month, so the bill tracks headcount rather than work done.
- **[InboxPilot](#inboxpilot-for-email-and-support), which is us,** is the specialist for the email layer: it reads what arrives in Gmail or Outlook, drafts from your own docs, and routes what it should not answer, priced by draft volume rather than seats.
- Most teams should run **one generalist plus one specialist**, not one tool stretched across both jobs. See [how to choose](#how-to-choose).
## What changed in 2026
The models all got good enough that raw capability stopped being the deciding factor for everyday work. What separates them now is where they live and what they can reach.
That shift favors specialists in one specific way. A general assistant can write an excellent reply to a customer email, but only after a human notices the email, opens a chat window, pastes the thread in, adds the context the model needs, copies the answer back, and edits it into the right tone. The writing was never the slow part.
## The six general assistants at a glance
| Assistant | Best for | Weakest at | Pricing signal |
|---|---|---|---|
| ChatGPT | Versatility, writing, broad productivity | Deep workflow automation | Free tier, around $20 per user per month |
| Gemini | Google Workspace teams, multimodal work | Mixed-ecosystem stacks | Free tier, around $20 to $30 per user per month |
| Copilot | Microsoft 365 and developer workflows | Open-ended creative work | Free tier, around $20 to $30 per user per month |
| Claude | Long documents, careful reasoning | Smaller integration ecosystem | Free tier, around $20 per user per month |
| Perplexity | Real-time research with citations | Long-form creative writing | Free tier, around $20 per month |
| Grok | Fast conversational use, X context | Long-form and research depth | Free for X users, around $30 per month |
Pricing here is approximate and moves often. Check each vendor's own pricing page before you budget.
## ChatGPT
OpenAI's assistant remains the most versatile option, and for most people it is the right default. It drafts, brainstorms, codes, and analyzes in one place, with the largest integration ecosystem of the six.
Where it struggles is retention across long threads, and the generalist tradeoff: it has less depth than purpose-built tools in areas like automated email workflows or compliance-heavy document work. It is also confidently wrong often enough that anything consequential needs checking.
**Choose it if** you want one assistant for the widest range of tasks and you are not committed to Google or Microsoft.
## Gemini
Google's assistant is built for teams already living in Gmail, Docs, Sheets, and Meet. It generates and summarizes inside those tools, which removes a lot of context switching.
The catch is the ecosystem boundary. Outside Google, integrations thin out, and some capabilities are still maturing in ways that make behavior less predictable for power users.
**Choose it if** your stack is Google-first. If your team lives in Gmail, also read our guide to [training Gmail on your own data](/blog/how-to-train-gmail-on-your-own-data), which covers what Gemini can and cannot reach.
## Copilot
Microsoft's assistant is embedded across Word, Excel, Outlook, Teams, and GitHub. For Microsoft-centric organizations and developers, it is the path of least resistance, and GitHub Copilot remains genuinely strong at context-aware code suggestions.
It is weaker for open-ended conversation or creative writing outside the suite, and premium plans get expensive at scale.
**Choose it if** your day runs in Outlook, Teams, and GitHub. For a closer look at what it does with email specifically, see our [Microsoft Copilot email comparison](/blog/alternative-microsoft-copilot-email).
## Claude
Anthropic's assistant is the pick for long documents, structured analysis, and work where being careful matters more than being fast. It handles reports, research summaries, and compliance-oriented drafting well.
Its ecosystem is smaller than ChatGPT's or Copilot's, and it is tuned for precision over highly creative output.
**Choose it if** you spend your day in long documents and analysis rather than short chat turns.
## Perplexity
Perplexity leads on real-time, citation-backed answers. When you need current facts with sources you can verify, it is the strongest of the six, and the citations make its output easy to audit.
It is not built for long-form creative work, and answers on niche topics run thin when the underlying sources are thin.
**Choose it if** research and fact-checking dominate your week. We compare its email side separately in [Perplexity for email](/blog/alternative-perplexity-email).
## Grok
Grok is built for speed and personality, with real-time context from X. For informal internal chat and quick questions it feels responsive in a way the others sometimes do not.
Its scope is narrower: weaker for long-form content, coding, and deep research, with a smaller ecosystem and less enterprise adoption.
**Choose it if** your use is conversational and social rather than document-heavy.
## Where a general assistant stops and an email agent starts
Every assistant above shares one architectural trait: it waits for you. That is the correct design for a research or writing tool, and the wrong design for an inbox.
Four things have to happen before a reply is worth sending, and a chat window only helps with the third:
1. **Something has to notice the email arrived.** A generalist does not watch your inbox.
2. **Something has to work out what it is.** An order status question, a quote request, and a complaint need different handling.
3. **Something has to write the reply.** This is the part general assistants do well.
4. **Something has to know your specifics.** Your lead times, your refund window, your prices. A generalist knows none of this unless a human pastes it in every single time.
Steps 1, 2, and 4 are the actual work, and they are the steps that repeat on every message. That is the gap a purpose-built email agent fills.
## InboxPilot for email and support
InboxPilot is the specialist for that layer, and it is us, so read the rest of this section knowing that.
It connects to Gmail and Outlook, including shared inboxes like support@ or info@, with no migration and no new interface. When mail arrives, it reads the thread, works out what is being asked, and drafts a reply grounded in your own documents, website, and past email rather than the open web. A person approves the send by default, and auto-send is something you turn on per workflow once you trust it. Anything it is unsure about gets escalated instead of guessed at.
Pricing works differently from the six above. Instead of a fee per seat, plans are sized by AI draft volume: free for 25 drafts a month, $29 for 200, $149 for 1,500 with unlimited inboxes, and $499 for 12,000, with unlimited seats on every paid plan. On security, InboxPilot is SOC 2 Type II certified and GDPR compliant, and customer data is never used to train AI models.
**Where it does not belong:** it is not a research assistant, a coding tool, a document analyzer, a chat widget, a phone system, or a ticket queue. If your problem is writing a strategy memo, one of the six above is the better answer. If your problem is that the same forty emails arrive every week and someone has to answer them by hand, that is the case for a specialist.
## How to choose
Match the tool to the job, and accept that you probably need two:
| If your main problem is | Use |
|---|---|
| Writing, brainstorming, general knowledge work | ChatGPT or Claude |
| Working inside Google Workspace | Gemini |
| Working inside Microsoft 365 or writing code | Copilot |
| Research that has to be current and cited | Perplexity |
| Fast informal chat and social context | Grok |
| Repetitive email your team answers by hand | InboxPilot |
The cost question is worth modeling before you commit. Per-seat assistants get more expensive as the team grows, whether or not the new people generate more work. Volume-based pricing tracks the work itself, which is usually the fairer proxy for teams whose headcount grows faster than their email.
If your inbox is the bottleneck, the free tier is 25 drafts a month, which is enough to judge the quality against your real mail before you decide anything.
## Related reading
- [The AI email assistant buyers guide](/blog/ai-email-assistant-buyers-guide-2026): how to evaluate tools in this category.
- [AI email assistants for teams](/blog/ai-email-assistant-for-teams): shared inboxes and where collaboration tools fit.
- [AI email tools and data privacy](/blog/ai-email-tools-data-privacy-guide): the questions to ask any vendor before connecting your inbox.
- [What an AI email agent actually is](/blog/ai-email-agent): the longer explanation of the category.
- [RFQ and quote request automation](/use-cases/rfq-email-automation): how quote requests get read, priced, and answered from your own catalog.
*Competitor pricing above is approximate, reflects publicly listed consumer and business tiers, and changes frequently; verify with each vendor before budgeting. InboxPilot is the publisher of this article and one of the tools discussed.*
---
## Email Automation for Real Estate Brokers | InboxPilot
Source: https://www.inboxpilot.co/blog/why-inboxpilot-real-estate-brokers-in-2026
Published: 2025-11-26
Buyers email several brokers at once and the first credible reply usually wins. How AI drafts listing, showing, and transaction email in Gmail and Outlook.
It is 10:47pm on a Tuesday. A pre-approved buyer just emailed to ask whether a listing is still available and whether they can see it this weekend. They are excited, and they sent roughly the same email to two other brokers in the same minute.
If your inbox sits quiet until morning, the showing often goes to whoever answered first. You never even knew the race happened. Real estate email is full of these small races, layered on top of transaction threads that never stop: lender updates, inspection scheduling, disclosure requests, title correspondence, and clients who want reassurance during the most stressful purchase of their lives.
**Disclosure:** we make [InboxPilot](/industries/real-estate), an AI email agent that drafts replies to listing, showing, and transaction email inside Gmail and Outlook. This post explains the workflow honestly, including where automation does not belong: no AI should be negotiating offers, discussing commission, or sending anything with legal weight unsupervised.
## TL;DR
- Speed decides more deals than brokers track. Harvard Business Review's 2011 audit of 2,241 companies found the **average first response to an inbound lead took 42 hours**, and 23% of companies never replied at all. See [why brokers lose deals in the inbox](#why-brokers-lose-deals-in-the-inbox).
- Email already eats a big slice of the week: McKinsey Global Institute puts it at **28% of working hours** for professionals generally, and a broker inbox adds a full transaction trail on top.
- The volume sorts into **five repeatable piles**: listing inquiries, showing requests, transaction coordination, document requests, and follow-ups. See [the five email types](#the-five-email-types-that-fill-a-broker-inbox).
- **[InboxPilot](#what-an-ai-email-agent-takes-off-your-plate), which is us,** classifies incoming email, drafts replies grounded in your listings and procedures, and routes the rest, with [a human approving sends by default](#the-workflow-from-midnight-inquiry-to-approved-reply).
- Offers, counters, and anything legal **skip automation entirely** via negative keywords. See [setting it up without risking a transaction](#setting-it-up-without-risking-a-transaction).
## Why brokers lose deals in the inbox
The classic response-time data is old, so we will date it plainly. In March 2011, Harvard Business Review published an audit of 2,241 US companies ("The Short Life of Online Sales Leads") that found the average first response to an inbound lead took 42 hours, 23% of companies never responded at all, and firms replying within an hour were roughly seven times more likely to qualify the lead ([HBR](https://hbr.org/2011/03/the-short-life-of-online-sales-leads), 2011). That study measured web leads across industries, not real estate inquiries, so treat it as directional. The direction is not controversial in a market where buyers and sellers routinely contact several brokers at once: the first credible answer shapes who gets the conversation.
The volume side compounds it. McKinsey Global Institute's research put email at 28% of the average professional's workweek ([McKinsey](https://www.mckinsey.com/industries/technology-media-and-telecommunications/our-insights/the-social-economy), 2012). A broker's inbox carries that baseline plus everything a live transaction generates: lender letters, inspection reports, escrow notices, HOA documents, and a nervous client cc'd on most of it.
So the two failure modes feed each other. The transaction email buries the new-lead email, the new lead goes to a faster broker, and the broker's highest-value hours go to retyping answers that have not changed since last month. We collected the broader numbers in our [email admin burden statistics roundup](/blog/admin-burden-email-statistics-2026).
## The five email types that fill a broker inbox
Ask anyone who runs a brokerage inbox and the traffic sorts into the same five piles:
| Workflow | What it looks like | Why it drags |
|---|---|---|
| **Listing inquiries** | "Is 214 Alder Court still available? What are the HOA fees?" | Time-sensitive, arrives at all hours, and the asker emailed your competitors too |
| **Showing requests** | "Can we see it Saturday?" plus the reschedules | Pure calendar coordination, but every hour of silence cools the lead |
| **Transaction coordination** | Inspection windows, appraisal scheduling, lender and title back-and-forth | Dozens of small threads per deal, each one capable of stalling the closing |
| **Document requests** | Disclosures, pre-approval letters, HOA docs, seller statements | Fetch-and-attach work that still interrupts someone's day |
| **Follow-ups** | "Any update?" from buyers, sellers, and everyone's attorney | Small individually, constant in aggregate, and silence reads as neglect |
Notice what the piles have in common. Almost none of this requires a broker's judgment. It requires availability, accuracy, and speed, which is exactly the profile of work that automates well. The judgment work (pricing strategy, negotiation, reading a seller in a listing appointment) is not on the list, and should not be.
## What an AI email agent takes off your plate
An inbox-native agent like InboxPilot works inside the Gmail or Outlook account you already use, including shared team inboxes. No new platform, no migration, no asking clients to use a portal. Here is what it can genuinely own.
### 1. Classify what just arrived
The agent reads each incoming email and tags it: listing inquiry, showing request, transaction thread, document request, follow-up, or none of the above. Triage sounds minor. It is the step that currently requires a person to open everything, and it is why a hot buyer inquiry sits unread between a title company notice and a newsletter.
### 2. Extract what matters
For an inquiry, that means the property, the timeline, the financing status, and what is missing. If the buyer never mentioned pre-approval, the draft asks for the letter, which is exactly what your best coordinator would do.
### 3. Draft the reply from your own material
This is the line between useful and dangerous. A generic AI will happily invent an HOA fee or a showing policy, and a wrong answer about a property is worse than a slow one. Grounded drafting means the agent writes only from sources you gave it: current listing sheets, showing procedures, buyer and seller FAQs, your standard disclosure language, past emails. When the answer is not in those sources, it escalates to you instead of guessing.
### 4. Answer the questions you have answered a hundred times
What are the HOA fees, is it still available, what does the inspection process look like, when is the open house. Fixed answers that live in documents are the highest-volume, lowest-risk automation target, and they are where the time comes back first.
### 5. Route the rest to the right person
Plain-English rules send lender email to the transaction coordinator, new inquiries to the listing agent, and invoices to the office. Negative keywords do the opposite job: any thread mentioning an offer, counter, commission, dispute, or attorney skips automation entirely and lands in front of a human with no draft attached.
## The workflow from midnight inquiry to approved reply
End to end, the loop looks like this:
1. **An inquiry lands** at 10:47pm while you are asleep.
2. **The agent classifies it** as a listing inquiry and pulls the property from your listing data.
3. **It drafts a reply** that confirms status, offers the actual showing windows, and asks for the pre-approval letter.
4. **The draft either waits for your morning approval**, the default, or **sends immediately** if you opted this category into auto-send.
5. **You wake up** to an engaged buyer instead of a cold one.
What that looks like in practice:
> **Incoming, 10:47pm:** "Hi, is 214 Alder Court still available? We would love to see it this weekend if possible. We are pre-approved and hoping to move by early fall."
> **AI draft, 10:48pm:** "Hi Dana, thanks for reaching out. 214 Alder Court is an active listing and this weekend works on our end. We have showing windows Saturday between 10am and 2pm; would 11am suit you? If you can send over your pre-approval letter beforehand, we can move quickly if the home is the right fit."
Notice what the draft does not do. It does not discuss price flexibility, speculate about other offers, or promise anything the calendar cannot support. Every fact in it traces to a document, and by default a person still reads it before it sends.
## Setting it up without risking a transaction
Three steps, and the guardrails matter more than the features:
1. **Connect the inbox.** Whatever address inquiries hit: your own, info@, or the team's shared inbox. Gmail or Outlook both work.
2. **Feed it your material.** Current listings, showing procedures, buyer and seller FAQs, standard disclosure language, and a handful of past replies you were proud of. Drafts are only as good as this grounding.
3. **Set the guardrails.** Trigger keywords like *available*, *showing*, *open house*, and *disclosure* route into drafting. Negative keywords like *offer*, *counter*, *commission*, *dispute*, and *attorney* route straight to a human, no draft. Leave draft-and-approve on, and opt narrow categories into auto-send only after you have watched the drafts for a while.
Draft-and-approve is not a setting we invented for this post; it is how InboxPilot works by default, and the AI draft is the unit every plan is metered by. Free covers 25 drafts to test on real traffic, Hobby is $29 per month, and Standard at $149 per month covers 1,500 drafts, unlimited inboxes, and the knowledge base grounding doing the heavy lifting in step 2. Paid plans include unlimited seats, so a growing team does not change the bill. Details on the [pricing page](/pricing).
**[See how InboxPilot works for real estate teams →](/industries/real-estate)**
The real estate page includes draft examples for listing inquiries, showing coordination, and transaction email.
## Related reading
- [Property management email automation](/blog/property-management-email-automation): the adjacent inbox, where maintenance and tenant email follow the same pattern.
- [Instant lead replies for sales teams](/blog/sales-team-instant-lead-replies): the response-speed problem framed for inbound leads generally.
- [Email admin burden statistics 2026](/blog/admin-burden-email-statistics-2026): the sourced numbers on what inbox time costs.
- [Best shared inbox software for Gmail and Outlook](/blog/best-shared-inbox-software): if team coordination, not drafting, is your bigger gap.
- [Document collection automation](/use-cases/document-collection-automation): the fetch-and-chase workflow behind disclosures and pre-approval letters.
If the 10:47pm inquiry going cold is the deal you keep losing, that is the specific gap InboxPilot closes: the draft is ready before you are awake, and you still decide what sends.
---
*Statistics are attributed to their original sources with publication years stated, including where those years are older than this article: the HBR response-time audit is from 2011 and the McKinsey email-share research is from 2012. Both measured broader markets than real estate and are labeled as directional above. InboxPilot pricing was verified against the pricing page in July 2026. InboxPilot is the publisher of this article.*
---
## Why Your Inbox Deserves a Purpose-Built AI Email Assistant
Source: https://www.inboxpilot.co/blog/why-inbox-deserves-purpose-built-ai-email-assistant
Published: 2025-11-20
General chatbots bolt AI onto email: copy-paste, prompting, generic tone. Why purpose-built inbox agents like InboxPilot do the work instead.
Watch someone answer email with a general AI chatbot and count the steps. Open the thread. Copy it. Switch windows. Paste it into the chatbot with a prompt explaining who the sender is and what the reply should say. Read the output. Fix the tone. Copy the result. Switch back. Paste, proofread, send.
That is nine steps to produce one reply, and the ninth email of the morning takes just as many as the first. The drafting got faster. The workflow got longer. This is what bolting AI onto email looks like, and it is worth being precise about why it fails at scale, because the fix is not a better chatbot.
**Disclosure:** we make [InboxPilot](/), an inbox-native AI email agent, so we are arguing our own book here. This is an opinion piece about a category distinction, and it includes the cases where a general assistant is genuinely the better choice and where InboxPilot does not belong: chat widgets, ticket queues, phone support, and personal productivity for executives.
## TL;DR
- The copy-paste loop is the diagnostic: if using AI on email means moving text between windows and prompting, the AI is bolted on, not built in. See [the copy-paste loop is the tell](#the-copy-paste-loop-is-the-tell).
- General assistants are missing the four things email replies actually run on: **thread context, company knowledge, workflow, and a data boundary**. See [what a general assistant cannot see](#what-a-general-assistant-cannot-see).
- Purpose-built means the tool works inside Gmail or Outlook, drafts from your own docs, and keeps **a human approving sends by default**. See [what purpose-built actually means](#what-purpose-built-actually-means).
- **[InboxPilot](#where-inboxpilot-fits-and-where-it-does-not)**, which is us, is the purpose-built example in this piece, and it is the wrong buy for some readers: low email volume, chat-first support, or a personal exec inbox.
- If you write three emails a day, keep the chatbot. The distinction matters at operational volume, where email is the work; the [six-point test](#what-purpose-built-actually-means) tells you which side you are on.
## The copy-paste loop is the tell
General assistants are remarkable at what they were built for: open-ended questions, research, writing help, one-off tasks. Email at volume is none of those things. It is a stream of semi-repetitive external messages, each carrying history, each needing an answer grounded in facts about your business, many of them close variants of messages you answered last week.
Point a chatbot at that stream and the seams show immediately. Every message needs its context carried over by hand. Every draft needs a prompt. Every reply makes a round trip through another window, which is where wrong-thread pastes and dropped recipients come from. The volume problem this was supposed to solve is real: in 2025, Microsoft's Work Trend Index measured the average worker receiving 117 emails a day and getting interrupted every two minutes during core hours ([Microsoft WorkLab, Breaking Down the Infinite Workday](https://www.microsoft.com/en-us/worklab/work-trend-index/breaking-down-infinite-workday), 2025). A tool that adds a manual loop per message does not subtract from that number. It adds to it.
The prompting tax is the part people underestimate. The chatbot does not know your customer, your pricing, your policies, or what you told this sender last month, so you supply all of it, per message, forever. You have not automated the email. You have become the integration.
## What a general assistant cannot see
Strip the argument to its parts and the gap is four missing inputs.
| What a reply needs | General chatbot | Purpose-built inbox agent |
|---|---|---|
| **Thread context** | Only what you paste in | Reads the full thread and history in the inbox |
| **Company knowledge** | Generic training data | Grounded in your docs, website, and past email |
| **Workflow** | You copy, prompt, paste, send | Drafts appear on incoming mail; rules route and escalate |
| **Data boundary** | Depends on plan and settings | Should be contractual: SOC 2, GDPR, no training on your data |
| **Pricing basis** | Typically per seat | InboxPilot prices per AI draft, unlimited seats on paid plans |
Two of these deserve expansion.
**Grounding is the difference between a draft and a liability.** A generic model asked about your return policy will produce something confident and plausible. Plausible is the problem: an invented policy in a customer reply is worse than no reply. A purpose-built agent drafts only from sources you gave it and escalates to a human when the answer is not there. Guessing is the failure mode the whole design exists to prevent.
**The data boundary should be a product guarantee, not a settings hunt.** Consumer tiers of general assistants may use conversations to improve models unless you opt out, and either way, pasting customer emails into a personal chatbot account is a data-handling decision most companies never consciously made. Email content is exactly the material that deserves a contractual answer. We keep a fuller breakdown in our [AI email privacy guide](/blog/ai-email-tools-data-privacy-guide).
## What purpose-built actually means
The label gets used loosely, so here is a concrete test. A purpose-built AI email assistant should:
1. **Work inside Gmail or Outlook**, including shared inboxes, with no migration and no new interface. The inbox is the workspace, not a source to copy from.
2. **Read incoming mail on its own** and produce drafts without being prompted, so the work is done when you arrive rather than started when you do.
3. **Ground every draft in your knowledge**: website, docs, past email. When the answer is not in those sources, it says so instead of improvising.
4. **Keep humans in control by default.** Drafts wait for approval; auto-send is something you opt into per workflow, for categories you trust, not a default you discover later.
5. **Take rules in plain English**: route quote requests to estimating, label by topic, and pull sensitive threads (complaints, legal, disputes) out of automation entirely.
6. **Price by work done, not people present.** Per-seat pricing punishes exactly the shared-inbox teams that need this most.
Notice what the list optimizes for. Not smarter prose. Fewer steps, verified facts, and control over what sends. The chatbot era proved the models can write. The purpose-built question is whether the tool can do the job around the writing.
## Where InboxPilot fits, and where it does not
InboxPilot, which is us, is built against that six-point list. It connects to Gmail and Outlook, reads incoming email, drafts replies grounded in your docs, website, and past email, and escalates when unsure. Approval-first is the default; auto-send is opt-in per workflow. Plain-English rules handle triage, labels, and routing across multiple inboxes, and integrations include Slack, Zendesk, Shopify, Pipedrive, Notion, and custom APIs. Pricing is flat by AI draft volume with unlimited seats on paid plans, from a free tier of 25 drafts a month to Standard at $149 per month for 1,500 drafts and unlimited inboxes ([pricing](/pricing)).
The sweet spot is operational email: RFQs and quotes, order status, returns, document collection, bookings, routine support. The repetitive 70% of an operational inbox is where grounding plus workflow pays for itself fastest.
And here is the honest boundary. InboxPilot is not the right buy if:
- **You want a chat widget or a ticketing system.** We are an email layer, not a support suite. Fin and Zendesk live in that world; we integrate with the latter rather than replace it.
- **Your pain is a personal executive inbox.** Triage-and-summarize tools for individuals are a different category, and a general assistant add-on may serve you fine there.
- **Your email volume is low or mostly one-off.** Novel, high-context conversations need a human with, at most, a chatbot assist. Twenty distinct emails a week is not an automation problem.
- **Phone or chat is your primary channel.** We do not touch either.
General assistants keep their territory too, and it is large: research, analysis, writing that is not email, and the occasional genuinely hard message where you want a thinking partner rather than an automation. The mistake is not owning a chatbot. It is asking it to run an inbox.
## Related reading
- [AI email assistant buyers guide 2026](/blog/ai-email-assistant-buyers-guide-2026): the full evaluation checklist for this category.
- [Microsoft Copilot for email, and its alternatives](/blog/alternative-microsoft-copilot-email): the in-inbox assistant compared against agents.
- [Gemini for Gmail alternatives](/blog/alternative-gemini-for-gmail): same comparison on the Google side.
- [AI email tools and data privacy](/blog/ai-email-tools-data-privacy-guide): what to demand before any AI reads your mail.
- [Email admin burden statistics 2026](/blog/admin-burden-email-statistics-2026): the numbers on what the inbox costs before automation.
- [RFQ and quote request automation](/use-cases/rfq-email-automation): how quote requests get read, priced, and answered from your own catalog.
If drafting one email faster were the problem, the chatbot already solved it. If the problem is an inbox full of repetitive external email that has to be answered accurately, every day, by somebody, that is the job purpose-built agents exist for, and the one [InboxPilot](/) was built to do.
---
*The Microsoft Work Trend Index figure is from 2025 and cited with its source above. Claims about general assistant data practices are stated conditionally because they vary by vendor, plan, and settings; check your vendor's current terms. InboxPilot pricing was verified against the pricing page in July 2026. InboxPilot is the publisher of this article.*
---
## AI Email for Law Firms: Intake and Updates Without Risk
Source: https://www.inboxpilot.co/blog/ai-for-law-firms
Published: 2025-10-21
What law firms can safely automate in the inbox: intake, status questions, document requests, with an attorney approving anything close to advice.
A prospective client emails your firm at 9:40 on a Tuesday night. Custody question, short paragraph of facts, wants to know if you can help and what a consultation costs. By the time anyone opens it on Thursday, she has already retained the firm that answered Wednesday morning.
Small firms rarely lose that client on the lawyering. They lose her in the gap between an email arriving and a person getting to it, because the people who could answer are in depositions, in court, or billing hours.
**Disclosure:** we make [InboxPilot](/), an AI email agent that drafts replies to intake and client emails inside Gmail and Outlook. This post lays out what a law firm can safely automate, and it is blunt about the line: nothing that could be read as legal advice should leave the building without an attorney approving it.
## TL;DR
- Intake is a speed race. A 2011 Harvard Business Review audit found the average company took 42 hours to answer an inbound lead and 23% never replied. See [why intake email decides which firm gets hired](#why-intake-email-decides-which-firm-gets-hired).
- Most of a firm's inbox is [five email types](#the-five-email-types-in-a-law-firm-inbox), and only some of them are safe to automate.
- The safe pattern is draft-and-approve: the AI writes, a person sends, and [advice never goes out unsupervised](#what-ai-can-draft-and-what-it-must-never-send).
- **[InboxPilot](#setting-up-intake-automation-without-an-ethics-problem), which is us,** drafts intake and client replies from the firm's own documents, with negative keywords pulling settlement and dispute threads out of automation entirely.
- It is not practice management software and it will not draft pleadings. See [where it does not fit](#where-inboxpilot-does-not-fit).
## Why intake email decides which firm gets hired
The classic data on response speed is old, so we will date it honestly. In March 2011, Harvard Business Review published an audit of 2,241 US companies that found the average first response to an inbound lead took 42 hours, 23% of companies never responded at all, and firms replying within an hour were roughly seven times more likely to qualify the lead ([HBR](https://hbr.org/2011/03/the-short-life-of-online-sales-leads), 2011). That study measured web leads, not legal intake, so treat it as directional. The direction is not controversial: a person emailing three firms tends to hire the one that answers.
The volume side has not improved. In 2025, Microsoft's Work Trend Index measured the average worker receiving 117 emails a day and getting interrupted every two minutes during core hours ([Microsoft WorkLab, Breaking Down the Infinite Workday](https://www.microsoft.com/en-us/worklab/work-trend-index/breaking-down-infinite-workday), 2025). That is all industries, not just legal. The legal-specific twist is that the people receiving those emails bill by the hour, so every minute spent re-typing the consultation fee is a minute the firm pays for twice.
## The five email types in a law firm inbox
Ask whoever triages your intake address what is in it and you will get some version of the same five piles:
| Email type | What it looks like | Automation fit |
|---|---|---|
| **New client intake** | "Can you take my case?" with a paragraph of facts | Safe to acknowledge, confirm practice area fit, and request the intake form. Case merits stay with an attorney |
| **Status questions** | "Any update on my filing?" | Safe to draft an acknowledgment and next-step timing; anything substantive routes to the responsible attorney |
| **Billing and fee questions** | "What do you charge for an uncontested divorce?" | Safe when the answer comes from your published fee schedule, not from the AI's imagination |
| **Document requests** | IDs, signed engagement letters, records, retainers | Fetch-and-remind work: low risk, high volume, constant interruptions |
| **Scheduling and follow-ups** | Consult bookings, reschedules, "did you get my documents?" | Safe with simple rules and calendar links |
Notice what is not on the list: settlement discussions, correspondence with opposing counsel, subpoenas, anything in active litigation. Those should never touch automation, and a good setup enforces that with rules rather than good intentions.
## What AI can draft, and what it must never send
The useful question is not whether AI can write a lawyerly email. It can. The question is which emails it should be allowed to draft, and what stands between a draft and a send.
**Classify what arrived.** The AI reads each incoming email and tags it: new intake, status question, billing, document request, or none of the above. Triage is the step that currently requires a person to open everything, and it is why a Tuesday-night inquiry sits unread until Thursday.
**Draft from the firm's own documents.** Grounded drafting means the AI writes only from sources you gave it: practice area descriptions, your consultation process and fee, the intake form, FAQ answers, and reply templates that already carry your "this is not legal advice" disclaimer language. When the answer is not in those sources, it escalates instead of guessing. A generic chatbot that improvises about statutes of limitation is a malpractice exposure, not a productivity tool.
**Route the rest to a human with no draft attached.** Negative keywords do the protective work: anything mentioning a settlement, subpoena, opposing counsel, malpractice, or a bar complaint skips automation entirely and lands in front of an attorney.
In [the construction version of this playbook](/blog/construction-rfq-email-automation) we wrote that no AI should send final pricing unsupervised. The legal version is stricter: no AI should send anything that could be read as legal advice, full stop. The automation-friendly zone is the administrative shell around the legal work, not the legal work itself.
## The workflow from inquiry to approved reply
1. **An inquiry lands** at intake@ at 9:40pm.
2. **The AI classifies it** as new intake, family law, and flags the names for a conflict check.
3. **It checks your documents**: practice areas, consultation process and fee, intake form.
4. **It drafts an acknowledgment** that thanks her, confirms the firm handles custody matters, explains the consultation process and fee, and links the intake form. It does not comment on the facts of her case.
5. **A paralegal approves** at 8am, edits one line, and sends. Your reply arrives before competing firms have opened their inbox.
The draft never assessed her chances, never quoted anything beyond the published consultation fee, and never skipped the disclaimer. Every sentence traces to a document the firm wrote.
## Setting up intake automation without an ethics problem
Three steps, and the guardrails matter more than the features:
1. **Connect the inbox.** Whatever address inquiries hit: intake@, info@, or an attorney's own mailbox. Gmail or Outlook, shared mailboxes included.
2. **Feed it your documents.** Practice area pages, fee schedule, FAQ, intake form, and the reply templates you already trust, disclaimers and all. The drafts are only as good as what you give them.
3. **Set the guardrails.** Trigger keywords like *consultation*, *intake*, and *appointment* route into drafting. Negative keywords like *settlement*, *subpoena*, *opposing counsel*, and *bar complaint* route straight to an attorney, no draft. Leave draft-and-approve on. The AI writes, a person sends.
On confidentiality: InboxPilot is SOC 2 Type II audited, GDPR compliant, and customer data never trains AI models. That covers the vendor half of the equation. The other half is yours: most bars now expect technology competence, so read your jurisdiction's guidance before connecting anything client-facing. Our [data privacy guide for AI email tools](/blog/ai-email-tools-data-privacy-guide) lists the questions worth asking any vendor.
Pricing is flat, by draft volume, with unlimited seats on paid plans: Free covers 25 AI drafts a month to test on real intake traffic, Hobby is $29 per month for 200 drafts, and Standard at $149 per month covers 1,500 drafts, unlimited inboxes, and the knowledge grounding doing the heavy lifting in step 2. No per-attorney fees. Details on the [pricing page](/pricing).
**[See how InboxPilot automates document collection for client intake →](/use-cases/document-collection-automation)**
## Where InboxPilot does not fit
Honest non-fits, so you do not buy the wrong thing:
- **It is not practice management.** It will not replace Clio or MyCase; it works in the email layer alongside whatever runs your matters.
- **It will not draft pleadings, contracts, or legal analysis.** Wrong tool, wrong risk profile.
- **No live chat, phone, or e-signature.** If those are the gaps, look at dedicated tools.
- **Not for a partner's personal inbox.** It automates repetitive operational email, not executive correspondence.
If the lawyering is fine but intake replies go out days late, the inbox is the piece to fix. Connect a mailbox, load your fee schedule and FAQ, and judge the drafts on a week of real inquiries.
## Related reading
- [Document collection automation](/use-cases/document-collection-automation): the intake checklist, acknowledgment, and reminder workflow in full.
- [The data privacy guide for AI email tools](/blog/ai-email-tools-data-privacy-guide): what to verify before any AI touches client email.
- [Email automation for accounting firms](/blog/accounting-firm-email-automation): the same playbook for the other document-heavy profession.
- [Best shared inbox software for Gmail and Outlook](/blog/best-shared-inbox-software): where intake@ actually lives.
- [How to generate emails from your own documents](/blog/how-to-generate-emails-using-your-documents): the grounding step, explained.
---
*Statistics are attributed to their original source with the year stated: the HBR response-time audit is from 2011 and the Microsoft Work Trend Index figures are from 2025. Neither is legal-industry-specific and both are labeled as directional above. InboxPilot pricing was verified against the pricing page in July 2026. InboxPilot is the publisher of this article.*
---
## How to Automate Your Gmail Inbox: 7 Setups That Work
Source: https://www.inboxpilot.co/blog/automate-your-gmail
Published: 2025-10-19
SuperOffice found 62% of businesses never answer customer email. Here are seven Gmail automations, from filters and labels to AI drafts, in order.
Some emails need you. Most do not. The pricing question you have answered forty times, the "did you get my invoice" nudge, the status check that takes three minutes of lookup and thirty seconds of typing. If you run a business inbox in Gmail, a real share of your week goes to messages whose answers already exist somewhere.
Automating that inbox is not one magic switch. It is a short ladder: it starts with the filters and templates Gmail already includes free, and it ends with AI that reads the question and drafts the answer for you. This guide climbs the ladder in seven setups, in the order worth doing them.
**Disclosure:** we make [InboxPilot](/integrations/gmail), an inbox-native AI email agent that drafts replies inside Gmail using your own docs and policies. The first steps below are native Gmail features that cost nothing, and if your inbox is mostly one-off personal mail, those native features are genuinely all you need.
## TL;DR
- **Most businesses answer slower than they think.** SuperOffice found 62% never respond to customer email at all. See [the response-time data](#most-businesses-answer-email-slower-than-they-think).
- **Gmail covers the basics free.** Filters, labels, and saved templates handle predictable mail. See [what Gmail gives you](#start-with-what-gmail-gives-you).
- **Seven setups, in order.** Start with filters, end with AI drafts grounded in your own documents. See [the seven automations](#seven-automations-from-filters-to-ai-drafts).
- **Native rules cannot read.** Filters match keywords, not meaning, and a template cannot answer a question it has never seen. See [the limits](#the-limits-of-native-gmail-automation).
- **[InboxPilot](#where-inboxpilot-fits)**, which is us, adds the understanding layer: it reads incoming mail, drafts replies from your knowledge base, and waits for your approval by default. See [where it fits](#where-inboxpilot-fits).
## Most businesses answer email slower than they think
The case for automating is not comfort, it is speed. SuperOffice studied company response times and found that [62% of businesses never respond to customer emails at all](https://www.superoffice.com/blog/response-times/), with an average response time of over 12 hours, while nearly half of customers expect a reply within four hours.
That gap is rarely about effort. Teams answer the mail they see when they see it. The problem is that repetitive messages bury the important ones, and every reply that requires a lookup, a search through old threads, or a policy check adds minutes that compound across the day. Automation attacks both ends: sorting decides what you see first, and drafting removes the retype.
## Start with what Gmail gives you
Before adding any tool, use the free layer. Gmail filters can automatically label, archive, star, or forward messages that match a sender, subject, or keyword. Labels give you a visual queue: a "needs reply" label you clear daily beats a thousand-message inbox. Gmail templates (enable them under Settings, Advanced) let you save a reply once and insert it in a few clicks, and the setup takes about five minutes.
Gmail also has a vacation responder, though it only works in whole-day units. If you want an auto-reply that switches on after business hours, that takes a workaround, which we cover in [how to set up an automated response in Gmail](/blog/how-to-setup-an-automated-response-on-your-gmail-account).
These features are rule-based. They act on what a message literally contains, not on what it means. That distinction decides where each of the seven setups below belongs.
## Seven automations, from filters to AI drafts
### 1. Filter and label incoming mail
Build filters for your highest-volume senders and topics: receipts and notifications skip the inbox and get an archive label, known customers get a "customer" label, anything with "invoice" in the subject gets flagged. Ten minutes of filter setup permanently removes the mail you never needed to see.
### 2. Save templates for your most repeated replies
Write down the five replies you send most often and save each as a Gmail template. Even without AI, inserting a saved reply and editing two lines beats composing from scratch. This is also useful groundwork: those five replies are exactly what you will later teach an AI agent to draft.
### 3. Let AI triage and prioritize
This is where a tool like InboxPilot enters. Instead of keyword rules, the agent reads each incoming message and classifies it by what it actually is: urgent, customer inquiry, vendor question, noise. You describe the categories in plain English, and the [smart triage](/product/smart-triage) applies labels and priorities so the messages that need a human land on top.
### 4. Auto-draft replies, with guardrails
Configure how the agent responds per inbox: the tone you want, trigger topics it should handle (pricing, hours, order status), and negative keywords that must always route to a person (complaints, legal, anything angry). When a covered question arrives, a drafted reply is waiting in Gmail for you to review and send. Nothing goes out without you until you decide otherwise.
### 5. Route and forward with workflow rules
Some mail should not be answered, it should be moved. [Email workflows](/product/email-workflows) written in plain English can forward invoices to accounting, route sales questions to the right teammate, and file the rest. If your team runs a helpdesk, a [Zendesk connection](/integrations/zendesk) lets complex cases become tickets while routine ones are answered in the inbox.
### 6. Ground the drafts in your own knowledge
An AI reply is only useful if it is correct. Upload your FAQs, policies, and product docs to the [knowledge base](/product/knowledge-base), or point it at your website. Drafts then cite your actual refund window and your actual pricing rather than a plausible guess. We cover this step in depth in [how to generate emails using your documents](/blog/how-to-generate-emails-using-your-documents).
### 7. Review, then automate the safe slice
Run in draft mode for a week or two and watch what the agent produces. Where drafts are consistently right, turn on auto-send for that workflow and nothing else. Where they are thin, add a doc or an FAQ pair. The end state is not full autopilot. It is a fast draft on everything and automatic handling of the narrow slice you have verified.
## The limits of native Gmail automation
Worth being plain about what the free layer cannot do, because this is where most people stall:
- **Filters match text, not meaning.** A filter on the word "refund" catches "please refund me" and also "no refund needed, just checking in." It cannot tell an angry escalation from a routine question.
- **Templates cannot answer.** A saved reply covers the question it was written for. The moment a customer asks a variant, someone has to read, think, and edit.
- **Nothing drafts for you.** Native Gmail can sort, file, and forward, but every reply still starts with a human composing or pasting.
- **No shared logic across a team.** Filters and templates live per Google account, so three teammates end up with three diverging systems.
If your repetitive mail is low-volume and truly identical, these limits may never bite. They bite when volume grows or when the questions require answers from your own data.
## Where InboxPilot fits
InboxPilot is the understanding layer on top of Gmail: an [inbox-native AI email agent](/integrations/gmail) that reads incoming mail, drafts replies grounded in your docs, website, and past email, and escalates when it is unsure. Every draft waits for human approval by default, and auto-send is opt-in per workflow. Pricing is flat by draft volume with unlimited seats on paid plans: Free covers 25 drafts a month, Hobby is $29/month for 200, Standard is $149/month for 1,500 with unlimited inboxes, and Pro is $499/month for 12,000.
To be honest about fit: InboxPilot is built for repetitive operational email, things like quotes, order status, and routine support in a business inbox. It is not a chat widget, not a ticket queue, and not a personal productivity coach for an executive inbox. If your Gmail problem is ten personal emails a day, the native filters and templates above will serve you fine.
## Related reading
- [How to generate emails using your documents](/blog/how-to-generate-emails-using-your-documents)
- [How to train Gmail on your own data](/blog/how-to-train-gmail-on-your-own-data)
- [How to set up an automated response in Gmail](/blog/how-to-setup-an-automated-response-on-your-gmail-account)
- [Booking request automation](/use-cases/booking-request-automation): turning booking and appointment enquiries into confirmed slots.
Start with the filters this afternoon, and if the drafting layer is the piece you are missing, [try InboxPilot free](https://www.inboxpilot.co/) with 25 AI drafts a month and see what it writes against your real mail.
---
## InboxPilot vs Help Scout: AI Agent or Shared Inbox? (2026)
Source: https://www.inboxpilot.co/blog/helpscout-vs-inboxpilot
Published: 2025-10-19
Help Scout organizes email for humans to answer. InboxPilot drafts and sends the answers. Compare pricing models, AI depth, and which one your team needs.
The Help Scout question usually shows up at a specific moment: the support address has outgrown one person, two people keep answering the same customer, and somebody says "we need a real tool for this." Help Scout is a good answer to that problem. It has been the default upgrade from a messy Gmail account for over a decade.
But before you sign up, it is worth noticing what Help Scout does not change. After the migration, after the tags and assignments and saved replies, a human still reads every email and writes every response. The queue is tidier. The work is the same.
That is the actual comparison here. Help Scout organizes email so people can answer it faster. InboxPilot answers it.
**Disclosure:** we make [InboxPilot](/solutions/support-teams), so read our framing with that in mind. We have tried to be specific about where Help Scout genuinely wins, and it does win for some teams: if you need live chat, a customer knowledge base, or a full ticket queue, InboxPilot is not that product and we say so below.
## TL;DR
- **These are different categories.** Help Scout is a shared inbox platform where humans write replies. **[InboxPilot](#where-inboxpilot-is-different-which-is-us)** is an inbox-native AI email agent that drafts and can auto-send them. See [the comparison table](#inboxpilot-vs-help-scout-at-a-glance).
- **Help Scout wins on collaboration surface**: chat widget, knowledge base, assignment, collision detection, reporting. See [where Help Scout fits](#where-help-scout-fits).
- **InboxPilot wins on the writing itself**: replies grounded in your docs and past email, approval by default, auto-send opt-in, no migration off Gmail or Outlook.
- **Pricing models differ more than prices.** Help Scout charges per user from $20 per user per month. InboxPilot is flat by draft volume with unlimited seats. See [the pricing math](#pricing-per-seat-or-flat-usage).
- **The honest split:** collaboration problem, pick Help Scout. Repetitive-answer problem, pick InboxPilot. See [which fits you](#choose-help-scout-when-choose-inboxpilot-when).
## InboxPilot vs Help Scout at a glance
| | InboxPilot | Help Scout |
|---|---|---|
| **Category** | Inbox-native AI email agent | Shared inbox and support platform |
| **Where you work** | Inside Gmail or Outlook, no migration | Help Scout's own interface |
| **Who writes replies** | AI drafts, grounded in your docs and past email; humans approve or auto-send per workflow | Humans, helped by saved replies and workflows |
| **Chat widget** | No | Yes |
| **Knowledge base** | Used internally to ground drafts | Customer-facing help center (Docs) |
| **Ticket queues and assignment** | Lighter: triage, labels, routing rules | Full assignment, collision detection, reporting |
| **Pricing model** | Flat by AI draft volume, unlimited seats on paid plans | Per user, from $20 per user per month |
| **Main tradeoff** | Email only, no chat or ticket queue | You still write every reply yourself |
## What are you actually buying
"Email tool for our support inbox" hides two different purchases, and mixing them up is how teams end up paying for the wrong one.
**A collaboration purchase** fixes coordination: two people answering the same customer, requests falling through cracks, no visibility into who handles what. The output is an organized queue. Help Scout, [Hiver](/blog/hiver-inboxpilot), [Missive](/blog/missive-inboxpilot), and the rest of the [shared inbox category](/blog/best-shared-inbox-software) are collaboration purchases.
**An automation purchase** fixes the writing: the same twenty questions arriving every week, each one costing a human five minutes to answer from memory or a doc nobody updated. The output is a drafted, grounded reply. That is the category InboxPilot is in.
The reason the distinction matters is response time. SuperOffice's study of company response times found that [62% of businesses never respond to customer emails at all](https://www.superoffice.com/blog/response-times/), with an average response time of over 12 hours for those that do. A tidier queue helps with that. A tool that has the reply drafted before anyone opens the thread helps more.
## Where Help Scout fits
Help Scout is one of the most mature products in the shared inbox category, and its strengths are real.
The shared inbox itself is polished: conversations get assigned to owners, collision detection stops two agents replying to the same customer, private notes keep discussion out of the customer's thread, and tagging plus workflows handle rules-based routing. Docs, its knowledge base product, gives you a customer-facing help center that can deflect questions before they become email. Reporting shows managers response times and volumes per agent. It also connects to a wide app ecosystem, including Slack and HubSpot.
Help Scout has added AI-assist features over the years, but the product's center of gravity has not moved: it is built around a queue of conversations that people work through. The automation shapes the queue. Humans produce the answers.
Two things follow from that design. First, the price scales with people, because the product's unit of value is an agent seat. Second, you move your support out of Gmail or Outlook and into Help Scout's interface, which is a genuine migration: forwarding rules, retraining, new habits.
Compared to the anchor problem, that is the gap. If your inbox pain is "we answer the same questions all day," Help Scout makes that work more organized without making it smaller.
## Where InboxPilot is different (which is us)
InboxPilot starts from the opposite assumption: the inbox you have is fine, the repetitive writing is the problem.
It connects to your existing Gmail or Outlook account, including shared inboxes, and reads incoming mail. For questions it recognizes, it drafts a reply grounded in your own material: help docs, website, policies, and how your team has answered similar emails before. Drafts wait for human approval by default. Once you trust a specific workflow, say order status or pricing questions, you can let those auto-send and keep everything else on review. When it is not confident, it escalates to a person instead of guessing.
Routing and triage are written in plain English rather than a rules builder: "label invoice emails and forward them to accounting," "flag anything mentioning a cancellation for me." It works across multiple inboxes, and it integrates with Slack, [Zendesk](/blog/inboxpilot-and-zendesk-integration), Shopify, Pipedrive, and Notion. On security, it is SOC 2 Type II certified and GDPR compliant, and customer data never trains AI models.
**The honest tradeoffs.** InboxPilot is email only: no chat widget, no phone, no customer-facing help center. Its assignment and collision features are lighter than Help Scout's, because it assumes AI drafting removes most of the coordination load rather than managing it. If you run a large support team that lives in ticket queues, Help Scout's operational tooling is deeper. And InboxPilot is a newer product than Help Scout, with a shorter track record.
## Pricing per seat or flat usage
We are only quoting prices already published by each vendor.
**Help Scout** charges per user: Standard at $20 per user per month, Plus at $40, Pro at $65. Straightforward, and cheap for two people. The number to watch is growth: every hire who touches the inbox adds a seat, so an eight-person team on Plus is $320 a month before anyone sends a better reply.
**InboxPilot** charges a flat rate by AI draft volume, with unlimited seats on paid plans: Free (25 drafts a month), Hobby at $29 per month (200 drafts), Standard at $149 per month (1,500 drafts, unlimited inboxes), Pro at $499 per month (12,000 drafts), Enterprise custom. Never per seat, never per resolution. ([Pricing](/pricing))
The models reward different shapes of team. Per-seat favors small headcount with high manual effort. Flat usage favors teams where many people touch email but the volume of repetitive questions is the real cost.
## Choose Help Scout when, choose InboxPilot when
**Choose Help Scout when:**
- You need live chat or a customer-facing knowledge base alongside email.
- Your bottleneck is coordination: assignment, collision detection, agent reporting.
- Your questions are mostly novel, so a human writing each reply is the right default.
- You want a mature platform with a long track record and a big integration ecosystem.
**Choose InboxPilot when:**
- Most of your inbox is repetitive: order status, pricing, policies, how-to questions.
- You want replies drafted from your own docs and past email, not typed from scratch.
- You do not want to migrate the team off Gmail or Outlook.
- Per-seat pricing punishes you because lots of people touch the inbox.
- You want the option to auto-send the routine 80% while a human keeps the rest.
Plenty of teams are honestly in the middle. A useful test: open your last 50 support emails and count how many a well-grounded draft could have answered. Under a third, Help Scout's collaboration tooling is probably the better spend. Over half, you have an automation problem wearing a collaboration costume.
## Related reading
- [Best shared inbox software for Gmail and Outlook](/blog/best-shared-inbox-software): the wider category Help Scout sits in.
- [InboxPilot vs Hiver](/blog/hiver-inboxpilot): the same comparison against a Gmail-native shared inbox.
- [InboxPilot vs Missive](/blog/missive-inboxpilot): against a team email client with omnichannel support.
- [AI email assistant for teams](/blog/ai-email-assistant-for-teams): what inbox-native AI looks like day to day.
- [AI support for support teams](/solutions/support-teams): how InboxPilot handles a support inbox end to end.
- [Order status email automation](/use-cases/order-status-email-automation): answering WISMO and shipping questions from your system of record.
Help Scout will make your queue calmer, and for some teams that is exactly the fix. But if the real cost is the hours spent typing answers that already exist in your docs, drafting is the piece you are missing, and you can [try InboxPilot free](https://www.inboxpilot.co/) on 25 drafts without moving off the inbox you already run.
---
## InboxPilot vs Missive: Team Inbox or AI Agent? (2026)
Source: https://www.inboxpilot.co/blog/missive-inboxpilot
Published: 2025-09-07
Missive puts email, chat, and SMS in one team app, but people still write every reply. InboxPilot drafts them in Gmail or Outlook. Compare both honestly.
Missive is the tool people recommend in forum threads about team email, and usually with real enthusiasm. One app holds your shared email, team chat, SMS, and social messages, and your teammates discuss a thread right next to the thread itself. For a small team that lives in conversations, the design is genuinely good.
Here is the question worth asking before you move in: after the move, who writes the replies? In Missive, the answer is the same as it was in Gmail. A person opens each conversation, reads it, and types the response, including the twentieth "what is your pricing" of the week. Missive makes coordinating that work pleasant. It does not make the work go away.
InboxPilot starts at the other end. It stays inside your existing Gmail or Outlook and drafts the replies, grounded in your own docs and past email, before anyone opens the thread. Which approach wins depends on which problem you actually have, so that is how this comparison is organized.
**Disclosure:** we make [InboxPilot](/solutions/support-teams), so read our framing accordingly. Missive has honest wins in this matchup, and we call them out: if your support spans SMS, chat, and social channels, or your team wants one workspace for talking and working, Missive does things InboxPilot deliberately does not.
## TL;DR
- **Different bets.** Missive bets the fix is a better workspace for humans. **[InboxPilot](#where-inboxpilot-is-different-which-is-us)** bets the fix is not writing most replies by hand. See [the table](#inboxpilot-vs-missive-at-a-glance).
- **Missive wins on channels and collaboration**: email, SMS, and social in one app, with team chat and task assignments beside every thread. See [where Missive fits](#where-missive-fits).
- **InboxPilot wins on the writing**: grounded drafts in Gmail or Outlook, approval by default, opt-in auto-send, no new interface to learn.
- **Watch the entry price.** Missive starts at $14 per user per month, but that tier has no AI and no integrations; the practical plan is Productive at $24. InboxPilot is flat by draft volume with unlimited seats. See [the math](#pricing-per-user-or-flat-usage).
- **The short version:** multichannel coordination problem, Missive. Repetitive-email problem, InboxPilot. See [which fits](#choose-missive-when-choose-inboxpilot-when).
## InboxPilot vs Missive at a glance
| | InboxPilot | Missive |
|---|---|---|
| **Category** | Inbox-native AI email agent | Team inbox and chat app |
| **Where you work** | Inside Gmail or Outlook, no new interface | Missive's own app |
| **Channels** | Email only | Email, SMS, WhatsApp, and social in one inbox |
| **Who writes replies** | AI drafts grounded in your docs and past email; approve or auto-send per workflow | Humans, helped by rules and templates |
| **AI drafting** | Included on every plan, including Free | Not on Starter; higher plans, with separate credits and setup |
| **Pricing model** | Flat by AI draft volume, unlimited seats on paid plans | Per user, from $14 per user per month |
| **Main tradeoff** | Email only, lighter on assignment and team chat | People still write every reply |
## Two different bets on the same inbox
Strip the feature lists away and each product is a wager about where your team's time actually goes.
**Missive bets on coordination.** The waste it targets is switching and confusion: support in one tab, texts in another, team discussion in Slack, and nobody sure who took the thread. Pull every channel and every conversation into one app, let the team talk beside the work, and the friction drops. If your days are lost to handoffs and "did anyone reply to this?", that bet pays off.
**InboxPilot bets on composition.** The waste it targets is the writing itself: most operational inboxes are dominated by questions the company has answered many times, and every one still costs a person minutes to answer from memory or a doc nobody updated. Draft those replies automatically, grounded in your own material, and the queue shrinks instead of just getting tidier.
Both bets are defensible. But they are different, and buying the wrong one is expensive in a quiet way: a team drowning in repetitive email that adopts Missive gets a beautifully organized version of the same workload.
## Where Missive fits
Missive is one of the strongest products in the team inbox space, and its strengths compound for small, chatty teams.
The core design puts collaboration inside the conversation: teammates comment on a thread in a side channel the customer never sees, assign it as a task, and hand it off without forwarding anything. The omnichannel inbox is the other pillar: email, SMS, WhatsApp, and social messages land in one place, so a customer who emails today and texts tomorrow stays one conversation. The rules engine is unusually deep, supporting up to 1,000 rules on its Productive tier and above, and the app is provider-agnostic, sitting on top of Gmail, Outlook, or plain IMAP accounts.
The tradeoffs are the mirror image. Missive is a new workspace: your team stops living in Gmail or Outlook and starts living in Missive, which is a real habit change even without a data migration. AI is not part of the entry experience: the $14 Starter tier includes no AI and no integrations, and the AI that exists on higher tiers runs on separately purchased credits and its own setup rather than working out of the box. And the automation is routing automation. Rules move conversations around with real sophistication, but a person still writes what gets sent.
Against the anchor question: if your support genuinely spans channels and your team needs to talk while it works, Missive earns its recommendation. If your inbox is mostly repeat questions, Missive organizes the repetition without reducing it.
## Where InboxPilot is different (which is us)
InboxPilot is an inbox-native AI email agent. It connects to the Gmail or Outlook account you already run, including shared inboxes, and goes after the part Missive leaves alone: producing the reply.
It reads incoming email and drafts responses grounded in your company's own material: help docs, website, policies, and how your team answered similar threads before. Drafts wait for human approval by default. When a specific workflow proves reliable, order status updates, standard pricing answers, you can opt that workflow into auto-send while everything else stays on review. When the AI is unsure, it escalates to a person rather than improvising.
Triage and routing run on plain-English rules instead of a rules builder: "label invoice emails and forward them to accounting," "flag anything that mentions cancellation." It handles multiple inboxes and integrates with Slack, [Zendesk](/blog/inboxpilot-and-zendesk-integration), Shopify, Pipedrive, and Notion. On security, it is SOC 2 Type II certified and GDPR compliant, and customer data never trains AI models.
**The honest tradeoffs.** InboxPilot is email only: no SMS, no WhatsApp, no chat widget, no social inbox. Its assignment and collaboration features are lighter than Missive's, with no in-thread team chat, because it assumes drafting removes most of the coordination load rather than hosting it. Teams that need to discuss every conversation will feel that gap. It is also the younger product, with a shorter track record than Missive.
## Pricing per user or flat usage
Only published prices below.
**Missive** charges per user: Starter at $14, Productive at $24, and Business at $36 per user per month. The Starter tier excludes AI and integrations, so for automation purposes the realistic entry point is Productive. ([missiveapp.com/pricing](https://missiveapp.com/pricing))
**InboxPilot** charges a flat rate by AI draft volume, with unlimited seats on paid plans: Free (25 drafts a month), Hobby at $29 per month (200 drafts), Standard at $149 per month (1,500 drafts, unlimited inboxes), Pro at $499 per month (12,000 drafts), Enterprise custom. Never per seat, never per resolution. ([Pricing](/pricing))
Run the numbers for your own team, but the pattern is consistent: a five-person team on Missive Productive pays $120 a month before any AI credits, and grows by $24 with every hire who touches the inbox. The same team on InboxPilot pays $29 or $149 depending on volume, whether five people share the inbox or fifteen. Per-user pricing taxes headcount; usage pricing taxes email volume. Pick the smaller tax.
## Choose Missive when, choose InboxPilot when
**Choose Missive when:**
- Your support genuinely spans email, SMS, WhatsApp, or social, and you want one inbox for all of it.
- Your team needs to discuss threads constantly, and chat-beside-the-conversation is the workflow you want.
- Your email is mostly one-off conversations a human should write anyway.
- You want a deep rules engine and are happy configuring it.
**Choose InboxPilot when:**
- Your support is email, and a large share of it is repetitive questions with knowable answers.
- You want grounded drafts included from the first plan, not gated behind tiers, credits, and setup.
- You do not want your team to learn a new interface on top of Gmail or Outlook.
- Per-user pricing punishes you because many people touch the shared inbox.
- You want routine workflows to eventually auto-send while a human keeps the exceptions.
A practical tiebreak: open your last 50 inbound conversations and sort them into "needed a human" and "our docs already answer this." If the second pile is small, Missive's coordination is the better spend. If it is half the stack, you have a writing problem, and no amount of workspace design writes the replies.
## Related reading
- [Best shared inbox software for Gmail and Outlook](/blog/best-shared-inbox-software): the wider category Missive competes in.
- [InboxPilot vs Help Scout](/blog/helpscout-vs-inboxpilot): the same decision against a full support platform.
- [InboxPilot vs Hiver](/blog/hiver-inboxpilot): against a Gmail-native shared inbox layer.
- [InboxPilot vs Gmelius](/blog/gmelius-inboxpilot): against another Gmail collaboration tool.
- [AI email assistant for teams](/blog/ai-email-assistant-for-teams): what grounded drafting looks like in practice.
- [RFQ and quote request automation](/use-cases/rfq-email-automation): how quote requests get read, priced, and answered from your own catalog.
Missive is the right call when your team's conversations sprawl across channels and coordination is the real cost. If the real cost is typing the same answers every day, drafting is the piece you are missing, and you can [try InboxPilot free](https://www.inboxpilot.co/) on 25 drafts inside the inbox your team already uses.
---
## InboxPilot vs Hiver: Gmail Shared Inbox or AI Agent? (2026)
Source: https://www.inboxpilot.co/blog/hiver-inboxpilot
Published: 2025-09-06
Hiver turns Gmail into a shared inbox where humans answer everything. InboxPilot drafts the answers. Compare per-user vs flat pricing and where each wins.
Hiver's pitch has always been honest and specific: your team already lives in Gmail, so instead of moving support into a helpdesk, add the helpdesk features to Gmail. Assignments, shared labels, notes, analytics, all inside the interface everyone knows. For coordinating a team on support@, it works.
Here is the part the pitch skips. Once every email has an owner, the owner still has to write the reply. If your inbox is 60% repeated questions about hours, pricing, order status, and password resets, Hiver has organized that work beautifully and eliminated none of it.
InboxPilot attacks the other side: it reads the incoming email and drafts the answer, grounded in your own docs and past replies, inside the same Gmail inbox. This post lays out where each approach actually wins.
**Disclosure:** we make [InboxPilot](/solutions/support-teams), so we have a side. We have kept Hiver's real strengths in, including the places its collaboration tooling is deeper than ours, because if coordination is your bottleneck you should buy the coordination tool.
## TL;DR
- **Different layers of the problem.** Hiver organizes who answers each Gmail conversation. **[InboxPilot](#where-inboxpilot-is-different-which-is-us)** drafts the answers, in Gmail or Outlook. See [the table](#inboxpilot-vs-hiver-at-a-glance).
- **Hiver wins on team mechanics**: assignment, collision detection, round-robin, per-agent analytics, all native to Gmail. See [where Hiver fits](#where-hiver-fits).
- **Hiver is Gmail-first.** Outlook needs its separate Omni product. InboxPilot runs natively in both.
- **Pricing models diverge fast.** Hiver is per user from $25 per user per month on annual billing. InboxPilot is flat by draft volume, unlimited seats. See [the math](#pricing-per-user-or-flat-usage).
- **The honest split:** coordination problem, Hiver. Repetitive-writing problem, InboxPilot. See [which fits](#choose-hiver-when-choose-inboxpilot-when).
## InboxPilot vs Hiver at a glance
| | InboxPilot | Hiver |
|---|---|---|
| **Category** | Inbox-native AI email agent | Gmail-native shared inbox |
| **Email platforms** | Gmail and Outlook, including shared inboxes | Gmail; Outlook via separate Omni product |
| **Who writes replies** | AI drafts grounded in your docs and past email; approve or auto-send per workflow | Humans, with templates and rules to help |
| **Assignment and collision detection** | Lighter: plain-English routing and labels | Full workflow: assignment, collision detection, round-robin |
| **Analytics** | Draft and workflow level | Per-agent response times and SLAs |
| **Pricing model** | Flat by AI draft volume, unlimited seats on paid plans | Per user, free tier then $25 per user per month annual |
| **Main tradeoff** | Email only, lighter team-management features | Humans still write every reply |
## Two different fixes for the same inbox
When a shared inbox hurts, it hurts in one of two ways, and they need different tools.
**The coordination failure:** two people answer the same customer, or nobody does because everyone assumed someone else had it. Ownership is unclear, managers have no visibility. Hiver was built for exactly this, and so was the broader [shared inbox category](/blog/best-shared-inbox-for-gmail).
**The volume failure:** ownership is perfectly clear and the owner is drowning, because 30 of today's 50 emails are questions the company has answered a thousand times. No amount of assignment fixes this. Someone still types the same paragraph about your return policy for the third time before lunch.
Most articles treat these as one problem. They are not, and the numbers on the second one are grim: SuperOffice's response-time research found [62% of businesses never respond to customer emails at all](https://www.superoffice.com/blog/response-times/), with an average of over 12 hours for those that do. Teams do not skip replies because nobody was assigned. They skip them because writing every reply by hand does not scale.
## Where Hiver fits
Hiver is one of the strongest products in the Gmail-native shared inbox space, and its focus is a feature, not a limitation.
Everything happens inside Gmail: shared inboxes like support@ or billing@ become collaborative spaces with owners, statuses, and internal notes. Collision detection stops duplicate replies. Round-robin assignment spreads incoming email across the team automatically, which maps well to support rotations and quoting desks. Analytics show response times and workloads per agent, and SLAs put numbers on promises. There is a free tier, so a small team can start without a purchase decision.
The tradeoffs are the mirror image. Hiver is Gmail-first: Outlook requires its separate Omni product, which matters because plenty of companies run Microsoft 365. Reviewers also report performance lag at higher volumes. And the automation is workflow automation, routing and tagging and templates, not answer automation. A person writes each reply, so cost and effort both scale with headcount, which is exactly what the per-user pricing reflects.
Against the anchor problem: if your pain is coordination, Hiver solves it well. If your pain is repetitive writing, Hiver organizes the pain.
## Where InboxPilot is different (which is us)
InboxPilot is an inbox-native AI email agent. It connects to the Gmail or Outlook account you already run, including shared inboxes, and does the part Hiver leaves to humans: producing the reply.
It reads incoming email and drafts responses grounded in your company's own material, help docs, website, policies, and how your team answered similar threads before. Every draft waits for human approval by default. When a workflow proves itself, routine order-status updates, standard pricing questions, you can opt that specific workflow into auto-send while everything else stays on review. When the AI is not confident, it escalates to a person rather than improvising.
Triage and routing are plain English: "label anything about refunds and route it to Sara," "flag emails from our top accounts." It handles multiple inboxes, integrates with Slack, [Zendesk](/blog/inboxpilot-and-zendesk-integration), Shopify, Pipedrive, and Notion, and on the security side is SOC 2 Type II certified and GDPR compliant, with customer data never used to train AI models.
**The honest tradeoffs.** InboxPilot is email only: no chat widget, no ticket queues, no phone. Its assignment features are lighter than Hiver's, with no collision detection or per-agent SLA dashboards, because it assumes drafting removes most of the coordination load rather than managing it. Large teams that live in queue metrics will find Hiver's operational reporting deeper. It is also a younger product than Hiver.
## Pricing per user or flat usage
Only published prices below.
**Hiver** has a free tier, then charges per user: Growth at $25 per user per month on annual billing, Pro at $55, Elite at $85. ([hiverhq.com/pricing](https://hiverhq.com/pricing))
**InboxPilot** charges flat by AI draft volume, with unlimited seats on paid plans: Free (25 drafts a month), Hobby at $29 per month (200 drafts), Standard at $149 per month (1,500 drafts, unlimited inboxes), Pro at $499 per month (12,000 drafts), Enterprise custom. ([Pricing](/pricing))
Run your own numbers, but the shape is clear. A five-person team on Hiver Growth is $125 a month, and the tenth hire makes it $250. The same team on InboxPilot pays $29 or $149 depending on volume, whether three people or thirty touch the inbox. Per-user pricing taxes headcount; usage pricing taxes email volume. Pick the tax that is smaller for you.
## Choose Hiver when, choose InboxPilot when
**Choose Hiver when:**
- Your team is all-in on Gmail and the pain is coordination, not composition.
- You need round-robin assignment, collision detection, and per-agent analytics.
- Your email is mostly one-off conversations a human should write anyway.
- You want a free tier to trial team workflows before paying.
**Choose InboxPilot when:**
- A large share of your inbox is repetitive questions with knowable answers.
- You want drafts grounded in your docs and past email waiting when you open the thread.
- You run Outlook, or might, and want one tool across both platforms.
- Per-user pricing punishes you because many people touch the shared inbox.
- You want routine workflows to eventually auto-send while a human keeps the exceptions.
If you are torn, look at your actual inbox rather than feature lists. Count how many of the last 50 threads were questions your docs already answer. That number, more than anything in this post, tells you whether you need a coordinator or a drafter.
## Related reading
- [Best shared inbox for Gmail](/blog/best-shared-inbox-for-gmail): the category Hiver leads, compared honestly.
- [InboxPilot vs Help Scout](/blog/helpscout-vs-inboxpilot): the same decision against a full support platform.
- [InboxPilot vs Gmelius](/blog/gmelius-inboxpilot): against another Gmail-native collaboration tool.
- [AI email assistant for teams](/blog/ai-email-assistant-for-teams): what grounded drafting looks like in practice.
- [AI support for support teams](/solutions/support-teams): the InboxPilot workflow end to end.
- [RFQ and quote request automation](/use-cases/rfq-email-automation): how quote requests get read, priced, and answered from your own catalog.
Hiver earns its place if coordination is what is breaking. If the real cost is the same answers typed over and over, drafting is the missing piece, and you can [try InboxPilot free](https://www.inboxpilot.co/) on 25 drafts inside the Gmail account you already use.
---
## InboxPilot vs Gmelius: Shared Inbox or AI Agent? (2026)
Source: https://www.inboxpilot.co/blog/gmelius-inboxpilot
Published: 2025-09-05
Gmelius adds shared inboxes and Kanban boards to Gmail, but humans still write every reply. InboxPilot drafts them. Compare pricing models and fit.
Gmelius has one of the clearest pitches in the shared inbox market: your team already works in Gmail, so bring the collaboration into Gmail instead of moving everyone to a helpdesk. Shared inboxes, internal notes, assignments, Kanban boards, automation rules, all layered onto the interface your team opens every morning.
For teams whose problem is coordination, that pitch delivers. The support address stops being a black hole, every conversation gets an owner, and the board view shows exactly where each request stands.
Notice what stays the same, though. Once every email has a card and an owner, somebody still types the reply. If half your inbox is the same questions arriving on repeat, Gmelius gives that work better project management and makes none of it smaller. That gap is the real difference between these two tools.
**Disclosure:** we make [InboxPilot](/solutions/support-teams), so we are not neutral here. We have tried to be plain about where Gmelius genuinely wins, and it does win for some teams: if you want Kanban pipelines and team coordination inside Gmail, Gmelius is built for exactly that and InboxPilot is not.
## TL;DR
- **Different jobs.** Gmelius coordinates who handles each Gmail conversation. **[InboxPilot](#where-inboxpilot-is-different-which-is-us)** reads the email and drafts the reply, in Gmail or Outlook. See [the table](#inboxpilot-vs-gmelius-at-a-glance).
- **Gmelius wins on visual workflow**: shared inboxes, notes, assignments, Kanban boards, SLA tracking, all native to Gmail. See [where Gmelius fits](#where-gmelius-fits).
- **Gmelius is Gmail only.** No Outlook support, which decides this comparison for plenty of companies before features come up.
- **Pricing models diverge.** Gmelius is per user from $19 per user per month on annual billing. InboxPilot is flat by AI draft volume with unlimited seats. See [the math](#pricing-per-user-or-flat-usage).
- **The short version:** coordination problem, Gmelius. Repetitive-writing problem, InboxPilot. See [which fits](#choose-gmelius-when-choose-inboxpilot-when).
## InboxPilot vs Gmelius at a glance
| | InboxPilot | Gmelius |
|---|---|---|
| **Category** | Inbox-native AI email agent | Gmail-based shared inbox and collaboration tool |
| **Email platforms** | Gmail and Outlook, including shared inboxes | Gmail only |
| **Who writes replies** | AI drafts grounded in your docs and past email; approve or auto-send per workflow | Humans, with rules and templates to help |
| **Team features** | Lighter: plain-English triage, labels, routing | Assignments, notes, Kanban boards, SLA tracking |
| **Pricing model** | Flat by AI draft volume, unlimited seats on paid plans | Per user, from $19 per user per month annual |
| **Main tradeoff** | Email only, lighter on assignment and boards | Humans still write every reply |
## What are you actually trying to fix
Shared inbox pain comes in two flavors, and they call for different tools.
**The visibility failure.** Nobody knows who owns which email. Two people reply to the same customer, a third request sits untouched for days, and the manager finds out when the customer does. Gmelius exists for this, along with the rest of the [Gmail shared inbox category](/blog/best-shared-inbox-for-gmail).
**The volume failure.** Ownership is clear and the owner is buried, because most of today's email is questions the company has answered hundreds of times: pricing, order status, policies, how-tos. A board view makes this failure easier to watch. It does not make it smaller.
The second failure is more common than teams admit. SuperOffice's response-time research found that [62% of businesses never respond to customer emails at all](https://www.superoffice.com/blog/response-times/), and those that do average over 12 hours. Companies do not skip replies because no card was assigned. They skip them because writing every reply by hand stops scaling long before headcount catches up.
Work out which failure is costing you more before you pick a tool. The rest of this comparison follows from that answer.
## Where Gmelius fits
Gmelius is one of the better-known names in Gmail-native collaboration, and its feature set maps cleanly onto the visibility failure.
Shared inboxes like support@ or sales@ become spaces the whole team can work: conversations carry owners, internal notes keep team discussion out of the customer thread, and shared labels keep everyone's view consistent. The Kanban boards are the signature feature, turning an inbox into a pipeline of cards you drag between stages, which suits teams that manage email like a queue of small projects. Automation rules tag and route conversations as they arrive, and SLA tracking puts numbers on response promises.
Gmelius has added AI-flavored features over time, but the product's center of gravity has not moved: it organizes conversations so that people can answer them. The rules decide where an email goes. A person decides what it says, and types it.
Two structural tradeoffs follow. First, Gmelius is Gmail only. There is no Outlook support, so a company on Microsoft 365, or one that might acquire or merge its way onto it, cannot standardize on Gmelius. Second, pricing is per user, because the product's unit of value is a collaborating seat. Both are reasonable choices for the product Gmelius is. They are also exactly where it diverges from InboxPilot.
Against the anchor question: if your inbox pain is coordination, Gmelius addresses it well. If your pain is that the same answers get typed over and over, Gmelius arranges that work on a board and leaves all of it for you.
## Where InboxPilot is different (which is us)
InboxPilot is an inbox-native AI email agent. It connects to the Gmail or Outlook account you already run, including shared inboxes, and takes on the part Gmelius leaves to humans: producing the reply.
It reads incoming email and drafts responses grounded in your company's own material: help docs, website, policies, and the way your team has answered similar threads before. Every draft waits for human approval by default. Once a specific workflow earns trust, routine order-status updates or standard pricing questions, you can opt that workflow into auto-send while everything else stays on review. When the AI is not confident, it escalates to a person instead of guessing.
Triage and routing are written in plain English rather than a rules builder: "label anything about refunds and send it to Dana," "flag emails from our largest accounts." It works across multiple inboxes and integrates with Slack, [Zendesk](/blog/inboxpilot-and-zendesk-integration), Shopify, Pipedrive, and Notion. On security, InboxPilot is SOC 2 Type II certified and GDPR compliant, and customer data never trains AI models.
**The honest tradeoffs.** InboxPilot is email only: no chat widget, no ticket queue, no phone. It is also lighter on team-management features than Gmelius, with no Kanban boards, no collision detection, and no SLA dashboards, because it assumes drafting removes most of the coordination load rather than visualizing it. Teams that genuinely run their inbox as a pipeline will find Gmelius deeper there. And InboxPilot is the younger product, with a shorter track record.
## Pricing per user or flat usage
Only published prices below.
**Gmelius** charges per user: Meli at $19, Growth at $25, and Pro at $40 per user per month on annual billing. ([gmelius.com/pricing](https://gmelius.com/pricing))
**InboxPilot** charges a flat rate by AI draft volume, with unlimited seats on paid plans: Free (25 drafts a month), Hobby at $29 per month (200 drafts), Standard at $149 per month (1,500 drafts, unlimited inboxes), Pro at $499 per month (12,000 drafts), Enterprise custom. Never per seat, never per resolution. ([Pricing](/pricing))
The shapes matter more than the numbers. A five-person team on Gmelius Growth pays $125 a month, and each hire who touches the inbox adds $25. The same team on InboxPilot pays $29 or $149 depending on email volume, no matter how many people share the inbox. Per-user pricing taxes headcount. Usage pricing taxes repetitive email. Pay the smaller tax.
## Choose Gmelius when, choose InboxPilot when
**Choose Gmelius when:**
- Your team is committed to Gmail and the pain is coordination, not composition.
- You want to manage email visually, as Kanban cards moving through stages.
- You need assignments, shared labels, and SLA tracking more than you need drafted replies.
- Your email is mostly one-off conversations a human should write anyway.
**Choose InboxPilot when:**
- A large share of your inbox is repetitive questions with knowable answers.
- You want grounded drafts waiting in the thread before anyone opens it.
- You use Outlook, or want the option, and need one tool across both platforms.
- Per-user pricing punishes you because many people touch the shared inbox.
- You want routine workflows to eventually auto-send while a human keeps the exceptions.
If you are stuck, audit your own inbox instead of feature pages. Pull the last 50 threads and count how many a well-grounded draft could have answered from your docs. A low count means coordination is your bottleneck and Gmelius deserves the look. A high count means the writing is the bottleneck, and no board layout fixes that.
## Related reading
- [Best shared inbox for Gmail](/blog/best-shared-inbox-for-gmail): the category Gmelius competes in, compared honestly.
- [InboxPilot vs Hiver](/blog/hiver-inboxpilot): the same decision against the other big Gmail-native shared inbox.
- [InboxPilot vs Help Scout](/blog/helpscout-vs-inboxpilot): against a full support platform instead of a Gmail layer.
- [AI email assistant for teams](/blog/ai-email-assistant-for-teams): what grounded drafting looks like day to day.
- [AI support for support teams](/solutions/support-teams): the InboxPilot workflow end to end.
- [RFQ and quote request automation](/use-cases/rfq-email-automation): how quote requests get read, priced, and answered from your own catalog.
Gmelius is a solid choice if what your team lacks is coordination inside Gmail. If what it lacks is time, because the same answers get typed all day, drafting is the piece you are missing, and you can [try InboxPilot free](https://www.inboxpilot.co/) on 25 drafts without leaving the inbox you already use.
---
## How to Export Emails from Gmail: A Step-by-Step Guide
Source: https://www.inboxpilot.co/blog/how-to-export-emails-from-gmail
Published: 2025-05-05
Two free ways to export Gmail: Forward as attachment for up to 50 emails as EML files, or Google Takeout for a full MBOX archive. Steps and limits.
Sooner or later, most Gmail accounts hit a moment when some of the mail needs to leave. You are switching providers and want the history to come along. Your Google storage is full and old threads are the obvious weight to cut. A project wraps and the client wants a record. Or you simply want a backup that does not depend on one login.
Gmail covers all of these with two free, built-in paths: a quick trick for a handful of specific emails, and Google Takeout for the whole mailbox. Neither is obvious from the inbox itself, which is why most people only find them when they urgently need them.
This guide walks through both methods step by step, which format you get from each, and the limits worth knowing before you start a multi-gigabyte download.
**Disclosure:** we make [InboxPilot](/product/knowledge-base), an AI email agent that drafts replies inside Gmail grounded in your docs and email history. Everything below uses Gmail's own free tools; InboxPilot only becomes relevant at the end, for the case where the export is really a search problem in disguise.
## TL;DR
- **Two native methods cover almost every case.** Forward as attachment for a few specific emails, Google Takeout for bulk. See [which to use when](#which-method-to-use-when).
- **Forward as attachment exports up to 50 emails as EML files** you can open in Outlook, Thunderbird, or Gmail. See [the steps](#export-selected-emails-as-eml-files).
- **Google Takeout exports your whole mailbox as an MBOX archive**, downloadable or sent straight to Google Drive. See [the steps](#export-your-whole-mailbox-with-google-takeout).
- **Both have real limits**: the 50-email cap, no per-email selection in Takeout, and an archive that goes stale the day after you make it. See [the limits](#the-limits-of-gmail-exports).
- **If you export mail to dig answers out of old threads**, [InboxPilot](#if-you-export-email-to-find-answers-skip-the-export), which is us, uses that history in place instead. See [when that applies](#if-you-export-email-to-find-answers-skip-the-export).
## Export selected emails as EML files
When you need specific messages rather than everything, Gmail's Forward as attachment feature is the fastest path. It handles up to 50 emails at a time.
Log in to Gmail and check the boxes next to the emails you want to export. To grab everything under a label, click "Select all X conversations in [Label]" at the top of the list.
Click the "More" button (three vertical dots) in the top menu bar above the message list.
Pick "Forward as attachment" from the dropdown. Gmail opens a new email with each selected message attached as an individual `.eml` file.
Address the email to yourself (or a trusted recipient) and send. Treat it carefully: those attachments contain the full content of the original emails, including anything sensitive.
Open the received email and download the `.eml` attachments. They open in email clients like Outlook, Mozilla Thunderbird, or Gmail itself.
EML is a lightweight, widely compatible format, and each file is one self-contained email. If your selection is bigger than 50, skip this method and go straight to Takeout.
## Export your whole mailbox with Google Takeout
For bulk exports, Google Takeout is the tool. It downloads all your Gmail (and any other Google data you select) in one job.
Go to the [Google Takeout page](https://takeout.google.com) and sign in with the account you want to export.
Choose "Gmail" from the product list, and deselect anything you do not need (Drive, Photos, and the rest are included by default). Click "Next step."
Pick a delivery method (a download link by email, or "Add to Drive" to send the archive straight to Google Drive), a file format (`.zip` or `.tgz`), and a maximum file size. Large exports split into multiple files at that size.
Click "Create export" and wait. Google notifies you when the archive is ready to download or has landed in your Drive.
Takeout delivers your mail in the **MBOX** format: one archive file holding the whole mailbox, compatible with many email clients but not directly readable on its own. Control is coarser than the EML method. You can filter by label or category, but you cannot hand-pick individual emails.
The "Add to Drive" delivery option is worth highlighting: if the point of the export is a cloud backup rather than a local copy, it keeps gigabytes off your computer entirely.
## Which method to use when
| Method | Best for | Format | Main limit |
| --- | --- | --- | --- |
| Forward as attachment | Up to 50 specific emails | EML, one file per email | Hard 50-email cap |
| Google Takeout | Full mailbox or whole labels | MBOX archive | No per-email selection |
| Takeout with Add to Drive | Cloud backup without local downloads | MBOX in Google Drive | Same as Takeout, uses Drive storage |
The short version: a handful of known emails, use Forward as attachment. Everything else, use Takeout.
## The limits of Gmail exports
Both methods are free and reliable, and both have edges worth knowing before you commit an afternoon:
- **The 50-email cap is hard.** Forward as attachment will not take more, and there is no native middle ground between 50 emails and a whole-label Takeout job.
- **Takeout cannot cherry-pick.** Labels and categories are the finest filter, so exporting "just the Johnson project threads" means labeling them first.
- **MBOX is not a reading format.** The archive needs an email client to open, so a Takeout export is a storage artifact, not something you browse like a folder of PDFs.
- **An export is a snapshot.** It is accurate the moment it finishes and stale the day after, so backups need repeating on a schedule.
- **EML attachments carry everything.** Forwarding emails as attachments moves their full content, so be deliberate about where that forward goes.
For genuine backup, migration, or compliance needs, these are acceptable trade-offs and Takeout is the right tool. The one case it serves poorly is the most common one.
## If you export email to find answers, skip the export
A lot of Gmail exports are not really backups. They are attempts to get at the knowledge buried in old threads: what we quoted this customer last year, how we handled that refund, what the agreed spec was. Exporting a mailbox to MBOX so you can search it elsewhere is a lot of ceremony for what is, at heart, a lookup problem.
That lookup is the problem InboxPilot works on directly. It is an inbox-native AI email agent that grounds its drafts in your own email history, docs, and website, inside the Gmail account where the conversations already live. When a question arrives that your old threads already answer, the agent drafts the reply from that history, with a human approving each send by default. The knowledge stays where the conversations happen, and it stays current, which a snapshot never does.
To be honest about fit: InboxPilot is built for repetitive operational email in business inboxes, not for archiving. If you need a legal record, an offline backup, or a migration file, Takeout is free and correct, and nothing replaces it.
## Related reading
- [How to automate your Gmail inbox: 7 setups that work](/blog/automate-your-gmail)
- [How to train Gmail on your own data](/blog/how-to-train-gmail-on-your-own-data)
- [How to generate emails using your documents](/blog/how-to-generate-emails-using-your-documents)
- [How to create custom email templates in Gmail](/blog/automate-your-gmail)
- [Document collection automation](/use-cases/document-collection-automation): chasing missing documents without writing the reminders yourself.
Run the Takeout export if you need the archive, and if what you actually need is the answers inside those threads, [try InboxPilot free](https://www.inboxpilot.co/) with 25 AI drafts a month and let the history keep working where it is.
---
## How to Set Up an Automated Response in Gmail: 3 Ways That Actually Work
Source: https://www.inboxpilot.co/blog/how-to-setup-an-automated-response-on-your-gmail-account
Published: 2025-03-20
Set up a Gmail automated response three ways: the vacation responder for time away, filters plus templates for specific senders, and AI replies for repeat questions.
Gmail can answer email for you in three different ways, and most guides only cover the first. The vacation responder handles time away. Filters plus templates handle predictable, specific senders. And for the mail that needs a real answer rather than the same canned paragraph, an AI layer can draft or send replies grounded in your own information.
**Disclosure:** we make InboxPilot, the AI tool covered in method 3. Methods 1 and 2 are built into Gmail and free, and for plenty of situations they are all you need. We tell you when that is the case.
## TL;DR
- **Going away?** Use the [vacation responder](#method-1-the-vacation-responder-for-time-away): gear icon, See all settings, General tab, Vacation responder. Two minutes, free, done.
- **Same reply to a specific kind of email?** Use a [filter plus a template](#method-2-filters-plus-templates-for-specific-senders): enable Templates under Advanced settings, then create a filter with the Send template action.
- **Emails that need real answers?** Built-in Gmail sends everyone the same text. [AI replies from a tool like InboxPilot](#method-3-ai-replies-for-email-that-needs-a-real-answer) read each message and respond from your own docs.
- **Know the limits:** the responder replies to each sender at most once every 4 days, runs on whole days only, and cannot answer questions. Details in [the limits section](#the-limits-nobody-mentions).
## Method 1: the vacation responder, for time away
This is the right tool when you are out and simply need senders to know it. Setup takes about two minutes:
1. **Open settings.** In Gmail, click the gear icon in the top right, then **See all settings**.
2. **Find the responder.** Stay on the **General** tab and scroll down to **Vacation responder**.
3. **Turn it on and set dates.** Pick a first day, and optionally a last day. With a last day set, Gmail switches the responder off for you.
4. **Write the message.** Say when you are back and who to contact meanwhile. Something like: "I am out of office until August 4 with limited email access. For anything urgent, contact ops@yourcompany.com. I will reply when I return."
5. **Choose who gets it.** Tick "Only send a response to people in my Contacts" if you want to avoid auto-replying to newsletters and cold outreach. On Google Workspace accounts there is also an option to reply only to people in your organization.
6. **Save and test.** Click **Save Changes**, then email yourself from another account to confirm the reply arrives.
On mobile, the same setting lives under the menu, then Settings, your account, and Vacation responder (Android) or Out of Office AutoReply (iOS).
## Method 2: filters plus templates, for specific senders
The vacation responder is all-or-nothing. If you want Gmail to auto-reply only to certain messages, say anything with "pricing" in the subject, or anything sent to a support@ alias, chain two features together:
1. **Enable templates.** Settings, **Advanced** tab, set **Templates** to Enable, and save.
2. **Save the reply as a template.** Compose the reply you want sent automatically. Then click the three-dot menu in the compose window, choose **Templates**, then **Save draft as template**, and give it a name.
3. **Create the filter.** Click the sliders icon in the Gmail search bar, define what should trigger the reply (a to-address, a subject keyword, a sender domain), and click **Create filter**.
4. **Attach the template.** In the filter's actions, tick **Send template** and pick the one you saved. Create the filter, and it is live.
This works well for genuinely uniform requests: "send me your price list," "what are your opening hours," "where do I upload documents." Every match gets the identical text, instantly, around the clock.
Two things to know: the Send template option only appears after step 1's Advanced setting is enabled, and template replies send from your primary address even if the message came in through an alias. If you maintain a set of these, our guide to [automating your Gmail](/blog/automate-your-gmail) covers keeping them organized and shared across a team.
## Method 3: AI replies, for email that needs a real answer
Both built-in methods share a ceiling: they send predetermined text. The sender asking "where is my order 1482" or "does your plan include API access" gets a paragraph that ignores the question.
This is the gap [InboxPilot](/) covers. It connects to the Gmail account you already have, reads each incoming email, and drafts a reply grounded in your own material: help docs, policies, past threads, and connected tools like Shopify or Notion. The customer asking about order 1482 gets the status of order 1482. You choose the mode per category: drafts waiting in your inbox for one-click approval, or fully automatic sending for the questions you trust it on. Setup is connecting the inbox, uploading or linking your docs, and setting the rules in plain English.
It is the right tool when the volume of *answerable* email is the problem. If all you need is "I am away until Monday," stick with method 1 and spend nothing. When you are ready to go further, our guide to [automating email support](/blog/ai-email-agent) covers what to hand off first.
## The limits nobody mentions
The vacation responder's constraints are documented but rarely spelled out:
- **One reply per sender per 4 days.** However many times someone emails during that window, they get your auto-reply once. Editing the responder message resets this.
- **Whole days only.** It runs from 12:00 AM on the first day to 11:59 PM on the last. It cannot cover only evenings and weekends; for that you need the filter-plus-template method below.
- **It skips most automated mail.** Messages flagged as spam and messages from mailing lists you are subscribed to do not get a response, which is usually what you want.
- **It answers nothing.** Every sender gets the same text regardless of what they asked.
The filter-plus-template method removes the 4-day and whole-day limits but keeps the last one: the reply is fixed text, so it fits uniform requests only.
## Which method to use
Match the method to the mail. Time away with a human backstop: vacation responder, two minutes, free. A handful of predictable requests hitting a shared or personal address: filters plus templates, free, and worth the fifteen minutes of setup. A steady stream of questions that each need a specific answer: that is volume, not scheduling, and it is what [InboxPilot](/pricing) is built for. Plenty of teams run all three at once, and there is no reason not to start with the free two today.
## Related reading
- [How to automate your Gmail](/blog/automate-your-gmail): filters, labels, and workflows beyond auto-replies.
- [How to automate email support](/blog/ai-email-agent): deciding what to hand to AI first.
- [Booking request automation](/use-cases/booking-request-automation): turning booking and appointment enquiries into confirmed slots.
- [Shared mailbox auto-reply](/blog/shared-mailbox-auto-reply): what changes when the address belongs to a team rather than a person.
---
## AI Email Writer: What It Is and When It Helps
Source: https://www.inboxpilot.co/blog/ai-email-writer
Published: 2025-03-15
What an AI email writer actually does, how grounded drafting differs from generic text generation, and where InboxPilot leads for operational email.
You can already get a machine to write email for free. Paste any message into a chatbot and it returns a polite, grammatical reply in seconds. If that solved the problem, your inbox would be empty by now.
It is not, because writing was never the slow part. The slow part is knowing what to say: what the refund policy actually allows, what you quoted this customer in March, whether the order shipped, which answer is true. Fluent text without that knowledge is not a reply. It is a guess you now have to fact-check.
That gap is the whole story of the AI email writer category, and it is why the tools that hold up in daily use look different from the ones that demo well.
**Disclosure:** we make [InboxPilot](/product/ai-email-writer), an inbox-native AI email agent that drafts replies inside Gmail and Outlook, grounded in your own documents and past email, with a person approving each send. This post explains the category honestly, including the jobs an AI email writer, ours included, should not be doing: marketing campaigns, chat widgets, and phone support are different tools.
## TL;DR
- **The useful distinction is grounding, not writing quality.** Generic generators produce fluent guesses; grounded tools draft from your own documents and data. See [generic writers versus grounded drafting](#generic-writers-versus-grounded-drafting).
- **Volume is why the category exists.** In 2025, Microsoft's Work Trend Index measured the average worker receiving 117 emails a day and getting interrupted every two minutes during core hours. See [what an AI email writer actually is](#what-an-ai-email-writer-actually-is).
- **Five email types automate well**: routine questions, status checks, quote requests, document requests, and follow-ups. See [the five email types worth handing to AI](#the-five-email-types-worth-handing-to-ai).
- **[InboxPilot](#where-inboxpilot-leads-and-where-it-does-not-fit), which is us,** leads for repetitive operational email inside Gmail and Outlook. It is the wrong pick for chat widgets, large ticket-queue operations, and campaign sends.
- **Draft-and-approve is the guardrail** that separates useful automation from liability. See [the guardrails that make automation safe](#the-guardrails-that-make-automation-safe).
## What an AI email writer actually is
At its simplest, an AI email writer reads an incoming email and composes a reply. That covers a wide range of tools: the compose helpers built into Gmail and Outlook, standalone chatbots you paste text into, and agents that sit on the inbox and draft responses on the actual thread.
The reason anyone shops for one is volume. In 2025, Microsoft's Work Trend Index put the average worker at 117 emails a day, with an interruption every two minutes during core hours ([Microsoft WorkLab, Breaking Down the Infinite Workday](https://www.microsoft.com/en-us/worklab/work-trend-index/breaking-down-infinite-workday), 2025). Most of that traffic is not novel. It is the same twenty questions arriving in slightly different words, and someone re-typing the same twenty answers.
And the cost of falling behind is measurable. SuperOffice studied company response times and found that [62% of businesses never respond to customer emails at all](https://www.superoffice.com/blog/response-times/), with an average response time of over 12 hours, while nearly half of customers expect a reply within four hours. The teams buying AI email writers are mostly trying to close that gap without hiring for it.
## Generic writers versus grounded drafting
Here is the split that matters more than any feature list:
| | Generic AI writer | Grounded email agent |
|---|---|---|
| **Where it lives** | A separate app or chat window you paste into | Inside Gmail or Outlook, on the real thread |
| **What it knows** | General knowledge from training data | Your documents, website, policies, and past email |
| **When it lacks the answer** | Writes something plausible anyway | Escalates to a person instead of guessing |
| **What you get** | Text to copy, edit, and paste | A draft waiting for approval in your inbox |
A generic writer is genuinely useful for tone and phrasing: softening a message, tightening a rambling draft, translating. What it cannot do is answer a customer, because it does not know your refund window, your lead times, or your rates. When it fills that void with a confident invention, you have created work, not removed it.
Grounded drafting inverts the model. The tool writes only from sources you gave it: help docs, the website, rate sheets, past threads. When the answer is not in those sources, the correct behavior is to say so and hand the email to a human. That single behavior, escalate instead of guess, is the difference between an AI email writer you can trust with customers and one you can only trust with wording.
## The five email types worth handing to AI
Ask any team what actually fills the inbox and you get versions of the same five piles:
| Email type | Example | Why it automates well |
|---|---|---|
| **Routine questions** | "What is your return policy?" "Do you ship to Canada?" | The answer is fixed and lives in a document |
| **Status checks** | "Where is my order?" "Any update on my application?" | The answer lives in a system and just needs looking up |
| **Quote and RFQ requests** | "Can you price 500 units of X?" | Requirements can be extracted and a first reply drafted from your catalog |
| **Document requests** | "Can you send the invoice / certificate / W-9?" | Pure fetch-and-attach work |
| **Follow-ups** | "Did you get my last email?" | Small individually, constant in aggregate |
Notice what is not on the list: negotiations, complaints, anything where the answer depends on judgment rather than lookup. Those emails still deserve a human first touch, and a good tool routes them to one rather than drafting at them.
## Where InboxPilot leads and where it does not fit
InboxPilot is an inbox-native AI email agent, which means it works inside the Gmail or Outlook inbox you already have, shared inboxes included, with no migration and no new interface. It reads incoming email, drafts replies grounded in your docs, website, and past threads, and routes what it cannot answer to the right person. Rules are written in plain English ("when someone asks about order status, pull the order from Shopify and draft an update"), and it handles triage, labels, and multi-inbox routing alongside the drafting.
Pricing is flat and metered by AI drafts, with unlimited seats on paid plans: Free covers 25 drafts a month, Hobby is $29 per month for 200, and Standard is $149 per month for 1,500 drafts with unlimited inboxes. Never per-seat, never per-resolution. Details on the [pricing page](/pricing).
Just as important is where InboxPilot does not belong, because the category is crowded with tools claiming to do everything:
- **You want a chat widget on your site.** That is a chatbot product, not an email agent.
- **You run a large ticket-queue operation** with SLAs, agent shifts, and QA scores. A helpdesk platform is the right backbone; email drafting is a layer, not a replacement.
- **You want outbound campaigns and newsletters.** That is marketing software. An AI email writer in this sense answers inbound mail; it does not blast lists.
- **You are an executive looking for personal inbox triage.** Different problem, different tools.
## The guardrails that make automation safe
The failure mode everyone fears is an AI sending something wrong under your name. The fix is not better AI so much as better defaults:
1. **Draft-and-approve stays on.** The AI writes, a person sends. Auto-send is opt-in, per workflow, after you have watched the drafts perform on real traffic.
2. **Grounding is enforced.** Replies come from your documents or they do not go out. When the source material lacks the answer, the email escalates.
3. **Negative keywords pull threads out of automation.** Words like *dispute*, *refund*, *legal*, or *cancel* can route an email straight to a human with no draft attached.
Set up that way, the AI takes the lookup and the typing, and people keep the judgment. That division holds up: the machine handles the 80% of email that is repetition, and the 20% that needs a human still gets one, faster, because the queue in front of it is shorter.
## Related reading
- [What is an AI email agent](/blog/ai-email-agent): the deeper version of the generic-versus-grounded distinction, with worked examples.
- [How to generate emails from your own documents](/blog/how-to-generate-emails-using-your-documents): the grounding setup, step by step.
- [AI email assistant buyers guide for 2026](/blog/ai-email-assistant-buyers-guide-2026): how to run an evaluation, including the questions vendors hope you skip.
- [Best email management software](/blog/ai-email-agent): where drafting tools fit next to shared inboxes and helpdesks.
- [RFQ and quote request automation](/use-cases/rfq-email-automation): how quote requests get read, priced, and answered from your own catalog.
If the writing was never your bottleneck and the knowing is, that is the exact piece InboxPilot was built to cover. The [free plan](/pricing) includes 25 AI drafts a month, enough to test it on your real traffic before paying anything.
---
*Statistics are attributed to their original source with the year of publication stated. InboxPilot pricing was verified against the pricing page in July 2026. InboxPilot is the publisher of this article.*
---
## Best Fyxer AI Alternatives in 2026 (and How They Compare)
Source: https://www.inboxpilot.co/blog/alternative-fyxer
Published: 2025-01-23
Fyxer AI drafts replies and takes meeting notes for $30 per user. Where it fits, where it does not, and when a flat-rate email agent is the better buy.
Fyxer AI calls itself an AI executive assistant, and for once the label is accurate. It sorts your inbox into categories, drafts replies that sound like you, and joins your meetings to take notes. If your problem is your own overflowing inbox, that is a real product doing a real job.
But many people searching for a Fyxer alternative are not trying to fix their own inbox. They are trying to fix `sales@` or `support@`: the shared mailbox where quote requests, order questions, and routine support requests wait, because they belong to everyone and therefore to no one.
**Disclosure:** we make [InboxPilot](/), so this comparison is written by one of the two vendors in it. We have kept it to checkable facts, and we are upfront about the split: Fyxer is a personal productivity tool, InboxPilot is a team automation tool, and buying the wrong one wastes money in either direction.
## TL;DR
- **[InboxPilot](#inboxpilot-built-for-the-company-inbox-which-is-us)** is the better pick when the email you want off your plate is company email: RFQs, order status, returns, and routine support handled in a shared Gmail or Outlook inbox, with flat pricing and unlimited seats.
- **[Fyxer AI](#fyxer-ai-a-personal-assistant-for-your-own-inbox)** wins on personal productivity: triage for your own mail, drafts in your voice, and a meeting notetaker, priced per user.
- The decision is less about features than about [which problem you are hiring for](#what-are-you-actually-replacing): one persons inbox or the companys.
- Pricing diverges fast with headcount. Ten people on Fyxer Starter cost $300 a month, while InboxPilot Standard runs a [flat $149 for the whole team](#pricing-per-user-vs-flat-rate).
- Neither is a drop-in replacement for the other. The [decision map](#which-one-fits) at the end gives honest picks by situation.
## Fyxer vs InboxPilot at a glance
| Tool | Best for | Pricing model | Main tradeoff |
|---|---|---|---|
| **InboxPilot** | Teams automating repetitive operational email in shared inboxes | Flat tiers by AI draft volume, unlimited seats, from $29/mo (free plan: 25 drafts) | Email only: no meeting notes, no chat widget, no ticket queue |
| **Fyxer AI** | Individuals who want their own inbox triaged and their meetings noted | Per user: Starter $30/mo, Professional $50/mo, about 25% less billed annually | Cost scales with headcount, and drafting stays personal rather than workflow-driven |
## What are you actually replacing
Before comparing features, name the job. People arrive at this comparison from two very different situations.
**Situation one: your own inbox is the problem.** Half of your mail needs a reply from you personally, and you spend evenings catching up. You want triage, drafts in your voice, and notes from the meetings you sat through. That is the job Fyxer was built for.
**Situation two: the company inbox is the problem.** Quote requests sit in `sales@` until someone notices. Order status questions get answered by whoever happens to look. The answers already live in your docs and your past email, and retyping them is a real chunk of someones week. That is workflow automation, not personal productivity, and it is the job InboxPilot was built for.
Most feature tables blur this line because both products "draft email with AI." What they draft, for whom, and what happens after the draft are entirely different.
### InboxPilot: built for the company inbox (which is us)
InboxPilot is an inbox-native AI email agent. It works inside Gmail and Outlook, including shared inboxes, with no migration and no new interface for the team to learn. It reads incoming mail, works out what each message is asking, and drafts a reply grounded in your website, docs, and past email rather than generic AI text.
Human approval is the default: drafts wait for a person to review. Auto-send is opt-in per workflow, so the fifth identical order-status question can go out automatically while quote requests still get human eyes. When the AI is not confident, it escalates instead of guessing. Triage, labels, and routing run on plain-English rules across multiple inboxes.
The sweet spot is repetitive operational email: RFQs and quotes, order status (there is a Shopify integration), returns and refunds, document collection, bookings, purchase orders, and routine support.
- **Best fit:** teams answering the same operational questions in a shared inbox every day.
- **Pricing:** flat, by AI draft volume, unlimited seats on paid plans. Free 25 drafts/mo, Hobby $29/mo (200 drafts), Standard $149/mo (1,500 drafts, unlimited inboxes), Pro $499/mo (12,000 drafts), Enterprise custom. ([Pricing](/pricing))
- **Security:** SOC 2 Type II, GDPR compliant, and customer data never trains AI models.
- **The honest tradeoff:** it is email only, and it is not a personal assistant. No meeting notetaker, no calendar management, no chat widget, no ticket queue. If the inbox that hurts is your own rather than the companys, Fyxer is the better tool, and buying InboxPilot for that job would be a mistake.
### Fyxer AI: a personal assistant for your own inbox
Fyxer earns its category label. It organizes your inbox and calendar, learns how you write, and produces drafts that sound convincingly like you. The meeting notetaker is the feature that separates it from pure email tools: it joins your calls, produces notes, and that context feeds your follow-ups. Slack and Teams integrations round out the assistant framing.
Pricing is per user. Starter at $30 a month (or $22.50 billed annually) covers one inbox with calendar organization, AI-drafted replies, and the notetaker. Professional at $50 ($37.50 annually) adds multiple inboxes, advanced scheduling, Fyxer Chat, a HubSpot integration, and file uploads. Enterprise is custom.
The limits show up when you point it at company email. Drafting stays personal: Fyxer writes as you, from your context, for you to send. There is no equivalent of grounding replies in a company knowledge base, no plain-English workflow rules, and no per-workflow auto-send. Because it is priced per user, giving everyone an assistant multiplies the bill by headcount.
- **Best fit:** founders, execs, and anyone whose personal inbox and meeting load are the bottleneck.
- **Pricing:** Starter $30/mo, Professional $50/mo, roughly 25% less on annual billing. Enterprise custom.
- **The honest tradeoff:** built for one person at a time. It polishes how you handle your mail; it does not take a category of company email off the team entirely.
Back to the anchor problem: if `sales@` is where email goes to die, Fyxer does not fix that, and to its credit it does not claim to.
## Pricing: per user vs flat rate
The models diverge with headcount. Fyxer charges per person: ten people on Starter is $300 a month and twenty is $600, before anyone answers more email than they did last quarter. InboxPilot charges by AI draft volume with unlimited seats: Standard at a flat $149 covers 1,500 drafts a month across as many teammates and inboxes as you have.
Neither model is universally better. If exactly one exec needs help, $30 for Fyxer is a smaller line item than $149 (though InboxPilot Hobby at $29 covers 200 drafts for a single light workflow). If eight people share three inboxes, per-user pricing is the wrong shape for the problem.
## Which one fits
- **You are an exec or founder buried in your own email and meetings.** Fyxer. This is its home turf, and the notetaker alone can justify the seat.
- **Your team answers the same operational questions daily in a shared inbox.** InboxPilot. Grounded drafts plus routing is the actual fix, and flat pricing covers the whole team.
- **You want AI notes from every call.** Fyxer. InboxPilot does not touch meetings.
- **You need replies grounded in your docs and policies, with auto-send for the safe cases.** InboxPilot.
- **You want both jobs done.** They barely overlap. Some companies run a personal assistant for execs and an email agent on the shared inboxes; just do the per-user math honestly before rolling either out company-wide.
## Related reading
- [AI email assistant for teams](/blog/ai-email-assistant-for-teams): what changes when the inbox is shared.
- [Superhuman pricing and AI in 2026](/blog/alternative-superhuman-ai): the same personal-versus-team split, premium client edition.
- [Shortwave pricing and an alternative](/blog/alternative-shortwave): when the AI email tool is a whole new client.
- [Best shared inbox software](/blog/best-shared-inbox-software): the wider category for team email.
- [What an AI email agent actually does](/blog/ai-email-agent): the product category underneath this comparison.
- [RFQ and quote request automation](/use-cases/rfq-email-automation): how quote requests get read, priced, and answered from your own catalog.
If the inbox you keep thinking about is your own, take Fyxer for a spin and see whether the drafts sound like you. If it is the shared one your team answers all day, that is the gap [InboxPilot](/pricing) was built for, and the free plans 25 drafts a month are enough to test it on real email.
*InboxPilot is the publisher of this article and one of the two tools discussed.*
---
## InboxPilot vs Gemini for Gmail: Which to Use (2026)
Source: https://www.inboxpilot.co/blog/alternative-gemini-for-gmail
Published: 2025-01-23
Gemini is a drafting layer inside Gmail. InboxPilot automates repetitive team email in shared inboxes. What each does, and when you need both.
If your company runs on Google Workspace, you already have Gemini in Gmail. It summarizes long threads, drafts replies with Help Me Write, and answers natural-language questions about your own mail. For the person at the keyboard, it makes email noticeably faster.
So the real question is not "InboxPilot or Gemini" as rivals. It is whether a drafting layer for individuals covers what your team needs, or whether the repetitive email arriving in sales@ and support@ needs something that works when nobody is at the keyboard at all.
**Disclosure:** we make [InboxPilot](/), an inbox-native AI email agent for team and operational email. Gemini is not really our competitor for personal drafting inside Gmail; it is good at that, it is already bundled, and we say so below. This comparison is about where each layer stops.
## TL;DR
- **[InboxPilot](#inboxpilot-the-pick-for-team-and-support-email-automation)** is the pick for automating repetitive team email, which is us: grounded drafts, triage, and routing inside shared Gmail and Outlook inboxes.
- [Gemini for Gmail](#gemini-for-gmail-the-assistant-layer-bundled-with-workspace) is the pick for personal drafting and summarizing, and for most Workspace users it is already there at no extra decision.
- The two solve [different layers of the email problem](#what-are-you-actually-replacing): assistance for the person typing versus automation for the inbox itself.
- Gemini works only in Google's ecosystem; InboxPilot covers Gmail and Outlook, which matters for mixed or Microsoft-based teams.
- See [which one fits](#which-one-fits) for the honest mapping, including the common case where the answer is both.
## InboxPilot and Gemini for Gmail at a glance
| Tool | Best for | Pricing model | Main tradeoff |
|---|---|---|---|
| **InboxPilot** | Teams automating repetitive email in shared Gmail or Outlook inboxes | Flat, by AI draft volume, unlimited seats on paid plans | Email only: not a chat widget, ticket queue, or personal productivity suite |
| **Gemini for Gmail** | Individuals drafting, summarizing, and searching their own Gmail | Bundled with qualifying Google Workspace plans | Assists one person per message; no shared-inbox automation, Gmail only, context limited to your Google data |
## What are you actually replacing
A drafting assistant and an email automation layer fail in different directions, so start with the failure you actually have.
**If people on your team spend too long writing individual emails**, Gemini is the obvious first move. It is native, it is bundled with Workspace, and there is nothing to buy or integrate. Faster drafting for humans is exactly what it does.
**If the problem is the inbox rather than the typing**, drafting speed does not fix it. A shared mailbox receiving order-status questions, quote requests, and returns does not need each reply written faster. It needs messages recognized, routed, and answered from company knowledge, with a human reviewing rather than composing. That is an automation problem, and it is the layer Gemini does not attempt.
Plenty of Workspace teams end up with both: Gemini for the humans, an agent like InboxPilot for the inbox.
## The two tools, honestly
### InboxPilot: the pick for team and support email automation
InboxPilot is an inbox-native AI email agent, and it is our product, so weigh this section with that in mind. It connects to Gmail and Outlook, including shared inboxes, with no migration and no new interface. It reads incoming email and drafts replies grounded in your company's docs, website, and past email, so the answer to "where is my order" or "can you quote this" comes from your actual policies and history.
Human approval is the default; auto-send is opt-in per workflow. Teams typically start in draft mode, watch the accuracy, then switch on auto-send for the narrow categories they trust, with the agent escalating whenever it is unsure. Plain-English rules handle triage, labels, and routing across multiple inboxes, and integrations include Slack, Zendesk, Shopify, Pipedrive, and Notion alongside Gmail and Outlook.
It earns its keep on repetitive operational email: RFQs and quotes, order status, returns and refunds, document collection, bookings, and routine support. It is SOC 2 Type II and GDPR compliant, and customer data never trains AI models.
- **Best fit:** teams whose shared inboxes answer the same questions daily and want grounded, consistent replies without a human writing each one.
- **Pricing:** flat, by AI draft volume, never per seat. Free (25 drafts a month), Hobby $29, Standard $149 (1,500 drafts, unlimited inboxes), Pro $499 (12,000 drafts), Enterprise custom. ([Pricing](/pricing))
- **Tradeoff:** email only, team-first. It is not a chat widget, ticket queue, or phone tool, and it will not make an individual's personal Gmail feel faster the way a native drafting layer does.
Against Gemini specifically: InboxPilot picks up where per-message assistance stops, at the shared inbox that needs handling whether or not anyone is looking at it.
### Gemini for Gmail: the assistant layer bundled with Workspace
Gemini for Gmail is Google's AI woven directly into the Gmail interface. Help Me Write drafts and refines messages with options like Formalize, Elaborate, and Shorten. It summarizes long threads into key points, suggests quick replies, proofreads beyond spelling and grammar, helps with scheduling, and answers natural-language questions about your own mail, the "who was the plumber that quoted me last year" kind of search.
Its honest wins are real. It is native, so there is no new tool to adopt or connect. It ships as part of Google Workspace rather than as a separate purchase decision. And for personal drafting and thread comprehension inside Gmail, being built by the company that makes Gmail shows.
The limits follow from the design. Gemini assists the person at the keyboard: drafts and summaries are produced one message at a time, and every send is manual. Its context is your Gmail and Google data rather than a curated company knowledge base, so it cannot ground replies in your product docs or policy pages the way a dedicated agent does. It works only in Gmail, which leaves Outlook-based or mixed teams out. And it has no shared-inbox workflow layer: no routing rules, no escalation logic, no multi-inbox triage.
- **Best fit:** individuals on Google Workspace who want faster drafting, summarizing, and inbox search with zero setup.
- **Pricing:** included with qualifying Google Workspace plans; full features require a business subscription rather than a free personal account.
- **Tradeoff:** a general assistant layer, not an automation system. The inbox still depends on a human opening every message.
Against InboxPilot specifically: Gemini is the tool for making people faster inside Gmail, not for taking categories of email off the team entirely.
## Which one fits
- **You are on Workspace and your complaint is drafting speed.** Use Gemini. It is already there, and buying a separate tool for personal drafting is hard to justify.
- **Your shared inboxes receive repetitive operational email.** Use InboxPilot. Summaries and suggested replies do not triage sales@ or answer from your return policy.
- **Your team is on Outlook, or split between Gmail and Outlook.** Gemini is out of scope by design; InboxPilot covers both.
- **You want replies grounded in company docs, with approval or opt-in auto-send.** That is InboxPilot's core loop; Gemini has no equivalent.
- **You want both faster humans and a handled inbox.** Run both. They sit at different layers and do not conflict.
If the missing layer is the one that answers your repetitive email instead of just drafting it faster, [start on InboxPilot's free plan](/pricing) and test it against your real inbox.
## Related reading
- [InboxPilot vs Microsoft Copilot for email](/blog/alternative-microsoft-copilot-email): the same layer question on the Microsoft side.
- [How to train Gmail on your own data](/blog/how-to-train-gmail-on-your-own-data): grounding replies in company knowledge, step by step.
- [Automate your Gmail](/blog/automate-your-gmail): what Gmail-native automation can and cannot do.
- [AI email assistant for teams](/blog/ai-email-assistant-for-teams): what changes when email is a team sport.
- [Best shared inbox for Gmail](/blog/best-shared-inbox-for-gmail): the wider shared-inbox toolset for Google shops.
- [RFQ and quote request automation](/use-cases/rfq-email-automation): how quote requests get read, priced, and answered from your own catalog.
---
## InboxPilot vs Jace: Which AI Email Assistant Fits (2026)
Source: https://www.inboxpilot.co/blog/alternative-jace
Published: 2025-01-23
Jace is a personal AI assistant for your own inbox. InboxPilot automates team email in shared inboxes. How the two differ, and how to choose.
Jace pitches itself as a second brain for email: an AI assistant that reads your inbox, learns your voice, and drafts the replies you would have written anyway. For a founder or executive whose personal mailbox eats the first two hours of every day, that pitch lands.
But most people weighing Jace against InboxPilot are not comparing two versions of the same product. They are holding two different problems. One is "my own inbox is unmanageable." The other is "our sales@ and support@ addresses get the same forty questions every week, and replies take too long."
Those are different jobs, and each tool is built for exactly one of them.
**Disclosure:** we make [InboxPilot](/), the team-email side of this comparison, so read our take on Jace with that in mind. Where Jace is the better fit, a single busy personal inbox with no repetitive operational email behind it, we say so plainly.
## TL;DR
- **[InboxPilot](#inboxpilot-the-pick-for-team-and-support-email-automation)** is the pick for team and support email automation, which is us. It works inside Gmail and Outlook shared inboxes and drafts replies grounded in your own docs and past email.
- [Jace](#jace-a-personal-ai-assistant-for-your-own-inbox) is the pick for personal inbox management: one busy professional, drafting in their voice, with a chat assistant across their connected tools.
- The decision hinges on [what you are actually replacing](#what-are-you-actually-replacing): a personal assistant, or an operational process.
- Pricing models diverge: Jace charges per user ($20-40 per user per month), InboxPilot charges flat by AI draft volume with unlimited seats on paid plans.
- The [which one fits](#which-one-fits) section maps common situations to a pick, including the case where the honest answer is both.
## InboxPilot and Jace at a glance
| Tool | Best for | Pricing model | Main tradeoff |
|---|---|---|---|
| **InboxPilot** | Teams automating repetitive email in shared Gmail or Outlook inboxes | Flat, by AI draft volume, unlimited seats on paid plans | Email only: not a chat widget, ticket queue, or personal productivity tool |
| **Jace** | One person managing their own inbox with AI drafts and a chat assistant | Per user, $20 (Plus) or $40 (Pro) per month | Drafts stay drafts until you send them; context is your mailbox, not a company knowledge base |
## What are you actually replacing
Before comparing features, work out which job you are hiring for. The two failure modes look similar from inside an inbox but need opposite tools.
**If the pain is your own mailbox**, you want a personal assistant: something that reads your threads, knows your voice, and gets you to inbox zero faster. Per-user pricing is fine because there is one user. Draft-only mode is fine because you were always going to read everything anyway.
**If the pain is a shared mailbox**, you want an operational tool: something that watches sales@ or support@, recognizes the order-status question or the quote request it has seen two hundred times, and answers it from company knowledge without a human writing from scratch. Here draft-only assistance barely moves the needle, because the bottleneck is not typing speed. It is that nobody has picked the message up yet.
Most "Jace vs InboxPilot" searches resolve in this section, before any feature table.
## The two tools, honestly
### InboxPilot: the pick for team and support email automation
InboxPilot is an inbox-native AI email agent, and it is our product, so weigh this section accordingly. It connects to Gmail and Outlook, including shared inboxes, with no migration and no new interface. It reads incoming email and drafts replies grounded in your company's own docs, website, and past email, so answers reflect your actual policies rather than a generic model's guess.
Human approval is the default. Auto-send is opt-in per workflow, so a team can automate the order-status and document-request replies it trusts while keeping a human on everything else. When the AI is unsure, it escalates instead of improvising. Plain-English workflow rules handle triage, labels, and routing across multiple inboxes.
The sweet spot is repetitive operational email: RFQs and quotes, order status, returns and refunds, document collection, bookings, and routine support. Security posture matters at this layer, and InboxPilot is SOC 2 Type II and GDPR compliant, and customer data never trains AI models.
- **Best fit:** teams whose shared inboxes receive the same questions on repeat and need fast, consistent, grounded replies.
- **Pricing:** flat, by AI draft volume, never per seat. Free (25 drafts a month), Hobby $29, Standard $149 (1,500 drafts, unlimited inboxes), Pro $499 (12,000 drafts), Enterprise custom. ([Pricing](/pricing))
- **Tradeoff:** it is email only and team-first. No chat widget, no ticket queue, no phone. And if the inbox you want tamed is your own executive mailbox, a personal assistant like Jace is closer to that job than we are.
Against Jace specifically: InboxPilot is the tool when the email problem belongs to the company, not to one person.
### Jace: a personal AI assistant for your own inbox
Jace is a personal AI assistant built around your individual mailbox. It drafts replies from the context of your threads, applies AI labels to categorize and prioritize what arrives, and setup is quick, on the order of a minute to connect Gmail or Outlook. Its "chief of staff" chat interface lets you ask questions and complete tasks across connected tools without leaving email.
That integration set is genuinely broad for a personal tool: alongside Gmail and Outlook, Jace connects to HubSpot, Salesforce, Notion, GitHub, Jira, and Slack. For an individual who lives across those systems, having one assistant that can see them all is a real win, and it is not something InboxPilot tries to replicate.
The limits are the flip side of the design. Jace works in draft mode, so every reply still needs your review and your click to send. Its context is your inbox and connected tools rather than a maintained company knowledge base, and there is no shared-inbox workflow layer for routing operational email across a team. Pricing is per user: Plus at $20 per user per month, Pro at $40, with custom enterprise plans.
- **Best fit:** a founder, executive, or busy professional managing their own high-volume inbox.
- **Pricing:** $20-40 per user per month, per Jace's published plans.
- **Tradeoff:** drafting help, not automation. The reading, deciding, and sending stay with you, and per-user costs scale with headcount if you roll it out to a team.
Against InboxPilot specifically: Jace is the tool when the email problem is yours alone, and no shared operational inbox sits behind it.
## Which one fits
- **You are a founder or executive and your personal inbox is the problem.** Pick Jace. A personal assistant that knows your voice and your tools is the right shape, and InboxPilot is honestly not built for personal-inbox productivity.
- **Your team runs sales@, support@, or quotes@ and the same questions arrive daily.** Pick InboxPilot. Draft-only personal assistants do not triage a shared mailbox or answer from company docs.
- **You want some replies to go out without a human touching them.** Pick InboxPilot. Opt-in auto-send with escalation is the core of the product; Jace keeps every send manual.
- **Your team already lives in Notion, Jira, and Slack and wants one assistant across them.** Jace's integration breadth wins there.
- **You have both problems.** Use both. They overlap far less than a comparison page implies.
If the piece you are missing is a team inbox that answers its own repetitive email, [try InboxPilot on the free plan](/pricing) with your real inbox before paying anything.
## Related reading
- [InboxPilot vs Superhuman AI](/blog/alternative-superhuman-ai): another personal-productivity comparison, same dividing line.
- [AI email assistant for teams](/blog/ai-email-assistant-for-teams): what team-grade email AI needs that personal tools skip.
- [AI email assistant for executives](/blog/ai-email-assistant-for-executives): the personal-inbox side of the problem, taken seriously.
- [Best shared inbox software](/blog/best-shared-inbox-software): the category where operational email actually lives.
- [AI email assistant buyers guide](/blog/ai-email-assistant-buyers-guide-2026): the full evaluation checklist.
- [RFQ and quote request automation](/use-cases/rfq-email-automation): how quote requests get read, priced, and answered from your own catalog.
---
## Notion Mail vs InboxPilot: Which Fits Your Team in 2026?
Source: https://www.inboxpilot.co/blog/alternative-notion-mail
Published: 2025-01-23
Notion Mail organizes a personal inbox with AI labels and views. What it does well, where it stops, and when a team email agent is the better buy.
Notion Mail is what happens when a workspace company rebuilds the inbox. AI auto-labels sort incoming mail by what you have told it matters, custom views slice the same inbox into different lenses for different parts of your day, and meeting scheduling plus a live connection to your Notion workspace round it out. If your company already runs on Notion, it is a genuinely pleasant way to read your own email.
It is also free to start, which makes it the easiest experiment on this page. The catch sits one layer down: unlimited AI use is tied to Notion's paid plans, and the whole product is built around one persons inbox.
So the comparison is not really Notion Mail versus InboxPilot on features. It is a personal email client versus a team email agent, and which of those you actually need depends on which inbox is hurting.
**Disclosure:** we make [InboxPilot](/), so this comparison comes from one of the two vendors in it. We have kept it to checkable facts and drawn the line clearly: Notion Mail is a personal email client, InboxPilot is a team automation tool, and neither substitutes for the other.
## TL;DR
- **[InboxPilot](#inboxpilot-an-email-agent-for-the-company-inbox-which-is-us)** is the better pick when the email you want handled is company email: RFQs, order status, returns, and routine support answered from shared Gmail or Outlook inboxes, with flat pricing and unlimited seats.
- **[Notion Mail](#notion-mail-your-inbox-organized-the-notion-way)** wins on personal organization: AI labels, custom views, scheduling, and native Notion workspace integration, free to start.
- The real decision is [what you are actually replacing](#what-are-you-actually-replacing): the way you read your own mail, or the manual work of answering the companys.
- Pricing follows the same split: unlimited AI in Notion Mail rides on [per-member Notion plans](#pricing-ecosystem-seats-vs-flat-rate), while InboxPilot Standard is a flat $149 a month for the whole team.
- Neither replaces the other. The [decision map](#which-one-fits) at the end gives honest picks by situation.
## Notion Mail vs InboxPilot at a glance
| Tool | Best for | Pricing model | Main tradeoff |
|---|---|---|---|
| **InboxPilot** | Teams automating repetitive operational email in shared inboxes | Flat tiers by AI draft volume, unlimited seats, from $29/mo (free plan: 25 drafts) | Not an email client: no redesigned reading experience, nothing for personal organization |
| **Notion Mail** | Individuals who want their own inbox organized, especially Notion users | Free client; unlimited AI tied to paid per-member Notion plans | Organizes mail rather than answering it, and context stays inside the Notion workspace |
## What are you actually replacing
The two products get compared because both put AI in your inbox. They put it there for opposite reasons.
**Situation one: your inbox is a mess.** Everything arrives in one undifferentiated stream, and you want it sorted: labels that apply themselves, views that show only what matters right now, scheduling without the back-and-forth. That is the job Notion Mail was built for, and if you live in Notion already, the workspace integration is a real bonus.
**Situation two: the company inbox is a workload.** Messages to `sales@` or `support@` ask the same questions every week, the answers live in your docs and past threads, and someone spends hours retyping them. Organizing that mail better does not shrink the work. Answering it automatically does.
An organized inbox and an answered inbox are different products. Notion Mail sorts; it does not send. That single fact settles most of this comparison.
### InboxPilot: an email agent for the company inbox (which is us)
InboxPilot is an inbox-native AI email agent. It works inside Gmail and Outlook, including shared inboxes, with no migration and no new interface for the team to learn. It reads incoming mail, works out what each message is asking, and drafts a reply grounded in your website, docs, and past email rather than generic AI text.
Human approval is the default: drafts wait for a person to review. Auto-send is opt-in per workflow, so the routine order-status reply can go out automatically while anything unusual still gets human eyes. When the AI is not confident, it escalates instead of guessing. Triage, labels, and routing run on plain-English rules across multiple inboxes, and Notion itself is one of the supported knowledge sources, alongside Slack, Zendesk, Shopify, and others.
The sweet spot is repetitive operational email: RFQs and quotes, order status (there is a Shopify integration), returns and refunds, document collection, bookings, purchase orders, and routine support.
- **Best fit:** teams answering the same operational questions in a shared inbox every day.
- **Pricing:** flat, by AI draft volume, unlimited seats on paid plans. Free 25 drafts/mo, Hobby $29/mo (200 drafts), Standard $149/mo (1,500 drafts, unlimited inboxes), Pro $499/mo (12,000 drafts), Enterprise custom. ([Pricing](/pricing))
- **Security:** SOC 2 Type II, GDPR compliant, and customer data never trains AI models.
- **The honest tradeoff:** it is not an email client. There is no redesigned reading experience, no custom views, no scheduling assistant for your own calendar. If what you want is a nicer personal inbox, Notion Mail does that job and InboxPilot does not.
### Notion Mail: your inbox, organized the Notion way
Notion Mail brings Notion's core idea, that your tools should bend to how you think, into email. You tell it what matters and the AI auto-labels incoming mail accordingly. Custom views split one inbox into focused slices: today's priorities, newsletters, a view per project. Meeting scheduling is built in, and the connection to your Notion workspace means the context you keep in Notion sits close to your mail.
The pricing model follows Notion's. The client is free, with limited AI included. Unlimited AI use is tied to Notion's paid Business and Enterprise plans, priced per member, so the full experience effectively assumes a team-wide Notion subscription.
The limits are structural rather than missing features. Everything is draft-and-send-yourself: there are no workflow rules and no auto-send, so it cannot take routine replies off anyones plate. Context for AI comes from your Notion workspace, not your website, external docs, or CRM. And it is built around an individuals inbox, not a shared operational mailbox with routing and escalation.
- **Best fit:** individuals, especially in Notion-first companies, who want their own inbox organized without paying for a separate email tool.
- **Pricing:** free client; unlimited AI tied to paid per-member Notion plans.
- **The honest tradeoff:** it organizes email rather than answering it, and its intelligence stays inside the Notion ecosystem.
Back to the anchor problem: if quote requests sit unanswered in `sales@`, Notion Mail will label them beautifully. Someone still has to write every reply.
## Pricing: ecosystem seats vs flat rate
The comparison here is less about dollar amounts than about what the dollars attach to. Notion Mail's unlimited AI rides on Notion's per-member paid plans, so the cost scales with headcount and assumes the company wants Notion everywhere. If you are already paying for Notion Business, Notion Mail is close to a free upgrade for your team, which is a genuine point in its favor.
InboxPilot charges by AI draft volume with unlimited seats: Standard at a flat $149 a month covers 1,500 drafts across as many teammates and inboxes as you have, whether or not anyone at the company uses Notion. The free plan (25 drafts a month) and Hobby at $29 (200 drafts) exist to test a single workflow before committing.
The honest summary: for Notion-first teams wanting personal email organization, Notion Mail is nearly free at the margin. For email automation, headcount-independent flat pricing is the shape that fits.
## Which one fits
- **Your company runs on Notion and your own inbox needs order.** Notion Mail. The integration and the price at the margin are hard to argue with.
- **You want AI labels and custom views without buying anything.** Notion Mail. The free client is the lowest-risk trial in this comparison.
- **Your team answers the same operational questions daily in a shared inbox.** InboxPilot. Grounded drafts plus routing and opt-in auto-send is the actual fix, and flat pricing covers everyone.
- **You need replies grounded in your website, docs, and past email, not just workspace pages.** InboxPilot. It can even pull from Notion as one source among several.
- **You do not use Notion and do not plan to.** InboxPilot, or a different personal client entirely. Notion Mail without Notion loses most of its point.
- **You want both jobs done.** They coexist cleanly. Read your own mail in Notion Mail, and let an email agent handle the shared inboxes.
## Related reading
- [Shortwave pricing and an alternative](/blog/alternative-shortwave): another AI email client, same client-versus-agent split.
- [Superhuman pricing and AI in 2026](/blog/alternative-superhuman-ai): the premium end of personal email clients.
- [AI email assistant for teams](/blog/ai-email-assistant-for-teams): what changes when the inbox is shared.
- [Best shared inbox software](/blog/best-shared-inbox-software): the wider category for team email.
- [What an AI email agent actually does](/blog/ai-email-agent): the product category underneath this comparison.
- [Document collection automation](/use-cases/document-collection-automation): chasing missing documents without writing the reminders yourself.
If your own inbox just needs order and your company already lives in Notion, try Notion Mail first; it is free and it fits. If the shared inbox is where the real hours go, that is the gap [InboxPilot](/pricing) was built for, and the free plans 25 drafts a month are enough to test it on real email.
*InboxPilot is the publisher of this article and one of the two tools discussed.*
---
## Shortwave Pricing 2026: Plans, Limits, and an Alternative
Source: https://www.inboxpilot.co/blog/alternative-shortwave
Published: 2025-01-23
Shortwave charges $24 to $100 per seat for an AI email client. What each plan includes, and when a flat-rate email agent fits your team better.
Shortwave is one of the few AI email tools that asks you to change where you read your email. It is a full replacement client: Ghostwriter drafts replies that sound like you, natural language search digs through years of history in plain English, and the whole interface is rebuilt around AI. For people who live in email all day, that pitch has real appeal.
The price of admission is the switch itself. Shortwave runs $24 to $100 per seat per month, and everyone who uses it has to move into a new client and learn it.
That is a fair trade if you are shopping for a better personal inbox. It is the wrong shape entirely if the thing you are trying to fix is `sales@` or `support@`: the shared mailbox where the same questions arrive every day and wait for whoever cracks first.
**Disclosure:** we make [InboxPilot](/), so this comparison comes from one of the two vendors in it. We have kept it to checkable facts and drawn the line clearly: Shortwave is a personal email client with strong AI, InboxPilot is a team automation tool, and neither replaces the other.
## TL;DR
- **[InboxPilot](#inboxpilot-automation-inside-the-inbox-you-already-have-which-is-us)** is the better pick when the goal is taking repetitive company email off the team: grounded drafts, routing, and opt-in auto-send inside the Gmail or Outlook inboxes you already use, at a flat rate.
- **[Shortwave](#shortwave-a-new-email-client-with-ai-built-in)** wins on the personal inbox experience: Ghostwriter drafts in your voice, natural language search, and translation, priced per seat from $24 a month.
- The real decision is [what you are replacing](#what-are-you-actually-replacing): your email client, or the manual work of answering company email.
- Pricing diverges with headcount. Ten people on Shortwave Business cost $240 a month, while InboxPilot Standard is a [flat $149 for the whole team](#pricing-per-seat-vs-flat-rate).
- The [decision map](#which-one-fits) at the end gives honest picks by situation, including the cases where Shortwave is simply the better buy.
## Shortwave vs InboxPilot at a glance
| Tool | Best for | Pricing model | Main tradeoff |
|---|---|---|---|
| **InboxPilot** | Teams automating repetitive operational email in shared inboxes | Flat tiers by AI draft volume, unlimited seats, from $29/mo (free plan: 25 drafts) | Not a new client: no redesigned interface, no personal productivity features |
| **Shortwave** | Individuals who want an AI-native email client | Per seat: Business $24/mo, Premier $36/mo, Max $100/mo | Requires switching clients, and AI stays draft-only with per-tier usage caps |
## What are you actually replacing
People land on this comparison from two different problems, and the feature tables rarely separate them.
**Situation one: you want a better inbox.** Your current client feels slow, search never finds anything, and writing replies eats your afternoons. You want drafts in your voice and a smarter way to dig through old threads. That is the job Shortwave was built for, and it does it well.
**Situation two: the company inbox is the problem.** Quote requests, order questions, and routine support sit in a shared mailbox until someone notices. The answers already live in your docs and past email, and retyping them is a real chunk of someones week. A nicer client does not fix that; the work is still manual, just in a prettier window.
Both products "draft email with AI," which is why they end up in the same searches. What they draft, from what context, and what happens after the draft are entirely different.
### InboxPilot: automation inside the inbox you already have (which is us)
InboxPilot is an inbox-native AI email agent. It works inside Gmail and Outlook, including shared inboxes, with no migration and no new interface for anyone to learn. That is the direct contrast with Shortwave: instead of moving your team to a new client, it changes what happens to the mail inside the one you have.
It reads incoming email, works out what each message is asking, and drafts a reply grounded in your website, docs, and past email rather than generic AI text. Human approval is the default. Auto-send is opt-in per workflow, so the tenth identical order-status question can go out on its own while quote requests still get human eyes. When the AI is not confident, it escalates instead of guessing. Triage, labels, and routing run on plain-English rules across multiple inboxes.
The sweet spot is repetitive operational email: RFQs and quotes, order status (there is a Shopify integration), returns and refunds, document collection, bookings, purchase orders, and routine support.
- **Best fit:** teams answering the same operational questions in a shared inbox every day.
- **Pricing:** flat, by AI draft volume, unlimited seats on paid plans. Free 25 drafts/mo, Hobby $29/mo (200 drafts), Standard $149/mo (1,500 drafts, unlimited inboxes), Pro $499/mo (12,000 drafts), Enterprise custom. ([Pricing](/pricing))
- **Security:** SOC 2 Type II, GDPR compliant, and customer data never trains AI models.
- **The honest tradeoff:** it is not an email client. There is no redesigned interface, no personal triage experience, no AI search across your own history. If what you want is a nicer way to work your own inbox, Shortwave is the better product, and InboxPilot would be the wrong purchase.
### Shortwave: a new email client with AI built in
Shortwave commits fully to the client-replacement bet, and the payoff is coherence. Ghostwriter learns how you write and produces drafts that sound like you, not like a template. Natural language search is the standout: you describe the thread you half-remember and it finds it, no operators required. Translation for reading and writing in other languages and AI help with scheduling emails round out the package.
Pricing is per seat with AI usage metered by tier. Business at $24 a month includes daily AI request caps and five years of search history. Premier at $36 roughly doubles the AI allowance and removes the search history limit. Max at $100 carries the highest AI limits plus live 1:1 training, and Enterprise is custom. There is a 14-day trial but no permanent free tier.
The limits show up when you point it at company email. Every AI reply is a draft that a person reviews and sends; there are no workflow rules that let the routine cases go out automatically. Context comes primarily from your own email history rather than a company knowledge base. And because it is a client, adopting it is a team-wide migration: every person moves, learns the interface, and adds a seat to the bill.
- **Best fit:** individuals and small teams who want the best AI-native inbox experience and will happily switch clients to get it.
- **Pricing:** Business $24/mo, Premier $36/mo, Max $100/mo per seat, Enterprise custom. 14-day trial, no free tier.
- **The honest tradeoff:** it upgrades how you personally process mail. It does not take a category of company email off the team, and it was never meant to.
Back to the anchor problem: if the shared inbox is where email goes to die, a faster personal client does not resuscitate it, and Shortwave does not claim otherwise.
## Pricing: per seat vs flat rate
The models pull apart as headcount grows. Shortwave charges per person: ten people on Business is $240 a month, and $360 on Premier, with each seat carrying its own daily AI caps. InboxPilot charges by AI draft volume with unlimited seats: Standard at a flat $149 covers 1,500 drafts a month across as many teammates and inboxes as you have.
For one person the gap nearly vanishes. Shortwave Business at $24 and InboxPilot Hobby at $29 (200 drafts, and a free plan with 25 to test first) are in the same range; the choice is about the job, not the price. For eight people sharing three inboxes, per-seat pricing is the wrong shape for the problem.
## Which one fits
- **You want the best personal inbox experience and do not mind switching clients.** Shortwave. This is its home turf.
- **You constantly hunt for old threads and attachments.** Shortwave. The natural language search is the feature people stay for.
- **Your team answers the same operational questions daily in a shared inbox.** InboxPilot. Grounded drafts plus routing is the actual fix, and flat pricing covers everyone.
- **You need replies grounded in your docs and policies, with auto-send for the safe cases.** InboxPilot. Shortwave drafts from your mail history and always waits for a human send.
- **Nobody on your team wants to change email clients.** InboxPilot. It works inside Gmail and Outlook as they stand.
- **You want both jobs done.** They barely overlap. A power user can run Shortwave personally while the shared inboxes run on an email agent; just price the seats honestly first.
## Related reading
- [Superhuman pricing and AI in 2026](/blog/alternative-superhuman-ai): the other premium client, same personal-versus-team split.
- [Best Fyxer AI alternatives](/blog/alternative-fyxer): when the personal tool is an assistant rather than a client.
- [AI email assistant for teams](/blog/ai-email-assistant-for-teams): what changes when the inbox is shared.
- [Best shared inbox software](/blog/best-shared-inbox-software): the wider category for team email.
- [What an AI email agent actually does](/blog/ai-email-agent): the product category underneath this comparison.
- [RFQ and quote request automation](/use-cases/rfq-email-automation): how quote requests get read, priced, and answered from your own catalog.
If a sharper personal inbox is what you are after, take Shortwave's trial and see whether the drafts sound like you. If the inbox that hurts is the shared one your team answers all day, that is the gap [InboxPilot](/pricing) was built for, and the free plans 25 drafts a month are enough to test it on real email.
*InboxPilot is the publisher of this article and one of the two tools discussed.*
---
## Superhuman Pricing and AI in 2026: Worth $30+ Per User?
Source: https://www.inboxpilot.co/blog/alternative-superhuman-ai
Published: 2025-01-23
Superhuman costs $30 to $40 per user for a premium AI email client. Where that money is well spent, and when flat-rate team automation fits better.
Superhuman is the email client people evangelize. The keyboard shortcuts, the split inbox, the speed: for a certain kind of operator it makes email feel like a solved problem. The AI layer (Write with AI, Instant Reply, Auto Drafts, Voice and Tone Match) is woven into that same experience, so your drafts arrive sounding like you.
At $30 to $40 per user per month, it is also one of the pricier ways to read email, and what the money buys is personal speed.
That is the whole comparison in one line. If your own inbox is the bottleneck, Superhuman is a defensible spend. If the bottleneck is the shared inbox where quote requests, order questions, and routine support pile up, a faster personal client does not touch the problem.
**Disclosure:** we make [InboxPilot](/), so this comparison comes from one of the two vendors in it. We have kept it to checkable facts and been upfront about the split: Superhuman is a personal productivity tool, InboxPilot is a team automation tool, and buying the wrong one wastes money in either direction.
## TL;DR
- **[InboxPilot](#inboxpilot-built-to-take-company-email-off-the-team-which-is-us)** is the better pick when the email you want handled is company email: RFQs, order status, returns, and routine support answered from a shared Gmail or Outlook inbox, with flat pricing and unlimited seats.
- **[Superhuman](#superhuman-speed-for-your-own-inbox)** wins on personal throughput: a fast client, drafts in your voice, and polished scheduling, priced per user with no free tier.
- The decision hinges on [what you are actually replacing](#what-are-you-actually-replacing): your own email habits, or the manual work of answering the companys mail.
- Pricing diverges fast with headcount. Ten people on Superhuman Starter cost $300 a month, while InboxPilot Standard runs a [flat $149 for the whole team](#pricing-per-user-vs-flat-rate).
- Neither replaces the other. The [decision map](#which-one-fits) at the end gives honest picks by situation.
## Superhuman vs InboxPilot at a glance
| Tool | Best for | Pricing model | Main tradeoff |
|---|---|---|---|
| **InboxPilot** | Teams automating repetitive operational email in shared inboxes | Flat tiers by AI draft volume, unlimited seats, from $29/mo (free plan: 25 drafts) | Not a premium client: no keyboard-driven interface, no calendar, nothing for personal speed |
| **Superhuman** | Individuals who want the fastest possible personal email experience | Per user: Starter $30/mo, Business $40/mo, Enterprise custom | Cost scales with headcount, and AI stays draft-only for one persons inbox |
## What are you actually replacing
Before comparing features, name the job, because people arrive at this page from two very different problems.
**Situation one: you are the bottleneck.** You get more email than you can process, replies slip, and you want to move through your inbox at double speed with drafts that sound like you. That is precisely what Superhuman sells, and its users are loyal for a reason.
**Situation two: the company inbox is the bottleneck.** Messages to `sales@` or `support@` wait for whoever notices them. The answers already exist in your docs, your site, and last months threads, and retyping them is a standing tax on the team. Making one person faster does not clear that queue; automating the repetitive share of it does.
Both tools "write email with AI." One writes as you, for you to send faster. The other answers the companys mail from company knowledge, and can send the routine cases on its own.
### InboxPilot: built to take company email off the team (which is us)
InboxPilot is an inbox-native AI email agent. It works inside Gmail and Outlook, including shared inboxes, with no migration and no new interface to learn. It reads incoming mail, works out what each message is asking, and drafts a reply grounded in your website, docs, and past email rather than generic AI text.
Human approval is the default: drafts wait for a person to review. Auto-send is opt-in per workflow, so the fifth identical shipping question can go out automatically while a complex quote request still gets human eyes. When the AI is not confident, it escalates instead of guessing. Triage, labels, and routing run on plain-English rules across multiple inboxes.
The sweet spot is repetitive operational email: RFQs and quotes, order status (there is a Shopify integration), returns and refunds, document collection, bookings, purchase orders, and routine support.
- **Best fit:** teams answering the same operational questions in a shared inbox every day.
- **Pricing:** flat, by AI draft volume, unlimited seats on paid plans. Free 25 drafts/mo, Hobby $29/mo (200 drafts), Standard $149/mo (1,500 drafts, unlimited inboxes), Pro $499/mo (12,000 drafts), Enterprise custom. ([Pricing](/pricing))
- **Security:** SOC 2 Type II, GDPR compliant, and customer data never trains AI models.
- **The honest tradeoff:** it is not a personal productivity tool. No redesigned client, no keyboard-shortcut speed, no calendar, nothing that makes you personally faster at your own mail. If that is the job, Superhuman is the better product, and InboxPilot would be the wrong buy.
### Superhuman: speed for your own inbox
Superhuman earns its reputation as a client. Split inbox keeps the mail that matters in front of you, the shortcut-driven interface removes friction from every action, and features like Smart Send and Recent Opens give you timing and read signals most clients hide. Built-in calendaring works with Zoom, Google Meet, and Microsoft Teams.
The AI features fold into that flow. Starter at $30 a month ($300 annually) includes Write with AI, Instant Reply, Auto Drafts, Voice and Tone Match, and basic team collaboration. Business at $40 ($396 annually) adds Ask AI, Custom Auto Labels with AI, and integrations with HubSpot, Salesforce, and Pipedrive. Enterprise is custom, and there is no free tier.
The limits appear when you aim it at company email. Every AI reply is a draft one person reviews and sends; there are no workflow rules that let routine replies go out on their own. Context comes from the inbox rather than a company knowledge base, so it cannot answer policy or product questions it has never seen you answer. And per-user pricing means the bill grows with headcount whether or not the mail volume does.
- **Best fit:** executives, founders, and power users whose personal inbox is the constraint on their day.
- **Pricing:** Starter $30/mo or $300/yr, Business $40/mo or $396/yr, Enterprise custom.
- **The honest tradeoff:** it makes one person faster at their own mail. It does not remove a category of company email from the team, and it is priced per person either way.
Back to the anchor problem: if messages to the shared inbox sit for two days, Superhuman makes the eventual reply faster to type. It does not make it arrive sooner.
## Pricing: per user vs flat rate
The models diverge with headcount. Superhuman charges per person: ten people on Starter is $300 a month and $400 on Business, before anyone answers more email than last quarter. InboxPilot charges by AI draft volume with unlimited seats: Standard at a flat $149 covers 1,500 drafts a month across as many teammates and inboxes as you have.
Neither model is universally better. For exactly one exec, $30 for Superhuman is a smaller line item than $149, and InboxPilot Hobby at $29 (200 drafts) only competes if the job is a light automation workflow rather than personal speed. For eight people sharing three operational inboxes, per-user pricing is the wrong shape for the problem.
## Which one fits
- **You are an exec or founder who processes hundreds of personal emails a day.** Superhuman. This is its home turf, and the speed is real.
- **You want drafts in your own voice inside a beautiful client.** Superhuman. Voice and Tone Match plus the interface is the package you are paying for.
- **Your team answers the same operational questions daily in a shared inbox.** InboxPilot. Grounded drafts plus routing and opt-in auto-send is the actual fix, and flat pricing covers everyone.
- **You need replies grounded in your docs and policies, not just your writing style.** InboxPilot. Superhuman writes as you; it does not know your return policy.
- **You want the whole team on one tool without a client migration.** InboxPilot. It works inside the Gmail and Outlook accounts you already run.
- **You want both jobs done.** They barely overlap. Some companies put Superhuman in front of two executives and an email agent on the shared inboxes; just do the per-user math before rolling either out company-wide.
## Related reading
- [AI email assistant for executives](/blog/ai-email-assistant-for-executives): the personal-inbox side of this split, covered properly.
- [Shortwave pricing and an alternative](/blog/alternative-shortwave): the other AI-native client, same tradeoffs.
- [Best Fyxer AI alternatives](/blog/alternative-fyxer): when the personal tool is an assistant rather than a client.
- [AI email assistant for teams](/blog/ai-email-assistant-for-teams): what changes when the inbox is shared.
- [What an AI email agent actually does](/blog/ai-email-agent): the product category underneath this comparison.
- [RFQ and quote request automation](/use-cases/rfq-email-automation): how quote requests get read, priced, and answered from your own catalog.
If the inbox slowing you down is your own, Superhuman is worth a serious look, and its fans are not wrong about the speed. If it is the shared one your team answers all day, that is the gap [InboxPilot](/pricing) was built for, and the free plans 25 drafts a month are enough to test it on real email.
*InboxPilot is the publisher of this article and one of the two tools discussed.*
---
## How Sales Teams Close More Deals with Instant Lead Replies
Source: https://www.inboxpilot.co/blog/sales-team-instant-lead-replies
Published: 2025-01-23
HBR audited 2,241 firms: average lead response took 42 hours and 23% never replied. How sales teams send fast, accurate lead replies from Gmail and Outlook.
A lead fills out your contact form at 4:52 on a Friday afternoon. She is comparing three vendors, yours included, and her email asks two questions: rough pricing for a 20-person team, and whether you integrate with the tools she already runs. Your rep sees it Monday at 9:15, drafts a reply by 9:40, and gets back a polite "thanks, we went another direction."
Nothing about that loss was about the product. It was about 64 hours of silence in a purchase process that was moving at the speed of the fastest competitor. Sales teams call this speed to lead, and most teams lose on it not because reps are lazy but because inbound email is nobody's full-time job.
This post covers what the trustworthy research actually says about response time, why leads sit unanswered, and how to get an accurate first reply out in minutes from the Gmail or Outlook inbox your team already uses.
**Disclosure:** we make [InboxPilot](/solutions/sales-teams), an inbox-native AI email agent that drafts replies to inbound leads inside Gmail and Outlook. This post is about inbound response; if your problem is cold outbound sequences or phone-based SDR work, InboxPilot is the wrong tool and we say so below.
## TL;DR
- The audited numbers are damning enough: HBR's 2011 study of 2,241 companies found a 42-hour average first response and a 23% no-response rate. See [the numbers worth trusting](#the-speed-to-lead-numbers-worth-trusting).
- Leads sit because of [structural gaps](#why-inbound-leads-sit-unanswered), nights, weekends, rep capacity, context gathering, that hiring alone does not close.
- A good instant reply does three things: [acknowledges, answers, and asks](#what-a-good-instant-reply-contains) one qualifying question. It does not try to close.
- **[InboxPilot](#where-inboxpilot-fits-and-where-it-does-not)**, which is us, classifies inbound lead email and drafts grounded replies from your own pricing page, docs, and past threads, with [draft-and-approve by default](#draft-mode-or-auto-send).
- Measure the change with [response time and qualification rate](#how-to-measure-whether-it-worked), not vanity multipliers.
## The speed-to-lead numbers worth trusting
You have probably seen the big multipliers in vendor decks: contact rates 21 times higher, 100 times higher, conversion up 391 percent. Most of those figures trace to vendor lead-response studies that are old, methodologically fuzzy, or both, so we are not going to lean on them.
The number we will lean on is older but audited and published. In March 2011, Harvard Business Review reported an audit of 2,241 US companies ("The Short Life of Online Sales Leads") that found the average first response to an inbound web lead took 42 hours, 23% of companies never responded at all, and firms replying within an hour were roughly seven times more likely to qualify the lead than those replying an hour later ([HBR](https://hbr.org/2011/03/the-short-life-of-online-sales-leads), 2011).
Fifteen years on, treat the exact figures as directional. The two conclusions underneath them have not aged: most companies are far slower than they believe, and the first credible answer frames the shortlist. That second point is the practical one, because it means the bar you need to clear is set by your slowest competitor, and that bar is low.
## Why inbound leads sit unanswered
If speed mattered this much and were easy, everyone would be fast. Leads sit for structural reasons:
- **Nobody owns the first five minutes.** Inbound email lands in sales@ or a founder's inbox, and every rep assumes someone else saw it.
- **Leads arrive when reps do not work.** Evenings, weekends, and the other side of the world. The Friday-afternoon form fill is the canonical lost deal.
- **The first reply requires homework.** Answering "does it integrate with X, and what does it cost for 20 seats" means checking docs and pricing, so the easy emails get answered first and the valuable ones wait.
- **Volume is spiky.** A launch or a mention somewhere triples inbound for a week, and the queue backs up exactly when it matters most.
The traditional fixes each solve part of this. Hiring adds capacity but not coverage. Canned autoresponders add coverage but answer nothing ("We received your message and will respond shortly" is a receipt, not a reply). The gap is a first response that is both instant and substantive.
## What a good instant reply contains
The first reply's job is not to close the deal. It is to keep the buyer from booking a demo with someone else while yours waits. Three parts:
1. **Acknowledge specifically.** Reference what they actually asked, not a generic thanks-for-reaching-out.
2. **Answer what has a documented answer.** Pricing that is on your pricing page, integration facts that are in your docs, plan limits. If the answer is public, there is no reason to withhold it for a call.
3. **Ask one qualifying question and offer one next step.** Team size, timeline, or use case, plus a calendar link. One question, not a form's worth.
That structure is exactly what makes this automatable. Every input, the enquiry, the docs, the pricing, the calendar link, exists in writing before the lead ever emails.
## The workflow from form fill to approved reply
Here is the loop an inbox-native agent runs, end to end:
1. **A lead emails** sales@ at 4:52pm Friday asking about pricing for 20 people and an integration.
2. **The agent classifies it** as an inbound lead, distinct from support, billing, and spam, and routes it under your plain-English rules.
3. **It checks your sources**: pricing page, integration docs, past replies to similar questions, and whatever CRM context is connected.
4. **It drafts the reply**: answers the two questions from the documents, asks one qualifying question about timeline, and offers two demo slots.
5. **A person approves and sends**, or, for routine cases you have chosen to trust, it sends on its own and flags the thread for follow-up.
The important property is grounding. The draft can only say what your documents say, and when the answer is not in them, enterprise pricing, a legal question, a custom integration, it escalates to a rep instead of improvising. An instant wrong answer is worse than a slow right one.
## Draft mode or auto-send
Every workflow needs a decision: does the AI send, or does a person? The honest default is draft-and-approve. The AI writes, a rep reads and sends, and response time drops from hours to whenever someone next glances at the inbox, which is a large win with zero new risk.
Auto-send is the second step, not the first, and it should be opt-in per workflow. Reasonable candidates: acknowledgment-plus-scheduling replies, documented pricing questions, and after-hours first responses. Keep human approval on anything involving discounts, contracts, enterprise deals, or an obviously frustrated sender. Negative keywords make this mechanical: threads mentioning refunds, legal, or cancellation skip automation entirely.
## How to measure whether it worked
Skip the vanity multipliers and track four numbers you can pull from your own inbox and CRM:
| Metric | What it tells you |
|---|---|
| Time to first substantive reply | The headline number; measure median and after-hours separately |
| Percent of leads receiving any reply | HBR found 23% of companies never replied; make yours 100 |
| Lead-to-meeting conversion | Whether faster replies turn into booked calls |
| Rep time on first responses | The hours automation returned to actual selling |
Run the comparison honestly: measure two or three weeks of baseline before turning anything on. We are deliberately not quoting improvement percentages here, because the honest answer is that the lift depends on how slow you are today and how much of your inbound has documented answers.
## Where InboxPilot fits, and where it does not
InboxPilot is an inbox-native AI email agent: it works inside the Gmail or Outlook inbox your leads already write to, shared inboxes included, with no migration and no new interface for reps. It classifies inbound lead email, drafts replies grounded in your pricing page, docs, and past threads, routes by plain-English rules, and escalates when unsure. Drafts wait for approval by default; auto-send is per-workflow opt-in. It connects to Slack, Pipedrive, Notion, and custom APIs, so lead context can flow in and activity can flow out to your CRM. Pricing is flat by draft volume with unlimited seats on paid plans: free for 25 drafts a month, $29 Hobby, $149 Standard with 1,500 drafts and unlimited inboxes, $499 Pro for 12,000.
Where it does not fit: InboxPilot does not do cold outbound, so if your pipeline problem is sequencing and prospecting, you want a different tool. It is not a chat widget, not a phone or SDR dialer, and not a CRM. It is the layer that makes the inbound email you already get answer itself faster, with your team still holding the send button where it counts.
## Related reading
- [InboxPilot for sales teams](/solutions/sales-teams): lead reply automation, routing, and CRM handoff in more depth.
- [AI email automation by industry](/industries): the same first-response problem across our supported verticals.
- [Construction RFQ email automation](/blog/construction-rfq-email-automation): speed to lead where the lead is a quote request with plans attached.
- [Best shared inbox software for Gmail and Outlook](/blog/best-shared-inbox-software): where sales@ should live and how teams coordinate on it.
- [AI email for teams](/blog/ai-email-assistant-for-teams): keeping tone and accuracy consistent across every rep who touches the inbox.
- [RFQ and quote request automation](/use-cases/rfq-email-automation): how quote requests get read, priced, and answered from your own catalog.
If the deals you lose are the ones nobody answered fast enough, the fix is not another hire watching the inbox on Friday nights. Try InboxPilot free on 25 real leads and see what an instant, grounded first reply looks like on your own traffic.
---
## InboxPilot and Zendesk: Automate Email Before the Ticket
Source: https://www.inboxpilot.co/blog/inboxpilot-and-zendesk-integration
Published: 2024-03-01
How the InboxPilot Zendesk integration works: AI drafts grounded in your macros and help center, auto-triage and tags, and clean escalation paths.
Open a Zendesk queue on a Monday morning and look at what is actually in it. A password reset. Three where-is-my-order messages. A refund policy question the help center already answers. Then, somewhere in the pile, the genuinely hard ticket: an angry customer, a billing edge case, something that needs a human with context and judgment.
Zendesk is good at organizing that pile. What it does not change is who produces the answers. An agent still opens each ticket, finds the right macro, adjusts it, and sends, and the repetitive tier of the queue eats the hours that the hard tickets deserve.
That is the gap the InboxPilot Zendesk integration is built for. InboxPilot handles the repetitive email layer, before it becomes a ticket and inside the queue itself, and hands Zendesk the tickets that actually need an agent.
**Disclosure:** we make [InboxPilot](/integrations/zendesk), and this post explains how our own integration works, so it is not a neutral review. And Zendesk does real things InboxPilot does not: live chat, phone, a full omnichannel help desk. This post is about using both well, not replacing one with the other.
## TL;DR
- **The pairing in one line:** [InboxPilot](#what-inboxpilot-adds-to-zendesk) is an inbox-native AI email agent that clears the repetitive layer; Zendesk stays the system of record for tickets that need an agent.
- **Automate upstream.** InboxPilot answers routine email in Gmail or Outlook [before it becomes a ticket](#handle-email-before-it-becomes-a-ticket), with human approval by default.
- **Escalate cleanly.** Complex or low-confidence conversations are [routed into Zendesk](#route-the-complex-tickets-to-zendesk) with tags, priority, and a summary for the agent.
- **Setup is three steps**: connect, sync your macros and help center, describe workflows in plain English. See [the outline](#set-it-up-in-three-steps).
- **You may not need both.** Email-only support teams often run [InboxPilot alone](#inboxpilot-alone-or-inboxpilot-with-zendesk); chat, phone, and big agent teams are when Zendesk earns its seat.
## What InboxPilot adds to Zendesk
InboxPilot is an inbox-native AI email agent. It works inside Gmail and Outlook, including shared inboxes, reads incoming email, and drafts replies grounded in your company's own material: help docs, website, policies, and past email. Drafts wait for human approval by default, auto-send is opt-in per workflow, and it escalates when it is not confident.
Connected to Zendesk, that engine gets pointed at your support stack in two places:
**Upstream, in the inbox.** Most support "tickets" begin life as an email to support@. InboxPilot resolves the routine ones there, so they never enter the queue at all.
**Inside the queue.** For tickets that do land in Zendesk, InboxPilot drafts replies grounded in your Zendesk macros and help center, applies tags and priority as tickets arrive, and assigns them to the right group with a summary and the full thread context. Agents review and send instead of writing the same answer again.
Both halves run on workflows you describe in plain English, like "when a billing ticket comes in, draft a reply from our macros, tag it, and assign it to the billing group." No rules builder, no scripting.
## Handle email before it becomes a ticket
The cheapest ticket is the one that never gets created. Every routine email that turns into a Zendesk ticket picks up overhead on the way: it gets an ID, waits in a view, gets triaged, gets opened by an agent, and finally gets an answer the help center already contained.
InboxPilot intercepts that loop at the inbox. Sitting inside your Gmail or Outlook support address, it recognizes the repetitive categories, order status, password resets, policy questions, routine how-tos, and drafts a grounded reply on arrival. A person approves each draft by default. Once a workflow has proven itself, you can let that specific workflow auto-send while everything else stays on review.
The effect on Zendesk is subtraction. The queue that reaches your agents is smaller and denser: fewer copy-paste answers, more of the conversations that justify having trained agents in the first place. First response time improves on the routine tier too, because the reply is drafted the moment the email lands, not when an agent works down to it.
## Route the complex tickets to Zendesk
Automation earns trust by knowing what not to touch. InboxPilot is built to hand off rather than improvise, and the handoff is where Zendesk does what it is best at.
When a conversation is complex, sensitive, or outside what InboxPilot is confident about, an upset customer, a billing dispute, a thread with history, it escalates instead of sending. Routed into Zendesk, that conversation arrives as a proper ticket: tagged, prioritized, assigned to the right group, and carrying a summary with the full context, so the agent starts informed instead of scrolling.
The same plain-English rules control the routing: "anything mentioning a refund over $200 goes to the billing group as high priority," "flag threads from our largest accounts for a senior agent." Your escalation policy becomes a sentence, and every exception lands in front of a human with judgment.
The division of labor ends up clean. InboxPilot owns the repetitive layer. Zendesk owns the queue of exceptions, the SLAs, the reporting, and the channels beyond email.
## Set it up in three steps
1. **Connect Zendesk.** Authorize InboxPilot with a scoped [Zendesk connection](/integrations/zendesk) and choose the views and groups it should work across.
2. **Sync your knowledge.** InboxPilot indexes your Zendesk macros and help center, alongside your docs and website, so every draft stays on your approved answers.
3. **Describe your workflows.** Write the rules in plain English: which categories to draft, which tags and priorities to apply, and what escalates to which group. InboxPilot runs them on incoming email and new tickets.
Every draft stays on human review until you decide otherwise, so the safe starting point is to approve everything for a week, see where the drafts are reliable, and opt those workflows into auto-send one at a time.
## InboxPilot alone or InboxPilot with Zendesk
Not every team needs both halves of this pairing.
**InboxPilot alone fits when support is email.** If your customers write to a shared Gmail or Outlook address and your team answers there, InboxPilot covers triage, routing, and grounded drafting without a help desk in the stack. Many small and mid-size teams in this position never need ticket IDs at all, and skipping the help desk also skips its per-agent pricing.
**Add Zendesk when the queue is the product.** Live chat and phone support, a large agent team that needs managed views and SLAs, manager-grade reporting across channels: that is help desk territory, and Zendesk is one of the strongest options in it. InboxPilot deliberately does not do chat widgets, phone, or ticket queue management.
**Run both when you have both problems.** A real agent team on Zendesk plus a heavy repetitive email load is the case this integration exists for: InboxPilot shrinks and pre-drafts the queue, Zendesk manages what remains. Where Zendesk wins outright is covered below.
## Related reading
- [Zendesk integration](/integrations/zendesk): capabilities, setup, and FAQ for the integration itself.
- [InboxPilot vs Help Scout](/blog/helpscout-vs-inboxpilot): the same AI-agent-or-help-desk question against another support platform.
- [Gorgias alternative](/blog/gorgias-alternative): the ecommerce-flavored version of this decision.
- [AI support for support teams](/solutions/support-teams): how InboxPilot handles a support inbox end to end.
- [Order status email automation](/use-cases/order-status-email-automation): answering WISMO and shipping questions from your system of record.
If your Zendesk queue is mostly questions your macros already answer, the missing piece is not another view or trigger, it is drafting. You can [try InboxPilot free](https://www.inboxpilot.co/) on 25 drafts, connect Zendesk, and watch the repetitive tier of the queue start arriving pre-written.
# Legal
---
## InboxPilot Privacy Policy
Last updated: June 17, 2025
At InboxPilot, we respect your privacy and are committed to protecting your personal data. This privacy policy explains how we look after your personal data when you visit our website, use our services, or otherwise communicate with us — and it tells you about your privacy rights and how the law protects you.
## 1. Important information and who we are
### 1.1 Purpose of this privacy policy
This privacy policy aims to give you information on how InboxPilot collects and processes your personal data through your use of our website, our InboxPilot services, or otherwise when you communicate or interact with us in the course of business.
### 1.2 Controller
If you are a registered customer of InboxPilot, we act as the **data controller** of personal data about you and your use of InboxPilot, but as the **data processor** of personal data in the information you submit to InboxPilot to use InboxPilot's products and services (such as information about your emails, email accounts, connected integrations, and knowledge-base content). If we are the data processor of your personal data (i.e., not the data controller), please contact the controller party in the first instance to address your rights with respect to such data.
If you have any questions about this privacy policy, including any requests to exercise your legal rights referred to below, please contact us using the details set out below.
### 1.3 Contact details
We are: **InboxPilot** of 2810 N Church St PMB 16104, Wilmington, Delaware 19802-4447, USA.
If you need to get hold of us for any reason in connection with your personal data, please email us at [privacy@inboxpilot.co](mailto:privacy@inboxpilot.co) or [support@inboxpilot.co](mailto:support@inboxpilot.co).
If you are located in the United Kingdom or European Economic Area, you have the right to make a complaint at any time to your local supervisory authority. We would, however, appreciate the chance to deal with your concerns about privacy and data protection before you approach a regulator, so please contact us in the first instance.
### 1.4 Changes to the privacy policy and your duty to inform us of changes
This version was last updated on **June 17, 2025**. If you use our website or the InboxPilot services after any changes to this privacy policy have been posted, that means you agree to all of the changes. It is important that the personal data we hold about you is accurate and current. Please keep us informed if your personal data changes during your relationship with us.
## 2. The data we collect about you
We may create aggregated, de-identified, or anonymized data from the personal data we collect, including by removing information that makes the data personally identifiable to a particular user. We may use such aggregated, de-identified, or anonymized data and disclose it with third parties for our lawful business purposes, including to analyze, build, and improve the InboxPilot services and promote our business, provided that we will not disclose such data in a manner that could identify you.
We may collect, use, store, and transfer different kinds of personal data about you which we have grouped together as follows:
- **Contact Data** includes name, role at business, email address, and phone number.
- **Account Data** includes login credentials, profile picture or avatar, organization details, and subscription preferences.
- **Financial Data** includes billing information and payment card details (processed by our payment provider).
- **Correspondence Data** includes email correspondence with our team, support tickets, and notes of conversations where these express an opinion.
- **Usage Data** includes information about how you use our website or services, including feature usage and configuration settings.
- **Technical Data** includes internet protocol (IP) address, login data, browser type and version, time zone setting and location, browser plug-in types and versions, operating system and platform, and other technology on the devices you use to access this website or our services.
- **Email and Integration Data** includes message IDs, thread IDs, AI-generated draft and sent responses, and metadata necessary to provide our email automation services. We do not store full email content beyond what is required to deliver the service.
We explicitly do **not**:
- Store email attachments
- Sell your data to third parties
- Share data with information resellers
- Use your data for advertising or credit assessment
- Use data obtained through Google Workspace APIs to develop, improve, or train generalized AI or machine learning models
## 3. How is your personal data collected?
We use different methods to collect data from and about you including through:
1. **Direct interactions.** We collect the majority of your data through our InboxPilot products and services on our website, by email, over the phone, in person at meetings, or otherwise.
2. **Automated technologies or interactions.** As you interact with our website, we may automatically collect Technical Data about your browsing actions and patterns. We collect this personal data by using cookies and other similar technologies. You can set your browser to refuse all or some browser cookies, or to alert you when websites set or access cookies.
3. **Third parties or publicly available sources.** We may receive Technical Data about you from analytics providers with servers based outside of Europe.
## 4. How we use your personal data
We will only use your personal data when the law allows us to. Most commonly, we will use your personal data in the following circumstances:
- In anticipation of or in accordance with the terms of use or service agreement that we have with you;
- Where it is necessary for our legitimate interests (or those of a third party) in the operation of our business and we have made an objective assessment that your interests and fundamental rights do not override those interests (for example to manage our relationship with you, to improve the service that we offer, or to answer an enquiry you make to us); or
- Where we need to comply with a legal or regulatory obligation.
Please contact us if you need details about the specific legal ground we are relying on to process your personal data.
## 5. Gmail, Outlook, and connected account access
InboxPilot uses OAuth to connect to your Gmail, Outlook, and other supported accounts with the permissions necessary to read, draft, and send emails on your behalf. We are committed to ensuring the privacy and security of your data. Here is how we handle connected account data:
- **Email access.** We access your emails solely to provide AI drafting, triage, labeling, workflows, and automation features you configure.
- **Data minimization.** We store only what is necessary to operate the service, such as message IDs, thread IDs, and outgoing AI-generated responses for logging and quality assurance.
- **Data security.** All data interactions are encrypted and handled securely. We adhere to industry-standard security practices to protect your information.
- **User control.** You can revoke InboxPilot's access to your connected accounts at any time through your Google or Microsoft account settings, or by disconnecting the integration within InboxPilot.
## 6. Data shared with third-party AI models
### 6.1 Data shared with AI models
To provide email drafting, categorization, triage, and automation features, our service employs machine learning models using third-party AI providers, including OpenAI, LLC. We require our AI service providers to use your information only for the purpose of providing our service. We do not allow those providers to train their AI models using your data.
The following data types may be shared with these AI models:
- **Email content and data:** Subject lines, email body text, sender and recipient information (limited to what is required for the requested feature).
- **Knowledge-base and integration data:** Content from documents, websites, and connected tools you choose to ground replies in.
- **Calendar and CRM context:** Where you connect supported integrations, relevant event or contact context needed to draft accurate replies.
This data is processed for the sole purpose of delivering the services you request and is not used for any other functions within the AI models.
### 6.2 User consent for data sharing with AI models
Before sharing your data with our AI models, we seek your consent through our onboarding flow and account connection process. Significant changes to how we use AI processing will be communicated through updates to this policy and, where appropriate, in-product notices.
### 6.3 Third-party AI data retention
We configure third-party AI services to not retain or use your personal data, email content, or customer information for training their models. We use API configurations that disable data retention and training features where available, and we have contractual protections in place with AI providers that prohibit use of your data for model training or improvement.
## 7. Disclosures of your personal data
We will need to share your personal data with the parties set out below for the purposes set out in section 4 above:
- **Our service providers** acting as processors who may be based in the US or elsewhere outside the EEA and who provide us with cloud hosting, IT support, data storage, payment processing, email and integration services, customer support tooling, and language model services. Our current sub-processors include Amazon Web Services, Inc., Google LLC, OpenAI, LLC, Stripe, Inc., and Zendesk, Inc. (where used).
- **Analytics service providers** which may have servers based in the US for the purpose of analyzing user behavior on our website.
- **Third parties to whom we may choose to sell, transfer, or merge parts of our business or our assets.** Alternatively, we may seek to acquire other businesses or merge with them. If a change happens to our business, then the new owners may use your personal data in the same way as set out in this privacy policy.
We require all third parties to respect the security of your personal data and to treat it in accordance with the law. We do not allow our third-party service providers to use your personal data for their own purposes and only permit them to process your personal data for specified purposes and in accordance with our instructions.
For more detail on how we process data on your behalf, see our [Data Processing Agreement](/legal/dpa).
## 8. International transfers
A number of our service providers processing your personal data on our behalf are based in the US or elsewhere outside the EEA, so their processing of your personal data will involve a transfer of data outside the EEA.
Whenever we transfer your personal data out of the EEA, we ensure a similar degree of protection is afforded to it by ensuring that either:
- We have a specific contract with that processor in a form approved by the European Commission which ensures that the service provider gives your personal data the same protection it has in Europe; or
- If the provider is based in the US, it participates in an approved transfer mechanism such as the EU-US Data Privacy Framework or Standard Contractual Clauses.
Information we collect about you will also be processed in the United States. By using InboxPilot's services, you acknowledge that your personal information may be processed in the United States. Please contact us if you want further information on the specific mechanism used by us when transferring your personal data out of the EEA.
## 9. Data security
We have put in place appropriate security measures to prevent your personal data from being accidentally lost, used, or accessed in an unauthorized way, altered, or disclosed. In addition, we limit access to your personal data to those employees, agents, contractors, and other third parties who have a business need to know. They will only process your personal data on our instructions and they are subject to a duty of confidentiality.
Our security measures include:
- Encryption of data in transit and at rest
- Secure cloud infrastructure with industry-standard protections
- Regular security assessments and updates
- Access controls, authentication mechanisms, and audit logging
We have put in place procedures to deal with any suspected personal data breach and will notify you and any applicable regulator of a breach where we are legally required to do so.
## 10. How long will you use my personal data for?
- We will only retain your personal data for as long as necessary to fulfill the purposes we collected it for, including for the purposes of satisfying any legal, accounting, or reporting requirements.
- To determine the appropriate retention period for personal data, we consider the amount, nature, and sensitivity of the personal data, the potential risk of harm from unauthorized use or disclosure of your personal data, the purposes for which we process your personal data and whether we can achieve those purposes through other means, and the applicable legal requirements.
- Outgoing AI-generated emails, message IDs, and thread IDs may be retained for service functionality and quality assurance while your account is active.
- In some circumstances, you can ask us to delete your data (see below for further information).
- In some circumstances we may anonymize your personal data (so that it can no longer be associated with you) for research or statistical purposes in which case we may use this information indefinitely without further notice to you.
You may request deletion of your data by contacting our Privacy Team at [support@inboxpilot.co](mailto:support@inboxpilot.co), using deletion tools in your account settings, or revoking access through your connected account provider.
## 11. Your legal rights
You have the right in certain circumstances to:
- Request access to your personal data (a "data subject access request").
- Request correction of the personal data that we hold about you.
- Request erasure of your personal data.
- Object to processing of your personal data where we are relying on a legitimate interest (or those of a third party) and there is something about your particular situation which makes you want to object to processing on this ground as you feel it impacts on your fundamental rights and freedoms.
- Request restriction of processing of your personal data.
- Request the transfer of your personal data to you or to a third party.
More information on these rights and when they apply is available from the [UK Information Commissioner's Office](https://ico.org.uk/for-organisations/guide-to-the-general-data-protection-regulation-gdpr/individual-rights/).
You will not have to pay a fee to access your personal data (or to exercise any of the other rights). We may need to request specific information from you to help us confirm your identity and ensure your right to access your personal data (or to exercise any of your other rights). This is a security measure to ensure that personal data is not disclosed to any person who has no right to receive it. We may also contact you to ask you for further information in relation to your request to speed up our response.
We try to respond to all legitimate requests within one month. Occasionally it may take us longer than a month if your request is particularly complex or you have made a number of requests. In this case, we will notify you and keep you updated.
## 12. Children's data
We do not knowingly attempt to solicit or receive information from children.
## 13. Questions, concerns, or complaints
If you have questions, concerns, or complaints regarding this Privacy Policy or our data practices, please contact us at:
**InboxPilot**
2810 N Church St PMB 16104
Wilmington, Delaware 19802-4447
[privacy@inboxpilot.co](mailto:privacy@inboxpilot.co)
Thank you for choosing InboxPilot. We are committed to ensuring your privacy and providing a secure platform.
---
## Terms of Service
Last updated: June 17, 2025
THESE TERMS OF SERVICE (the "Agreement") GOVERN YOUR RECEIPT, ACCESS TO, AND USE OF THE SERVICES PROVIDED BY INBOXPILOT ("InboxPilot"). BY (A) PURCHASING ACCESS TO THE SERVICE THROUGH AN ONLINE ORDERING PROCESS THAT REFERENCES THIS AGREEMENT, (B) SIGNING UP FOR A FREE OR PAID ACCESS PLAN FOR THE SERVICE VIA A PLATFORM THAT REFERENCES THIS AGREEMENT, OR (C) CLICKING A BOX INDICATING ACCEPTANCE, YOU AGREE TO BE BOUND BY THE TERMS OF THIS AGREEMENT. THE INDIVIDUAL ACCEPTING THIS AGREEMENT DOES SO ON BEHALF OF A COMPANY OR OTHER LEGAL ENTITY ("Customer"); SUCH INDIVIDUAL REPRESENTS AND WARRANTS THAT THEY HAVE THE AUTHORITY TO BIND SUCH ENTITY AND ITS AFFILIATES TO THIS AGREEMENT. IF THE INDIVIDUAL ACCEPTING THIS AGREEMENT DOES NOT HAVE SUCH AUTHORITY, OR IF THE ENTITY DOES NOT AGREE WITH THESE TERMS AND CONDITIONS, SUCH INDIVIDUAL MUST NOT ACCEPT THIS AGREEMENT AND MAY NOT USE THE SERVICES. CAPITALIZED TERMS HAVE THE MEANINGS SET FORTH HEREIN. THE PARTIES AGREE AS FOLLOWS:
## 1. The Service
### 1.1 Service Description
InboxPilot owns and provides a cloud-based artificial intelligence service offering automated email triage, drafting, labeling, workflows, and customer support inside Gmail and Outlook (the "Service"). Anything the Customer (including Users) configures, customizes, uploads, or otherwise utilizes through the Service is considered a "User Submission." Customer is solely responsible for all User Submissions it contributes to the Service. Additional terms regarding User Submissions, including ownership, are in Section 9.2 below. The Service may include templates, scripts, documentation, and other materials that assist Customer in using the Service ("InboxPilot Content"). Customers will not receive or have access to the underlying code or software of the Service (collectively, the "Software") nor receive a copy of the Software itself.
### 1.2 Customer's Subscription
Subject to the terms of this Agreement, Customer may purchase a subscription to, and has the right to access and use, the Service as specified in one or more ordering screens agreed upon by the parties through InboxPilot's website or service portal that reference this Agreement and describe the business terms related to Customer's subscription ("Order(s)"). All subscriptions are for the period described in the applicable Order ("Subscription Period"). Use of and access to the Service is permitted only for individuals authorized by the Customer and solely for Customer's own internal business purposes, not for the benefit of any third party ("Users").
### 1.3 InboxPilot's Ownership
InboxPilot owns the Service, Software, InboxPilot Content, Documentation, and anything else provided by InboxPilot to the Customer (collectively, the "InboxPilot Materials"). InboxPilot retains all rights, title, and interest (including all intellectual property rights) in and to the InboxPilot Materials, all related and underlying technology, and any updates, enhancements, modifications, or fixes thereto, as well as all derivative works of or modifications to any of the foregoing. No implied licenses are granted under this Agreement, and any rights not expressly granted to the Customer are reserved by InboxPilot.
### 1.4 Permissions
The Service includes customizable settings allowing Users to grant permissions to other Users to perform various tasks within the Service ("Permissions"). It is solely the Customer's responsibility to set and manage all Permissions, including determining which Users can set such Permissions. Accordingly, InboxPilot has no responsibility for managing Permissions and no liability for Permissions set by the Customer and its Users. The Customer may provide access to the Service to its Affiliates, in which case all rights granted and obligations incurred under this Agreement shall extend to such Affiliates. The Customer represents and warrants it is fully responsible for any breaches of this Agreement by its Affiliates and has the authority to negotiate this Agreement on behalf of its Affiliates. The Customer is also responsible for all payment obligations under this Agreement, regardless of whether the use of the Service is by the Customer or its Affiliates. Any claim by an Affiliate against InboxPilot must be brought by the Customer, not the Affiliate. An "Affiliate" of a party means any entity directly or indirectly controlling, controlled by, or under common control with that party, where "control" means the ownership of more than fifty percent (50%) of the voting shares or other equity interests.
## 2. Restrictions
### 2.1 Customer's Responsibilities
The Customer is responsible for all activity on its account and those of its Users, except where such activity results from unauthorized access due to vulnerabilities in the Service itself. The Customer will ensure its Users are aware of and comply with the obligations and restrictions in this Agreement, bearing responsibility for any breaches by a User.
### 2.2 Use Restrictions
The Customer agrees not to, and not to permit Users or third parties to, directly or indirectly: (a) modify, translate, copy, or create derivative works based on the Service; (b) reverse engineer, decompile, or attempt to discover the source code or underlying ideas of the Service, except as permitted by law; (c) sublicense, sell, rent, lease, distribute, or otherwise commercially exploit the Service; (d) remove proprietary notices from the Service; (e) use the Service in violation of laws or regulations; (f) attempt unauthorized access to or disrupt the Service; (g) use the Service to support products competitive to InboxPilot; (h) test the Service's vulnerability without authorization. If the Customer's use of the Service significantly harms InboxPilot or the Service's security or integrity, InboxPilot may suspend access to the Service, taking reasonable steps to notify the Customer and resolve the issue promptly.
### 2.3 API Access Restrictions
InboxPilot may provide access to APIs as part of the Service. InboxPilot reserves the right to set and enforce usage limits on the APIs, and the Customer agrees to comply with such limits. InboxPilot may also suspend or terminate API access at any time.
## 3. Third-Party Services
The Service may interface with third-party products, services, or applications that are not owned or controlled by InboxPilot ("Third-Party Services"), including email providers (such as Google Gmail and Microsoft Outlook), CRMs, help desks, and other integrations. Customers have the discretion to utilize these Third-Party Services in conjunction with our Service. Should the integration of the Service with any Third-Party Service require it, customers will be responsible for providing their login information to InboxPilot solely for the purpose of enabling InboxPilot to deliver its Service. Customers affirm that they have the authority to provide such information without violating any terms and conditions governing their use of the Third-Party Services. InboxPilot does not endorse any Third-Party Services. Customers acknowledge that this Agreement does not cover the use of Third-Party Services, and they may need to enter into separate agreements with the providers of these services. InboxPilot expressly disclaims all representations and warranties concerning Third-Party Services. Customers must direct any warranty claims or other disputes directly to the providers of the Third-Party Services. The use of Third-Party Services is at the customer's own risk. InboxPilot shall not be liable for any issues arising from the use or inability to use Third-Party Services.
## 4. Financial Terms
### 4.1 Fees
Customers are required to pay for access to and use of the Service as detailed in the applicable order ("Fees"). All Fees will be charged in the currency stated in the order or, if no currency is specified, in U.S. dollars. Payment obligations are non-cancellable and, except as explicitly stated in this Agreement, Fees are non-refundable. InboxPilot reserves the right to modify its Fees or introduce new fees at its discretion. Customers have the option not to renew their subscription if they disagree with any revised fees.
### 4.2 Payment
InboxPilot, either directly or through its third-party payment processor ("Payment Processor"), will bill the customer for the Fees using the credit card or ACH payment information provided by the customer. InboxPilot reserves the right to charge the customer's credit card or ACH payment method for any services provided under the order, including recurring Fees. It is the customer's responsibility to ensure that InboxPilot has current and accurate credit card or ACH payment information. Failure to provide accurate information may lead to a suspension of access to the Services. InboxPilot also reserves the right to offset any Fees owed by the customer. If the customer pays through a Payment Processor, such transactions will be subject to the Payment Processor's terms, conditions, and privacy policies, in addition to this Agreement. InboxPilot is not responsible for errors or omissions by the Payment Processor. InboxPilot reserves the right to correct any errors made by the Payment Processor, even if payment has already been requested or received. If the customer authorizes, through accepting an order, recurring charges will be automatically applied to the customer's payment method without further authorization until the customer terminates this Agreement or updates their payment method.
### 4.3 Taxes
Fees do not include any taxes, levies, duties, or similar governmental assessments, including value-added, sales, use, or withholding taxes, imposed by any jurisdiction (collectively, "Taxes"). Customers are responsible for paying all Taxes associated with their purchases. If InboxPilot is obligated to pay or collect Taxes for which the customer is responsible, InboxPilot will invoice the customer for such Taxes unless the customer provides InboxPilot with a valid tax exemption certificate authorized by the appropriate taxing authority beforehand. For clarity, InboxPilot is solely responsible for taxes based on its income, property, and employees.
### 4.4 Failure to Pay
If a customer fails to pay any Fees when due, InboxPilot may suspend access to the Service until overdue amounts are paid. InboxPilot is authorized to attempt charging the customer's payment method multiple times if an initial charge is unsuccessful. If a customer believes they have been incorrectly billed, they must contact InboxPilot within sixty (60) days from the first billing statement showing the error to request an adjustment or credit. Upon receiving a dispute notice, InboxPilot will review and provide the customer with a written decision, including evidence supporting this decision. If it is determined that the billed amounts are due, the customer must pay these amounts within ten (10) days of receiving InboxPilot's written decision.
## 5. Term and Termination
### 5.1 Agreement Term and Renewals
Subscriptions to access and use InboxPilot's service ("Service") commence on the start date specified on the applicable Order ("Subscription Start Date") and continue for the duration of the Subscription Period. Customers may opt not to renew their Subscription Period by notifying InboxPilot at [support@inboxpilot.co](mailto:support@inboxpilot.co) (provided that InboxPilot confirms such cancellation in writing) or by modifying their subscription through the Customer's account settings within the Service. This Agreement takes effect on the first day of the Subscription Period and remains effective for the duration of the Subscription Period stated on the Order, including any renewals of the Subscription Period and any period that the Customer is using the Service, even if such use is not under a paid Order ("Term"). If this Agreement is terminated by either party, it will automatically terminate all Orders. If a Customer cancels or chooses not to renew their paid subscription to the Service, the Customer's subscription will still be accessible but will automatically be downgraded to a version of the Service with reduced features and functionality that InboxPilot offers to unpaid subscribers ("Free Version"). Should this Agreement be terminated by either InboxPilot or the Customer, or should the Customer delete its workspace within the Service, access to the Free Version will be revoked.
### 5.2 Termination
Either party may terminate this Agreement with written notice to the other party if the other party materially breaches this Agreement and such breach is not cured within thirty (30) days after receipt of such notice. InboxPilot may terminate a Customer's access to the Free Version at any time upon notice.
### 5.3 Effect of Termination
If the Customer terminates this Agreement due to an uncured breach by InboxPilot, InboxPilot will refund any unused, prepaid Fees for the remainder of the then-current Subscription Period. If InboxPilot terminates this Agreement due to an uncured breach by the Customer, the Customer will pay any unpaid Fees covering the remainder of the then-current Subscription Period after the date of termination. No termination will relieve the Customer of the obligation to pay any Fees payable to InboxPilot for the period prior to the effective date of termination. Upon termination, all rights and licenses granted by InboxPilot will cease immediately, and the Customer will lose access to the Service. Within thirty (30) days of termination for cause, upon the Customer's request, or if the Customer deletes its workspace within the Service, InboxPilot will delete the Customer's User Information, including passwords, files, and submissions, unless an earlier deletion is requested in writing. For Customers using the Free Version, InboxPilot may retain User Submissions and User Information to facilitate continued use. InboxPilot may delete all User Submissions and User Information if an account remains inactive for more than one (1) year.
### 5.4 Survival
Sections titled "InboxPilot's Ownership", "Third-Party Services", "Financial Terms", "Term and Termination", "Warranty Disclaimer", "Limitation of Liability", "Confidentiality", "Data" and "General Terms" will survive any termination or expiration of this Agreement.
## 6. Warranties and Disclaimers
### 6.1 Warranties
Customers represent and warrant that all User Submissions submitted by Users comply with all applicable laws, rules, and regulations.
### 6.2 Warranty Disclaimer
EXCEPT AS EXPRESSLY STATED HEREIN, THE SERVICES AND ALL RELATED COMPONENTS AND INFORMATION ARE PROVIDED ON AN "AS IS" AND "AS AVAILABLE" BASIS WITHOUT ANY WARRANTIES OF ANY KIND, AND INBOXPILOT EXPRESSLY DISCLAIMS ANY AND ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. CUSTOMERS ACKNOWLEDGE THAT INBOXPILOT DOES NOT WARRANT THAT THE SERVICES WILL BE UNINTERRUPTED, TIMELY, SECURE, OR ERROR-FREE. GIVEN THE PROBABILISTIC NATURE OF MACHINE LEARNING, USE OF THE SERVICE MAY IN SOME SITUATIONS PRODUCE OUTPUT THAT IS INACCURATE OR INCOMPLETE. CUSTOMERS REMAIN RESPONSIBLE FOR REVIEWING AI-GENERATED OUTPUT BEFORE SENDING OR RELYING ON IT. SOME JURISDICTIONS DO NOT ALLOW THE DISCLAIMER OF CERTAIN WARRANTIES, SO THE FOREGOING DISCLAIMERS MAY NOT APPLY TO THE EXTENT PROHIBITED BY LAW.
## 7. Limitation of Liability
NOTWITHSTANDING ANY PROVISION TO THE CONTRARY, INBOXPILOT WILL NOT BE LIABLE FOR ANY INDIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL DAMAGES, OR DAMAGES BASED ON THE USE OR ACCESS, INTERRUPTION, DELAY, OR INABILITY TO USE THE SERVICE, LOST REVENUES OR PROFITS, LOSS OF BUSINESS OR GOODWILL, DATA CORRUPTION, OR SYSTEM FAILURES, REGARDLESS OF THE LEGAL THEORY. FURTHER, INBOXPILOT'S TOTAL LIABILITY WILL NOT EXCEED THE TOTAL FEES PAID OR PAYABLE BY THE CUSTOMER FOR THE SERVICE DURING THE TWELVE (12) MONTHS PRIOR TO THE CLAIM. THESE LIMITATIONS APPLY REGARDLESS OF WHETHER INBOXPILOT HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
## 8. Confidentiality
### 8.1 Definition
Each party (the "Receiving Party") recognizes that the other party (the "Disclosing Party") may share business, technical, or financial information pertaining to the Disclosing Party's operations that, due to the nature of the information and the context of disclosure, is reasonably considered confidential ("Confidential Information"). For InboxPilot, Confidential Information includes non-public details about features, functionality, and performance of the Service. For Customers, Confidential Information comprises User Information and User Submissions. This Agreement, along with all related Orders, is considered Confidential Information of both parties. However, Confidential Information does not include information that: (a) becomes publicly available without breaching any duty to the Disclosing Party; (b) was known to the Receiving Party before disclosure by the Disclosing Party without breaching any duty; (c) is received from a third party without breaching any duty; or (d) was independently developed by the Receiving Party without using the Disclosing Party's Confidential Information.
### 8.2 Protection and Use of Confidential Information
The Receiving Party must: (a) protect the Disclosing Party's Confidential Information with at least the same degree of care it uses for its own similar information, but no less than a reasonable level of care; (b) restrict access to Confidential Information to personnel, affiliates, subcontractors, agents, consultants, legal advisors, financial advisors, and contractors ("Representatives") who need this information in relation to this Agreement and who are bound by confidentiality obligations similar to those in this Agreement; (c) not disclose any Confidential Information to third parties without prior written consent from the Disclosing Party, except as expressly stated herein; and (d) use the Confidential Information solely to fulfill obligations under this Agreement. This does not prevent sharing of Agreement terms or the other party's name with potential investors or buyers under standard confidentiality terms.
### 8.3 Compelled Access or Disclosure
If required by law, the Receiving Party may access or disclose the Disclosing Party's Confidential Information, provided that it notifies the Disclosing Party in advance (when legally permissible) and offers reasonable help, at the Disclosing Party's expense, if the Disclosing Party wants to contest the disclosure.
### 8.4 Feedback
Customers may occasionally offer feedback on the Service ("Feedback"). InboxPilot may choose to incorporate this Feedback into its services. Customers grant InboxPilot a royalty-free, worldwide, perpetual, irrevocable, fully transferable, and sublicensable license to use, disclose, modify, create derivative works from, distribute, display, and exploit any Feedback as InboxPilot sees fit, without any obligation or restriction, except for not identifying the Customer as the source of Feedback.
## 9. Data
### 9.1 User Information
Customers and their Users must provide information like names, email addresses, usernames, IP addresses, browsers, and operating systems ("User Information") to access the Service. Customers authorize InboxPilot and its subcontractors to store, process, and retrieve User Information as part of the Service usage. Customers guarantee they have the necessary rights to provide User Information to InboxPilot for processing as described in this Agreement. Customers are liable for their User Information and any unauthorized use of their credentials.
### 9.2 User Submissions
Customers grant InboxPilot a non-exclusive, worldwide, royalty-free, transferable license to use, process, and display User Submissions solely to provide the Service. Beyond the rights granted here, Customers retain all rights to User Submissions, with no implied licenses under this Agreement.
### 9.3 Service Data
InboxPilot collects data on Service performance and operation ("Service Data") as Customers use the Service. Provided Service Data is aggregated and anonymized, without disclosing any personal information, InboxPilot can use this data freely. InboxPilot owns all rights to Service Data, but will not identify Customers or Users as its source.
### 9.4 Data Protection
InboxPilot maintains reasonable security practices to protect Customer Data, including User Submissions and User Information. Nonetheless, Customers are responsible for securing their systems and data. InboxPilot processes all Customer Data in accordance with its [Privacy Policy](/legal/privacy) and [Data Processing Agreement](/legal/dpa).
### 9.5 AI and Third-Party Language Models
InboxPilot uses third-party AI providers, including large language model providers, to power email drafting, triage, and automation features. InboxPilot may share User Submissions and related data with such providers solely to deliver the Service. InboxPilot configures these providers not to retain or use Customer data for training their models, and Customer data is not used to train InboxPilot's own generalized models. For more detail, see our [Privacy Policy](/legal/privacy).
## 10. General Terms
### 10.1 Publicity
With prior written consent from the Customer, InboxPilot is allowed to identify the Customer and use and display the Customer's name, logo, trademarks, or service marks on InboxPilot's website and in InboxPilot's marketing materials. This will help in demonstrating the clientele and user base of InboxPilot without compromising any confidential information or privacy rights of the Customer.
### 10.2 Force Majeure
InboxPilot shall not be liable for any failure or delay in performing its obligations hereunder caused by events beyond its reasonable control, including but not limited to failures of third-party hosting or utility providers, strikes (excluding those involving InboxPilot's employees), riots, fires, natural disasters, wars, terrorism, or government actions.
### 10.3 Changes
InboxPilot acknowledges that its service is an evolving, subscription-based product. To enhance customer experience, InboxPilot reserves the right to make modifications to the Service. However, InboxPilot commits to not materially reducing the core functionality provided to Customers. Furthermore, InboxPilot may modify the terms of this Agreement unilaterally, provided that Customers are notified at least thirty (30) days before such changes take effect, with changes posted prominently on the [InboxPilot terms page](/legal/terms).
### 10.4 Relationship of the Parties
This Agreement does not create a partnership, franchise, joint venture, agency, fiduciary, or employment relationship between InboxPilot and the Customer. Both parties are independent contractors, maintaining their respective operations and autonomy while cooperating under the terms laid out in this Agreement.
### 10.5 No Third-Party Beneficiaries
This Agreement is strictly between InboxPilot and the Customer. It is not intended to benefit any third party, nor shall any third party have the right to enforce any of its terms, directly or indirectly.
### 10.6 Email Communications
Notices under this Agreement will be communicated via email, although InboxPilot may choose to provide notices through the Service instead. Notices to InboxPilot must be directed to [support@inboxpilot.co](mailto:support@inboxpilot.co), while notices to Customers will be sent to the email addresses provided by them through the Service. Notices are considered delivered the next business day after emailing or the same day if provided through the Service.
### 10.7 Amendment and Waivers
No modifications to this Agreement will be effective unless in writing and signed or acknowledged by authorized representatives of both parties. Neither party's delay or failure to exercise any right under this Agreement will be deemed a waiver of that right. Waivers must also be in writing and signed by the party granting the waiver.
### 10.8 Severability
Should any provision of this Agreement be found unlawful or unenforceable by a court, it will be modified to the minimum extent necessary to make it lawful or enforceable, while the remaining provisions continue in full effect.
### 10.9 Assignment
Neither party may assign or delegate their rights or obligations under this Agreement without the other party's prior written consent, except that InboxPilot may do so without consent in cases of mergers, acquisitions, corporate reorganizations, or sales of substantially all assets. Any unauthorized assignment will be void. This Agreement binds and benefits the parties, their successors, and permitted assigns.
### 10.10 Governing Law and Venue
This Agreement will be governed by the laws of the State of Delaware, USA, excluding its conflict of laws principles. Disputes arising under this Agreement will be resolved in the state or federal courts in New Castle County, Delaware, to which both parties consent to jurisdiction and venue. There is a waiver of any right to a jury trial for disputes arising under this Agreement. The prevailing party in any enforcement action is entitled to recover its reasonable costs and attorney fees.
### 10.11 Entire Agreement
This Agreement, including any referenced documents and Orders, constitutes the full agreement between InboxPilot and the Customer, superseding all prior discussions, agreements, and understandings of any nature.
---
## Data Processing Addendum
Last updated: June 17, 2025
This Data Processing Addendum ("DPA") supplements the [Terms of Service](/legal/terms) (the "Agreement") entered into by and between Customer (as defined in the Agreement) and InboxPilot of 2810 N Church St PMB 16104, Wilmington, Delaware 19802-4447, United States ("InboxPilot"). By executing the Agreement, Customer enters into this DPA on behalf of itself and, to the extent required under applicable Data Protection Laws, in the name and on behalf of its Affiliates, if any. This DPA incorporates the terms of the Agreement, and any terms not defined in this DPA shall have the meaning set forth in the Agreement. The parties therefore agree as follows:
## 1. Definitions
1. **Affiliate** means (i) an entity of which a party directly or indirectly owns fifty percent (50%) or more of the stock or other equity interest, (ii) an entity that owns at least fifty percent (50%) or more of the stock or other equity interest of a party, or (iii) an entity which is under common control with a party by having at least fifty percent (50%) or more of the stock or other equity interest of such entity and a party owned by the same person, but such entity shall only be deemed to be an Affiliate so long as such ownership exists.
2. **Authorized Sub-Processor** means a third party who has a need to know or otherwise access Customer's Personal Data to enable InboxPilot to perform its obligations under this DPA or the Agreement, and who is either (1) listed in Exhibit B or (2) subsequently authorized under Section 4.2 of this DPA.
3. **InboxPilot Account Data** means personal data that relates to InboxPilot's relationship with Customer, including the names or contact information of individuals authorized by Customer to access Customer's account and billing information of individuals that Customer has associated with its account. InboxPilot Account Data also includes any data InboxPilot may need to collect for the purpose of managing its relationship with Customer, identity verification, or as otherwise required by applicable laws and regulations.
4. **InboxPilot Usage Data** means Service usage data collected and processed by InboxPilot in connection with the provision of the Services, including without limitation data used to identify the source and destination of a communication, activity logs, and data used to optimize and maintain performance of the Services, and to investigate and prevent system abuse.
5. **Data Exporter** means Customer.
6. **Data Importer** means InboxPilot.
7. **Data Protection Laws** means any applicable laws and regulations in any relevant jurisdiction relating to the use or processing of Personal Data including: (i) the California Consumer Privacy Act as amended by the CPRA ("CCPA"), (ii) the General Data Protection Regulation (Regulation (EU) 2016/679) ("EU GDPR") and the EU GDPR as it forms part of the law of England and Wales by virtue of section 3 of the European Union (Withdrawal) Act 2018 (the "UK GDPR") (together, collectively, the "GDPR"), (iii) the Swiss Federal Act on Data Protection, (iv) the UK Data Protection Act 2018; and (v) the Privacy and Electronic Communications (EC Directive) Regulations 2003; in each case, as updated, amended or replaced from time to time. The terms "Data Subject", "Personal Data", "Personal Data Breach", "processing", "processor," "controller," and "supervisory authority" shall have the meanings set forth in the GDPR.
8. **EU SCCs** means the standard contractual clauses approved by the European Commission in Commission Decision 2021/914 dated 4 June 2021, for transfers of personal data to countries not otherwise recognized as offering an adequate level of protection for personal data by the European Commission (as amended and updated from time to time), as modified by Section 6.2 of this DPA.
9. **ex-EEA Transfer** means the transfer of Personal Data, which is processed in accordance with the GDPR, from the Data Exporter to the Data Importer (or its premises) outside the European Economic Area (the "EEA"), and such transfer is not governed by an adequacy decision made by the European Commission in accordance with the relevant provisions of the GDPR.
10. **ex-UK Transfer** means the transfer of Personal Data covered by Chapter V of the UK GDPR, which is processed in accordance with the UK GDPR and the Data Protection Act 2018, from the Data Exporter to the Data Importer (or its premises) outside the United Kingdom (the "UK"), and such transfer is not governed by an adequacy decision made by the Secretary of State in accordance with the relevant provisions of the UK GDPR and the Data Protection Act 2018.
11. **Services** shall have the meaning set forth in the Agreement.
12. **Standard Contractual Clauses** means the EU SCCs and the UK SCCs.
13. **UK SCCs** means the EU SCCs, as amended by the UK Addendum.
## 2. Relationship of the Parties; Processing of Data
1. The parties acknowledge and agree that with regard to the processing of Personal Data, Customer may act either as a controller or processor and, except as expressly set forth in this DPA or the Agreement, InboxPilot is a processor. Customer shall, in its use of the Services, at all times process Personal Data, and provide instructions for the processing of Personal Data, in compliance with Data Protection Laws. Customer shall ensure that the processing of Personal Data in accordance with Customer's instructions will not cause InboxPilot to be in breach of the Data Protection Laws. Customer is solely responsible for the accuracy, quality, and legality of (i) the Personal Data provided to InboxPilot by or on behalf of Customer, (ii) the means by which Customer acquired any such Personal Data, and (iii) the instructions it provides to InboxPilot regarding the processing of such Personal Data. Customer shall not provide or make available to InboxPilot any Personal Data in violation of the Agreement or otherwise inappropriate for the nature of the Services, and shall indemnify InboxPilot from all claims and losses in connection therewith.
2. InboxPilot shall not process Personal Data (i) for purposes other than those set forth in the Agreement and/or Exhibit A, (ii) in a manner inconsistent with the terms and conditions set forth in this DPA or any other documented instructions provided by Customer, including with regard to transfers of personal data to a third country or an international organization, unless required to do so by Supervisory Authority to which InboxPilot is subject; in such a case, InboxPilot shall inform the Customer of that legal requirement before processing, unless that law prohibits such information on important grounds of public interest, or (iii) in violation of Data Protection Laws. Customer hereby instructs InboxPilot to process Personal Data in accordance with the foregoing and as part of any processing initiated by Customer in its use of the Services.
3. The subject matter, nature, purpose, and duration of this processing, as well as the types of Personal Data collected and categories of Data Subjects, are described in Exhibit A to this DPA.
4. Following completion of the Services, at Customer's choice, InboxPilot shall return or delete Customer's Personal Data, unless further storage of such Personal Data is required or authorized by applicable law. If return or destruction is impracticable or prohibited by law, rule or regulation, InboxPilot shall take measures to block such Personal Data from any further processing (except to the extent necessary for its continued hosting or processing required by law, rule or regulation) and shall continue to appropriately protect the Personal Data remaining in its possession, custody, or control.
5. **CCPA.** Except with respect to InboxPilot Account Data and InboxPilot Usage Data, the parties acknowledge and agree that InboxPilot is a service provider for the purposes of the CCPA (to the extent it applies) and is receiving personal information from Customer in order to provide the Services pursuant to the Agreement, which constitutes a business purpose. InboxPilot shall not sell any such personal information. InboxPilot shall not retain, use or disclose any personal information provided by Customer pursuant to the Agreement except as necessary for the specific purpose of performing the Services for Customer pursuant to the Agreement, or otherwise as set forth in the Agreement or as permitted by the CCPA.
## 3. Confidentiality
1. InboxPilot shall ensure that any person it authorizes to process Personal Data has agreed to protect Personal Data in accordance with InboxPilot's confidentiality obligations in the Agreement. Customer agrees that InboxPilot may disclose Personal Data to its advisers, auditors or other third parties as reasonably required in connection with the performance of its obligations under this DPA, the Agreement, or the provision of Services to Customer.
## 4. Authorized Sub-Processors
1. Customer acknowledges and agrees that InboxPilot may (1) engage its Affiliates as well as the Authorized Sub-Processors on the List (defined below) to access and process Personal Data in connection with the Services and (2) from time to time engage additional third parties for the purpose of providing the Services, including without limitation the processing of Personal Data. By way of this DPA, Customer provides general written authorization to InboxPilot to engage sub-processors as necessary to perform the Services.
2. A list of InboxPilot's current Authorized Sub-Processors (the "List") is set forth in Exhibit B. InboxPilot will provide at least ten (10) days' notice before enabling any third party other than existing Authorized Sub-Processors to access or participate in the processing of Personal Data, by updating the List and notifying Customer at the email address associated with Customer's account. Customer may object to such an engagement by informing InboxPilot in writing within ten (10) days of receipt of such notice, provided such objection is in writing and based on reasonable grounds relating to data protection. Customer acknowledges that certain sub-processors are essential to providing the Services and that objecting to the use of a sub-processor may prevent InboxPilot from offering the Services to Customer.
3. If Customer reasonably objects to an engagement in accordance with Section 4.2, and InboxPilot cannot provide a commercially reasonable alternative within a reasonable period of time, Customer may discontinue the use of the affected Service by providing written notice to InboxPilot. Discontinuation shall not relieve Customer of any fees owed to InboxPilot under the Agreement.
4. If Customer does not object to the engagement of a third party in accordance with Section 4.2 within ten (10) days of notice by InboxPilot, that third party will be deemed an Authorized Sub-Processor for the purposes of this DPA.
5. InboxPilot will enter into a written agreement with the Authorized Sub-Processor imposing on the Authorized Sub-Processor data protection obligations comparable to those imposed on InboxPilot under this DPA with respect to the protection of Personal Data. In case an Authorized Sub-Processor fails to fulfill its data protection obligations under such written agreement with InboxPilot, InboxPilot will remain liable to Customer for the performance of the Authorized Sub-Processor's obligations under such agreement.
## 5. Security of Personal Data
1. Taking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of processing as well as the risk of varying likelihood and severity for the rights and freedoms of natural persons, InboxPilot shall maintain appropriate technical and organizational measures to ensure a level of security appropriate to the risk of processing Personal Data. Exhibit C sets forth additional information about InboxPilot's technical and organizational security measures.
## 6. Transfers of Personal Data
1. The parties agree that InboxPilot may transfer Personal Data processed under this DPA outside the EEA, the UK, or Switzerland as necessary to provide the Services. Customer acknowledges that InboxPilot's primary processing operations take place in the United States, and that the transfer of Customer's Personal Data to the United States is necessary for the provision of the Services to Customer. If InboxPilot transfers Personal Data protected under this DPA to a jurisdiction for which the European Commission has not issued an adequacy decision, InboxPilot will ensure that appropriate safeguards have been implemented for the transfer of Personal Data in accordance with Data Protection Laws.
2. **Ex-EEA Transfers.** The parties agree that ex-EEA Transfers are made pursuant to the EU SCCs, which are deemed entered into (and incorporated into this DPA by this reference) and completed as follows:
- Module One (Controller to Controller) of the EU SCCs apply when InboxPilot is processing Personal Data as a controller pursuant to Section 9 of this DPA.
- Module Two (Controller to Processor) of the EU SCCs apply when Customer is a controller and InboxPilot is processing Personal Data for Customer as a processor pursuant to Section 2 of this DPA.
- Module Three (Processor to Sub-Processor) of the EU SCCs apply when Customer is a processor and InboxPilot is processing Personal Data on behalf of Customer as a sub-processor.
3. For each module, where applicable the following applies:
- The optional docking clause in Clause 7 does not apply.
- In Clause 9, Option 2 (general written authorization) applies, and the minimum time period for prior notice of sub-processor changes shall be as set forth in Section 4.2 of this DPA;
- In Clause 11, the optional language does not apply;
- In Clause 17 (Option 1), the EU SCCs will be governed by Delaware law.
- In Clause 18(b), disputes will be resolved before the courts of New Castle County, Delaware;
- Exhibit B to this DPA contains the information required in Annex I and Annex III of the EU SCCs;
- Exhibit C to this DPA contains the information required in Annex II of the EU SCCs; and
- By entering into this DPA, the parties are deemed to have signed the EU SCCs incorporated herein, including their Annexes.
4. **Ex-UK Transfers.** The parties agree that ex-UK Transfers are made pursuant to the UK SCCs, which are deemed entered into and incorporated into this DPA by reference, and amended and completed in accordance with the UK International Data Transfer Addendum to the EU Standard Contractual Clauses issued by the UK Information Commissioner's Office.
5. **Supplementary Measures.** In respect of any ex-EEA Transfer or ex-UK Transfer, InboxPilot shall notify Customer without undue delay if InboxPilot receives a request from a government authority requiring disclosure of Customer's Personal Data, unless such notification is prohibited by law. InboxPilot shall not voluntarily disclose Personal Data to any law enforcement or government agency except as required by law.
## 7. Rights of Data Subjects
1. InboxPilot shall, to the extent permitted by law, notify Customer upon receipt of a request by a Data Subject to exercise the Data Subject's right of access, rectification, erasure, data portability, restriction or cessation of processing, withdrawal of consent to processing, and/or objection to being subject to processing that constitutes automated decision-making (such requests individually and collectively "Data Subject Request(s)"). If InboxPilot receives a Data Subject Request in relation to Customer's data, InboxPilot will advise the Data Subject to submit their request to Customer and Customer will be responsible for responding to such request, including, where necessary, by using the functionality of the Services.
2. InboxPilot shall, at the request of the Customer, and taking into account the nature of the processing applicable to any Data Subject Request, apply appropriate technical and organizational measures to assist Customer in complying with Customer's obligation to respond to such Data Subject Request and/or in demonstrating such compliance, where possible, provided that (i) Customer is itself unable to respond without InboxPilot's assistance and (ii) InboxPilot is able to do so in accordance with all applicable laws, rules, and regulations. Customer shall be responsible to the extent legally permitted for any costs and expenses arising from any such assistance by InboxPilot.
## 8. Actions and Access Requests; Audits
1. InboxPilot shall, taking into account the nature of the processing and the information available to InboxPilot, provide Customer with reasonable cooperation and assistance where necessary for Customer to comply with its obligations under the GDPR to conduct a data protection impact assessment and/or to demonstrate such compliance, provided that Customer does not otherwise have access to the relevant information. Customer shall be responsible to the extent legally permitted for any costs and expenses arising from any such assistance by InboxPilot.
2. InboxPilot shall maintain records sufficient to demonstrate its compliance with its obligations under this DPA, and retain such records for a period of three (3) years after the termination of the Agreement.
3. Upon Customer's written request at reasonable intervals, and subject to reasonable confidentiality controls, InboxPilot shall, either (i) make available for Customer's review copies of certifications or reports demonstrating InboxPilot's compliance with prevailing data security standards applicable to the processing of Customer's Personal Data, or (ii) allow Customer's independent third party representative to conduct an audit or inspection of InboxPilot's data security infrastructure and procedures that is sufficient to demonstrate InboxPilot's compliance with its obligations under Data Protection Laws, provided that (a) Customer provides reasonable prior written notice of any such request for an audit and such inspection shall not be unreasonably disruptive to InboxPilot's business; (b) such audit shall only be performed during business hours and occur no more than once per calendar year; and (c) such audit shall be restricted to data relevant to Customer. Customer shall be responsible for the costs of any such audits or inspections, including without limitation a reimbursement to InboxPilot for any time expended for on-site audits. InboxPilot may satisfy audit requests via SOC 2 Type II or equivalent certification.
4. InboxPilot shall immediately notify Customer if an instruction, in InboxPilot's opinion, infringes the Data Protection Laws or Supervisory Authority.
5. In the event of a Personal Data Breach, InboxPilot shall, without undue delay, inform Customer of the Personal Data Breach and take such steps as InboxPilot in its sole discretion deems necessary and reasonable to remediate such violation (to the extent that remediation is within InboxPilot's reasonable control).
6. In the event of a Personal Data Breach, InboxPilot shall, taking into account the nature of the processing and the information available to InboxPilot, provide Customer with reasonable cooperation and assistance necessary for Customer to comply with its obligations under the GDPR with respect to notifying (i) the relevant Supervisory Authority and (ii) Data Subjects affected by such Personal Data Breach without undue delay.
7. The obligations described in Sections 8.5 and 8.6 shall not apply in the event that a Personal Data Breach results from the actions or omissions of Customer.
## 9. InboxPilot's Role as a Controller
The parties acknowledge and agree that with respect to InboxPilot Account Data and InboxPilot Usage Data, InboxPilot is an independent controller, not a joint controller with Customer. InboxPilot will process InboxPilot Account Data and InboxPilot Usage Data as a controller (i) to manage the relationship with Customer; (ii) to carry out InboxPilot's core business operations, such as accounting, audits, tax preparation and filing and compliance purposes; (iii) to monitor, investigate, prevent and detect fraud, security incidents and other misuse of the Services, and to prevent harm to Customer; (iv) for identity verification purposes; (v) to comply with legal or regulatory obligations applicable to the processing and retention of Personal Data to which InboxPilot is subject; and (vi) as otherwise permitted under Data Protection Laws and in accordance with this DPA and the Agreement. InboxPilot may also process InboxPilot Usage Data as a controller to provide, optimize, and maintain the Services, to the extent permitted by Data Protection Laws. Any processing by InboxPilot as a controller shall be in accordance with InboxPilot's [Privacy Policy](/legal/privacy).
## 10. Conflict
In the event of any conflict or inconsistency among the following documents, the order of precedence will be: (1) the applicable terms in the Standard Contractual Clauses; (2) the terms of this DPA; (3) the Agreement; and (4) InboxPilot's Privacy Policy. Any claims brought in connection with this DPA will be subject to the terms and conditions, including, but not limited to, the exclusions and limitations set forth in the Agreement.
## 11. Execution and Adoption
1. This DPA is incorporated by reference into the Agreement and becomes effective upon Customer's acceptance of the InboxPilot Terms of Service.
2. By using the Service, Customer acknowledges and agrees to be bound by the terms of this DPA. No separate signature is required for this DPA to be effective.
3. If Customer requires a signed DPA for compliance purposes, Customer may contact [support@inboxpilot.co](mailto:support@inboxpilot.co) to request a countersigned copy. Upon receipt of a signed DPA, the signed version will supersede this automatically incorporated DPA.
---
## Exhibit A — Details of Processing
**Nature and Purpose of Processing:** InboxPilot will process Customer's Personal Data as necessary to provide the Services under the Agreement, for the purposes specified in the Agreement and this DPA, and in accordance with Customer's instructions as set forth in this DPA. The nature of processing includes, without limitation:
- Receiving data, including collection, accessing, retrieval, recording, and data entry
- Processing email content and metadata to provide AI drafting, triage, labeling, and automation
- Protecting data, including restricting, encrypting, and security testing
- Holding data, including storage, organization, and structuring
- Erasing data, including destruction and deletion
- Sharing data, including disclosure to subprocessors as permitted in this DPA
**Duration of Processing:** InboxPilot will process Customer's Personal Data as long as required (i) to provide the Services to Customer under the Agreement; (ii) for InboxPilot's legitimate business needs; or (iii) by applicable law or regulation.
**Categories of Data Subjects:** Customer's employees, consultants, contractors, agents, and Customer's end users, customers, or contacts whose data is processed through the Services.
**Categories of Personal Data:** InboxPilot processes Personal Data contained in InboxPilot Account Data, InboxPilot Usage Data, and any Personal Data provided by Customer (including email content, subject lines, sender and recipient information, message and thread IDs, knowledge-base documents, integration data, names, email addresses, job titles, IP addresses, and billing information) or collected by InboxPilot in order to provide the Services.
**Sensitive Data or Special Categories of Data:** Customers are prohibited from providing sensitive personal data or special categories of data to InboxPilot through the Services unless expressly agreed in writing and permitted by applicable law.
---
## Exhibit B — Sub-Processors and Transfer Details
### Authorized Sub-Processors
| Sub-Processor | Purpose | Location |
| --- | --- | --- |
| Amazon Web Services, Inc. | Cloud hosting and infrastructure | USA |
| Google LLC | Gmail OAuth and related services | USA |
| Microsoft Corporation | Outlook OAuth and related services | USA |
| OpenAI, LLC | AI language model services | USA |
| Stripe, Inc. | Payment processing | USA |
| Zendesk, Inc. | Customer support ticketing (where used) | USA |
**Updated:** June 17, 2025
### Description of the Transfer
| Field | Details |
| --- | --- |
| **Data Subjects** | As described in Exhibit A of the DPA |
| **Categories of Personal Data** | As described in Exhibit A of the DPA |
| **Nature of the Processing** | As described in Exhibit A of the DPA |
| **Purposes of Processing** | As described in Exhibit A of the DPA |
| **Duration of Processing** | As described in Exhibit A of the DPA |
| **Frequency of the transfer** | As necessary to perform all obligations and rights with respect to Personal Data as provided in the Agreement or DPA |
| **Recipients of Personal Data** | Authorized Sub-Processors listed above |
### Data Exporter
**Name:** Customer, as stated and defined in the applicable Order under the Agreement
**Address:** Customer's registered business address and any address provided to InboxPilot when Customer uses the Services
**Contact:** The contact of the person that accepts and binds Customer to the Agreement
**Role:** Controller
### Data Importer
**Name:** InboxPilot
**Address:** 2810 N Church St PMB 16104, Wilmington, Delaware 19802-4447, United States
**Contact:** [privacy@inboxpilot.co](mailto:privacy@inboxpilot.co)
**Activities relevant to the data transferred:** As described in Section 2 of the DPA
**Role:** Processor (and Controller for InboxPilot Account Data and InboxPilot Usage Data as described in Section 9)
---
## Exhibit C — Technical and Organizational Security Measures
| **Measure** | **Details** |
| --- | --- |
| Encryption of personal data | Personal data is encrypted in transit using TLS 1.2+ and at rest using industry-standard AES-256 encryption. |
| Confidentiality, integrity, and availability | InboxPilot maintains access controls, authentication requirements, and monitoring to protect processing systems and services. |
| Backup and recovery | Production data is backed up on a regular schedule. Backups are encrypted and tested periodically. |
| User identification and authorization | Production access requires multi-factor authentication where applicable. Access is granted on a least-privilege basis. |
| Physical security | InboxPilot uses cloud infrastructure providers that maintain industry-standard physical and environmental controls. |
| Logging and monitoring | Security-relevant events are logged and reviewed. Incident response procedures are maintained. |
| Data minimization | InboxPilot processes only the data necessary to provide the Services configured by Customer. |
| Data retention and deletion | Customer data is deleted or returned upon termination in accordance with this DPA, subject to legal retention requirements. |
| Personnel security | Personnel with access to Personal Data are subject to confidentiality obligations and security training. |
| Sub-processor security | InboxPilot requires Authorized Sub-Processors to implement appropriate technical and organizational measures through written agreements. |
---
## Related Documents
- [Privacy Policy](/legal/privacy)
- [Terms of Service](/legal/terms)