Character.AI filed for Chapter 11 bankruptcy on October 12, 2026, with Disney bidding $20 million for a license to some of its IP. The company blamed "legal, regulatory, and operational headwinds." Specifically, lawsuits over teen users and a state suit alleging its bot gave out a fake medical license number. If your business runs customer conversations entirely inside someone else's hosted AI chatbot, this is the risk you're carrying and probably haven't priced in.
What the Character.AI bankruptcy filing actually says#
Character.ai filed voluntarily in the U.S. Bankruptcy Court for the District of Delaware on Monday, October 12, to run a court-supervised sale of its assets. Disney is the stalking-horse bidder at $20 million for a non-exclusive, perpetual license to some of the company's IP. Other bidders can top that offer, and the sale is expected to close in November or December.
CEO Colin Adams said the board decided this gives the company "the best opportunity to maximize value for all stakeholders." Translation: the chatbot stays up for now, "with minimal disruptions," but could shut down entirely if nobody closes a deal that keeps it running.
The legal backdrop is why it got here. In 2025, families sued after teens died or attempted suicide following interactions with the bot. Pennsylvania sued in May 2026 over a chatbot that allegedly claimed to be a licensed medical professional, complete with a made-up license number.
Does this actually affect your business?#
If you're running a WhatsApp Business API setup through your own number, your own API key, and a workflow you can export, this doesn't touch you directly. You can stop reading.
If your customer support, lead qualification, or sales conversations live entirely inside a hosted consumer AI app (one where you don't own the account, can't export the flow, and have no API relationship), you're more exposed than you've probably clocked. Not because that app is bad. Because you're a tenant, not an owner, and tenants find out about an eviction the same day everyone else does. A Delaware filing doesn't send you a warning email first.
The honest trade-offs#
Hosted consumer AI platforms are fast and cheap to stand up. No infrastructure to manage, no DevOps bill, a bot live in an afternoon. That's real, and for low-stakes use cases it's often the right call.
The downside: you're building on someone else's roadmap, someone else's legal exposure, and someone else's balance sheet. Character.ai raised serious money and still ended up in Chapter 11 inside what, by its own telling, was a legal and regulatory problem it couldn't out-grow.
Whether Disney keeps the product running or just absorbs the IP and lets it die isn't settled yet. Forbes's reporting doesn't say either way, and neither does Character.ai. That's the genuine unknown here, and I wouldn't pretend otherwise. We've seen the same ambiguity play out with other SaaS vendors cutting deep into product lines this year. The acquirer rarely commits to a roadmap on day one.
How we're handling it#
We build client chatbot and WhatsApp automation on infrastructure the client's business actually controls, not inside a vendor's walled consumer app. For Profitlink's communications stack, the WhatsApp layer runs on AiSensy wired through n8n, sitting behind a single company number the client owns outright, not a personal account or a hosted bot we're renting on their behalf.
For Lionaire's product concierge bot, we built it in Voiceflow specifically because the project, the flows, and the knowledge base all export. Nothing lives only inside a platform we can't pull out of if the vendor's circumstances change.
We reviewed the Character.ai filing the day it dropped, and it confirmed something we'd already built around: the trade-offs we flagged when a client's WhatsApp bot sits on a platform they don't fully control apply here too, just with a sharper edge. At WebEpex, every WhatsApp build we ship uses Meta's own Business API tied to a number the client holds, with the automation logic documented and exportable.
It's slightly more setup work up front. It means a vendor's bankruptcy filing is their news story, not our client's emergency.
What I'd tell a client asking about this week#
Open your contract with whatever chatbot or AI vendor is handling customer conversations and check two things: can you export your flows and data, and does your business own the number or account customers actually message. If both answers are yes, do nothing. You're not exposed the way Character.ai's customers are. If either answer is no, that's worth fixing before it's forced on you, not after a bankruptcy notice shows up in a news feed.
If you want a second opinion on whether your current chatbot or WhatsApp setup actually belongs to you, send me what you're running and I'll tell you straight (takes two minutes, no pitch attached). cal.com/webepex/growth-review