Import your Crisp help center into GetFoxChat in 3 minutes

The auto-importer reads your Crisp Helpdesk articles, brings them into the GetFoxChat knowledge base, and has the GetFoxChat AI Operator (starts as Foxy; rename it and change the avatar anytime) 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 GetFoxChat dashboard. Go to Knowledge Base, choose Import and pick Crisp. You will need your Crisp website ID and a Crisp plugin or user key (identifier and key). Crisp offers Helpdesk articles on its paid plans.
Run the import and watch the article count climb. GetFoxChat reads every published article in your Crisp Helpdesk. Each one becomes an entry in your knowledge base, grouped by its category. The dashboard shows how many came across and lists any that failed, with the reason.
Ask your chat a few common questions. Open your site, ask the questions your visitors ask most, and check that each answer comes with the right source. If one is wrong or thin, open that entry in the knowledge base editor and fix it.

A small help centre usually comes across in a few minutes. Larger ones take longer and need nothing from you once the import has started.

What gets imported

The importer brings across every published article in your Crisp Helpdesk: the title, the body, the category it sits in and a link back to the article.

Images stay where they are: an article that shows a screenshot keeps pointing at the copy hosted by Crisp. Your AI operator answers from the article text.

View counts, votes and author names are not imported. Your AI operator ranks articles by how well they match the visitor's question, not by how popular they were.

What does not get imported

Only published help articles come across. Ticket rules, saved replies, macros, automations, past conversations and article comments stay in Crisp. Articles that are not published can be added by hand in the knowledge base editor, or uploaded as a CSV of questions and answers.

What changes after import

The first change is retrieval quality. Crisp's in-Helpdesk search is a keyword match against titles and tags; GetFoxChat 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 your AI operator could not answer, the question lands in the unanswered list in your GetFoxChat dashboard. 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 GetFoxChat it closes inline inside the operator inbox.

The third change is operational. If you keep Crisp running for its multi-channel inbox, the GetFoxChat 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 GetFoxChat, your AI operator handles inbound chat with the imported content as the grounding source.

Common questions

Do I need a Crisp admin to run the import?

You need your Crisp website ID and a plugin or user key (identifier and key), which an admin of your Crisp workspace can give you. Nothing else is needed.

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

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

How often does the import re-sync?

On demand: run the import again from the dashboard whenever your articles change. Each run updates the entries it imported before and adds new articles.

What about article comments and ratings?

They are not imported. The questions your AI operator could not answer are grouped for you in the dashboard, which covers what article comments were often used for.

Will my Crisp MagicReply templates transfer?

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

Will I lose my chat history?

Your past Crisp conversations stay in Crisp. GetFoxChat does not delete or import your old transcripts, so nothing is lost. New conversations start fresh in GetFoxChat from the day you install the widget.

How long does the migration take?

The technical part, adding the GetFoxChat snippet and removing the Crisp one, takes a few minutes. Bringing over your Helpdesk articles and refining answers usually takes most teams under an hour. You are live the moment the snippet is in place.

Do I need a developer?

No. If you can paste a line of HTML before the closing body tag, or add a snippet through your site builder or tag manager, you can install GetFoxChat yourself.