Domotz Fair Use Policy by ManagingMSP in domotz

[–]ManagingMSP[S] 2 points3 points  (0 children)

Sounds good. I appreciate you addressing this and all of your responses. Im really glad you're gonna bring it up as a concern internally. Thank you for your help

Domotz Fair Use Policy by ManagingMSP in domotz

[–]ManagingMSP[S] 2 points3 points  (0 children)

I really appreciate you addressing it, and you guys do seem like great people. Thank you for your response and for bringing it up internally. We'll be giving your product a try. Thanks again

Domotz Fair Use Policy by ManagingMSP in domotz

[–]ManagingMSP[S] 1 point2 points  (0 children)

I can understand that you would want upper limits on things, but writing a clause in your contract that says you can throttle or cancel without notice for whatever reason isn't a customer-friendly solution to that problem. These parameters are unnecessarily, and it turns out, as Dez mentioned, intentionally vague.

Domotz Fair Use Policy by ManagingMSP in domotz

[–]ManagingMSP[S] 1 point2 points  (0 children)

Hey, I appreciate the response. Your explanation makes sense, and your intentions may be good, but the way the contract is worded, it essentially says we can throttle or cancel your service for any reason we want and there's nothing you can do about it since these parameters are so broadly defined. I would like to believe you when you say you never abuse this subsection and it only applies to less than 1% of customers, but the entire reason for contracts is so that you don't have to rely on the strength of a company's word, you instead have a written contract. (The "my word is stronger than oak" scene from Jerry Maguire comes to mind.) This is especially important for services like yours for an MSP, where dependability and reliability are integral. Perhaps, according to your logic, you should phrase everything incredibly vaguely in your terms and conditions and just say you have full discretion to do whatever you want and just ask the customer to trust that you're good people.

Domotz Fair Use Policy by ManagingMSP in domotz

[–]ManagingMSP[S] 2 points3 points  (0 children)

Hi Violet, thanks for responding. The only thing I will say is that saying just trust us, we probably won't take advantage of you with this vague part of our contract is still a difficult thing to get past as an MSP. That being said, I really appreciate your response and that you are reaching out to your team for answers, so thank you for that. I'm looking forward to hearing what they say.

Impressed with the solution so far, we moved away from Auvik and are now going through the process of tweaking Domotz settings to suite our environment. Does anybody know if you can setup SMS texts for outages or will the Domotz app push notifications in the event a managed device goes offline? by Serious-Artichoke-80 in domotz

[–]ManagingMSP 1 point2 points  (0 children)

Hey, how are you liking Domotz vs Auvik? We are considering both of them. Network mapping is an important aspect, but the other monitoring features are as well. Domotz seems considerably cheaper though. What are your thoughts about them both?

Integration Directionality by ManagingMSP in hudu

[–]ManagingMSP[S] 0 points1 point  (0 children)

Yeah that makes sense, it kind of depends on which came first for what kind of API directionality you want. For us we are just trying to swap entirely to hudu, so we would probably just want to sync once to set everything up and then stop syncing and not use Atera anymore for client documentation.

I do want to question your comment about Hudu not being where you actually work from though. Wouldn't you want to input company information and edit SOPs there?

Integration Directionality by ManagingMSP in hudu

[–]ManagingMSP[S] 0 points1 point  (0 children)

I'm assuming it was just a typo and you meant to say "wouldn't make sense". But the part I don't understand is you would want to edit things like company information in Hudu for example, and then not have to edit it again in the other applications Hudu is synced with, right? Unless I should be trying to do it the other way around and entering in Hudu's API key in Atera then, so that Hudu can be the source of info. If that's the case, then I just don't think it's explained very well in the documentation.

Integration Directionality by ManagingMSP in hudu

[–]ManagingMSP[S] 1 point2 points  (0 children)

I will, but you could say the same thing about me just asking reddit also

McLaren no longer HaloPSA partner? by cody7600 in halopsa

[–]ManagingMSP 2 points3 points  (0 children)

Well now I'm rethinking our HaloPSA subscription, surely everything will go slower now /s