From Intercom to Chatlyst: The Complete Migration Guide
August 24, 2026
By Hunter Stone
Intercom built a beautiful product. Their UI is clean, their brand is strong, and they pioneered conversational support. But their pricing model has become a burden that growth-stage companies can no longer justify.
Here is how Intercom charges you today: $0.99 per AI resolution, plus $29 to $132 per seat per month, plus a $35 Copilot add-on per agent. The per-resolution fee is the killer. Every time Fin successfully resolves a customer query, Intercom charges you nearly a dollar. Sounds reasonable at low volume. At scale, it is devastating.
A 10-agent team using Intercom with moderate AI resolution volumes — roughly 1,500 resolutions per month — pays approximately $20,040 per year. That breaks down to $11,880 in seat fees (at $99/mid-tier pricing), $17,820 in resolution fees, and $4,200 for Copilot. The numbers pile up fast. And here is the cruel twist: the better your AI performs, the more you pay. Intercom punishes your success.
Reddit users have caught on. Threads in r/saas and r/customerservice regularly call Intercom “expensive fast” and warn founders about the resolution-pricing trap. One user posted their Intercom bill climbing from $800 to $4,200 in six months without adding headcount. Another called the pricing model “hostile to growth.”
The resolution rate compounds the pain. Intercom’s Fin resolves roughly 67% of conversations autonomously. That means one in three queries still requires human intervention — yet you have already paid the resolution fee for the other two-thirds. You are paying premium prices for incomplete automation.
Then there is the knowledge base problem. Intercom’s AI depends on documentation you manually maintain. When your product changes, your docs go stale, and Fin starts giving bad answers. Your team ends up babysitting the AI instead of focusing on strategic work.
Teams are done with it. They want predictable pricing. They want AI that actually learns. They want their support costs to scale linearly, not exponentially. That is why they are moving to Chatlyst.
What You Gain with Chatlyst
Chatlyst was built by support leaders who got tired of writing big checks to Intercom. The difference starts with pricing and extends into every part of how AI handles customer conversations.
Predictable costs, period. Chatlyst does not charge per resolution. A 10-agent setup runs approximately $6,000 per year — a straight 70% savings over Intercom. That is not a promotional rate. It is standard pricing. Your AI could resolve 10,000 conversations or 100,000, and your bill stays flat. This is how support pricing should work.
Resolution rates that matter. Chatlyst autonomously resolves 95% of conversations. Compare that to Intercom’s 67%. The gap is not marginal — it is the difference between a support function that still needs heavy human staffing and one that runs itself. At 95% resolution, your human agents handle only the complex, high-value interactions where their expertise actually matters.
AI that learns instead of forgets. Intercom’s Fin pulls from static documentation. When your docs are outdated, Fin hallucinates or deflects incorrectly. Chatlyst’s KC Bot learns continuously from every conversation, every agent response, and every customer outcome. It gets sharper over time without manual retraining.
Unified inbox that actually unifies. Chatlyst brings every channel — email, chat, WhatsApp, social — into one inbox with full context. No more switching between tools or losing conversation history when a customer changes channels.
The bottom line: you spend less, automate more, and your team works on what matters.
Pre-Migration Checklist
Before you touch a single export button, do your homework. A rushed migration creates data gaps, confused agents, and frustrated customers. Spend two days on preparation and save two weeks of cleanup later.
Audit your Intercom workspace. Count active teammates, inactive seats, and admin roles. Know exactly who needs access in Chatlyst. Document every connected channel — Messenger, email, Slack, SMS, WhatsApp. You will reconnect each one. Export conversation history for the past 90 days. You want enough data to identify topic patterns. Export all KB articles with their categories, tags, and publish dates. List your active workflows, custom bots, and assignment rules. Screenshots help. Note your current routing logic: how conversations get assigned, what triggers escalation, and your SLA targets.
Identify your top conversation topics. Run a simple topic analysis on your last 90 days of Intercom conversations. Group them into categories like billing questions, technical issues, account changes, feature requests, and refund requests. The top 5 topics will become the foundation of your Chatlyst knowledge base and AI training.
Set your migration timeline. Block 7 to 14 days on the calendar. Assign an internal project owner. Notify your team that a tool change is coming, and set customer-facing expectations if you anticipate any channel downtime during the switch.
Step-by-Step Migration
Follow these ten steps in order. Each one builds on the last.
Step 1: Export Your Intercom Data
Intercom lets you export conversations, teammate data, and KB articles from your workspace settings. Go to Settings > Data Export and request a full export. For conversations, you may need to use Intercom’s API or a third-party tool like Zapier to pull historical data into a structured format.
Save everything in a shared folder with clear naming: - intercom_conversations_90d.csv - intercom_kb_articles.json - intercom_teammates.csv - intercom_workflows_screenshots/
Step 2: Audit and Analyze Conversation History
Open your conversation export and categorize. Look for patterns:
- What percentage of conversations are repetitive FAQ-style questions?
- Which topics generate the most volume?
- What is your current first-response time and resolution time by topic?
- How often do conversations escalate from bot to human?
- What tone do your best-performing agents use?
This analysis becomes your blueprint for configuring Chatlyst’s AI responses and knowledge base. If 40% of your volume is “how do I reset my password,” that article gets top priority in your new KB.
Step 3: Set Up Your Chatlyst Workspace
Create your Chatlyst workspace at chatlyst.ai. Add your team members with appropriate roles — Admin, Agent, or Viewer. Connect your primary support channels: website chat widget, email, and any social messaging platforms you use. Chatlyst supports direct integrations with WhatsApp Business, Facebook Messenger, Instagram, and Slack.
Configure your business hours, timezone, and language settings. If you support multiple languages, set them up now. Chatlyst handles multilingual conversations natively.
Step 4: Import and Optimize Your Knowledge Base
Take your exported Intercom KB articles and import them into Chatlyst’s knowledge base. Do not just copy-paste. This is your chance to improve:
- Rewrite outdated articles. If a feature changed three months ago and your docs still describe the old version, fix it now.
- Break long articles into focused, scannable pieces. Chatlyst’s AI works best with concise, well-structured content.
- Add internal notes to articles where agents need extra context.
- Organize by category and tag articles with relevant keywords.
- Set article priority levels so the most common questions surface first.
Aim for quality over quantity. Fifty well-written articles beat two hundred stale ones.
Step 5: Configure Brand Voice and AI Responses
This is where Chatlyst diverges most dramatically from Intercom. Instead of generic bot responses, you define how your AI speaks.
Go to Chatlyst’s Brand Voice settings. Set your tone — professional, friendly, casual, or formal. Upload your style guide if you have one. Configure response length preferences. Some brands want short, direct answers. Others prefer detailed explanations with links.
Set up your welcome message, fallback responses for unknown queries, and your handoff phrase — the exact wording the AI uses when escalating to a human. Make it sound like your best agent, not a robot.
Test the AI with 20 real conversation snippets from your Intercom history. Rate the responses. Tweak the voice settings until the answers feel right. This takes an hour and saves weeks of customer confusion later.
Step 6: Set Escalation Triggers and Handoff Rules
Define exactly when the AI steps aside and a human takes over. Good escalation triggers include:
- Customer explicitly requests a human agent
- Sentiment detection flags frustration or anger
- Query involves account cancellation or refund above a threshold
- Technical issue requires backend investigation
- Conversation has gone back and forth more than 4 times without resolution
Configure assignment rules so escalated conversations land with the right team. Billing issues go to your finance specialist. Technical bugs go to engineering support. VIP accounts get priority routing.
Set your SLA timers. If a conversation escalates, what is your target first-response time? Chatlyst tracks this automatically and alerts supervisors when SLAs are at risk.
Step 7: Train Your Team on the Unified Inbox
Your agents’ daily workflow changes with Chatlyst. Schedule a 60-minute training session. Cover how the unified inbox works — all channels in one view. Show AI-suggested responses: when to use them, when to edit, when to ignore. Walk through internal notes and @mentions for team collaboration. Explain conversation tagging and custom fields for reporting. Demo the supervisor dashboard — how managers track queue health and agent performance. Show the mobile app basics for agents who handle support on the go.
Give every agent a checklist: log in, respond to a test conversation, tag it, assign it, resolve it. Hands-on practice beats slide decks.
Step 8: Run Parallel for One Week
Do not flip the switch on day one. Run both systems side by side for a week. Route new conversations through Chatlyst while keeping Intercom accessible as a backup.
During the parallel run, track resolution rate by topic, average handle time compared to Intercom, agent satisfaction with the new interface, customer satisfaction scores, and any conversations the AI handled incorrectly.
Hold a 15-minute daily standup with your support team. What worked? What confused customers? What needs tuning? Fix issues in real time.
Step 9: Execute the Full Migration
After a clean parallel week, cut over completely. Update your website chat widget to Chatlyst. Point your support email to your Chatlyst inbox. Redirect Intercom Messenger links.
Send a brief internal announcement: “As of today, all customer conversations flow through Chatlyst. Intercom is in read-only mode for 30 days, then we cancel.”
Export your final Intercom data archive and store it for compliance. Downgrade your Intercom plan to the minimum tier if you need extended access to historical data, or cancel outright if your data export is complete.
Step 10: Optimize with KC Bot Feedback Loops
Migration is not the finish line. The real gains come from continuous improvement.
Chatlyst’s KC Bot learns from every interaction. But you can accelerate its learning. Review the “AI unsure” report weekly. These are conversations where the AI had low confidence. Add missing KB articles or clarify existing ones. Monitor the “human override” log. When agents edit or replace an AI-suggested response, that is a signal the AI’s answer was incomplete or off-brand. Use these to refine your knowledge base. Track resolution rate trends. If a particular topic drops below 90% autonomous resolution, investigate and fix the root cause. Update your KB within 48 hours of any product change. New feature? New article. Updated pricing? Update the billing FAQ. The KC Bot only knows what you teach it.
Set a recurring 30-minute weekly session for knowledge base maintenance. One focused agent keeping the KB current will compound into massive resolution-rate gains over a quarter.
Handling Intercom-Specific Features in Chatlyst
Teams worry about losing functionality. Here is how Chatlyst handles the Intercom features your team relies on.
Intercom Messenger becomes Chatlyst Chat Widget. The widget is fully customizable — colors, position, launcher icon, and proactive messages. Install it with a single script tag, same as Intercom. You can trigger messages based on page URL, time on site, or user behavior.
Intercom Articles become Chatlyst Knowledge Base. Import via CSV, JSON, or direct copy-paste. The KB supports rich formatting, embedded images, video links, and collapsible sections. Internal-only articles keep agent notes separate from public docs.
Intercom Fin becomes Chatlyst AI Agent. The difference is resolution quality and pricing. Chatlyst’s AI resolves 95% autonomously versus Fin’s 67%, and you pay zero per-resolution fees.
Intercom Custom Bots become Chatlyst Workflows. Build multi-step conversation flows with conditional branching. Trigger based on user properties, page context, or time-based rules. No coding required.
Intercom Product Tours are not native to Chatlyst. If product tours are critical to your onboarding, keep a lightweight tool like Userpilot or Appcues alongside Chatlyst. Most teams find that the cost savings from migrating support more than cover a dedicated tour tool.
Intercom Series (outbound messaging) maps to Chatlyst Campaigns. Send targeted email and chat campaigns to user segments. Trigger based on behavior, time since last login, or custom events.
Team Training and Change Management
Tool migrations fail when teams resist adoption. Your agents have muscle memory from Intercom. New buttons in new places create friction. Address it head-on.
Name a migration champion. Pick one agent or team lead who owns the transition. They answer questions, gather feedback, and escalate blockers. This person becomes the team’s trusted guide, not management’s enforcer.
Run a side-by-side comparison session. Show your team the same conversation handled in Intercom versus Chatlyst. Let them see the AI suggestions, the unified inbox, and the faster routing. Concrete examples beat abstract benefits.
Address the fear directly. Some agents worry AI will replace them. Be honest: Chatlyst handles repetitive work so agents can focus on complex, relationship-building conversations. The job gets better, not smaller. Share your plan for redeploying time saved — quality initiatives, proactive outreach, VIP account management.
Create a feedback channel. A Slack channel or dedicated thread where agents post issues, suggestions, and wins. Review it daily during the first two weeks. Speed of response signals that their input matters.
Celebrate early wins. When the AI resolves its 100th conversation without human help, share that number. When first-response time drops 40%, announce it. Momentum builds buy-in.
Parallel-Run Strategy
The parallel week is your safety net. Treat it seriously.
Day 1–2: Route 25% of new conversations through Chatlyst. Keep the rest in Intercom. Monitor AI responses closely. Have an experienced agent review every Chatlyst conversation for accuracy.
Day 3–4: Increase to 50% volume. Expand the review to spot-checks rather than full review. Start measuring handle time and resolution rate comparisons.
Day 5–7: Route 75–100% through Chatlyst. Intercom stays live as a backup only. Run your full reporting suite. Confirm that CSAT, resolution time, and agent productivity meet or exceed Intercom benchmarks.
Go/No-Go decision: At the end of day 7, the team votes. If resolution rate is above 90%, agents are comfortable, and no critical bugs remain, proceed to full migration. If issues persist, extend the parallel run. There is no shame in taking an extra few days to get it right.
14-Day Migration Timeline
Days 1–2: Preparation - Export all Intercom data - Complete conversation topic analysis - Create Chatlyst workspace and add team
Days 3–4: Knowledge Base Setup - Import and rewrite KB articles - Configure brand voice and AI response settings - Build initial workflows and assignment rules
Days 5–6: Configuration - Set escalation triggers and handoff rules - Connect all channels (chat, email, social, WhatsApp) - Configure SLA targets and supervisor alerts
Day 7: Team Training - 60-minute training session for all agents - Hands-on practice with test conversations - Distribute quick-reference guides
Days 8–14: Parallel Run - Gradual volume ramp: 25% → 50% → 100% - Daily 15-minute standups - Real-time adjustments to AI and workflows - End-of-week go/no-go decision
Day 15: Full Migration - Complete cutover to Chatlyst - Intercom set to read-only or canceled - Internal announcement to company
Cost Comparison: Before and After
Let me show you the numbers for a realistic 10-agent support team handling 1,500 AI-resolved conversations per month.
Intercom Annual Cost: - Seat fees (10 agents × $99/month mid-tier): $11,880 - AI resolution fees (1,500/month × $0.99 × 12): $17,820 - Copilot add-on (10 × $35/month): $4,200 - Total: $20,040 per year
Chatlyst Annual Cost: - Flat team pricing: ~$6,000 - Total: $6,000 per year
Annual savings: $14,040 — a 70% reduction.
That is not theoretical. That is money back in your budget every single year. Reinvest it in headcount for complex support tiers. Fund product improvements. Drop it to your bottom line. The point is: you control it, not your support vendor.
And the savings grow with volume. If your traffic doubles, Intercom bills you an extra $17,820. Chatlyst stays flat. At scale, the gap becomes ridiculous.
Post-Migration: Continuous Improvement with KC Bot
The best support teams treat migration as the starting line, not the finish.
Chatlyst’s KC Bot is the difference between AI that plateaus and AI that compounds. Here is how to maximize it:
Weekly knowledge base sprints. Every Monday, spend 30 minutes reviewing the past week’s “AI unsure” and “human override” reports. Add missing articles. Clarify ambiguous ones. Update anything that went stale. This habit alone will push your resolution rate from 95% toward 98% within a quarter.
Monthly conversation analysis. Pull a sample of 100 resolved conversations. Categorize them by topic, complexity, and customer sentiment. Look for emerging patterns. Are customers asking about a new feature you have not documented yet? Is a recent product change generating confusion? Catch trends before they become volume spikes.
Quarterly brand voice reviews. Language evolves. Your product positioning shifts. Review your AI’s tone and response patterns quarterly. Does it still sound like your brand? Are responses the right length? Adjust and redeploy.
Agent feedback loops. Your agents are your best source of AI improvement ideas. They see where the bot stumbles. Create a simple process for them to flag bad AI suggestions. Review and act on these flags weekly.
The teams that see the best results from Chatlyst are not the ones with the best initial setup. They are the ones that commit to continuous refinement. AI is not a set-it-and-forget-it tool. It is a system that rewards attention.
Ready to Make the Switch?
Intercom had its moment. It pushed the industry toward conversational support and showed us what AI-powered help desks could look like. But its pricing model is stuck in an era where vendors could tax you for every automated conversation.
Chatlyst represents what comes next. Flat pricing. AI that learns continuously. Resolution rates above 95%. And support costs that scale predictably as you grow.
The migration takes 7 to 14 days. The savings start immediately. Most teams recover their migration effort cost within the first month.
Your support budget will thank you. Your agents will thank you. And your customers will get faster, better answers than ever before.