FILE 04 / 04
Provider dossier
xAI (Grok)
What Grok users keep running into, and the evidence that matters when they do. With xAI the default support path is silence, so precision and persistence carry the case.
The account architecture single point of failure
- Login is frequently bound to an X account.
- If the X account is suspended, even for unrelated or unclear reasons, the user can lose access to paid Grok and the billing/cancellation portal at once.
- This single point of failure is unique among the four major providers.
Billing and activation failures
- Money taken but the plan never activates.
- The Stripe portal sometimes missing the cancel button (ad-blockers or UI issues).
- Support replies pointing users back to the same inaccessible pages.
Support silence and status opacity
- support@x.ai frequently produces bot loops or multi-week non-responses; escalation paths are weaker and less documented than the other three.
- Service can be degraded while status reporting stays green, your own error timestamps and community corroboration are the record.
- Weekly limits that feel aggressive for the price; moderation can tighten without notice.
What moves the needle herexAI
Start with the boring stuff. It's usually the strongest stuff.
- Bank/Stripe confirmation of payment.
- Every unanswered support email logged with dates.
- Exact error messages (e.g. "unauthorized: x-user-suspended").
- Persistence. The default path is silence; a documented, dated trail is what eventually breaks it, and what your bank needs for a chargeback.
Where your evidence lives
Invoicesgrok.com / X Premium billing settings (or App Store / Play Store subscriptions). Download every receipt.
UsageScreenshot usage meters, limit notices, and error banners with the time visible.
StatusSearch "xAI status page" for the current URL; screenshot in-app errors as your primary record.
SupportIn-app support / help links from grok.com or X Premium settings. Capture any ticket ID.
APIconsole.x.ai → usage and billing. Export for the affected period.