Sorry for the confusion, I took a look back at your account notes and see that you did have some issues with one of our support reps. However it's important to note that this wasn't JeffMa as he works with us back here in the Customer Community department.
Our support role is a bit different than the standard support you'd call in or chat to, as we monitor our public support channels and work on guides for our support center. So Jeff was just doing his standard job of responding to a request here in our public Q&A section, and I don't see any mention of him working with your account previously, at least in our system.
I definitely apologize for the lackluster support experience that you had. It's no excuse, but we are all human, and at times our support reps could be dealing with increased call/chat volumes and this can lead to incidents where the correct information is not relayed appropriately.
All of us back here maintaining the documentation in our support center all worked standard support for some time, and we've had a great deal of success quickly helping customers by pointing them in the correct direction with documentation to solve their problem. Now this isn't full proof and unfortunately some times a link to the support center is given in haste without first fully understanding what the customer is having issues with.
In some cases we've had customers leave us comments on the article they were sent to, letting us know the rep they just spoke with on the phone told them that article would fix their problem and it doesn't. We're glad to look further into the issue, see if the article can be updated to point in the right direction, or if it should be clearly taught to all of support that particular issue needs to be handled without documentation.
With so much documentation, and so many support requests, it's a big project aligning our support time with this constantly evolving process. A great recent example of this was actually posted by Jeff back on 11/15 when there were some IMAP issues affecting Outlook2013 and Office 365. We had a flood of calls and chats because Microsoft updated their Office suite and worldwide started causing issues with email. If we were to spend time on the phone with all of Microsoft's customers explaining how to resolve this issue, we would have had extremely long wait times. Instead we documented a solution and then passed it onto customers contacting us about that problem to keep customers just having standard support requests from having to wait for support.
This very issue could have possibly been the cause for the haste in your original support request due to the timing. Because even while we had documentation, a support rep would have had to field a much larger than normal number of calls, and there wasn't even a problem with our service, just a lot of angry calls from customer's that their Outlook email wasn't working, and Microsoft forced the update on them.
I've alerted 2 members of management of your complaints, and they'll be responding back to your Manager feedback ticket today. If you had any suggestions for us on how we could do a better job at pointing customers in the right place to documentation, but knowing when to stop and treat the issue as a unique one please let us know as it's something we always strive to perfect.
If you had any other questions at all for us, please let us know!
Like this Question? Tweet
Support Center Login
Social Media Login
It looks like there are no related articles.
Would you like to ask a question about this page? If so, click the button below!