You upgraded to Plus specifically for Advanced Voice, opened the iOS app, tapped the waveform icon, and got “Advanced Voice is not available in your region” — or worse, the icon shows the old voice mode (canned voices, no interruptions) without any error at all. Advanced Voice is the real-time, speech-to-speech mode that streams audio in and out without a transcription hop. It is gated by a layered set of conditions: country of your OpenAI account, plan tier, app version, sometimes A/B rollout flags, and (in the EU/UK/CH/EEA) a separate compliance gate that lagged the US launch by weeks. Most failures are one of those gates, not a real outage.
Common causes
Ranked by what we see most in support threads.
1. Account country is on a staged-rollout list
OpenAI rolls Advanced Voice out by country, not by user IP. The country tied to your account (set at signup, sometimes inferred from billing address) determines eligibility. EEA, UK, Switzerland, and several APAC countries got it weeks after the US launch. A few countries still do not have it at all.
How to spot it: Settings → Account → Country shows a country that was added late. Friends in the US on the same plan see the feature; you do not.
2. Client app version is below the minimum
Advanced Voice requires a recent iOS / Android / macOS / Windows build (the exact minimum changes per platform). An app from six months ago will silently fall back to the legacy voice mode, even when your account is eligible.
How to spot it: App version string (Settings → About) is more than ~2 months old. Same account on a freshly installed device shows the feature.
3. Plan tier mismatch — free or expired Plus
Advanced Voice is Plus / Team / Pro / Enterprise only. If your Plus subscription lapsed (auto-renew failed, card declined), the feature flips off within hours. Free accounts get a limited preview minute count per day, but the full feature is gated.
How to spot it: Settings → Subscription shows “Free” or “Plus (expires …)” with a past date. See ChatGPT Plus downgraded without notice for the silent-downgrade pattern.
4. EU / EEA / UK regulatory hold lifted late
For a stretch of 2024-2025, Advanced Voice was withheld in the EU/EEA/UK/CH pending GDPR / DSA review. It has rolled out since, but the gate is still per-country, not per-region — France enabling does not mean Germany enabled the same day.
How to spot it: You are in the EU/EEA and the in-app banner mentions “available soon in your region” or the feature simply is missing from Settings.
5. Org / Enterprise admin disabled it
For Team / Enterprise accounts, the workspace admin can turn Voice off in the admin console (data-residency, compliance, or cost reasons). Individual users see the feature as if their plan does not include it.
How to spot it: Personal Plus account on the same device shows the feature; the Enterprise account does not.
6. VPN / DNS rerouting confuses the rollout flag
The client sends your network egress IP and account country to the rollout service. A VPN that puts you in a non-rolled-out country can flip the feature off, even when your account country is fine.
How to spot it: The feature works on cellular but not on Wi-Fi behind a corporate VPN, or vice versa.
7. Microphone permission revoked or muted
Less of a “region” issue but cosmetically identical: the Voice button is greyed out with a vague tooltip. If iOS / macOS denied mic permission, the client falls back to a disabled state that looks like a region gate.
How to spot it: System Settings → Privacy → Microphone shows ChatGPT toggled off, or the OS-level mic indicator never lights up when you tap the voice button.
Before you start
- Note the exact wording of the error / disabled state — “not available in your region” and “your plan does not include this” point at different gates.
- Confirm what country is on your account vs. where you are physically.
- Identify the platform (iOS / Android / macOS / Windows / web) and exact app version.
- If you are on Team / Enterprise, know whether you are admin or end user.
- Save a screenshot of the disabled state — useful for support tickets.
Information to collect
- OpenAI account country (Settings → Account).
- Subscription tier and renewal date.
- Client platform and version string.
- Network: cellular, home Wi-Fi, corporate VPN — and which ones the feature toggles between.
- For Team / Enterprise: admin console workspace settings → Voice toggle state.
- Microphone permission state at the OS level.
Step-by-step fix
Ordered to eliminate the cheapest gates first.
Step 1: Update the client to the latest version
App Store / Play Store / direct download. Force-quit and relaunch. On macOS, also clear the older build:
rm -rf "/Applications/ChatGPT.app"
# then re-download from openai.com/chatgpt/downloadAfter update, sign out and back in once — the client caches feature flags per session.
Step 2: Verify account country and subscription
Web: Settings → Account → Country. If wrong, you can update it (some users report this requires support contact in certain regions). Settings → Subscription should show an active plan with a future renewal date. If it shows past-due or free, see ChatGPT subscription not recognized.
Step 3: Disable VPN and corporate proxy, retest
Turn off any VPN. Switch to cellular if Wi-Fi runs through a corporate proxy. Restart the app. If the feature appears now, the gate was network-level — keep VPN off when using Voice or whitelist api.openai.com and the WebRTC endpoints in your VPN’s split-tunnel config.
Step 4: Check microphone permissions
iOS: Settings → ChatGPT → Microphone (must be ON). Android: Settings → Apps → ChatGPT → Permissions → Microphone (Allow). macOS: System Settings → Privacy and Security → Microphone → ChatGPT (ON). Windows: Settings → Privacy → Microphone → ChatGPT (ON).
If permission was previously denied, OS-level UI may not re-prompt — toggle off and on, then relaunch.
Step 5: For Team / Enterprise, check the workspace toggle
Admin console → Settings → Features → Voice mode. If your admin disabled it, individual user-side troubleshooting will not help. File a ticket internally rather than with OpenAI.
Step 6: Sign out everywhere and sign back in
Feature-flag caches are bound to the session. A full sign-out forces a fresh fetch from the rollout service:
- ChatGPT app → Settings → Sign out of all devices.
- Wait 30 seconds.
- Sign back in on your primary device only.
This single step fixes a surprising fraction of cases where the account is eligible but the cached flag says otherwise.
Step 7: If still missing, switch the model picker explicitly
In a new chat, tap the model picker. If it shows GPT-5.5 (Voice) or similar variant, select it explicitly. The default-routing logic sometimes routes around the voice-capable model in regions where it is partially rolled out.
Step 8: Last resort — file a support ticket with evidence
Go to help.openai.com and submit a ticket with: account country, plan, app version, platform, screenshots of the disabled state, and confirmation you tried steps 1-7. Tickets with this metadata get answered in days; vague “voice does not work” tickets often get a templated reply.
Verify
- Open a new chat. The voice button (waveform / sphere icon) is present and not greyed out.
- Tapping it shows the Advanced Voice UI (animated orb, no “Press to speak” intermediary), not the legacy mode.
- Speaking is interrupted naturally when you speak over the model — that confirms real-time bidirectional streaming.
- Switching to cellular and back keeps the feature available.
Long-term prevention
- Keep the ChatGPT app on auto-update; do not manually pin an old version.
- If you travel internationally, set your account country to your true residence — frequent changes can flag the account.
- For corporate networks, get
api.openai.comand WebRTC endpoints on the allowlist once, rather than per-incident. - Re-check the rollout status every couple of months in EU/EEA/UK — features ship in waves.
- For Team/Enterprise users, document the admin toggle state in your onboarding wiki so users do not file individual support tickets.
- Bookmark help.openai.com/voice-mode-availability for the official country list (it changes).
Common pitfalls
- Confusing the legacy “Voice” mode (turn-based, transcription-then-TTS) with Advanced Voice. Legacy mode has been available far longer and in more regions.
- Assuming a VPN-to-US workaround is supported — it sometimes works briefly, then the rollout service catches up and disables the feature again.
- Updating only the OS, not the app. App version is what matters.
- Believing a friend’s claim that “it works in country X” without confirming their account country (they may have a US account).
- Cancelling and re-subscribing to “reset” the feature flag — this does not help and may delay billing reactivation.
- Granting mic permission, then ignoring the secondary “Speech Recognition” toggle on iOS (separate permission for some versions).
FAQ
Q: Why does my web browser ChatGPT not have Advanced Voice?
Advanced Voice on web rolled out after mobile and is still gated to a subset of Plus / Team / Pro accounts in supported countries. Use the iOS / Android / desktop app for the most consistent availability.
Q: I switched my account country from EU to US. Will I get the feature now?
Probably not, and you risk an account flag. OpenAI uses billing-address and behavioral signals as well as the country field — changing the country alone usually does not flip the rollout flag.
Q: Does Advanced Voice count against my message cap?
It uses a separate voice-minutes quota on Plus/Team. Heavy use can trigger a per-day throttle even when your text message cap is fine. See ChatGPT message cap reached for the related text-side limit.
Q: The voice button works but the model sounds like the old voices. Did I get the wrong mode?
Probably yes — that is the legacy voice mode. Advanced Voice has a distinct animated orb UI, supports interruptions, and the voices are more expressive. If the UI shows a static waveform with a stop button, you are on legacy.
Q: I am on Enterprise with the toggle disabled. Can I bypass it on my personal account?
Switching to your personal Plus account on the same device will surface the feature if your personal account is eligible. The Enterprise toggle only affects the Enterprise workspace, not your personal subscription on the same client.