Import your Crisp help center into FoxChat in 3 minutes

The auto-importer reads your Crisp Helpdesk articles, 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 Crisp from the source list and paste your Crisp Helpdesk URL. For most teams that looks like help.yoursite.com or the default Crisp Helpdesk subdomain. The importer reads the published surface directly, so no Crisp admin OAuth, plugin install, or website ID copy is required.
Run the import and watch the article count climb. FoxChat walks through every published article across every category in your Crisp Helpdesk. Categories become topic groups in FoxChat, articles become KB entries, and the canonical slugs are preserved. A typical small Helpdesk completes in under sixty seconds. Larger libraries take a few minutes and surface any failed articles for one-click retry.
Spot-check the first dozen common answers. The dashboard surfaces the dozen most common questions Foxy can now answer. You scroll through them, see Foxy reply in plain language with the source article attached, and click any thin or wrong answer to open it in the KB editor for a fix. The fix lands in production immediately.

The end-to-end sequence is usually complete in three minutes for a small Helpdesk. The biggest variable is how many articles you have and how quickly you read through the dozen sample answers Foxy generates.

What gets imported

The importer brings across every published article in your Crisp Helpdesk: titles, body content, category structure, and last-updated timestamps. Article slugs are preserved so any deep links from your site or marketing material to specific Crisp articles continue to resolve once you redirect them to the FoxChat help paths. If you mark certain articles as featured in Crisp, those become high-priority entries in the FoxChat retrieval index.

Embedded media — images, screenshots, video thumbnails — transfers in two passes. The first pass references your Crisp-hosted media URLs at import time, which keeps the import fast and lets Foxy start answering immediately. The second pass mirrors the media to FoxChat's own storage so the KB has no remaining dependency on your Crisp instance. The second pass is a button in the dashboard you can run when convenient.

Article-author metadata, view counts, and reader-rating scores transfer as informational metadata. They are visible in the FoxChat editor but do not influence retrieval — Foxy ranks by semantic relevance plus full-text overlap, not by historical view popularity.

What does not get imported

Crisp's multi-channel inbox, the scripted Crisp bots, MagicReply suggestion templates, and segment-based campaign workflows all live outside the Helpdesk article surface, so they are out of scope for this importer. If those workflows matter to you, the FoxChat vs Crisp comparison explains which have FoxChat equivalents and which do not. The most common steady state for teams who use Crisp's multi-channel inbox is to keep Crisp running for email and SMS and use FoxChat for the web-chat surface.

Article comments, if you have them enabled, do not transfer as a live thread — they come across as metadata only. Visitor satisfaction ratings on individual articles transfer as informational data. Internal-only Helpdesk articles (those gated behind authentication) are not read by the public-surface importer; you can bring them in manually via paste or markdown upload.

What changes after import

The first change is retrieval quality. Crisp's in-Helpdesk search is a keyword match against titles and tags; FoxChat retrieval is semantic, so a visitor who types "why am I still getting charged after cancelling?" finds your cancellation-confirmation article even though it is titled "Cancellation processing". Same content, same visitor, different surface, materially better hit rate. Most teams notice the difference within the first day.

The second change is the closed loop. When Foxy could not answer, the question lands in an unanswered queue inside the FoxChat inbox. You answer once in plain prose and the answer becomes part of the knowledge base on save. In Crisp the equivalent path runs through the article-editor surface plus a publish step; in FoxChat it closes inline inside the operator inbox.

The third change is operational. If you keep Crisp running for its multi-channel inbox, the FoxChat KB becomes your single source of truth for help content and Crisp's Helpdesk becomes a static SEO surface. If you fully migrate the web-chat surface to FoxChat, Foxy handles inbound chat with the imported content as the grounding source.

Common questions

Do I need a Crisp admin to run the import?

No. The importer reads the public Helpdesk surface, which does not require authentication for published articles.

Can I keep Crisp's inbox while FoxChat handles chat?

Yes, and this is the most common steady state for teams migrating gradually. Crisp handles email and SMS, FoxChat handles web chat, both on the same site.

How often does the import re-sync?

On demand, from the dashboard. Most teams sync at install and again after major content edits.

What about article comments and ratings?

They come across as metadata, not as live threads. Most teams find the FoxChat closed-loop unanswered queue replaces the article-comment workflow cleanly.

Will my Crisp MagicReply templates transfer?

No. MagicReply is a Crisp-platform feature that lives outside the Helpdesk surface. FoxChat's retrieval-grounded AI does the equivalent work natively from your help content.