Re: cleaner wiring solution needed (resend)

[Crash Gordon® <NONE@xxxxxxxx>]

Fire detection adds another dimension to the liability...however, he has =
an obligation ...paying me. I kept careful records of every phone call =
(date & time & msg left if he wasn't home) AND sent out at least 8 =
demand letters via certified return reciept - which he DID sign for.

I was totally covered - if I wasn't the judge woulda said something =
other than what he did.

I never do this lightly...if I did I would have taken action much =
sooner...not wait over a year+. He had every opportunity to =
respond...but didn't. I'm very reasonable when it comes to working out =
payment plans if people are having problems, he could have talked to me =
at least. But, he didn't because his intent was to NOT ever pay...his =
token payments were made to keep me quiet, not satisfy his obligation.

I have another story like this only more involved...later.



"Frank Olson" <feolson@xxxxxxxxxx> wrote in message =
news:z0u%d.748741$8l.602665@xxxxxxxxxxx
>=20
> "Crash Gordon=AE" <NONE@xxxxxxxx> wrote in message=20
> news:fgq%d.80$SP2.959@xxxxxxxxxxxxxxxxxx
> > I said you didn't  have to enforce anything but you could.
> > If client doesn't answer repeated certified return reciept
> > demands for payment you certainly *could* impede  his
> > use of system.
>=20
>=20
> That could well expose you to a liability situation that you might =
want to=20
> reconsider.  All I'm saying is that we (as security professionals) =
have a=20
> "duty of care" to all our customers (even the ones that are "slow =
payers").=20
> You have the option of terminating his service, and if you happen to =
own the=20
> equipment (or they haven't paid for it yet), you can always cancel =
their=20
> service and remove the system.  Disabling it, or rendering it =
inoperable is=20
> not an option (at least in my book).
>=20
>=20
>=20
> >I had a guy once that skirted every attempt to
> > collect, and infact owed me a few bucks on the
> > actual install...he would send me 10 bucks here,
> > a couple of bucks there, this went on for over a
> > year, closer to 2 years by the time I took him to
> > small claims. Sent him to collections...nothing!...
> > I knew he WAS using the system because I had
> > programmed opening closings and daily tests and
> > could prove it. Took him to small claims court and
> > won...got my money + % + expenses. The judge
> > did ask me...why didn't you just turn him off?
> > I shoulda.
>=20
>=20
> Yes.  You could terminate his service with the proper notice.  I've =
run into=20
> a customer like this as well.  Every check he wrote to us bounced from =
the=20
> "get go".  He was difficult to get ahold of and I had thought of =
changing=20
> the master code on the system so he couldn't use it but decided =
against it=20
> because there was fire detection devices in the system and I didn't =
feel it=20
> appropriate to endanger his family.  As it turns out he was a real=20
> screw-ball, left his wife and kids, made threats, etc.  The wife's =
family=20
> wound up paying for the system and we changed the access codes for her =
when=20
> she got a restraining order on him.
>=20
>=20
>=20
>