The wrong question, asked helpfully
A caller with a real problem rings an after-hours line. The service that picks up does what services do. It asks for details. Who the principal is. Where they are staying. What has happened.
All of it goes into a message queue, read by whoever is on shift, stored wherever that vendor stores things.
Nothing has gone wrong yet. But a record now exists that should never have been created, and the caller has learned something about how you operate.
What it does
- Answers, identifies itself as automated, and says up front that it takes very little over this line.
- Takes four things: a name, a callback number, the broad category of engagement, and a rough timeframe.
- Accepts city-level geography and a rough shape of coverage if the caller volunteers them. It does not ask for either.
- Interrupts, politely, the moment a caller starts giving it more than it should hold.
- Routes anything inside seventy-two hours, or anything urgent, straight through as a priority.
- Tells a caller describing immediate danger to call 911 first, then flags it and closes.
What it never does
- Take a principal's name, role, employer, or anything that identifies them.
- Take an address, a hotel, a venue, a flight number, an itinerary or a route.
- Take the nature of a threat, an incident, or who the caller believes is involved.
- Take anything about current arrangements, staffing, gaps or posture.
- Take anything about family members, including children or schools.
- Describe your capabilities, licensing, staffing or methods to a caller.
Try to give it something it should not have
Call and start telling it about a principal by name, where they are staying, and why you are worried. It will stop you inside a sentence, and none of what you said will reach the record. Collecting less is the demonstration.
It will tell you itself, before you hang up, that it is a demonstration line and that nothing it took was real.
Which watch fits a protective services firm
Two tiers here, not three. The middle one is declined on purpose, and it is worth understanding why before you read the other two.
First Watch
An intake line built to hold less than the service that would otherwise pick up.
- Takes four things: a name, a callback number, the broad category, a rough timeframe.
- Interrupts the moment a caller starts giving it more than it should hold.
- Transfers to one named destination on the calls you say must reach a person — one number, no ordered list, no confirmation that it connected.
Standing Watch
Outbound re-contact creates a written record that a particular person retains protective services.
- That record is the exact thing your clients are paying you to avoid.
- We decline it in this vertical rather than price it and let you decide.
Silent Watch
Depth without a single outbound contact. The only high tier offered in this vertical.
- Up to twenty lines under one intake standard.
- Escalation tree: named people in order, with confirmation the handoff connected.
- A written response commitment, and attach surfaced to you rather than pitched at anyone.
The only price published on this site is the $300 Line Audit, and it comes off the setup if you go ahead. Build time to live is four weeks.
Compare all three →Request a Line Audit →Want to know what your intake line is collecting?
We'll call it, write down exactly what it asked us for, and show you what a stranger could put into your records in ninety seconds. If there's nothing to fix, we'll say so and leave you alone.
Request a Line Audit →