Skip to main content
AI News & Updates

ChatGPT Will Retire Advanced and Standard Voice: Run a Migration Check Before December 11

Check ordinary voice, custom GPTs, and video or screen sharing separately instead of assuming equivalent behavior

ENHE AI5 min4 views

OpenAI says Advanced Voice and Standard Voice will retire on December 11, 2026. Ordinary voice conversations will then default to GPT-Live, and Advanced Voice inside custom GPTs is deprecated on the same date. This guide provides a migration rehearsal rather than assuming the default switch is equivalent. Inventory devices, languages, headsets, custom GPTs, video, and screen sharing; then run one fixed script covering startup, interruption, numbers, names, background noise, and a longer exchange. Record feature gaps and rollback routes for each surface. Live video and screen sharing remain on Advanced Voice until GPT-Live supports them, so a visible voice button alone does not prove migration is complete.

More topic tags (9)
AI NewsAuto PublishingSEOGPTChatGPT VoiceAdvanced VoiceStandard VoiceGPT-Live语音迁移
ChatGPT Will Retire Advanced and Standard Voice: Run a Migration Check Before December 11

Key takeaways

Inventory by device, language, and surface; do not generalize one account result.
Use a fixed script for startup, interruption, numbers, names, noise, and longer conversation.
Keep separate fallback paths for video, screen sharing, and custom GPTs.

By ENHE AI · 2026-11-14 · AI-assisted drafting; pre-publication quality checks completed.

Direct answer: build a migration table before the default switch

Advanced Voice and Standard Voice retire on December 11, 2026. List phone, desktop, web, headset, language, and common scenarios, including current entry point and owner.

Ordinary voice will default to GPT-Live, but default entry does not prove that number dictation, names, noise, or interruptions work for your task. Rehearse once with low-risk content.

A fixed seven-part test script

Use the same public script to test startup, continuous speech, interruption, a six-digit number, two proper names, background noise, and a three-minute exchange. Record pass, error text, and recovery action.

Do not use customer, medical, personnel, or unreleased content in the first rehearsal. This article did not sign in, record audio, or reproduce GPT-Live, so it cannot guarantee device performance.

Validate custom GPTs separately

Advanced Voice in custom GPTs is deprecated on the same date. For each frequently used custom GPT, record opening instructions, tools, language, failure signal, and a non-voice fallback.

Test two representative non-sensitive tasks and confirm custom instructions still apply. Keep confirmation for tool actions. If a workflow depends on old voice behavior, move it to text or ordinary voice first.

An empty workstation represents migration preparation and fallback. Contextual stock photo, not a voice interface or evidence of retirement. Image: Unsplash.
An empty workstation represents migration preparation and fallback. Contextual stock photo, not a voice interface or evidence of retirement. Image: Unsplash.

Video and screen sharing are a separate transition

Live video and screen sharing stay on Advanced Voice until GPT-Live supports them. Put voice-only, camera, and screen sharing on separate rows and observe entry and exit for each.

Prepare text description, a redacted screenshot, or an ordinary meeting tool as fallback. Close notifications and unrelated windows before sharing. A voice pass does not complete visual migration.

FAQ

Will users need to select GPT-Live manually after December 11?

OpenAI says ordinary voice defaults to GPT-Live, but each account and surface should still be checked on the day.

Do video and screen sharing retire at the same time?

They have a separate transition and remain on Advanced Voice until GPT-Live supports them.

Fact evidence

  • Advanced Voice and Standard Voice will be retired on December 11, 2026. — OpenAI Help Center — Retiring Advanced and Standard Voice in ChatGPT
  • After retirement, voice conversations will default to the GPT-Live voice experience. — OpenAI Help Center — Retiring Advanced and Standard Voice in ChatGPT
  • Advanced Voice in custom GPTs is also deprecated on December 11, 2026. — OpenAI Help Center — Retiring Advanced and Standard Voice in ChatGPT
  • Live video and screen sharing remain on Advanced Voice until GPT-Live supports them. — OpenAI Help Center — Retiring Advanced and Standard Voice in ChatGPT

Related tools and reading

These production pages support the same decision, workflow, or safety boundary.

Conclusion

Voice migration is complete only when device, language, custom GPTs, and visual sharing each have observable results and fallback—not merely when a button works. One fixed-script rehearsal now makes the December 11 switch controllable.

What this means for everyday users

