MSP Teams in the SMB
-
@Carnival-Boy said in MSP Teams in the SMB:
As an example, a user phones the MSP and says "I tried to open our Accounts system and I get a message saying 'not responding'. How does the MSP handle the call? How does it get routed?
By whoever you have manning the phone. They will should be a L1 helpdesk type person. They will have documentation on the client and the clients LoB app.
Said document will have basic troubleshooting notes.
Once tried call goes up to a specialist based on the L1 finding errors.
-
Next it depends on what caused the issue. Troubleshooting is step two after figuring out what the client did to get said message.
This is all done in the first phone call.
-
If L1 can't handle it then a ticket is put in for up the chain for whoever needs to work on said item. Usually it's worked on very quickly from there but depends on that client's level of service they pay for.
-
Here is a more real world example, nothing makes this good or bad, it's just "how a real MSP would often handle a real situation."
- Client Y calls NTG and opens a ticket with the helpdesk. This is a human that takes the call, asks questions, determines the client, authoritization, issue basics and puts the data into a ticket along with ticket routing information. We like this method because there is immediate feedback and human verification of the issue and a human determines where the ticket goes.
- Ticket is assigned to the IT person that handles that account. @gjacobse is an example person for that, so let's say that the issue goes to him. Let's even say that it is the accounting system that is down or having a problem at client Y.
- @gjacobse logs into the customer's systems, sees that the application is really down like they said. He does some quick troubleshooting like seeing if the desktops are online, is the server up, are the services running, is there obvious issues?
- Assuming that the issue was not resolved above, @gjacobse collects documentation on the system, documents in the ticket what he has done already, determines what next step escalation is needed and escalates.
- Assuming the issue is Windows as an OS seems to be having an issue, the ticket and issue would escalate to the Windows Engineering and Administration (A&E) team who would assign someone to work on the issue to get Windows working at the server level. If they need to loop in someone from another team (say SQL Server DBA) they can do so.
- If a vendor is needed, normally @gjacobse would loop them in and get them involved and communicate logs or whatever to them while the other teams continue to work.
- @gjacobse would keep the customer up to date on the technical level (assuming there is a tech contact to talk to) or if it is all handled at a higher level, @art_of_shred would give management updates of states or completion.
Handled much like an internal ticket would be if there were enough resources for an internal team to work that way. This is how internal IT works at larger companies as well. Ticket -> Router -> Base Assignment -> Resource Team Specialists -> PM Oversight
-
@scottalanmiller said in MSP Teams in the SMB:
@Carnival-Boy said in MSP Teams in the SMB:
But in reality, the owner is more likely to take a 100% cut on top and buy a Ferrari. At least that's been the experience of all the MSPs I've known.
I've never found any MSPs like that. I certainly know that they exist, but I'm not coming across any in my travels. I know for certain that there are many MSPs not doing that that are not getting work. Maybe companies only like hiring people with Ferraris?
Before I found out about NTG, that's the only type of MSP I knew of. Know a guy that still works for one based in Youngstown, OH, and I don't know why he keeps working for them.
-
@scottalanmiller said in MSP Teams in the SMB:
@Dashrender said in MSP Teams in the SMB:
I stopped by my upstairs neighbors place in my office. They used to have an MSP handle their stuff. They dumped them after the MSP sent a tech who sat at their office for nearly 16 hours doing nearly nothing, my contact told me the tech was literally twiddling his thumbs. When my contact asked when it would be fix, the guy jumped to, and 30 mins later it was fixed and he left.
The MSP then billed that client for the 16 hours of the tech being there.
I have no additional details, but the client was pretty unhappy to see a tech just sitting there basically doing nothing, not typing, not searching the internet for fixes, just sitting for nearly 2 days, then suddenly, when asked when it will be fixed, hopping to and fixing it.
As Scott mentioned this was clearly and hourly bill situation, not a monthly contract (at least not a contract for break/fix - I do know they had a monthly reoccurring cost for things like backups on the server, and network monitoring).
This is clearly an example of a bad MSP - or at minimum a bad employee at an MSP.
Well, there is a bit of assumption there. What if that guy was busting hump for sixteen hours, knew what the issue was, had the fix underway, was waiting on a system to finish a reboot or update that had 30 minutes left and just happened to get asked how long it would be at the end after having done an excellent job for two days. We are assuming that he was twiddling his thumbs for two days, and likely that is true, but unless they really checked up, there is a ton of room for error there. What if that was an internal IT guy, would they have reacted the same? If not, why not? Internal IT staff are generally hourly as well, same factors.
I thought I left room for your added possible situation - but the fact that the tech didn't offer an explanation that of what had been going on for days, instead (as it was told to me ) the tech offered nothing, but jumped to a fix and was gone.
-
@scottalanmiller said in MSP Teams in the SMB:
What if that was an internal IT guy, would they have reacted the same? If not, why not? Internal IT staff are generally hourly as well, same factors.
Yes I think they would have questioned internal IT for just sitting there for 2 days preventing someone else from using the machine.
-
@Dashrender said in MSP Teams in the SMB:
@scottalanmiller said in MSP Teams in the SMB:
@Dashrender said in MSP Teams in the SMB:
I stopped by my upstairs neighbors place in my office. They used to have an MSP handle their stuff. They dumped them after the MSP sent a tech who sat at their office for nearly 16 hours doing nearly nothing, my contact told me the tech was literally twiddling his thumbs. When my contact asked when it would be fix, the guy jumped to, and 30 mins later it was fixed and he left.
The MSP then billed that client for the 16 hours of the tech being there.
I have no additional details, but the client was pretty unhappy to see a tech just sitting there basically doing nothing, not typing, not searching the internet for fixes, just sitting for nearly 2 days, then suddenly, when asked when it will be fixed, hopping to and fixing it.
As Scott mentioned this was clearly and hourly bill situation, not a monthly contract (at least not a contract for break/fix - I do know they had a monthly reoccurring cost for things like backups on the server, and network monitoring).
This is clearly an example of a bad MSP - or at minimum a bad employee at an MSP.
Well, there is a bit of assumption there. What if that guy was busting hump for sixteen hours, knew what the issue was, had the fix underway, was waiting on a system to finish a reboot or update that had 30 minutes left and just happened to get asked how long it would be at the end after having done an excellent job for two days. We are assuming that he was twiddling his thumbs for two days, and likely that is true, but unless they really checked up, there is a ton of room for error there. What if that was an internal IT guy, would they have reacted the same? If not, why not? Internal IT staff are generally hourly as well, same factors.
I thought I left room for your added possible situation - but the fact that the tech didn't offer an explanation that of what had been going on for days, instead (as it was told to me ) the tech offered nothing, but jumped to a fix and was gone.
Was there a reason for the tech to explain? Put yourself in the tech's position, you have no reason to think that the customer thinks what we think here. It was a major issue, a miracle that they fixed it so quickly, someone checked on status, he provided one. If the tech was screwing off, it would seem obvious that an excuse was needed. If the tech was working hard that whole time, there would be no reason to feel the need to offer an excuse. The assumption that an excuse would be provided if there was a valid one is, I think, backwards. If a valid excuse was available, the tech would never realize one should be offered. That no one asked for one does the same for me - that makes me assume that they were looking for an excuse to get rid of them and didn't care that there was possibly a totally valid reason. They saw an excuse and took it.
-
@Dashrender said in MSP Teams in the SMB:
@scottalanmiller said in MSP Teams in the SMB:
What if that was an internal IT guy, would they have reacted the same? If not, why not? Internal IT staff are generally hourly as well, same factors.
Yes I think they would have questioned internal IT for just sitting there for 2 days preventing someone else from using the machine.
AND they would fire him without asking for a reason? I find that unlikely and, if so, makes them a horrific company that is clueless and capricious. It's not okay to fire someone for fixing something. Sounds like a bad company making excuses. It sounds like marketing to make it sound like the MSP's fault. This isn't how a good customer behaves, they'd fine out WHY it took so long first. See if another company thinks that that makes sense. Not just fire people for something so incredibly random, that's beyond fishy.
-
Maid comes to clean my house. She's there ALL day long. I show up at the end of the day. I find her sitting around. I ask her when the floors will be dry so I can walk across the. She says in five minutes. I wait for her to go home and call the maid service and fire them because she "sits around the house all day" because I "checked and the floors weren't dry when I got home but were minutes later so clearly they do no work."
-
Instead of working from assumption, let's look at only the factual bits:
- MSP fixed the issue.
- MSP took two days to fix the issue.
- Customer checked in shortly before issue was fixed.
Those are the facts. The rest is conjecture and coincidence. Sure, there is every possibility that the tech was sitting idle wasting time. There is always every possibility that he was not. What we know for sure is that from the info given, the company has zero, literally zero, reason to fire the MSP. Maybe they have more info that they are not telling us, but maybe not. But if they did, don't you think they'd want it to sound like a valid firing rather than bragging that they randomly fired a guy who helped them out?
-
@scottalanmiller said in MSP Teams in the SMB:
@Dashrender said in MSP Teams in the SMB:
@scottalanmiller said in MSP Teams in the SMB:
@Dashrender said in MSP Teams in the SMB:
I stopped by my upstairs neighbors place in my office. They used to have an MSP handle their stuff. They dumped them after the MSP sent a tech who sat at their office for nearly 16 hours doing nearly nothing, my contact told me the tech was literally twiddling his thumbs. When my contact asked when it would be fix, the guy jumped to, and 30 mins later it was fixed and he left.
The MSP then billed that client for the 16 hours of the tech being there.
I have no additional details, but the client was pretty unhappy to see a tech just sitting there basically doing nothing, not typing, not searching the internet for fixes, just sitting for nearly 2 days, then suddenly, when asked when it will be fixed, hopping to and fixing it.
As Scott mentioned this was clearly and hourly bill situation, not a monthly contract (at least not a contract for break/fix - I do know they had a monthly reoccurring cost for things like backups on the server, and network monitoring).
This is clearly an example of a bad MSP - or at minimum a bad employee at an MSP.
Well, there is a bit of assumption there. What if that guy was busting hump for sixteen hours, knew what the issue was, had the fix underway, was waiting on a system to finish a reboot or update that had 30 minutes left and just happened to get asked how long it would be at the end after having done an excellent job for two days. We are assuming that he was twiddling his thumbs for two days, and likely that is true, but unless they really checked up, there is a ton of room for error there. What if that was an internal IT guy, would they have reacted the same? If not, why not? Internal IT staff are generally hourly as well, same factors.
I thought I left room for your added possible situation - but the fact that the tech didn't offer an explanation that of what had been going on for days, instead (as it was told to me ) the tech offered nothing, but jumped to a fix and was gone.
Was there a reason for the tech to explain? Put yourself in the tech's position, you have no reason to think that the customer thinks what we think here. It was a major issue, a miracle that they fixed it so quickly, someone checked on status, he provided one. If the tech was screwing off, it would seem obvious that an excuse was needed. If the tech was working hard that whole time, there would be no reason to feel the need to offer an excuse. The assumption that an excuse would be provided if there was a valid one is, I think, backwards. If a valid excuse was available, the tech would never realize one should be offered. That no one asked for one does the same for me - that makes me assume that they were looking for an excuse to get rid of them and didn't care that there was possibly a totally valid reason. They saw an excuse and took it.
If I hire you to do work for me.. and I see you sitting there for 2 days doing what appears to me like you just twiddling your thumbs for that time and I ask you what the status is - I fully expect a full blow by blow what you have been doing for 2 days. As the customer I feel I have to right to inquire what you are doing with the time I am paying you for.
You're saying that someone asking for a status update means they are trying to get rid of you? really? That seems backwards..
-
@scottalanmiller said in MSP Teams in the SMB:
@Dashrender said in MSP Teams in the SMB:
@scottalanmiller said in MSP Teams in the SMB:
What if that was an internal IT guy, would they have reacted the same? If not, why not? Internal IT staff are generally hourly as well, same factors.
Yes I think they would have questioned internal IT for just sitting there for 2 days preventing someone else from using the machine.
AND they would fire him without asking for a reason? I find that unlikely and, if so, makes them a horrific company that is clueless and capricious. It's not okay to fire someone for fixing something. Sounds like a bad company making excuses. It sounds like marketing to make it sound like the MSP's fault. This isn't how a good customer behaves, they'd fine out WHY it took so long first. See if another company thinks that that makes sense. Not just fire people for something so incredibly random, that's beyond fishy.
The MSP wasn't fired after this single instance, there were many issues this was just an instance they specifically mentioned to me. Yes I glossed over the other issues mentioned to me. But they had several complaints. Sadly price was one of them..
-
@scottalanmiller said in MSP Teams in the SMB:
Maid comes to clean my house. She's there ALL day long. I show up at the end of the day. I find her sitting around. I ask her when the floors will be dry so I can walk across the. She says in five minutes. I wait for her to go home and call the maid service and fire them because she "sits around the house all day" because I "checked and the floors weren't dry when I got home but were minutes later so clearly they do no work."
I think this is not an acceptable comparison to the tech. You could easily look around the rest of the house and see it was clean - my question is.. why is she sitting around at all? If the answer is, she can't leave until the floor is dry, fine, but if it's .. well she was done - then why didn't she leave? Yes there are all kinds of reasons she was 'sitting' around... some valid some not. but unlike the computer - you could inspect the other things she was suppose to clean to know work was done.. in the computer, it's pretty much an all or nothing situation.
If the work really took that amount of time, I'm sure the tech COULD have provided a reason for it that could satisfy the customer.
-
@scottalanmiller said in MSP Teams in the SMB:
- MSP provided good estimate of completion when asked.
What? I never said that!
-
@Dashrender said in MSP Teams in the SMB:
@scottalanmiller said in MSP Teams in the SMB:
- MSP provided good estimate of completion when asked.
What? I never said that!
are you claiming this because they guy left 30 mins after he was asked... if you are, that's an assumption on your part... my contact never told me the tech offered a repair time either when the call was opened or when he inquired about the status near the end of 2 days. I have no idea if he was given a time or not. this line just needs to be removed because it's completely unknown.
-
@Dashrender said in MSP Teams in the SMB:
@scottalanmiller said in MSP Teams in the SMB:
- MSP provided good estimate of completion when asked.
What? I never said that!
Oh, I thought that you had said that they asked how long, and he said half an hour. He didn't respond and just was done in half an hour?
-
@Dashrender said in MSP Teams in the SMB:
@Dashrender said in MSP Teams in the SMB:
@scottalanmiller said in MSP Teams in the SMB:
- MSP provided good estimate of completion when asked.
What? I never said that!
are you claiming this because they guy left 30 mins after he was asked... if you are, that's an assumption on your part... my contact never told me the tech offered a repair time either when the call was opened or when he inquired about the status near the end of 2 days. I have no idea if he was given a time or not. this line just needs to be removed because it's completely unknown.
Gotcha, I got that part incorrect. I'll adjust.
-
There you go.
-
@scottalanmiller said in MSP Teams in the SMB:
Instead of working from assumption, let's look at only the factual bits:
- MSP fixed the issue.
- MSP took two days to fix the issue.
- MSP provided good estimate of completion when asked.
Those are the facts. The rest is conjecture and coincidence. Sure, there is every possibility that the tech was sitting idle wasting time. There is always every possibility that he was not. What we know for sure is that from the info given, the company has zero, literally zero, reason to fire the MSP. Maybe they have more info that they are not telling us, but maybe not. But if they did, don't you think they'd want it to sound like a valid firing rather than bragging that they randomly fired a guy who helped them out?
LOL bragging - lol there was no bragging. They were unhappy with any reasoning they did receive, or didn't receive any for the amount of time that ticket took.
They also told me that they were slow to respond to tickets in general - but I have no idea what their SLA was, so can't say if this was acceptable or not.I'm not defending them firing them or not.. I'm just wanting to make sure Scott isn't crucifying someone when there really isn't enough information.
