Genesys TTS Deprecation 2026: What Every Contact Center Needs to Know

The Genesys TTS deprecation is the scheduled end of native Enhanced Text-to-Speech support for select Google and Microsoft voices in Genesys Cloud, effective August 5, 2026. After this date, affected voices will transition to third-party integrations under the BYOT-A billing model.

Understanding what is happening, which voices are affected, and what your options are before the deadline will save your team significant time, cost, and frustration.

This guide covers everything your contact center needs to know about the Genesys TTS deprecation, including the two paths forward and why a growing number of enterprise teams are using this moment to make a change they have been putting off for years.

What Is the Genesys TTS Deprecation?

Genesys Cloud currently provides native support for a range of text-to-speech voices from Google and Microsoft as part of the platform’s built-in capabilities. On August 5, 2026, that native support ends for select voices from both providers.

After this date, Genesys Cloud will treat these voices as third-party integrations rather than native features. To continue using them, contact centers will need to migrate to the Google TTS or Microsoft Azure TTS integrations available through the Genesys AppFoundry marketplace. These integrations operate under a new billing model called Bring Your Own TTS, Rate A, commonly referred to as BYOT-A.

In practical terms, this means additional cost, a new integration to configure and maintain, and continued reliance on the same AI-generated voices that have been frustrating callers for years.

Which Voices Are Affected?

The deprecation affects select Google Standard TTS voices and select Microsoft Azure TTS voices that are currently available as native features within Genesys Cloud. Contact centers using these voices for any Architect flow element, including IVR menus, auto attendant greetings, queue prompts, voicemail greetings, and on-hold messages, will need to take action before August 5, 2026.

If you are unsure whether your contact center uses affected voices, your Genesys administrator can review your current Architect flows to identify any TTS-generated prompts. Genesys has also published updated deprecation documentation in the Genesys Cloud Resource Center with specific voice names and migration timelines.

What Are Your Options?

Contact centers facing the August 5 deadline have two paths forward.

Option 1: Migrate to BYOT-A

The BYOT-A migration path allows contact centers to continue using Google or Microsoft TTS voices by connecting to those services directly through AppFoundry integrations. This is the most straightforward technical path for teams that want to maintain the status quo.

The tradeoffs are worth understanding before committing. BYOT-A introduces additional per-use billing on top of your existing Genesys licensing. It adds a new third-party integration to configure, monitor, and maintain. And it keeps your contact center on AI-generated voices, the same generic, synthetic prompts your callers have already been navigating for years.

For teams that need a fast, low-effort solution and are not concerned about voice quality or brand experience, BYOT-A is a viable path. But it solves the technical problem without solving the experience problem.

Option 2: Replace TTS Voices with Professional Human Recordings

The second path is to replace your deprecated TTS voices entirely with professionally recorded human voice prompts. This approach eliminates the need for any TTS integration, removes the BYOT-A billing entirely, and gives your contact center a voice experience that actually reflects your brand.

Human voice recordings for Genesys Cloud are produced, formatted, and delivered as static audio files that upload directly to your Genesys prompt library. Once they are in place, they require no ongoing TTS integration, no API connections, and no per-use costs. You own the files outright.

For contact centers that have been meaning to improve their caller experience, the August 5 deadline is a natural moment to do it properly.

Why the Deprecation Is Actually an Opportunity

The TTS deprecation is pushing many contact centers to revisit something they have quietly lived with for years, a phone experience that sounds automated, generic, and disconnected from the brand behind it.

Consider what your callers currently experience. A synthetic voice reads out menu options in a flat, robotic tone. Callers navigate through prompts that feel like they belong to any company in any industry. There is no warmth, no personality, and no sense that the business on the other end of the line has thought carefully about this interaction.

That experience shapes how callers perceive your brand, often before they have spoken to a single person.

Replacing deprecated TTS voices with professionally recorded human prompts does not just solve the compliance problem. It upgrades the entire first impression your contact center makes. Your callers hear a real voice that sounds like your brand. Your menus feel intentional rather than automated. And your team gains audio assets they own outright, with no ongoing integration costs.

What to Look for in a Genesys Voice Recording Partner

Not all audio production companies are equipped to handle Genesys Cloud voice replacements. Here is what to look for when evaluating a production partner:

Genesys-specific formatting. Every audio file must be formatted to Genesys Cloud’s exact technical specifications, the correct codec, sample rate, and file naming convention for direct upload to your prompt library. A production company that delivers generic audio files will create extra work for your IT team.

Complete production management. The best partners handle everything: scripting, voice casting, recording, editing, and delivery. You should not have to manage multiple vendors or coordinate between a scriptwriter, a voice agency, and an audio engineer. One partner, one step, finished files.

