Allow GPT builders to disable Voice Mode when Custom GPT Actions are not supported

I fully agree that the real solution should be Voice Mode working properly with function calls / Actions in Custom GPTs. If I could choose, that would absolutely be my preferred outcome as well. My point is not that an opt-out flag should replace proper Voice + Actions support. It is more of a practical fallback while that support is unavailable or unreliable. I can imagine that making function calls work fluently in a real-time, low-latency voice interaction may be technically difficult. But compared to that, conditionally disabling the Voice Mode entry point — or giving builders a simple flag to disable it — should be much easier. Right now the UX is worse than just “feature not supported.” The user is actively offered Voice Mode, enters it, and only then discovers that the GPT can no longer perform its core task. For GPTs that depend on backend calls, that is a broken flow. So yes: Voice Mode + Actions should be the goal. But until that works reliably, builders need a way to prevent users from being routed into a mode where the GPT is known to fail.