Fin vs. Zendesk AI agents: Comparing handoffs and billing while keeping your helpdesk
Teams with an existing support system should first identify the product line, then check human handoffs and billable results. Fin can charge for configured handoffs, while only Verified resolutions draw on Zendesk's new allowance. Keeping your helpdesk still involves data integration, existing seats, and reopened conversations.
Teams that already have a customer support workspace should compare Fin and Zendesk AI agents by first asking where people take over, then which results appear on the bill. If you already use Zendesk, its native AI agents are worth evaluating first. If you want to keep another helpdesk, Fin has a clearly documented add-on route, but Zendesk also offers a cross-platform option through the independent Forethought suite. This is not simply a choice between an open and a closed platform.
The more important question is whether you want to pay for fully automated resolution or are also willing to pay when AI completes preliminary work before handing off to a person. Fin outcomes can include the latter. Under Zendesk's current tier rules, an Assisted escalation that a person ultimately resolves does not draw on the resolution allowance. This distinction can matter more to your budget than the resolution rates the two vendors advertise.
First, identify the product you are buying
According to the official documentation current Zendesk AI agents can use knowledge sources, generative procedures, scripted dialogues, authorized actions, and API integrations. The former Essential offering is now legacy functionality, scheduled to become unavailable on December 10, 2026. The unified offering documentation explicitly states that the AI agent - Advanced add-on is no longer required to use all AI agent features. Old plan comparisons are therefore not a sound basis for placing an order.
Forethought AI agents by Zendesk is a separate suite that can serve teams not using the Zendesk platform. Specify the product line when requesting a quote. Forethought's capabilities, contracts, and prices should not all be treated as default components of Zendesk's native offering.
Keeping your helpdesk does not eliminate integration work
Fin's public pricing lists a plan for use with an existing helpdesk: US$0.99 per outcome, with a minimum of 50 outcomes per month and no additional Fin seat, platform, or integration fees. You still retain the subscription for your existing helpdesk. Moving to Intercom Helpdesk instead means accounting separately for its seats. This comparison focuses on text-based customer support, without mixing in sales lead qualification or voice pricing.
For teams keeping Zendesk, the current Fin ticket documentation describes handling email-originated tickets, with access subject to plan eligibility and administrator permissions in both systems. “Supports Zendesk” does not mean every ticket type or attachment can be handled. When a customer requests a person, the configured handoff step causes Fin to unassign itself, reopen the ticket, and return it to the Zendesk team.
This route avoids moving the human support workspace, but adds responsibility for another configuration layer and for passing data between systems. The data synchronization documentation requires field-setting steps to precede the handoff. Attributes originating in Zendesk are read-only in Fin, and regular synchronization runs hourly. A pilot should check whether the human agent receives the order number, issue category, and necessary context, rather than merely whether the bot says it is transferring the conversation.
If your existing system is Zendesk, the reason to test its native offering first is to narrow the scope of cross-system handoff checks, not because it has already been shown to answer more accurately. If your system is not Zendesk, ask Fin and Forethought to demonstrate the handoff inside your existing helpdesk, then compare their quotes. The native Zendesk costs discussed here cannot simply be applied to Forethought.
The same human handoff can have different billing reasons
Under the Fin outcomes rules, a resolution can be counted when the customer confirms satisfaction or stops requesting help after an answer. Successfully executing a Procedure configured to hand off to a person or workflow can also create a billable outcome. Ordinary default escalations, workspace escalation rules, and failed Procedures are not equivalent to billable Procedure handoffs. Each conversation is charged at most once. If a customer returns to the same conversation for further assistance after it was counted as resolved, that resolution is deducted, even across billing periods.
Do not simplify these rules to “any human involvement makes it free.” Fin's FAQ also describes a billable exception when information collection is enabled and a customer who requested help goes silent without supplying further information. Keep these edge cases in your acceptance sample and check the actual outcome, rather than only who eventually closes the ticket.
Zendesk's resolution tiers, introduced on May 18, 2026, distinguish three categories: Assisted escalation, where AI contributes before a person completes the resolution; Contained resolution, where no further help is requested but model verification fails; and Verified resolution, which passes verification. The first two do not draw on the allowance. Customer silence alone is therefore insufficient to establish a billable result.
Verification also has time boundaries. Email conversations end 72 hours after the first email. Messaging conversations end 2 hours after the first message by default, with an extension to 72 hours available on request. This is not a blanket guarantee against repeat charges forever. The new tier documentation reviewed does not provide a cross-billing-period deduction commitment for reopened conversations as explicit as Fin's. Ask sales to clarify reopened conversations and repeat contact across channels. The usage documentation provides ticket-level tracing and a dispute route, and explicitly states that deleting a ticket does not reverse usage.
Calculate costs using your own ticket mix
Zendesk is still transitioning billing models. Its account identification guidance tells administrators to establish the applicable model by checking whether they see Automated resolutions or Resolution usage and Resolution allowance in the admin interface. Do not treat a legacy resolution-pack unit price as a universal quote for the new tiers. Prices in the official upgrade examples are placeholders; actual rates require a quote.
The new model's default allowance is a currency pool: US$2 per paid agent seat per month for Suite Team and US$5 for Suite Professional, with a maximum default allowance of US$5,000 per year across all plans. Unused monthly allowance does not roll over. For example, 10 Suite Professional seats provide US$50 in monthly allowance, not 50 free resolutions. Beyond the allowance, contract rates matter. Overage billing is allowed by default; the native offering can be set to pause when the allowance runs out, routing more requests to people.
Consider a purely hypothetical monthly budget: 500 billable Fin resolutions plus 100 billable Procedure handoffs at US$0.99 each total US$594, before existing helpdesk and human support costs. If 500 of these qualify as Verified in Zendesk and the other 100 are Assisted escalations, the latter do not draw on the allowance, while the former consume the currency pool at contract rates. Without that quote, this calculation cannot establish which is cheaper. The two vendors may also classify the same conversations differently.
Teams already using Zendesk that prioritize paying usage fees only after AI fully resolves an issue can therefore start by establishing a baseline with its native offering. Teams willing to pay for preliminary work and planned human handoffs while retaining their existing helpdesk can include Fin in a pilot. Use the same set of real requests to compare complete resolutions, ordinary escalations, configured handoffs, and reopened conversations, checking the bill and human takeover time case by case. This is an analysis of official documentation, not a logged-in product test. Your own auditable results, rather than vendor resolution-rate rankings, should determine whether to adopt either option.
Content note:This article is based on publicly available information and is intended as a reference for evaluating tools. Features, pricing, and related policies may change at any time; please refer to the latest official information.
Original source:support.zendesk.com