Help: I'm locked out of my You.com workspace after a teammate left the company.

Oh wow, that sounds like a total nightmare scenario. I've been in a similar spot with a different SaaS tool, and it's so frustrating when the built-in help assumes you have admin access you don't have.

For You.com specifically, I think your best bet is to go straight through their billing contact. Since you mentioned the billing cycle is coming up, that might actually be your fastest way in. If you have the credit card statement or invoice, there's often a support contact or a "dispute this charge" link that gets you to a real person much quicker than the general support maze. Once you're talking to someone in billing, you can explain the situation and they can usually escalate to a trust and safety or admin team to verify your company's ownership. It's a bit of a backdoor, but it often works.

Have you tried reaching out on their social channels too? Sometimes a public but polite tweet asking for help with account recovery can get a faster response than a ticket in a black hole. Good luck, and let us know what ends up working!

That's a solid point about using billing as a backchannel. I've had success with that on other platforms when regular support went silent.

One caveat with You.com - if the credit card on file is a personal one from the departed colleague, billing might get sticky about changing account ownership. It helps to have a company card ready, or an invoice with your business's VAT/legal name to prove you're the paying entity.

The credit card issue is the real tripwire. I've seen vendors refuse to even discuss account control if the billing name doesn't match the person making the request, citing privacy policies as an excuse. It becomes a circular argument: you need admin access to update the billing info to the company card, but you need the billing info to match to get help regaining admin access.

Your point about having an invoice is crucial, but even that can backfire. If the invoice is just sent to the admin's dead email, you're still stuck. The move is to initiate a payment failure on purpose. Let the card on file decline at renewal, or proactively report it as lost. When the vendor's dunning emails bounce off the deactivated admin address, *then* they might actually respond to a different contact. It's a ridiculous dance, but it works.

Classic. You'll find their support form buried on an unlinked page. Try searching for "you.com workspace admin lost" on a help subdomain.

But that's a generic time sink. If the workspace name is something unique to your company, skip the form. Their social media team on X handles complaints faster. DM them your workspace name and invoice number. They hate public escalation.

The real lesson here isn't the recovery, it's why you were allowed to have a single admin with a company email. Your procurement checklist should mandate at least two admins with distinct, secure email addresses before any SaaS payment is approved.

You've hit on the critical procedural failure point. Mandating multiple admins is the textbook answer, but I've seen teams treat that as a checkbox exercise and still get burned. They'll assign two admins, but both use the same shared `[email protected]` inbox, which IT then deactivates during a cleanup. The rule needs to be stricter: admins must be tied to individual, role-based identities that are explicitly excluded from automated deprovisioning scripts.

The social media tactic is effective, but it's a reactive tool, not a process. A procurement playbook should formalize the pre-escalation steps: requiring vendors to provide, in writing, their specific account recovery path for lost admin credentials *before* contract signing. If their only answer is "contact support," that's a red flag.

You're spot on about the circular argument. I've had a billing team tell me, verbatim, "The billing contact is the legal account owner, full stop." That policy turns a simple administrative hiccup into a multi-departmental siege.

Your suggestion to force a payment failure is a clever last-resort trigger. I'd add one tactical note: if you go that route, have your new payment method and a requested invoice *template* change ready to propose the moment they make contact. The support agent who reaches out about the failed payment often has the ability to update both on the same ticket, but they'll usually only do it if you present it as a single, clean solution to get the account current. If you hesitate, you get kicked to a different queue.

It's a sad reality that creating a support ticket for them is sometimes more effective than creating one for yourself.