[VoiceOps] Past due/overdue invoices for Doctor offices - How to handle?

[Carlos Alvarez]

I guess the reverse of the question would be...why?  We've never been
approached by a real prospect who wanted to use it in such cases, nor has
anyone ever complained about this wording.  We took that language idea from
the many similar software license agreements, like the ones saying you
can't use it in a nuclear plant or air traffic control for example.  Our
lawyer said that fighting an indemnification battle is much harder than
"they violated our contract therefore we're not liable."

That choice was backed up when we were threatened with a lawsuit by a
plumbing company that takes emergency calls 24x7.  We had a planned outage
on a Sunday and they said they lost an emergency damage call, so we should
be partly responsible for the damage that they couldn't respond to promptly.

We fired them, by the way.  They were assholes anyway.  Any time a new
prospect comes to you saying he's looking for a great VoIP carrier because
the last four have sucked, don't let your ego tell you that you're better.
Realize that the common problem with all of them is that customer.



On Thu, Mar 9, 2017 at 5:24 PM, Alex Balashov <abalashov at evaristesys.com>
wrote:

> Carlos,
>
> On Thu, Mar 09, 2017 at 12:23:13PM -0700, Carlos Alvarez wrote:
>
> > Our ToS also includes:
> > This service may not be used in any life support, emergency response, or
> > other critical communications which may cause loss of life, injury, or
> > property damage.
>
> I am curious why you take this approach as opposed to allowing such use,
> provided that you are indemnified from any civil liability arising as a
> result of exclusive dependence on your service in such uses.
>
> --
> Alex Balashov | Principal | Evariste Systems LLC
>
> Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)
> Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20170309/14692023/attachment.html>