What are the best AI agents for email and support inboxes in 2026?

Vendors sell inbox agents as chat that lives in email. I buy them as workers.

The thread is the job. If the refund never posted, the agent failed, even if the sentence was kind.

I rank seven products that still had official pages in August 2026. The score is close-the-job, then handoff, then permissions, then traces. If a page did not publish a price I say so, and I did not invent a review.

Rank close-the-job, then handoff, permissions, traces

An inbox agent gets a thread, a short tool list, and a finish line you can check. I score products on whether they close that job, how they pass work to a person, what they may touch, and whether you can read every step. Chat polish is not on the card.

The definition is what is an inbox agent: a loop that reads the thread, calls tools, writes into systems of record, and stops. A draft in the composer is assist. A closed ticket with the order edited is the job.

r/AI_Agents compared graph workflows to agent loops on an inbox-triage job on 21 Aug 2026.

Anthropic’s January 2026 post Demystifying evals for AI agents draws the line I use in production. The transcript is the talk. The outcome is the state of the world.

OpenAI Agents SDK documentation in 2026 names the primitives I want from a packaged agent: tools, handoffs, guardrails, and tracing. Tracing records generations, tool calls, handoffs, and guardrails. If a vendor cannot show those, I treat the product as chat with a send button.

• Close-the-job: did the refund post, the order move, the ticket close on a rule you wrote, or did it only draft a paragraph.
• Handoff: when it stops, does a person receive the goal, the evidence, the next action, and the limits, or a raw dump of the thread.
• Permissions: can you split draft from send, lookup from refund, one inbox from another.
• Traces: can you inspect sources, tool calls, and why it escalated, and replay that on a frozen set before go-live.

How to evaluate AI agents is the same method. Freeze last month’s threads.

Run more than once. Score the artifact. A vendor resolution rate with no transcript is a press claim.

Seven inbox agents, same four columns

The table is the route, and job is the finish line. Human gate is where a person still owns send or spend, tools are what official pages say it may call, and notes are the catches I could verify, including price when the official page published one.

I left off personal mail copilots that only draft. Freshdesk Freddy AI Agent and Salesforce Agentforce Service-on-email both exist in 2026. They did not beat these seven on the four criteria, so they are not in the table.

Sierra

Sierra is the packaged agent whose public pages name actions in a system of record, a summary handoff, and guardrails. That is why it sits at the top of this table, not because I ran a bake-off I can publish.

The Meet your agent page names email next to phone, chat, and SMS. Beyond Q&A is the section that matters.

The agent is supposed to process an exchange or change a reservation by connecting to order management and CRM. When it cannot resolve, it gathers key details, summarizes, and hands off so the team does not start from zero.

Permissions sit in two places: Agent Studio for journeys, knowledge, and simulations, and the Agent SDK for goals, guardrails, and composable skills. Sierra’s 2026 blog also describes release governance (checks, approvals, staged rollout) around those guardrails.

Traces, as published: simulations, Insights, reporting on case resolution. Ask in the security review whether you can export every tool call for a frozen set of threads.

Price: Sierra’s site says you pay for a job well done. I did not find a public dollar amount on the official pages I opened.

Treat any number on a call as a quote. Buy Sierra when the job is a real action in a system of record and you will fund guardrails and simulations. Skip it if you need a self-serve seat this afternoon.

Fin AI Agent

Fin AI Agent publishes Procedures, Simulations, answer inspection, and a billed handoff in public help. That is the close-the-job loop I could verify without a sales call. The grants live in Procedures, not in an SDK I can fork, and that is the trade against Sierra, not a medal.

Intercom’s Fin AI Agent explained article is the primary source. Fin over email is a named deploy: full thread context, email-shaped answers, spam filters, escalate when it needs to.

Procedures follow Fin Tasks: a document-style editor that can include code and data connectors, meant for cancel-an-order or refund-a-subscription. Data connectors reach external systems so Fin can act, not only retrieve.

You configure how and when Fin triages or hands off. Fin also auto-hands off on high-risk content: self-harm, harmful content involving minors, jailbreaks, high-risk medical, legal, or financial advice.

A Procedure can end in a resolution or a handoff. From 12 March 2026 Fin bills on outcomes. The June 2026 outcomes article lists Procedure handoff as a billable type.

Test before live: Simulations, batch testing, answer inspection. After live: Performance dashboard, conversation monitoring in the inbox.

Price I could verify: the official meter is $0.99 per outcome. Fin Voice is sales-quoted.

