Intercom combines a support workspace with Fin, while LoopReply focuses on configurable AI Agents, knowledge, and conversation workflows. A migration decision should separate replacing the customer-facing Agent from replacing the helpdesk your team operates.
LoopReply publishes this guide. Intercom's official pricing was reviewed October 13, 2026. The sample budget is arithmetic using stated assumptions, not a customer result or a full quote.
Decide what you are replacing
Intercom's current pricing page lists Essential at $29 per seat per month on its annual-billing view, plus Fin outcomes from $0.99. It also offers Fin with another helpdesk, with no Intercom seats required for that option. Advanced lists additional inbox and workflow capabilities.
Those are different buying paths. If the team wants only a different automated answer layer, include the retained helpdesk in every budget. If the team wants to move the inbox too, include ticket handling, history, assignments, reporting, and operator training in the migration scope.
| Setup | Costs to include | What remains to test |
|---|---|---|
| Fin with Intercom | Intercom seats, Fin outcomes, and applicable channel or add-on charges | Inbox assignments, Agent answers, and operator handoff |
| Fin with an existing helpdesk | Fin outcomes, any minimum commitment, and the retained helpdesk subscription | The connection and handoff into that helpdesk |
| LoopReply | Plan allowances for messages, active users, Agents, and Workspace members, plus required external services | Your knowledge sources, configured workflow, and shared-inbox coverage |
Fin with an existing helpdesk does not require additional Fin seats, but minimum commitments can apply. An outcome is also not simply an answered message: consult the official Fin outcome definitions for the operations you enable. Do not convert an outcome allowance into a LoopReply message allowance without measuring a representative conversation.
A transparent cost example
Assume three Essential seats and 200 billable Fin outcomes in a month, using the displayed starting outcome rate:
- Seats: 3 × $29 = $87 per month equivalent on annual billing.
- Outcomes: 200 × $0.99 = $198.
- Combined example: $285 before other usage, add-ons, taxes, or different contract terms.
The 200 outcomes are a planning input, not an expected automation rate. The starting rate is not a guarantee that every Fin function has the same price. Ask the vendor to price the actual channels and outcome types you intend to use.
For LoopReply, map the same pilot to messages, active users, Agents, and Workspace members on the pricing page. Include an eligible paid plan for human takeover. A cheaper line item is not a complete saving if another system still performs essential support work.
Migrate one support topic before the whole inbox
Choose a public topic, such as account invitations. Copy the approved instructions into a clean knowledge source and test three questions: a normal invitation, an expired link, and an account-specific permission problem.
The first two may be explained from documentation. The third needs the appropriate signed-in process or a person. Record which route the Agent takes and whether the operator receives enough context. The SaaS onboarding example supplies a small reproducible set of expected outcomes.
Keep the old support route available during this pilot. Do not migrate unrelated tickets or disable existing routing until the new journey has a named owner and a working fallback.
Inspect the release boundary
LoopReply's Studio lets you review Settings, Workflow, and Versions beside the configuration conversation. Draft instructions and workflow edits wait for Publish; knowledge and certain model-context fields are live settings. Check the exact field before a change to an active Agent.
This actual interface capture uses illustrative data. Versions shows current draft and published state plus saved changes, not restorable historical snapshots. The Studio review tutorial walks through that distinction.
Keep or replace the helpdesk deliberately
Intercom deserves evaluation when its combined inbox, Fin, and support operations fit the team, or when Fin can serve an existing helpdesk. LoopReply is a candidate when configuring the Agent and routing is the priority and your required human workflow fits its shared inbox.
Use the customer support deployment guide to assign source ownership, operator coverage, and release responsibility. A migration is ready when those responsibilities still work after the widget changes.