# Codex phone verification loop still blocks access after support request

**URL:** <https://community.openai.com/t/codex-phone-verification-loop-still-blocks-access-after-support-request/1387455>\
**Category:** Codex\
**Created:** [July 19, 2026, 1:48am UTC](https://community.openai.com/t/codex-phone-verification-loop-still-blocks-access-after-support-request/1387455 "2026-07-19T01:48:18Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![lin\_hao](https://avatars.discourse-cdn.com/v4/letter/l/b4bc9f/32.png) [@lin\_hao](https://community.openai.com/u/lin_hao)\
**Post date:** [July 19, 2026, 1:48am UTC](https://community.openai.com/t/codex-phone-verification-loop-still-blocks-access-after-support-request/1387455/1 "2026-07-19T01:48:18Z")

</div>

Scheduled follow-up / new status update

My Codex access is still blocked by a phone-verification loop that only offers SMS or WhatsApp to an old, unavailable number. I have already submitted a support request through [help.openai.com](http://help.openai.com) and have been monitoring the related community discussion, but I still have no resolution.

Could an OpenAI staff member please advise whether this account-level verification issue can be reviewed or escalated? I can provide screenshots, billing proof, device and browser details, and any ownership verification through the official support channel. I am not posting personal contact details here.

Thank you.

---

<div class="post-metadata">

**Author:** ![EricGT](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/ericgt/32/20571_2.png) [@EricGT](https://community.openai.com/u/EricGT)\
**Post date:** [July 19, 2026, 11:34am UTC](https://community.openai.com/t/codex-phone-verification-loop-still-blocks-access-after-support-request/1387455/2 "2026-07-19T11:34:42Z")

</div>

OpenAI has no way to associate a Discourse forum account with a specific ChatGPT account.

That is why users are asked to post their Case ID. The case should already be linked to the email address associated with the affected ChatGPT account, while allowing private information to remain within the support correspondence. The Case ID then serves as the preferred single reference point for all information related to the issue.

---

<div class="post-metadata">

**Author:** ![lin\_hao](https://avatars.discourse-cdn.com/v4/letter/l/b4bc9f/32.png) [@lin\_hao](https://community.openai.com/u/lin_hao)\
**Post date:** [July 20, 2026, 3:09am UTC](https://community.openai.com/t/codex-phone-verification-loop-still-blocks-access-after-support-request/1387455/3 "2026-07-20T03:09:08Z")

</div>

Scheduled follow-up: I believe my OpenAI Support case number is 11775051. I am sharing only this reference as suggested; all personal verification details remain in the private support conversation. My Codex phone-verification issue is still unresolved, and I would appreciate any OpenAI follow-up on this case. Thank you.

---

<div class="post-metadata">

**Author:** ![OpenAI\_Support](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/openai_support/32/561845_2.png) [@OpenAI\_Support](https://community.openai.com/u/OpenAI_Support)\
**Post date:** [September 25, 2026, 8:07pm UTC](https://community.openai.com/t/codex-phone-verification-loop-still-blocks-access-after-support-request/1387455/4 "2026-09-25T20:07:02Z")

</div>

@lin\_hao, thanks for the update, and thanks to @EricGT for helping point you in the right direction.

I can see that the Support case you shared has already been reviewed and addressed by the Support team.

If you have any other questions or run into a new issue, feel free to open a new Community thread or reach out to OpenAI Support through help.openai.com.

-Farah

---

<div class="post-metadata">

**Author:** ![avinash.api](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/avinash.api/32/741581_2.png) [@avinash.api](https://community.openai.com/u/avinash.api)\
**Post date:** [September 25, 2026, 8:07pm UTC](https://community.openai.com/t/codex-phone-verification-loop-still-blocks-access-after-support-request/1387455/5 "2026-09-25T20:07:09Z")

</div>

Closed on September 25, 2026, 8:07pm UTC