Standalone Fin on another helpdesk is $0.99 per outcome with a 50-outcome monthly minimum and no seat fee ($49 base with 50 included), per intercom.com/pricing. Read Fin’s definition of outcome before you model cost.

Zendesk AI Agents

Zendesk is the pick when the artifact is a ticket. Official developer docs describe escalate-with-full-context and custom APIs, and Relate 2026 said AI agents are generally available across messaging, email, voice, and backend systems. The ticket is a finish line you can check, though the public trace is thinner than Fin’s inspection loop.

I rank it third. Zendesk’s AI Agents developer docs, still live in 2026, list what you can build: CRM and third-party APIs, session parameters, webhooks, escalate to humans with full context or custom logic, export conversation data.

You must have the AI agents - Advanced add-on to use those APIs. That add-on is the permission boundary Zendesk publishes for developers.

Agent Builder (early access around Relate 2026) is the no-code path to custom agents that can delegate. An AI agent conversation simulator EAP showed up in Zendesk’s August 2026 EAP list. Treat EAPs as not-yet-production unless your account says they are on.

Copilot is a different SKU: drafts, summaries, triage inside Agent Workspace. zendesk.com/pricing lists Copilot at $50 per agent per month billed annually. That is not the autonomous inbox agent.

Advanced AI agents is Talk to Sales on the same page. I did not copy a dollar amount Zendesk did not publish. Get the resolution meter in writing.

Ada

Ada is the enterprise email closer with a published handoff map into other inboxes. Official pages describe Actions as API calls, Playbooks as multi-step SOPs, and email as a channel that keeps context across replies. I rank it fourth because permissions are strong on paper, and Ada does not publish a price I can put in the table.

The email product page describes autonomous resolution and Playbooks on live data. The email-handoff integrations page names the gate: transfer conversation and ticket context into Amazon Connect, Dixa, Freshworks, Genesys, Gladly, Zendesk-class stacks. That is handoff as a product, not a hope.

Ada’s 26 August 2026 release notes add MCP tools: connect your own server, then choose per tool whether the agent acts as a shared account or as the customer after sign-in. Change sets stage configuration before it is live.

A 10 August 2026 note adds an audit log with interface-level attribution. Knowledge is what it may say.

Actions check an order or update an account. That split is the point.

I did not find a public dollar amount on Ada’s official product pages. Ask for the meter in the contract, and whether email sits on the same meter as chat. Buy Ada when you will keep Zendesk or Salesforce as the human inbox and you need change sets plus an audit log.

Decagon

Decagon still publishes email as a first-class channel and, in August 2026, a copilot that hands a summary to the person who takes over. Close-the-job and handoff improved on official posts in 2026. Public price is still absent, so this row is a mechanism check, not a winner.

The homepage describes Agent Operating Procedures: natural-language workflows you iterate without an engineering ticket. Chat, voice, and email sit on one layer.

Browser Actions (5 August 2026) let the agent act on web systems with no clean API. Tools close jobs.

They also break jobs. The AOP has to say when those tools are allowed.

Decagon Assist (19 August 2026) is a copilot for the human: summaries, suggested responses, in-tool actions. The summary covers the previous conversation with the Decagon agent, so the person is not rebuilding the thread live.

Demand the tool list in the same handoff, not only the prose. Official traces are testing, observability, experimentation. Ask for export of AOP version and tool calls.

Official pages do not publish a dollar amount. Customer stories quote resolution figures.

Those are their numbers, not mine. Buy Decagon when you want one agent across chat, voice, and email, and you will write AOPs as the source of truth.

Front Autopilot

Front Autopilot is the shared-inbox agent whose published human gate I could verify: auto-send on or off, Step in to stop the run, escalation that moves inbox and tags. Copilot, the assist SKU, is a different product. Do not confuse the auto-send toggle on Autopilot with a seat that only drafts.

Front’s Autopilot help article is the source. Playbooks mix defined steps and natural language: collect information, reply, application request via Connectors, comments, ticket status, conditions.

You pick shared inboxes and you test before enabling auto-replies. Official language support for Playbooks is English. Individual inboxes are out of scope.

The Automatically send messages toggle is the draft-versus-send split. Escalation fires on technical error or when the customer asks for a human.

Copilot, separately, inherits the teammate’s permissions and cannot see another person’s individual inbox. Playbooks write comments as they run.

The AI replies hub lists drafts and sent Autopilot replies with sources. The Autopilot report tracks resolution and Playbook completion.

