Forum Discussion
Quality of Office 365 support is sinking..
J 1901 and Luke Hoffman
Thanks for taking the time to send feedback. I'm currently out for the holidays for a few weeks; however, I saw your posts so wanted to at least get an initial response out to you.
Contacting support should be a worry-free experience that gets you a solution to your problem quickly. We know that sometimes this isn't possible - but it absolutely is how we design the system to work. If we're not delivering, you are right to call us out on it.
I had to contact the tech support department of a tech company yesterday for an issue I was having with some home automation hardware. The experience was terrible! I spent over an hour on the phone and was forced to repeat the same steps, in the same order, more than 10 times! While I was performing these futile steps, a few things went through my mind.
First - I'm absolutely confident that the experience I received was not the experience that the company wanted me to have. If they ever listen back to the call, I'm sure it will be used as an example of how NOT to deliver support and how to drive your customer insane.
Second - the net of my support experience is that I most likely have defective hardware, so no amount of hand-holding was going to solve my problem.
Third - the person who was helping me was either new, inexperienced, or poorly equipped to do their job. Lack of training or poor quality training or lack of access to more experienced resources.
As I think of the problems I was hitting in my own support experience, I think about how we equip our support teams to help our customers. It's absolutely possible that we face some of the same challenges I call out above - but it's certainly not how we design the system to work and we invest constantly to bring improvements to both the technology that powers the support experience and the people who deliver the service.
I can't explain why your support experiences in the past months haven't met the high bar we set, but I can tell you that we certainly didn't do anything detrimental to result in such a change. If anything, we're doing quite the opposite. Our teams are moving away from scripted interactions, we are adopting a growth mindset in our approach and using our "failures" as opportunities to learn, and we continue to build our tooling based on the feedback from both customers and our support teams.
Regarding fiddler traces - or the ask to collect any other logs, screenshots, error messages etc. - none of these are tactics to "buy time". If the frontline teams don't have the expertise or tools to analyse the information, they will be sending it to (or might have already been asked to request it by) our more experienced folks. In many of our teams now, we have a mix of "frontline" and "escalation" resources so that the experience is part of a single team which enables individuals to develop and solutions to be delivered faster.
All that said, if you aren't having a good support experience, let the person who's helping you know. In many cases, you should see their manager's contact details in e-mail communications that are sent to you. You can provide feedback to the manager directly (if available) or provide the feedback directly to the support person you are working with.
If you still don't see an improvement, I'd love to hear from you to find out why things aren't going well.
A few notes on this to set expectations for anybody else who happens to be reading:
1. I don't work 24x7 and I'm not "the escalation guy" :) If I'm slow to respond it because I'm taking care of my day job (or on vacation!)
2. Sending a case number to me doesn't magically = faster solution. I'm interested in specific cases because it helps me to see what opportunities we should be following-up on to improve our service. I always provide cases to the managers/leaders of the team so that they can take action where required.
3. It's always best to have a conversation with the support person who's helping you. Whether it feels like it or not, they are human and they are doing their best to help. If they understand your concern or complaint, they might be able to do something immediately to resolve it.
Thanks again for sending the feedback. If you have specific examples you'd like me to take a look at, you can PM me and I'll look at them when I'm back after the holidays.
If you are lucky enough to be taking time off over the next few weeks, I hope you enjoy a relaxing break.
-Russell.
I would like to thank you publicly for all your efforts to try and investigate the issues I have raised with you. I know that you have tried your best and for that I am very appreciative.
But the sad reality is it is not getting any better, my working life is being ruined by having to raise cases with the office 365 support team. Out of 10 issues raised this year only 2 have been dealt with correctly and in a timely fashion.
I dread having to contact the support team as most the time it a frustrating loop of "have you tried this, have you tried that, can you send me a screenshot of the error message that you already have pasted in the ticket when you raised it." and asking all the questions you would ask of a novice user and they cut and paste standard questions that are not related to the issue that you are encountering.
I search all the forums, documentation and status pages for a solution, before I raise a case, so to be asked these questions is tedious.
They email you when you have explicitly asked them to call you on the phone.
They call and email outside your normal working hours even when you have repeatedly told them what those are.
If the person assigned goes off sick, no-one else bothers to pick up the call in their absence - great for time urgent critical issues - NOT.
They have no power to escalate any issues to get anything fixed, be it simple documentation correction or getting an identified issue fixed by a developer.
Cases drag on for months and then just get shut by them when they get bored without resolution or telling the customer.
I wish I did not have to write this, I have tried so hard to get the message across, but it is just not working, You have too many feedback mechanisms and none of them result in anything getting fixed, in product feedback, uservoice, office insider forum, github documentation comments and different office 365 support teams. I have been let down by every single one of these methods in the past 12 months and have the apology emails to prove it.
But ultimately this is causing me to let my customers down, because I cannot get their issues fixed in a timely manner and both I and them are losing faith in Microsoft Office as a credible solution.
I will give an example of the latest debacle:- some elements are abbreviated for the sake of time
one of my customer found suddenly that 80% of their incoming and outgoing genuine emails were being tagged as junk. We tried using the inbuilt "report this as not spam" tool, nothing changed and they started to lose business because the order confirmations were hitting their customers junk folders. This was affecting ALL of their users in the company.
Before raising a case I did full troubleshooting myself, I checked that their anti spam settings were on the standard defaults, I used the Microsoft test console to check the message-id's of the submitted samples - which said that NO RULES had been hit, - yet it was still tagged as spam by Microsoft's filters. I even worked out by painstakingly modifying the contents of an affected email and repeatedly sending it in to the customer until it no longer went to their junk, was that it was related to all emails that contained their own domain in the message body!!! e.g. when you reply to someone it usually contains text that shows the original senders email like "fred@xyzcorp.com wrote: "
So having narrowed it right down, I opened a ticket and asked to be contacted by phone - first agent decides to send me an email instead and ask dumb questions that were already answered in the case when I logged it. A terrible start to the call, After a frustrated email reply from me asking them to actually call me like I had asked for in the first place, someone else did pick up the case and called me.
I was asked for more screenshots, message id's headers etc, wasting 2 days and then that agent wrote to me by email and those responses got overlooked by me because they went to my junk mail (and I work in a different tenant but probably caused because they contained the text of the affected domain in them). Why didn't she call me instead if she was not getting a reply from me ? The lady kept asking me for all sort of other information - when all you needed was the message ID's and to escalate the issue! The lady kept apologising and saying that there was nothing she could do to get the issue looked at any quicker. I then heard nothing for 2 days and eventually someone else took over the call meanwhile we are on day 5 of a critical issue and no further forward.
Then 2 days on from that, after he said he had no further update and had not heard anything back from the relevant team, I noticed it had magically started working again. It turns out that the team responsible for the spam system had made a change and not bothered to tell him or me! I then asked him to try and find out a root cause analysis and was told that you do not do that sort of thing, I pressed him again and asked him to go back to that team and at least ask them when and what they had changed this took a further 4 days and all I got back was a vague "they whitelisted the customers domain the previous night" but had not informed the agent on the case.
- How is it that a customers own domain can suddenly get tagged as spam - without this being shown in any of your test tools? (by the way before you ask, they do not send bulk marketing emails out).
- Why did several dozen emails being reported using the "this is not junk" tool not result in this problem being picked up automatically? surely that is the point of that feedback tool?
- Why did a simple yet critical issue take so many days to get escalated to the relevant team? and then 2 days after that to be actioned ?
- Why did I have to jump through so many unnecessary hoops? when all you needed to do was supply the affected message ID's and the extra info that I had already worked out to the team that manage the rules engine?
- why did the rules team not communicate the fix they had applied back to the support agent ?
- why do you not do a root cause analysis to prevent this happening to another customer?
- Why did the first agent that took my case, decide to ignore the specified contact method of phone for an urgent case and send an email with canned cut and paste dumb questions already answered by reading the information supplied in the case?
Well there you go, rant over, but this is just one of the many calls that have been handled poorly this year.
- Dean_GrossOct 30, 2019Silver ContributorFWIW, i have recently been getting call backs within an hour.
- DanHuberOct 30, 2019Iron ContributorYet another ticket where I wait and wait and wait...
Sigh... - DanHuberSep 26, 2019Iron Contributor
Hi technonath ,
I'm sad you made that experiences (too).
From my end, I have to say that the Office 365 Support has stabilized for the moment. Call back ist still not perfect, but at least I do not have to wait for days or weeks. I also get connected via email even when I explicitly gave phone number and local time frame for a call, and only for a call. In those emails they sometimes claim that they did not reach me by phone, but my phone-log does not show any missed attempt (I am the pbx manager too, so I should know). Yes, there are individualy who do not like to call a customer, but work in first line L1 support...
I recently did not have extremely painful issues, but rather annoyances I could not solve myself. Mostly due to the frequent changes in Office 365.
Your issue with the own domain being junklisted ist interesting. I think I had a similar issue, but I was able to workaround it by adding spezial rules and exceptions. Yet, just a workaround.. Which reminds me that I probably should remove that workaround again...
About the support quality, I think Microsoft should provide separate support access points for Microsoft Partners (we are a partner...) and experienced admin's, and standard requests from Office 365 users.
Opening a ticket as partner (or experienced admin), Office 365 support should assume that certain knowledge is available and certain pre-tests have been done.
I usually try to determine the knowledge of the person I get on the phone and act accordingly. Sometimes they are very advanced and are "bound" by some kind of script. Sometimes they actually go the extra mile. Most of the time though, they follow some procedure. The external 3rd-party support people are likely of the last kind.
You *can* get the advanced ones to understand fast. Sometimes.
The others.. well... I switch to stupid and just move the mouse where they point me to. Until I eventually loose patience, open the PowerShell window with the Office 365 connection and the Problem eventually visible, and thus show them that they might want to reconsider their approach.
All very time consuming, though.. so, I feel with you.
I *do* understand when support people sometimes re-ask questions. I worked for many many years in another big company in support. What a fellow support engineer is writing down in the ticket, what the customer wrote down, what I read and understand... not always matches.
So one of the first question I ask when they contact me is if they have read and understood what I wrote. Sometimes I "test" them by asking something specific about what I delivered. I know, this sounds, well.. perhaps arrogant.. but it helps me determine with what kind of support person I am talking to (new, experienced, old hat, ignorant, you name it.)
People/Organisations act as they are measured/paid. I am not sure how Office 365 support is setup in detail, but I would assume that Microsoft has outsourced L1 support at least in some regions to local 3rd party (I *do* ask each supporter I have on the phone, but not all of them seem comfortable telling me that they do not work for Microsoft). So, if it's a 3rd party, they need to make money. Either they are paid by ticket they close or by other means. For example, they might be hesitant to escalate to L2 (because that might be Microsoft) and thus they would not get the full fee for a ticket that has not been closed by themselves.
At the end, customer needs to be happy. The feedback after a ticket is important.
In my past experience in support, we actively only analyzed feedback that was extreme (positive and negative) AND had a remark attached. This is what I do.
So, if you might want to give feedback to a ticket, do it in the extreme. And write a comment, be direct and ask to be contacted. Medium feedback and such without comment, disappear in statistics.
Ah, and the support engineer is sometimes the poor one in between. In my comments, I explicitly point out if I had a problem with the person, the process, the product..
Dan