A True Story
The contract was due at 10 AM. Maria had been working on it all weekend. She opened Word, clicked the file - and got a spinning wheel. Then an error: "We're having trouble connecting to Office 365."
She tried again. Same error. Tried opening from OneDrive. Nothing. Her Excel files wouldn't open either. The whole Office suite was dead, and her client was expecting that contract in 48 minutes.
She called Microsoft support.
"Your estimated wait time is... thirty-five minutes. For faster service, visit support.microsoft.com."
Thirty-five minutes. For a document she needed to send in forty-eight.
She stayed on hold. When someone finally answered, they asked for her Microsoft account email. Then her subscription type. Then they wanted to run a diagnostic tool that required downloading something from a website that was loading at dial-up speed.
"I just need to open one Word document," she said. "It's been working fine for two years."
The tech asked if she'd tried signing out and back in. She had. He asked if she'd tried repairing the Office installation. That would take 20 minutes. She had 31 minutes left.
The contract went out late. The client wasn't happy.
THE NEXT WEEK
Maria found my number through a colleague. When her Outlook started freezing every time she opened an attachment - different problem, same panic - she texted me at 8:41 AM.
I called back in under a minute. Connected remotely in five. Turned out a recent Windows update had broken her Office credentials cache - a known issue I'd already fixed twice that week for other clients. Cleared the cache, re-authenticated her account.
Outlook was working again by 8:54.
There's a reason local IT support still exists. Some problems need a person who knows your setup.