Official Autopilot price on front.com/pricing is starting at $0.05 per conversation, sales-gated. I did not find $0.39 handoff on the official pricing page. Confirm the meter in writing.

Email resolution is no teammate follow-up within 72 hours. You are not charged if a teammate cancels, the customer asks for a human, or Front fails.

Copilot is $20 per seat per month on Starter and Professional, included on current Enterprise. Playbooks were still on a rolling waitlist in the help article I opened.

Gorgias AI Agent

Gorgias is on this list as a Shopify closer, not as a B2B inbox. Official pages describe track, return, refund, and order edit. If your desk is SaaS mail, skip this row.

The official information page (updated June 2026) and the AI Agent docs agree. One agent, two roles: Shopping Assistant before purchase, Support Agent after.

Email, chat, and SMS are in scope. Actions run on live Shopify data.

Docs say AI Agent is not supported on BigCommerce, Magento, or WooCommerce. If you are not on Shopify, this row does not apply.

You set rules for topics that always go to a human, situations that escalate automatically, and how edge cases are handled. Guidance is the instruction layer.

Ask the engineer to show the grant for refund versus lookup before you turn it loose. Dedicated AI Agent reports exist. The 2026 public roadmap lists ticket replay as a theme, which tells you it is not the default yet.

Price from the official information page: you pay when AI Agent fully resolves a conversation on its own. A human stepping in does not count.

Most plans $0.90 per AI-resolved conversation on annual billing, $1.00 monthly. Confirm on gorgias.com/pricing.

Helpdesk volume is a separate meter. Buy Gorgias for a Shopify support finish line. Skip it for B2B SaaS or any store not on Shopify.

Run an eval before you buy

Do not pick from this list by the demo. Freeze real threads, run the agent more than once, and score the outcome in the system of record. Anthropic’s 2026 eval post is the method, and OpenAI Agents SDK tracing is the log I want underneath it.

Demystifying evals for AI agents (9 January 2026) is written for this class of worker. Conversational agents maintain state, call tools, and act mid-thread.

Their example support task grades a state check (ticket resolved, refund processed), required tool calls (verify identity, process refund under a cap, send confirmation), and a turn cap. Tone can be a rubric. Tone is not the primary score.

They also name pass^k: the chance that every trial succeeds. Inbox agents need consistency, not one lucky reply.

A 75 percent per-trial success rate is about 42 percent if you demand three clean trials. Run the same thread more than once before you promote a Procedure, a Playbook, or an AOP.

1. 01

   Freeze last month’s threads

   Twenty is a start. Fifty is better. Write the finish line on each. If the set changes every week, the score is noise.

2. 02

   Grade outcome, then transcript

   Did the refund post. Then read the tool list. Do not require one exact path unless the path is a legal requirement. Grade the world, not the choreography.

3. 03

   Require the trace the SDK would have given you

   OpenAI Agents SDK traces, in the 2026 docs, wrap the run, each generation, each function call, each guardrail, each handoff. Ask the vendor for the same objects.

4. 04

   Split capability evals from regression evals

   Capability starts hard and should have room to climb. Regression should sit near a full pass and catch drift. That is Anthropic’s language. It is how you stop the agent from getting worse after a prompt change nobody can prove.

5. 05

   Keep a baseline

   Last week’s agent, a macro, or a careful human. If the new loop does not beat the baseline on the frozen set, it does not go live. Arena, in my shop, is the floor: same job, competing traces, artifact as the score.

When to build your own

Buy when the vendor’s tools match the job and you can see the trace. Build when the grant, the packet, or the log is not for sale. OpenAI Agents SDK is the runtime I reach for first, and the companion build page is the desk procedure, not a reason to skip the eval.

How to build an inbox agent is the companion to this list. The SDK’s 2026 overview still fits on one screen. Agents are models with instructions and tools.

Handoffs delegate to specialists. The docs even use customer support: order status, refunds, FAQs.

Guardrails validate input, output, and function tools. Tracing is on by default.

Human-in-the-loop can pause a run for approval. That is the permission split I want: the agent may draft, a person or a second guardrail may send.

Build when you must own the grants. An agent that can read the inbox should not also wire money.

Build when handoff has to be a packet you specify. Build when the trace has to land in your logs so you can grade it on every commit.

You then own eval, runtime, and on-call. That is the job. It is not a weekend wrapper.

If you buy, still write the finish line as if you were building. Put it in the contract.

Name the tools, the human gate, and the trace fields. Then run the frozen set.

The seven above can close real inbox work. None of them are done because the composer looks finished.