The auto-importer reads your Zendesk Guide 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.
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.
The importer brings across every published article in your Zendesk Help Center: the title, the body, the section it sits in, its labels (as search keywords) and a link back to the article. Draft articles are skipped.
Images stay where they are: an article that shows a screenshot keeps pointing at the copy hosted by Zendesk. 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.
Only published help articles come across. Ticket rules, saved replies, macros, automations, past conversations and article comments stay in Zendesk. Articles that are not published can be added by hand in the knowledge base editor, or uploaded as a CSV of questions and answers.
The most noticeable change is that your help content is suddenly findable in the way visitors actually search for it. Zendesk Guide search is a keyword match against article titles and tags. GetFoxChat retrieval is semantic, which means a visitor who types "can I cancel and get my money back?" finds your refund-policy article even though the article is titled "Refunds and account closures". The same content, queried with the same words, surfaces correctly in GetFoxChat where it missed in Guide. Most teams notice this within the first day.
The second change is the closed loop. When your AI operator could not answer a question, the question lands in the unanswered list in your dashboard. You answer it once, in plain prose, and the answer becomes a new KB entry on save. In Zendesk Guide the equivalent workflow runs through a knowledge-base manager role and a publishing step; in GetFoxChat the same loop closes inside the operator chair, in fifteen minutes a week.
The third change is operational. Your Zendesk Guide can stay live as a public help centre that humans browse, or it can be retired in favour of GetFoxChat answers inside the chat widget. Both modes are common. Many teams keep Guide for SEO surface and let GetFoxChat handle the in-product answering.
You need a Zendesk API token, which a Zendesk admin can create under Admin, Apps and integrations, APIs. You paste it with your subdomain; nothing else is needed.
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.
Re-running the import replaces the imported entries with the latest version from your help centre, so an edit you made in GetFoxChat to an imported entry is overwritten. Put your own additions in separate entries, or make the change in your help centre first.
Yes. The two are independent. Many teams keep Guide as a browsable public help centre while GetFoxChat handles in-chat answers.
The importer brings across published articles only. Internal or draft articles can be added by hand in the knowledge base editor, or uploaded as a CSV of questions and answers.
Sign up with no card. Three-minute import. The first month of any plan is free.
Start your trial