The Bench
What we run on ourselves first.
Nothing is installed in a customer’s business until it has run in ours. This page is the bench: the test we place before a first call, the message the system actually sends, the monthly check on what AI assistants say about a trade, and the limits we build in on purpose.
Fixed-scope installations · Monthly service plans · A reply within one business day
01 / 05The test call.
Before we contact a business, we call it. Method, not results.
We place a call after hours, from a number the business does not know, and we record four things: how many times it rang, whether a person answered, whether a message was taken, and whether anyone called back at all. Then we wait a full business day before counting the callback as missed.
We do not publish what we find about anyone. It belongs to the business we called, and we hand it over on the first conversation if they ask. The only figure we present about your business is one we observed directly. If we have already called yours, ask us and we will read it back to you.
02 / 05The same missed call, twice.
Drag the handle. Left is the call with nothing in place. Right is the same call with the system installed. The business name is fictional and the conversation is ours, not a customer’s.
Illustrative reconstruction. Northview Heating & Air is a name we use internally for testing. No customer records appear here.
Without the systemTuesday, 2:14 PM
You never knew that job existed until it was gone.
With the systemTuesday, 2:14 PM
The same reply reaches the owner’s phone as a normal text, with the name, the problem, and the address already in it.
Drag the handleor use the arrow keys
It captures the problem and the address and hands the conversation to a person. That limit is written into the proposal, not left to the wording.
as carrier rules require, in wording approved before launch.
03 / 05What the assistants say.
Once a month we ask the major AI assistants who to call, and we keep the answers.
Customers increasingly ask an assistant before they search. So once a month we put the same set of questions to the major assistants, in the plain words a homeowner would use, naming a trade and a town in our service area. We capture the full answer, record which businesses were named and in what order, and note which source page the assistant appears to have read.
The list is kept over time, because one reading proves nothing and a trend line is the only thing worth acting on. For a client, the same check is run on their trade and their towns and reported in the monthly summary. Nothing is scraped, nothing is bought, and nothing behind a login is touched.
04 / 05Where the system stops.
Five limits we build in before anyone asks for them.
-
Carrier registration first.
Business messaging runs on a registered campaign under your business name. We file the day the proposal is signed and the system does not go live until it clears.
-
STOP is handled, always.
Every message carries the business name and an opt-out. A STOP reply removes that number permanently, immediately, without anyone intervening.
-
Wording approved before launch.
Every message the system can send exists as a template you read and signed off. There is no free-form generation on the customer-facing path.
-
Shutoff from your phone.
You can stop the whole system in seconds, from the phone in your pocket, without calling us and without an explanation.
-
The data stays in your system.
Customer records remain where they already live. Where a system needs transcription or document reading, we run it on local hardware wherever the work allows, which is how our own call system is built.
05 / 05What gets counted.
Three measurements, the same three every time, taken from your systems rather than ours.
-
The call log.
Every inbound call, answered or not, and what happened next. It is your record, from your carrier, and it is the scoreboard the installation is judged on.
-
Response time.
The gap between an unanswered call and the text that went out, measured per call, not averaged into a claim.
-
The weekly summary.
One message every week: what ran, what failed, what changed, and the one thing worth your attention next week. The same format whether the week was good or bad.
Case studies are published as each installation completes its thirty-day verification, reported from the client’s own call log.
The shortest version
Ask us what your own test call sounded like.
If we have already called your business, we will read back exactly what we recorded: the rings, whether anyone answered, and whether anyone called back. It costs nothing and it is the shortest version of this whole page.