Botmind was placed in judicial liquidation by the Melun Commercial Court on September 16, 2026. If your chatbot runs on Botmind, no date for the service’s shutdown has been announced as of yet: the safest course of action is to back up your data now and prepare an alternative solution. A successful migration takes a few weeks, provided you retrieve your content immediately and test the new solution with your actual conversations before switching tools.
This guide is intended for e-commerce customer service managers who use Botmind (or another chatbot with an uncertain future). Here you’ll find the known facts, migration steps, available options, and questions to ask your future service provider.
Here are the facts that have been made public to date:
Source: La Clé Publique, article dated September 26, 2026. The same article notes that the commercial website remained accessible as of that date. It does not say whether the service is still operational, nor for how long.
On the customer side, uncertainty reigns. A customer service manager summed it up this way during a conversation in early October:
"Botmind is referring everything back to the agent. For now, we don't have a date. We don't even know if it's going to be shut down in the end."
In this context, it’s best to get organized without waiting for an official date, especially as Black Friday and the holidays approach, when the volume of inquiries rises sharply.
An e-commerce chatbot primarily handles simple, repetitive inquiries: “Where is my order?”, “How do I return an item?”, “When will I get my refund?” If this first line of support is removed, these inquiries go directly to your agents via chat, email, or a contact form.
Specifically, there are three risks:
That's why it's a priority: back up your data before making any decisions.
Before you even start comparing solutions, take stock of what you can export from Botmind while you still have access:
If the export option is not available in the interface, submit your request in writing to the liquidator. Keep a record of every communication.
This question comes up in almost all of our discussions. The answer depends on your contract and the current proceedings: in liquidation, the liquidator decides whether or not to continue existing contracts. Some clients tell us they are still under contract until the end of the year. Submit your question in writing to the liquidator and have your legal department or attorney review the response. This guide is not a substitute for legal advice.
In practice, there's nothing stopping you from trying out another solution at the same time. In fact, that's the best way to stay in control of your schedule.
Here is the five-step method we recommend.
Categorize conversations from the past few months by reason. In most online stores, a handful of reasons (order tracking, returns, refunds, product availability, address changes) account for the bulk of the volume. These are the ones the new solution must handle from day one.
Import your existing Q&As as a knowledge base. They’re the result of your hard work: build on what’s already working. One manager explained to us that his bot’s scenarios were yielding good results for transactional requests:
"We know that the good results mainly come from simple questions about tracking, orders, and follow-up."
Generative AI connected to your product catalog and FAQs can also cover other topics, such as product recommendations. Now is the perfect time to try it out.
To answer “Where is my package?”, the chatbot needs to access the order and its delivery status. Make sure the new solution integrates with your online store and your current help desk, without requiring you to switch to a different one. This way, you’ll avoid having to juggle two projects at once during peak season. For order tracking, see our guide on automating “Where is my order?” inquiries.
Before going live, test the new solution on a sample of real questions drawn from your historical data. Verify the accuracy of the answers, the tone (informal or formal address, brand-specific vocabulary), and how the system handles sensitive cases.
Start by rolling out the new chatbot on a few pages or to a percentage of your traffic, then expand it. Establish clear rules for escalating issues to a human agent: topics related to health or product safety, disputes, and dissatisfied customers. Our guide on escalating issues to support will help you define these rules. Once the results match those of your current setup, you can discontinue the old chatbot.
You have four main options to choose from. The right choice depends on your help desk, your volume, and the time you have available.
| Option | Implementation timeline | Ce qu'elle fait bien | Points d'attention |
|---|---|---|---|
| Attendre la suite de la procédure | None | Pas de projet à lancer | Aucune visibilité sur une date d'arrêt éventuelle, en pleine saison |
| Chatbot natif de votre helpdesk | Variable selon l'outil | Un seul fournisseur, intégration native | Arbres de décision souvent limités au transactionnel ; options IA parfois payantes en plus |
| Solution IA spécialisée branchée sur votre helpdesk | Quelques semaines | Réutilise vos contenus, garde votre helpdesk, couvre chat et email | Vérifier l'hébergement des données, le modèle de facturation et la qualité sur vos vraies questions |
| Développement interne | Plusieurs mois | Contrôle total | Coût de maintenance, compétences IA à recruter, délai difficile à tenir dans l'urgence |
If you use Zendesk, our comparison of AI tools compatible with Zendesk provides details on the available options.
The Botmind situation serves as a reminder that a provider’s stability is a key factor in the decision-making process. Here are the questions to ask:
The issue of identity is worth considering. A chatbot that displays order details based on a simple email address entered in the conversation exposes your customers' data. Ask for a detailed demonstration of this scenario.
Chat is often just one part of the workflow. Emails and forms frequently account for a larger volume, with the same recurring issues. Replacing the chatbot is an opportunity to take a holistic view: a single knowledge base can power the chatbot, provide answers to help desk agents, and handle a portion of the emails on its own.
At Klark, this is what we do for more than 150 brands: an AI-powered e-commerce chatbot, a co-pilot for agents, and automated responses, all integrated with the leading helpdesks (Zendesk, Gorgias, Salesforce, Freshdesk, Intercom). On average, our clients automate 43% of their tickets.
As of the date of publication, there is no public information indicating whether or when the service will be discontinued. The court-ordered liquidation was ordered on September 16, 2026. Contact the liquidator in writing and begin preparing a transition plan immediately.
Expect it to take a few weeks with a solution that integrates with your help desk and reuses your existing content. The timeframe depends mainly on how quickly your data can be exported and the number of integrations that need to be connected (online store, shipping carrier, CRM).
Yes, if you can still export them. A CSV file containing questions and answers is usually enough to populate a new knowledge base. Export them now, while you still have access.
No, and it's not recommended in an emergency. Choose a solution that works with your current help desk: this way, you minimize disruption for your agents and maintain your existing processes.
Stick to the same approach as you do today: route customers to live chat during business hours, and to email support outside of those hours. Make sure the new solution provides the agent with the context of the conversation so the customer doesn't have to repeat everything.
It depends on your contract and the liquidator's decisions. Submit your question in writing and have your legal department review the response.
Are you using Botmind and want to try out an alternative on your own conversations? Request a demo of Klark: we'll import your Q&As and show you the results in your chat history.
