If your contact center runs Agentforce Voice in Japanese, the speech model under it is changing owner, and nobody has said in writing what happens to it. ElevenLabs announced on November 16 that it will acquire Kotoba, the Japanese voice AI lab whose Koto model Salesforce uses to power Japanese conversations in Agentforce Voice. The announcement gives no price, expects closing "later in Q4 2026" subject to regulatory approvals, and says nothing about existing Kotoba customers, its APIs or the Salesforce integration. That leaves at most about six weeks to get continuity, data-handling and model-version terms on paper while you still have leverage.
ElevenLabs is the larger, better-funded buyer, and the deal may well make the Japanese stack stronger. The open question for a buyer is narrower: which model will be answering your customers' calls in 2027, under whose data terms, and who tells you when that changes.
What ElevenLabs Is Buying
ElevenLabs is buying a young research lab with one named model and an unusually well-placed customer list. Kotoba was founded in 2023 by Noriyuki Kojima and Jungo Kasai. Its model, Koto, does Japanese text-to-speech, speech-to-text and speech-to-speech for simultaneous interpretation, and ElevenLabs says "several major global enterprises" use it, naming only Salesforce.
Kotoba's own August 10 release on PR TIMES fills in the rest. Koto is an end-to-end speech model built for ultra-low-latency, real-time voice. It is strongest in Japanese, Korean and Chinese, and it supports on-premises and on-device deployment to fit varied corporate and security requirements. The company has raised ¥3.7 billion in total. Salesforce Ventures backed its seed round alongside Kindred Ventures and said Kotoba is positioning Koto as the de facto speech model for next-generation devices and agentic systems in East Asia.
The Kotoba website lists three ways to buy: the Koto model itself, a consumer interpretation app, and model licensing, with deployment on-premise, in the cloud or on-device. It now carries a press item titled "Kotoba Is Joining ElevenLabs" and nothing about customer terms.
The most telling line in ElevenLabs' announcement comes from its CTO, Piotr Dąbkowski, who said "Kotoba's team has done exceptional research on the Japanese language" and that combining the two teams' research will improve Japanese across ElevenLabs' products. That reads as a plan to fold Kotoba's research into ElevenLabs' own models. It does not say Koto survives as a separately sold, separately versioned product. Maybe it will. Nobody has committed to it.
Why Agentforce Voice Customers in Japan Are Exposed
Japanese Agentforce Voice customers are exposed because Koto is the Japanese speech layer Salesforce picked, and that layer now belongs to a company Salesforce does not control. Salesforce Japan made the Japanese version of Agentforce Voice generally available on August 7, 2026. It handles transcription and speech synthesis on live calls, then updates CRM records, creates cases, runs workflows and calls APIs based on what the caller said. In Japan it connects to Genesys and to Comdesign's CT-e1/SaaS cloud CTI.
So the speech model is upstream of real actions in your org. A transcription error on a customer name, an account number or an honorific changes what the agent writes back to Salesforce. Kotoba's own release argued that Japanese demands a lot from voice AI on honorifics, spoken phrasing and context-dependent nuance. That is the property you are relying on, and it is the property a model swap can quietly change.
A second Salesforce path runs through Kotoba too. On November 11, Cresta announced a partnership with Kotoba to integrate Kotoba STT and TTS models tuned for Cresta into its platform for Japanese contact centers. Nine days earlier, Salesforce signed a definitive agreement to acquire Cresta, expected to close in the first quarter of its fiscal 2028. We covered what that deal means for Service Cloud buyers in Salesforce to Acquire Cresta for Reported $2.7B to Add Voice Agents. If both deals close and Cresta ships the integration it has announced, Salesforce's two Japanese voice routes would lead back to one small lab owned by ElevenLabs.
The strongest counter-argument deserves a hearing. ElevenLabs lists Salesforce among its named customers, and it has every commercial reason to keep Agentforce Voice working in Japanese. A $22 billion company is a sturdier supplier than a seed-stage lab. That is probably right for the platform relationship between ElevenLabs and Salesforce. It tells you nothing about your tenant's model version, your data's processing location or your notice period, which sit in contracts you can read.
What ElevenLabs Plans for Japan
ElevenLabs says the deal is the first step in a longer Japan buildout, which is good news for capacity and a reason to expect the product line to change. The company says it will build out local sales leadership and keep investing in infrastructure in Japan, working more closely with Japanese enterprises and multinationals operating there.
It already has a base. ElevenLabs set up ElevenLabs Japan G.K. in Tokyo in April 2025 as its first international subsidiary. In September it ran a $300 million employee tender that valued the company at $22 billion, and said enterprise customers make up 55% of revenue and its models work in more than 90 languages. Its annual recurring revenue passed $500 million in the first four months of 2026, up from $350 million at the end of 2025.
ElevenLabs also sells its own voice agent platform, ElevenAgents, whose agents handle more than 15 million conversations a week. Owning the Japanese model behind Agentforce Voice and Cresta's planned Japanese integration gives ElevenLabs a better Japanese product of its own and a supplier position under two platforms that sell into the same contact centers. For a buyer, vendor neutrality is now a fair question to ask alongside continuity. If you are weighing voice vendors more broadly, our ElevenLabs page and the comparison in Azure Beats Cartesia and ElevenLabs on TTS Price cover the alternatives.
What Happened the Last Time a Voice Vendor Changed Hands
Recent voice deals show acquirers keeping the platform running while putting their own models first, so plan for gradual drift in the model you depend on. When Inworld bought Ultravox, it upgraded only its own voices. When Deepgram bought Daily, the open-source Pipecat code stayed under BSD-2, which protected developers who had self-hosted it and did little for those on the hosted service.
Kotoba's on-premises and on-device licensing is the closest analogue to that self-hosted escape hatch. If you run Koto inside your own environment under a license, the question is whether that license is perpetual, what support you get after close, and whether you get future model weights or only the version you have. If you call a hosted API, your protection is whatever notice and deprecation terms your contract carries. Our survey of AI vendor exit clauses found the window to get data out ranged from 0 to 90 days across five vendors. Check yours before close.
What to Do Before the Deal Closes
Use the weeks before closing to put three things in writing: who processes your audio, which model version you get, and how much notice you get before either changes. After close, the acquirer sets the defaults.
This Week:
- Ask your Salesforce account team, in writing, whether your Agentforce Voice Japanese tenant uses Koto, whether Kotoba appears on the subprocessor list that covers it, and whether Salesforce expects that entry to change to ElevenLabs.
- Inventory every direct Kotoba relationship: hosted API keys, on-premises or on-device licenses, the interpretation app, and any Cresta deployment in Japan that uses Kotoba models. Name an owner for each.
- Record a baseline. Pull a sample of recent Japanese calls and score transcription accuracy on customer names, addresses and honorifics, plus end-to-end latency. You cannot prove a regression later without numbers from today.
This Month:
- Request a continuity letter from Kotoba for direct contracts: the API and model versions supported after close, the minimum notice before deprecation, and whether pricing holds through your current term.
- Ask where audio and transcripts are processed and stored after close, and whether any data used under Kotoba's terms will move under ElevenLabs' terms or be used to train ElevenLabs models.
- If you hold an on-premises Koto license, confirm in writing that it stays valid without an ElevenLabs re-paper, and what support and security patching you get after close.
Before Renewal:
- Add a change-of-control clause to any voice AI contract that lacks one, with a termination right if the speech model or data processor changes without notice.
- Keep a tested second Japanese speech option. On Agentforce Voice that is a question for Salesforce; on your own stack, run your baseline set against at least one alternative such as Deepgram or Cartesia so you already know how a switch would perform.
- Re-run the cost per resolved call. Our voice AI pricing breakdown found Vapi's advertised $0.05 minute billing at $0.09 to $0.14, and an ownership change is a common point for list prices to move.
The Bottom Line
This follows a familiar pattern in contact-center software: a small specialist with a strong local-language model is absorbed by a platform, and its customers keep their service on terms they never renegotiated. ElevenLabs is buying Japanese voice capability and a supplier position under Salesforce and Cresta. Buyers running Japanese voice agents get a stronger parent and lose the line of sight they had to a single-product vendor.
The contract terms that protect you are the same ones you would ask for at any renewal: model version, data location, notice period and an exit right. The difference is the deadline. ElevenLabs expects to close in the fourth quarter, and until then your Salesforce and Kotoba account teams can still commit to terms individually.
Send the subprocessor question to Salesforce this week, and score your Japanese call baseline before the model changes under you.
Continue Reading
- Salesforce to Acquire Cresta for Reported $2.7B to Add Voice Agents
- Inworld Buys Ultravox and Upgrades Only Its Own Voices
- Pipecat's BSD-2 Code Stays Open as Deepgram Buys Daily
- Five AI Vendors Give Customers 0 to 90 Days to Get Data Out
- Your Agentforce Bill Depends on How Many Actions an Agent Takes
- Azure Beats Cartesia and ElevenLabs on TTS Price