Live video and screen sharing stay on Advanced Voice until GPT-Live supports them. Put voice-only, camera, and screen sharing on separate rows and observe entry and exit for each.

Related reading

A voice-agent release checklist for VAD, noise, interruptions, transcription, tools, and failure handoffs

A voice-agent release should not be accepted after one successful conversation in a quiet room. Test cases need to cover speech-activity detection start and stop behavior, silence and background noise, user interruption, transcription evidence and correction, spoken status around tool calls, and state recovery after timeouts or failures. The OpenAI Realtime API reference documents capabilities for real-time sessions, audio input and output, transcription, and server-side voice activity detection. This article turns those capabilities into a general acceptance checklist. It is not a release announcement, a claim about a particular product version, or a performance guarantee. Teams should define their own language, device, privacy, latency, escalation, and human-review criteria before deployment.

ElevenLabs Launches Eleven v4 and v4 Turbo for Expressive Speech

ElevenLabs launched Eleven v4 and the lower-latency Eleven v4 Turbo on September 28, 2026 and updated the announcement on October 5. The company says both models support more than ninety languages, stronger emotional and audio-tag control, multi-speaker dialogue, and more consistent speaker identity across generations. They are available through ElevenAgents, ElevenCreative, and the ElevenAPI. This guide helps creators choose v4 for produced narration, dubbing, and character work or v4 Turbo for interactive voice agents where response time matters. Test pronunciation, pacing, latency, regeneration consistency, and actual credit cost with your own scripts. Obtain clear permission before cloning a real person's voice, label synthetic audio where required, and keep a human listening review before publishing or using a voice agent with customers.

Amazon Polly Upgrades Generative Speech: Validate 14 New Voices Without Breaking Existing Apps

Amazon Polly upgraded its Generative engine on October 22, 2026, adding 14 voices across nine locales and making generative Hindi and Finnish generally available. Existing voice names and API calls remain unchanged, so applications do not need a code migration, but generated audio can still change. This article gives creators, course teams, contact-center operators, and accessibility teams a reversible acceptance test. It uses one multilingual script to compare pronunciation, pauses, latency, loudness, and fallback behavior before increasing traffic. It also separates the larger voice catalog from a key limitation: generative voices still do not provide speech marks, so workflows that synchronize captions, highlighting, or animation must keep a compatible engine or another timing source.

ChatGPT Adds an Accounting Plugin: Keep Source, Variance, and Approval Tables for Month-End Work

OpenAI announced the ChatGPT Accounting plugin on November 18, 2026. It can help reconcile transactions, draft invoice entries, and prepare month-end reports from records and templates, while Enterprise workspaces still require administrator approval before installation. This article does not provide personalized accounting or financial advice. Instead, it supplies three control tables: a source table for files, periods, and versions; a variance table for every unmatched amount; and an approval table that names who may confirm, export, or roll back a change. Bank access, payments, credentials, and final posting remain human-reviewed steps. The plugin output is a reviewable draft, not a closed accounting period or evidence that the underlying records are complete.

Gemini 4 Neon Reaches GitHub Copilot: Compare Cost per Accepted Result, Not List Price Alone

GitHub announced Gemini 4 Neon as generally available in Copilot on November 18, 2026 for Pro+, Max, Business, and Enterprise users. It uses provider list pricing under usage-based billing, administrators can manage access through model policy, and availability is rolling out gradually. This article proposes a same-task comparison instead of a list-price decision. Freeze three representative tasks and their inputs, then record accepted results, human edits, tool calls, elapsed time, and billed cost for Neon and the current model. If the model is missing, check plan, client, rollout, and policy before assuming an outage. Change the default route only when both outcome quality and total task cost meet the baseline. No model run, benchmark, or bill was performed for this article.

GitHub Copilot Evals Enters Preview: Regression-Test Skills, Agents, and MCP Changes

GitHub launched Copilot Evals in public preview on November 17, 2026. It creates repeatable tests for skills, custom agents, and MCP tools and lets users compare runs before and after a customization change. This guide defines a minimum regression set: choose three realistic tasks, then specify the input, allowed tools, success criteria, and prohibited behavior for each. Preserve at least one baseline run and one post-change run, including the result, execution path, failed checks, and human review. Merge a customization only when the change preserves the original task, permission boundary, and evidence chain. A single passing answer is not enough because model output can vary, and an automated check cannot decide every domain-specific quality or safety question.