[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

Re: the police was dispatched to ... the wrong house



Most companies I know have a strict protocol in place to make certain this
type of thing doesn't happen. I think that is one more reason why
downloading panels is better than keypad programming. The way we do it is
one person is responsible for obtaining the account number, and checks for
no duplicates from a master list. Another person in accounting reviews that
whole process when the customer record is created in the accounting
software. Then the panel is programmed and tested with that information and
checked a third time. If you have guys calling on the phone for an account
number and writing it on a scrap of paper, or trying to remember what the
account number was while they punch it in via the keypad, then yes these
kinds of things can happen.


"Mark Leuck" <m..leuck@xxxxxxxxx> wrote in message
news:46aaa2d8$0$31296$4c368faf@xxxxxxxxxxxxxxxxx
>
> "Robert L Bass" <RobertLBass@xxxxxxxxxxx> wrote in message
> news:GQtqi.740$8u1.138@xxxxxxxxxxx
>> > I tested my system and the alaram goes
>> > to the CS and is properly detected. The
>> > problem is that evidently so does some
>> > other security panel somewhere, which
>> > must have been programmed with my
>> > account #; and the CS does not use
>> > incoming CID to crosscheck the account
>> > #.
>>
>> In that case you have two choices:
>> (1) Change central station providers (this
>> is the preferred option)
>> (2) Stay with your current station but
>> ask them to change your account number
>> so this doesn't happen again (until the
>> next time one of their professional installers
>> screws up).
>
> You assume it's the central station's responsibility to reprogram someone
> elses installation
>
>




alt.security.alarms Main Index | alt.security.alarms Thread Index | alt.security.alarms Home | Archives Home