I took some time off from work this week. I’m going to spend a couple of days at home catching up and taking care of some things for my parents, then spend some time at the lake with my family. I know I need the break because even a few days of chores before going off to play sounds appealing to me. Today was my last day in the office until next Monday. Woot! Woot!
The company I work for was recently purchased by another company and we are now a subsidiary. My coworkers and I have all had to learn to adapt to change, which has come in waves over the last few months. Last week, our computers were moved from our old network to the new company’s network. There are many positive changes, but everything looks, feels and behaves differently than I’m used to. It seems to take me three times as long to do the same work. I know I’ll find my groove soon enough, but sometimes it’s hard to be patient. Thankfully, we are all given as much leeway as we need to figure out the new stuff.
This afternoon, as I was winding down for the day and getting ready to head home, I remembered that I wanted to turn on my out-of-office message so that any clients trying to contact me over the next few days would know that I was unavailable for the remainder of the week. But when I clicked the option to compose a message, I received an error stating that the action couldn’t be completed because the server was down. Of course, I didn’t believe the error message, so I checked with a coworker to see if she would have the same problem. She didn’t. Her out-of-office message assistant worked just fine.
One of the really nice perks of working for this new company is that they have a phenomenal help desk. All I have to do is dial a four-digit extension and someone is there to help me with whatever problem I might have. I don’t even have to identify myself. The help desk knows who is calling! So I called to ask for help with my out-of-office problem and I was assisted by a very nice guy named Tom.
Tom asked permission to remote into my computer and I handed over control. He looked around at my settings, tried various things, shut down Outlook and opened it up again, all to no avail. He created a new email profile to see if the out-of-office assistant would function, but that didn’t work either. He explained what he was doing and proposed various theories as he searched for an answer. He really seemed to know what he was doing, even though he couldn’t find an immediate answer to my problem. He then asked what time I was done for the day. “About ten minutes ago,” I said.
“Oh, well then,” he replied. “I’m here late tonight, so I can probably get it figured out before I go home. Once I know what the problem is, I’ll get in touch with you so you can test it to make sure it’s fixed. What time will you be in tomorrow?”
“I won’t be. Actually,” I said, “I’ll be … out of the office … tomorrow…?”
I swear I heard him slap himself on the forehead. Of course,” he said! “Hence the reason for your call!”
“Uh-huh,” I laughed. I assured Tom that I could probably survive without the out-of-office auto reply this time and that I would connect with him again on Monday, when I’m back in the office.
At least all this change and frustration comes with some laughs.