I’m looking for help getting an existing ChatGPT Sites support case surfaced to the appropriate team.
Existing Support Case: 13805023
This is not a request to troubleshoot the full issue publicly. I already have an established private Support case and substantial diagnostic evidence.
The problem is that I have received no response on the original case for several days. When I try to obtain assistance through a new Help Center conversation or email, Support begins responding under a new case, then automatically closes that new case as a duplicate and tells me to continue in Case 13805023.
I have also replied directly to the original Case 13805023 email thread multiple times without receiving a response.
Recent duplicate cases include:
- 14113805 — closed as duplicate
- 14116078 — closed as duplicate
This has created a loop:
new request → Support starts helping → system detects Case 13805023 → new case closes → original case remains unanswered
The underlying issue concerns ChatGPT Sites managed source provenance/authentication for an existing Site.
OpenAI Support previously asked me to run a bounded read-only diagnostic from a fresh Existing Site → Edit environment. That diagnostic confirmed the correct Site checkout and managed origin were present, but the Support-requested fetch reached the managed service and returned HTTP 401 before Git failed for lack of non-interactive credentials.
Subsequent Support guidance said the supported provenance workflow should instead use Sites saved versions. However:
- the current Sites Settings UI exposes no visible version/history/source identifier;
- Support then instructed me to ask the Site Edit assistant to list saved versions;
- that request enters Thinking briefly and then disappears with no response or persisted message.
I have complete diagnostics and screenshots attached to the private Support correspondence and do not need to expose them publicly.
I am deliberately avoiding source changes, Git credential workarounds, new saved versions, restoration, or deployment while this is unresolved.
Could an OpenAI Support staff member please help get Case 13805023 reviewed or routed to the ChatGPT Sites/platform team?
I am happy to continue all technical details privately inside the existing case. I primarily need help breaking the duplicate-case/no-response loop.
Thank you.
@OpenAI_Support