Data security. Your Genesys scripts contain sensitive information, internal routing logic, department structures, and branded messaging. Make sure your production partner does not process your scripts through third-party APIs or external platforms. Ask specifically whether your content stays in-house from start to finish.

Bilingual capabilities. For Canadian contact centers with English and French obligations, confirm your partner can produce parallel voice libraries in both official languages through professional native talent.

Fast turnaround. With a hard deadline approaching, turnaround time matters. Look for a partner that can deliver within 4 to 5 business days as a standard, with rush options available when needed.

Ongoing support. Your Genesys system will continue to evolve after the deprecation deadline. New departments, new flows, seasonal updates. Your voice recording partner should be able to support those changes on an ongoing basis without complicated contracts or retainer requirements.

How COHM Handles Genesys Voice Replacements

COHM has been producing professional voice audio for contact centers across North America for over 40 years. We produce human voice recordings specifically formatted for Genesys Cloud, handling everything from scripting and voice casting to production, formatting, and delivery in the exact file specification your Genesys prompt library requires.

The process is one step for you. Send us your current prompt list and scripts and tell us when you need them. We handle everything else. Most projects are completed within 4 to 5 business days. Rush turnaround is available for teams working to the August 5 deadline.

Your scripts never leave us. All production is handled entirely in-house with no third-party API connections and no external platforms at any stage. For enterprise contact centers in regulated industries, including healthcare, financial services, legal, and government, this means your internal routing logic and branded content stay completely private from start to finish.

COHM’s President serves as an AI Technical Advisor for CAVA, actively working with Canadian lawmakers on biometric data protection, AI voice rights, and data security standards for business. Our approach to data security reflects current best practice at a policy level, not just a product level.

Learn more about COHM’s human voice recordings for Genesys Cloud.

Frequently Asked Questions

The Genesys TTS deprecation is a deadline with a hard date. But for contact centers that act before August 5, 2026, it is also a rare opportunity to upgrade something that has been holding back the caller experience for years. The technology your platform runs on is world class. The voice your callers hear should match it.

Beyond August 5: The Ongoing Risks of TTS Dependency

The August 5, 2026 deprecation is not an isolated event. It is a symptom of a larger problem that contact centers running on third-party TTS voices will continue to face as long as their phone system depends on external API connections for something as fundamental as their brand voice.

Here is what enterprise teams need to understand about the ongoing risks of TTS dependency.

Price increases with no warning. Under the BYOT-A model, your voice costs are tied directly to Google and Microsoft pricing decisions. Either provider can raise their API rates at any time. That increase passes directly to your contact center budget with no negotiation and no notice. A 20% rate increase on a high-volume contact center compounds quickly.

Further deprecations are inevitable. This will not be the last one. AI voice technology is evolving rapidly and platform providers regularly sunset older voice models in favour of newer, more expensive neural TTS options. Every deprecation cycle is another migration project for your IT team, another budget line for reconfiguration, and another period of risk during the transition.

Voice quality changes without your consent. Google and Microsoft update their TTS models continuously. A model update can change the sound, pacing, and tone of your IVR prompts overnight without any notification. Your brand voice changes without your knowledge or approval. For enterprise contact centers that have invested in a consistent caller experience, this is a real and ongoing risk.

API outages affect your callers in real time. When your IVR prompts depend on a live API connection, any service disruption at Google or Microsoft affects your phone system immediately. Callers hear errors, silence, or degraded audio. Static human voice files have no API dependency. They play from your Genesys prompt library regardless of what is happening at any third-party provider.

Terms of service changes are outside your control. Any change to Google or Microsoft’s terms of service can affect how your scripts and audio data are processed, stored, or used. You have no visibility into those changes until they are already in effect.

The alternative is ownership. Human voice recordings produced by COHM are static audio files that you own outright. They cannot be deprecated, repriced, or changed without your knowledge. They are not dependent on any API connection, any third-party platform, or any vendor relationship. Once they are in your Genesys prompt library, they work. Full stop. No renewals, no integrations, no surprises.

For enterprise contact centers evaluating their options after the August 5 deprecation, the question is not just how to solve the immediate problem. It is whether to keep building on a foundation that has already proven unstable, or to invest in voice assets your organization owns and controls permanently.

COHM is ready to help. One step: send us your prompt list and tell us when you need it. We handle the rest.

Get started with COHM’s human voice recordings for Genesys Cloud.

Curious about how COHM can elevate your business? Don’t hesitate to reach out to us today. We prioritize prompt customer service and guarantee a response within 24 hours.

Ready to Collaborate?

"*" indicates required fields

Name*

Company*

Email*

Phone Number*

Interested in

Select…On-Hold MarketingIVR RecordingsPodcast Services

How did you hear about us?

Select…LinkedInFacebookInstagramGoogle SearchReferralPartner’s SiteOther

CAPTCHA