Moving from Crisp
Moving from a messaging suite to something that only does chat.
Should you actually move?
Read this bit before the steps.
Crisp is a capable product and most people leaving it are not leaving because it is bad. They are leaving because they use the chat and almost none of the rest, and they would rather not pay for or maintain the rest.
If you genuinely use the chatbot builder, the knowledge base and the campaign emails, this move will cost you things. Read the honest comparison first.
The full comparison with Crisp has a section on where they beat us.
What comes across, and what does not
There is no importer. Nothing is silently pulled from Crisp, and your old conversations do not appear in the Talkfront inbox. Plan for that rather than discovering it on the day.
You keep
- Your contacts, as a CSV you export before leaving
- Your transcripts, as an export you keep as an archive
- Your domain, your widget position and your brand colour, all reproducible in the customiser
- Verified identity: if you were signing user ids for Crisp, the same HMAC approach works here
You lose
- Conversation history inside the product. Old chats stay in your export, not in the Talkfront inbox
- Chatbot flows. There is no bot builder to import them into yet
- Knowledge base articles
- Campaign emails and the CRM segments built around them
- Any integration in their directory that we have not built yet
The move, in order
About an hour of real work, most of it making the widget look like yours. The order matters more than the speed: nothing touches your live site until step five.
01
Create the workspace and add your site
Sign up, add the domain chat runs on, and copy the site key. Nothing is live on your site yet.
02
Make it look like the widget you have now
Set the colour, position, greeting and avatar in the customiser. Draft and published settings are separate, so you can get it right before anyone sees it.
03
Set your hours and your team
Add operating hours and the closed-hours message, then invite your agents and set their roles. Do this before the swap, not after the first chat arrives.
04
Export everything from your old tool
Contacts and transcripts, while you still have a paid account. Keep the files: they are your archive, because history does not transfer.
05
Swap the snippet
Remove the old script tag and add the Talkfront one. One deploy, one line. Pick a quiet hour rather than a Monday morning.
06
Watch the inbox for a day
Send yourself a test chat from a phone and a laptop, check notifications reach the right people, and make sure the closed-hours message fires when it should.
07
Cancel the old subscription
Only once a real customer conversation has come through Talkfront and been answered. Not before.
Things that catch people out
Specific to leaving Crisp.
Check what your plan lets you export
Export limits differ by tier. Do the export while the account is still paid, not after you downgrade.
Their widget and ours both want the corner
If you run both during a trial, put one on the left and one on the right, and take the old one off the moment you are confident.
Your team will look for the bot
If a bot was handling first response, someone now has to. Set operating hours honestly so the widget says you are closed rather than leaving people waiting.
Stuck on any of it? Email support@talkfront.app and we will walk through it with you. We would rather spend an hour on that than have you give up halfway and end up paying for both.
Other guides
Start talking to your visitors today
Create a workspace, paste one line into your site, and answer your first chat in a few minutes.
Free plan, no card needed.