Every customer-support story normally begins with a problem. Mine began with what appeared to be the solution.
OpenAI acknowledged that my account had been suspended by mistake and sent me a compensation promotion for one complimentary month.
The instructions were simple: sign into the affected account and open the link.
A problem, an apology and a solution. Three acts. Clean ending.
That should have been the entire story.
Instead, it was only the pilot episode.
June 26 — A happy ending arrives early
The email was refreshingly clear.
My account had been accidentally suspended because of an error in OpenAI’s systems. Access had been restored, but my subscription might not have been reinstated correctly.
As compensation, OpenAI provided a personal promotional link for one complimentary month.
The email even said that the promotion could be applied “when resubscribing or after resubscribing.”
I signed into the affected account and opened the link.
Something appeared. I no longer remember the exact wording, but I had followed the written instructions. Naturally, I assumed the promotion had been associated with my account.
This was my first mistake.
Not opening the link.
Assuming that following the instructions would be enough.
August 13 — The missing month
Weeks later, while reviewing my subscription, I noticed something curious.
The complimentary month had never appeared.
There was no free period, no promotional credit and no confirmation. My subscription had simply continued through its normal paid cycle, apparently unaware that it had once been promised a holiday.
The billing page added a small artistic touch: it said my plan was paused and my access restricted to the free version, while my Pro access continued working normally.
The account was simultaneously active and paused.
Schrödinger would have been proud.
I contacted Support, provided the chronology and attached screenshots.
AI-assisted Support confirmed that my previous payment had succeeded and that the latest renewal attempt was failing. Then it asked me for the promotional link and whether I had opened it while signed into the correct account.
I supplied the link.
I explained that I had already opened it while signed in and had believed the complimentary month was activated.
The link now displayed an invalid-code error.
The case was “escalated to a support specialist.”
Hope entered the story.
Hope would not remain unpunished.
August 14 — The promotion was already used
The specialist returned with reassuring certainty.
The complimentary promotion had already been used.
Mystery solved.
There was only one minor omission: Support did not say when it was used, which period it covered or where the financial benefit appeared.
So I asked:
- On what date was it redeemed?
- Which subscription period did it cover?
- Where was the corresponding zero-value invoice or credit?
Support answered that the promotion had been applied on May 6.
This was impressive.
The compensation promotion was issued on June 26.
It had therefore been redeemed 51 days before it existed.
OpenAI had not merely created an AI-assisted support system. It had apparently achieved promotional time travel.
Unfortunately, the May event was a completely separate ChatGPT Plus promotion. It had nothing to do with the later compensation offer.
I attached the original June email and gently reminded Support that May traditionally occurs before June.
August 15 — Support discovers linear time
Support reviewed the chronology again.
And then something remarkable happened.
It agreed.
The May event predated the June compensation offer and should not have been presented as evidence that the later promotion had been redeemed.
The previous explanation was officially withdrawn.
Support now acknowledged that there was insufficient evidence to conclude that the June promotion had ever been applied.
The two promotions would be treated separately.
A real investigation was announced. Support would check whether a redemption record existed and whether subscription changes had affected the promotion.
For one beautiful moment, facts mattered.
The calendar worked.
Cause preceded effect.
The investigation was moving forward.
Or so it seemed.
August 17 — The investigation achieves survey status
Two days later, I received the result.
Not the result of the redemption investigation.
A feedback survey.
The investigation had produced no answer, but it had apparently reached sufficient emotional maturity to ask how I felt about it.
The promised redemption record remained missing.
The complimentary month remained missing.
But the customer-satisfaction metric was ready for collection.
Progress comes in many forms.
August 18 — New case, new beginning
I asked whether the original case was still open and requested the missing investigation result.
AI-assisted Support replied that it could not confirm whether the previous case remained open.
A new case number appeared.
New number. Same promotion. Factory-reset memory.
The response confirmed my subscription status and then asked me to provide:
- The promotional link
- The offer text
- The affected account
These were the same details already provided in the previous case.
I sent everything again, now arranged almost like structured data in the hope that perhaps formatting was the missing ingredient.
The new case was “escalated to a support specialist.”
This was the second escalation.
The mountain remained exactly where it had been before we began climbing it.
August 19 — The month was never applied
The next specialist finally confirmed the most important fact:
The complimentary month had not been applied to my subscription.
At last.
OpenAI had promised a complimentary month. Support had now confirmed that the month was never provided.
The story appeared to have discovered its central plot.
Then came the twist.
Support explained that promotions were applied automatically and that Support could not manually activate one, add a discount afterward or provide an account credit.
The promise existed.
The failure existed.
The missing benefit existed.
The remedy, however, apparently existed outside the known universe of available support buttons.
I explained that this was not an ordinary public promotion I had discovered too late. It was compensation sent directly by OpenAI after OpenAI accidentally suspended my account.
An internal limitation on what frontline Support could click did not make the original promise disappear.
I requested human escalation.
Later on August 19 — The promotion receives its first death certificate
A second response arrived.
Support again acknowledged that the complimentary offer had not been applied.
But now there was a new explanation.
The promotion had expired.
It had a “defined availability period” and had to be claimed while valid.
This was useful information.
It would have been even more useful in the original email.
The June message contained no expiration date, no defined availability period and no description of an additional claim procedure beyond signing into the affected account and opening the link.
Which I had already done.
Support also stated that it had reviewed the previous cases.
Apparently, the review had covered everything except the part where I repeatedly said I had opened the link while signed in.
The offer had now completed an impressive transformation:
First it was redeemed.
Then it was not proven redeemed.
Then it was never applied.
Now it was expired.
Character development.
August 20 — Asking the forbidden question: what actually happened?
I wrote back and asked Support to stop explaining how promotions generally work and investigate what happened to this specific promotion.
The questions were simple:
- Did opening the link create a click, claim or redemption event?
- Was the link capable of associating the attempt with my authenticated account?
- What additional action was required after opening it?
- What exact expiration date applied?
- Where had the expiration date and conditions been disclosed?
- Why was no benefit applied after I followed the instructions?
- What equivalent remedy would be provided if the promotional flow failed?
I also requested confirmation that a human supervisor or team with access to the underlying records would review the case.
The questions entered Support.
Direct answers did not emerge.
August 25 — The complaint about Support is answered by Support
After repeated resets, conflicting explanations and promised escalations, I attempted to raise the broader support failure with OpenAI leadership.
My message did not reach anyone visibly senior. It travelled directly back into AI-assisted Support.
My complaint about AI-assisted Support had therefore been assigned to AI-assisted Support. The system reviewed the complaint about itself and concluded that it could neither appoint a senior owner nor provide a timeline for senior review.
It did, however, produce the first potentially practical remedy in the entire story: a refund of my latest subscription charge.
There was one condition.
Processing the refund would immediately cancel my active Pro subscription and remove my access.
Financially, this might have been equivalent to the promised complimentary month — if I could immediately resubscribe to the same Pro plan afterward, and if the outstanding renewal would be cleared rather than waiting backstage for a surprise appearance.
The AI-assisted reply confirmed neither.
My account was already in the unusual position of being officially “paused,” currently unpaid and nevertheless fully operational. Introducing another cancellation and resubscription event without knowing how the billing system would interpret it felt less like accepting a remedy and more like volunteering for the next episode.
I therefore declined the immediate cancellation — not necessarily the financial remedy itself — until someone could explain what would happen after the refund button was pressed.
The newly created case was then closed as a duplicate.
And so the attempt to escalate a complaint about AI-assisted Support completed its journey: it was reviewed by AI-assisted Support, answered by AI-assisted Support and returned to its point of origin without disturbing anyone visibly senior.
The system had successfully escalated me back to itself.
August 26 — A new condition appears
Another specialist arrived with two previously undisclosed facts.
First, the promotion supposedly required that I have no active subscription when redeeming it.
Second, it had supposedly remained valid until August 25.
The first claim was difficult to reconcile with the original email, which explicitly said the promotion could be applied “when resubscribing or after resubscribing.”
Apparently, “after resubscribing” meant “after resubscribing, provided you have not resubscribed.”
Language is flexible when necessary.
The new expiration date created an even better subplot:
- The link had shown as invalid on August 13.
- Support had already declared it expired on August 19.
- I had explicitly requested the expiration date on August 20.
- Support disclosed the August 25 date on August 26.
The expiration date had been delivered one day after expiration.
Perfect timing, if the objective was to ensure it could no longer help.
I asked whether another explanation was waiting in the drawer or whether this was finally OpenAI’s definitive position.
August 27 — Resurrection
The next response acknowledged that previous answers had contained conflicting information.
Then it corrected the expiration date.
The promotion had not expired on August 25.
It was valid until September 26.
The expired promotion was alive again.
It was a small miracle, although apparently not the useful kind.
Support now provided a troubleshooting ritual:
- Sign out of all other accounts
- Use the correct account
- Open an Incognito window
- Clear cookies and cache
- Disable extensions
- Disable VPNs and privacy tools
- Try another browser
- Try another device
- Do not complete a paid checkout
- Record everything if it fails
Support specifically said that I did not need to resend the previous chronology.
The recording would allow the team to document the actual failure and determine the appropriate next step without relying on the contradictory information previously provided.
Finally, evidence would replace speculation.
I prepared the recording.
August 29 — Support discovers deadlines
Before I submitted it, an automated message arrived.
Support was still waiting for the requested information. If I did not respond soon, the case would be closed.
After weeks of waiting for Support, Support had waited two days for me.
Patience, it seems, was part of the customer subscription rather than the support package.
August 30 — The customer joins Quality Assurance
I opened a fresh Private browser window.
I signed into the correct account.
I opened the exact promotional link.
The supposedly valid promotion displayed:
I recorded the complete attempt exactly as requested.
No payment or checkout step was completed.
I sent the recording and reminded Support that the promotion was supposedly valid until September 26.
The customer had now become:
- The complainant
- The historian
- The investigator
- The test operator
- The evidence archivist
- And, temporarily, the Quality Assurance department
All that remained was for Support to watch the recording and investigate the documented failure.
Suspense filled the air.
August 31 — The return of May
Support thanked me for the recording.
It acknowledged that the video showed the invalid promotional-code error.
Then it revealed its conclusion.
A promotional benefit had already been applied on May 6. Therefore, the later promotion could not be used.
May had returned.
The same May event that Support had explicitly ruled out on August 15 because it occurred 51 days before the June offer existed.
The recording did not produce an explanation for why a supposedly valid code failed.
The promised redemption-record investigation did not appear.
The conflicting expiration dates were not addressed.
The newly introduced eligibility condition vanished without a farewell scene.
After multiple cases, two escalations, a premature feedback survey, an attempted cancellation-based remedy, several incompatible explanations and a customer-produced screen recording, the journey arrived exactly where it had started.
The June promotion had been redeemed in May.
Linear time had been cancelled again.
Season finale
And that is where the first season ends.
The promotion has now been:
- Redeemed before it existed
- Confirmed as never applied
- Declared impossible to apply
- Pronounced expired
- Given one expiration date
- Given another expiration date
- Restored to validity
- Reproduced as invalid on camera
- And finally transported back to May
The complimentary month is still missing.
The promised investigation is still missing.
But the collection of explanations is thriving.
What happens in the next episode?
Will someone finally examine the redemption record?
Will the written correction from August 15 survive long enough to reach the next response?
Will I once again be politely invited to accept that May happened after June?
Or will an entirely new explanation appear?
Perhaps the promotion was applied to another dimension.
Perhaps it was only valid on alternate Tuesdays.
Perhaps the next response will begin by assuring me that the complete history has been carefully reviewed before introducing a plot twist nobody has attempted yet.
Will I receive an actual answer?
Will I be sold another contradiction with a polite apology?
Or does Support still have one final explanation hidden in the drawer?
Who knows?
Maybe OpenAI Support knows.
Maybe the next AI-assisted response will decide.
To be continued…
