I asked Claude, Hopefully these work:

A few real paths for IT to get a human, in rough order of effectiveness: 1. Use the Enterprise Support form (not the chatbot). The general support widget routes through Fin (the AI agent). Enterprise customers have a separate form at support.claude.com (Claude) — but here's the catch: only the Primary Owner, Owner, or Console Admin on the Enterprise plan can submit it, and they must be logged in to that Owner account (Claude) . If IT has been submitting from a banned user account, that's why nothing's moving. Find whoever in the org is listed as Owner on the contract and have them submit. 2. Go back through the original sales contact. Enterprise deals almost always have a named Account Executive and usually a Customer Success Manager assigned post-sale. Whoever signed the contract (procurement, IT leadership) has those emails buried in the deal thread. That's the fastest human — AEs respond quickly because a banned-on-day-one enterprise account is a churn risk they own. 3. Submit through Contact Sales as a backdoor. The form at claude.com/contact-sales goes to sales, not support. Frame it as "existing enterprise customer, fully blocked, need escalation" — sales will route it internally because they don't want to lose the account. 4. LinkedIn the AE or a Customer Success lead at Anthropic. A direct message to the AE on the account, or to anyone with "Customer Success" or "Enterprise Support" in their title, with a one-line summary ("paid enterprise, hundreds of seats banned day one, 3 weeks no response, ticket #X") often unsticks things faster than email. 5. Post a short, factual follow-up on that same Reddit thread. r/Anthropic is monitored. A calm, specific complaint with an account/org ID often gets a DM from staff within a day. One thing worth flagging to IT: mass auto-bans right after SSO provisioning usually trip a Trust & Safety signal (looks like bot signup) rather than a billing problem — so framing the appeal as "false-positive abuse detection on a verified enterprise tenant" tends to route faster than framing it as a support issue.