Switching from Crisp

Moving from Crisp to ClerkChat

Crisp's chatbot follows scenarios you build by hand, so unlike the other moves on this list there is no training data to bring with you. Your help centre is the asset that matters, and Crisp has a good one.

Realistic time: An hour or two
The catch: Write, do not export

What you lose

The question everyone actually has, answered first.

Scenarios and bot rulesThere is no export and no equivalent structure. This is a rewrite rather than a port, though the rewrite is prose rather than logic.
The shared inbox and team featuresCrisp is an inbox with a bot attached. Assignment, notes and team presence have no counterpart here.
CRM data and contact profilesCrisp builds a contact record over time. Export it before you cancel.
Campaigns and triggered messagesWe do not send outbound campaigns.

What carries across

Your Crisp Helpdesk articlesIf you built a help centre in Crisp, that is your training material and it is already written. Point us at the published URLs or export the articles.
The widget position on your siteBoth embed with a script tag, so nothing moves visually for your visitors.
The answers inside your scenariosEach scenario branch contains a real answer. Written out as prose, those become sources.

How to do it

1
Start from the help centre, not the botIf you have Crisp Helpdesk articles, that is the migration. Point us at them and the agent has real material immediately.
2
Convert the scenarios you built by handOpen each scenario and write out what it tells people. You are turning branches back into sentences.
3
List what always reached a humanRule-based bots fall through constantly. Those questions are the ones worth documenting, because they are what the rules could never cover.
4
Test, then swap the snippetCompare on the questions that used to escape the bot. Replace the script tag once you are satisfied.

What catches people out

There is genuinely nothing to export from the botPeople expect a training-data export and there is not one, because Crisp's bot was never trained. Budget an hour of writing instead of ten minutes of exporting.
Crisp's free and cheap tiers are hard to beat on price aloneIf cost is the only reason you are looking, Crisp is inexpensive and does a lot. Move because rules keep missing questions, not to save money.

When not to move

If any of these describe you, staying with Crisp is the right call and we would rather say so than sell you a migration you regret.

You need a shared inbox with a team working it
Your questions are genuinely predictable and the scenarios rarely fall through
Price is the deciding factor and your volume is low

Questions

Can I export my Crisp chatbot to ClerkChat?: No. Crisp's bot follows scenarios you built rather than training on documents, so there is nothing in a portable form. Your Crisp Helpdesk articles are the asset that moves, and they are usually enough on their own.
Do I lose the shared inbox?: Yes. Crisp is an inbox with a bot attached; we are an agent that answers and escalates. If a team works that inbox daily, that is what you would be giving up.

Moving from something else

Answer the questions the rules kept missing

Point us at your help centre and see. Free plan, no card needed.

Start free See pricing