Certainly some *interesting* logic by Mr. K.
First he claims the reason for the charge is to "combat false alarms."
Considering that municipal false alarm fines, usually charge after one to three false alarms, and have fines ranging from $100 to over $500 and ultimately suspension of response service, your subscribers should appreciate, not resent, the effort you are making to reduce false alarms.
The "effort you are making" here is simply billing them. But it's not so simple, since
The real issue may be getting the central station to identify the false alarm and then let you know so that you can charge the subscriber on the next invoice.
So you are billing them for something you have no part in, just so that they realize how serious this is?
There is some specious moral justification included as well:
Why not? We already have a separate charge for Alarm Verification, though most of you don't charge for it because your central stations aren't charging you for it. But that may not really be true. Your central station calculates its charges based on its expenses, and those expenses have to take into consideration the amount of operators the central station has to employ on any given shift. We know that for traditional alarm monitoring an operator can handle about 1000 accounts. That can't be the case when false alarms become excessive, forcing the operator to ignore the signal or get sloppy with how it's responded to. So your central station may have already factored in the extra employees required to handle the average day's signals, false and real.
Sure, but haven't you already taken into account what the central station charges you, in total, and 'factored' that in to your customer's rate?
Finally, some straight denial:
Think the charge will cost you subscribers? Well, it won't because you will already have the subscriber under contract.
Yet they are not under contract to pay the $1 until they sign a new contract, so what does K mean here exactly?