Import your Intercom help center into FoxChat in 3 minutes

The auto-importer reads your Intercom Articles collection, brings them into the FoxChat knowledge base, and has Foxy answering visitor questions from them within minutes. Here is the whole process, end to end.

The 3-step process

Open the import tool in your FoxChat dashboard. The Knowledge Base panel has an Import button. Choose Intercom from the source list and paste your help-centre URL. For most teams that is a URL of the form help.yoursite.com. The importer reads the public surface directly — no Intercom admin login, OAuth scope, or developer app is required for a public help centre.
Run the import and watch the article count climb. FoxChat enumerates every published article across every collection in your Intercom help-centre. Collections become categories in FoxChat, articles become KB entries, and the slug structure is preserved so any deep links you have elsewhere continue to resolve once you redirect them. A typical help centre of a few hundred articles completes in under sixty seconds; larger ones take a few minutes and never require manual intervention.
Spot-check the first dozen common answers. The dashboard surfaces the dozen most common questions Foxy can now answer from your imported content. You scroll through them, watch Foxy reply in plain language with the source article attached, and click any thin or wrong answer to open it in the KB editor. Fixes land in production immediately.

The whole sequence completes in roughly three minutes for a typical Intercom help centre. The slower step in practice is usually you reading through the answers Foxy generated, which is a sign that the import did its job.

What gets imported

The importer brings across every published article in your Intercom help-centre: titles, body content, collection assignments, sub-collection nesting, and last-updated dates. The slug structure is preserved, so a redirect from the Intercom URL pattern to the FoxChat help URL keeps your external links resolvable. Featured articles in Intercom are marked as high-priority entries in the FoxChat retrieval index, surfacing earlier in answer generation.

Article media transfers in two passes. Embedded images, inline screenshots, and video thumbnails are referenced by their original Intercom-hosted URLs at import time, which keeps the import fast. The optional follow-up sync mirrors media to FoxChat's own storage so your KB has no remaining dependency on your Intercom instance. The sync is a button in the dashboard.

Article author bylines, last-updated timestamps, and reader-rating scores all transfer as metadata. They are visible in the FoxChat editor but do not weight retrieval — we rank by semantic relevance plus full-text overlap, not by historical view popularity, because views often reflect findability rather than correctness.

What does not get imported

Things that do not transfer are things that have no FoxChat equivalent or live outside the help-centre surface. Custom bots scripted in Intercom's bot builder, Series-based message campaigns, and the workflow rules behind Intercom's Fin AI agent are all platform features rather than help-centre content, so they are out of scope for this importer. If those workflows are important to you, see the FoxChat vs Intercom comparison for the equivalents that exist and the ones that do not.

Internal-only help articles (the ones gated behind login) are not read by the public-surface importer. You can bring them in manually via paste or markdown upload from the dashboard if you need them in the FoxChat knowledge base. Article comments, if you have them enabled in Intercom, do not transfer as a live thread; they come across as metadata.

What changes after import

The most visible change is that your help content becomes findable the way visitors actually search for it. Intercom's help-centre search is a keyword match. FoxChat retrieval is semantic, which means a visitor who types "how do I stop the monthly charge?" finds your subscription-management article even though it is titled "Managing your billing". The same content, the same visitor, finds the answer in FoxChat where Intercom's search misses it. Most teams notice this within the first day.

The second change is the closed loop. Foxy logs unanswered questions in a queue inside the FoxChat inbox. You answer the question once, in plain prose, and the answer becomes part of the knowledge base on save. The same workflow in Intercom runs through the article-editor surface and a publish step; in FoxChat it happens inline in the operator inbox in roughly fifteen minutes a week.

The third change is operational. If you are also switching the chat widget itself from Intercom Messenger to FoxChat, Foxy starts handling inbound chat in the words your visitors actually use, with the imported help-centre content as the grounding source. If you are keeping Intercom Messenger and only moving the help-centre content into FoxChat, you can use the FoxChat answers programmatically via the API while leaving the visible widget alone.

Common questions

Do I need an Intercom admin to run the import?

No. The importer reads the public help-centre surface, which does not require authentication for published articles. Anyone with the help-centre URL can start the import.

Will the Intercom widget conflict with FoxChat on my site?

No. Both can run side by side during evaluation. Most teams keep Intercom Messenger live for a week or two while spot-checking FoxChat's answers, then choose one as the primary visible chat surface.

How often does the import re-sync?

On demand, from the dashboard. Most teams sync at install and again after major content edits. Continuous sync is on the Agency tier roadmap.

What if I edit an article in FoxChat after import?

The FoxChat edit stays in FoxChat. A subsequent re-import does not overwrite edits by default — the dashboard surfaces conflicts and you choose per article.

Can I import multiple Intercom workspaces?

Yes, if they live on separate help-centre URLs. Each becomes its own knowledge base in FoxChat, mapped to its own site. The Agency plan covers up to five sites.