In this article, as a founder, I’ll mention our new vision about the product, our new roadmap, how we will keep you in the loop while prioritizing things, and how it will affect you as a user.
A short history of Mevo
In October 2022, Mevo was a live chat solution, planned as a Crisp alternative, even the domain was “mevo.chat” instead of “usemevo.com”. We had a working alpha version, then something big happened, and we decided to jump on to the AI train. We turned the platform into a dedicated chatbot training solution, and somehow we decided to add a rule-based chatbot because we wanted Mevo to be a chatbot generator. So whether you need AI or a traditional rule-based chatbot, if you use Mevo, you should have everything you need in one platform.
We released our first version in April 2023, and after a few months, in September 2023, we released our AppSumo deal. After 18 months, AppSumo is still a vital customer acquisition channel for us and will continue to be so for a short while.
What’s the current situation?
We recently released our new interface, which makes things easier. We introduced the New Inbox, Notification Receivers, Tags, Email replies when AI responses are insufficient, and more.

But we know there is still a long way to go. There are some known problems, and there are some processes to be improved, (we know our customer support flow should be improved, it’s ironic while we’re providing a solution to make customer support flows better, but it’s also an opportunity), white labeling for agencies, live-chat support, critical integrations like Whatsapp, Discord, Telegram, Shopify, the option to have other LLMs, and more.
You should have noticed that our latest release is December 2024. Of course, we shipped many minor fixes after that date, but there were no significant features. Even some people start to think, isn’t it Mevo maintained yet?

The reason was planning. We were planning and identifying the product pain points. We read the Discord messages, Frill feature requests, AppSumo questions, reviews, and emails from our users. It wasn’t easy to understand and decide which should be part of our new vision and which would not.
We know the pain points now, the things we should improve, the things we don’t even need in the product, the strengths of our product, and the weaknesses. Of course, we also know this is a dynamic process, and we should keep you in the loop, and we will.
What’s next?
As I mentioned, customer support is one of our heaviest tasks, too. Some of you have already noticed late replies to your emails, lack of information about the status of your requests, and sync problems that occur because of having multiple support channels (emails, Discord server, app Sumo questions, and even social media accounts).
We’ve decided those are the pain points we want to focus on. If we can’t solve our customer support issues, how can we claim to do this for our customers?
Even if it’s impossible to quickly handle all the customer queries due to the increased number of questions, we can at least provide an elegant way to follow that and create a transparent process. We can define support tiers, distribute the workload between agents, and try to find better ways to use AI.
And that’s precisely what we’re going to do; We’re going to turn Mevo into an end-to-end customer service platform.
Your customer asks a question. Your AI agent first attempts to answer using your internal or public knowledge base. If the customer isn’t satisfied, they can seamlessly transition to live chat. You can then convert this conversation into a customer support ticket, assign it to the relevant team, and your customer will receive notifications about each update. You will have an internal ticket management system and CRM module in minimal form.
How will it affect you as an existing Mevo customer?
We know some customers use Mevo to create general-purpose chatbots so that these changes won’t affect them too much. We’ll keep rule-based chatbots available because we’re still convinced of their value for customer support flows. We’ll find a way to fit them into the single chatbot flow with AI and live chat features.
However, there may be some features we’ll remove because they don’t fit with our new vision anymore;
- Custom domains for standalone chatbot web pages. Offering a standalone page won’t fit with our new product vision, even if it’ll be technically possible to provide chatbots by using it as a link like bot.usemevo.com/bot-id, linking custom domains to them won’t be an option.
- Ability to provide OpenAI key support. Therefore, Assistants API support will also be deprecated. We want to make the platform LLM agnostic because different models perform better for various kinds of problems, and this isn’t possible when relying directly on OpenAI.
- Web scraping features. We don’t believe this offers as good a value as it sounds. Instead, we’ll introduce public knowledge bases that you can add to your content as support articles, and your chatbot will rely on that information specifically designed for support purposes.
Actions you should take
All of those features will sunset on 1 April 2025, so if you use one of those, you should take some actions, like updating the places you use a custom domain for your chatbot with our internal bot URLs, removing your OpenAI key and Assistant connection, and training your chatbot again after you remove the connection. You can continue using your chatbots using your Mevo credits in your plan. Your chatbot will work smoothly (probably better than before) if you provide all the same training content.
We understand that it is unpleasant for you to lose these rights that you have, and we think it is fair that you gain something in return. To compensate for the removal of these features:
- For each lost custom domain feature, your training character limit will increase by 5M.
- Losing the OpenAI key feature will grant you an additional 5M character limit.
- Losing the web scraping feature adds yet another 5M characters.
- Additionally, you’ll receive three extra user seats as compensation for these changes.
We will also offer optional credit plans that you can choose to use once you run out of token credits. These plans will be significantly more accessible and discounted for our existing customers.
We’ll keep you in the loop
You already know we’ve been using a feature request platform, Frill, for a while. We’ll keep using it, and when you check it, you’ll see our updated roadmap. You can still create feature requests, vote on the ideas you like, and leave comments on the ideas.
We’ll also announce a webinar soon about the upcoming changes, and it’ll include a Q&A session. If you have any comments or questions, you can raise them directly with the founder.
We’ll also announce a meeting day, that you can book a 15-minute call slot with 1-on-1 with the founder, this will be a survey-like conversation about the product, what are your favorite features, what features are you missing in Mevo, etc. And if you join these calls, you’ll gain rewards like extra tokens, credits and more.
Final
Thanks for reading this long post.
We believe this vision shift positions Mevo as a powerful alternative among customer service platforms, ultimately simplifying and enhancing your experience. If you have any comments, feel free to share with us by using hi@usemevo.com
Furkan Başaran,
Founder