Sentinel is call analytics for contractors: AI reads every recorded call your office takes and shows you the callers who were ready to book and never got asked. You get the actual number on the first call, not the third.
What your recorded call volume actually is, what Sentinel finds on calls like yours, and what it would take on your phones.
Three things, and not one of them reaches your field service platform, because no job was ever created.
No job was created, so there is nothing to report on. Your booking rate only counts what got booked. The caller who was ready is invisible.
That is a rebid starting, and the last moment a save costs you nothing. It reaches your renewal report six months later as a loss.
Your CSR knew at 9:40 that morning and had no way to flag it. You find out next quarter, on a survey or on Google.
Ten specific things that happened on your phones, ranked by what they cost you.
A caller who was ready and never got asked.
A customer hinting at putting work out to bid.
An angry customer, the same day, not next quarter.
A call that ended without what dispatch needs.
An arrival window or callback nobody kept.
A job unfinished that needs a second trip.
A customer who needed you the same day.
A price request, and how long you took to quote.
A repair call that could have been an agreement.
Every call sorted by the job type it was about.
In the dashboard, or in your inbox
Every finding lands in your Sentinel dashboard, and it can also email the people you name, so nobody has to remember to log in to find out.
You pick which findings send the moment they happen and which wait for the morning digest. Most accounts run two or three same-day alerts and put the rest in the summary, which is what stops it becoming noise your team learns to ignore.
TeleCloud Sentinel
Alert triggeredNotification rule triggered
A monitored call matched one or more alert rules.
Call details
From (908) 555-0114 · To Office, main line
Call summary
Caller asked about the maintenance agreement coming up for renewal and mentioned they were getting a couple of other numbers this year. The call ended on the original service question. No save attempt, no note, nobody escalated it.
Triggered rules
Rebid signal on a service agreement
Analysis
Commercial account, six years on a service agreement. Procurement language sits upstream of an actual cancellation, and this call will not reach your renewal report until the agreement is already gone. Trigger sentence: “We are getting a couple of other numbers this year before we renew.”
Sent by TeleCloud Sentinel · Conversational Insights
View call in SentinelThe measured failure is upstream, at the phone, not in the field.
Change the four numbers to yours. The math updates as you type, and nothing here is sent to us.
Both modules are optional, available on any tier, and priced on top of it.
An illustration, not a promise. Every input is yours. Sentinel measures the first two from your own calls once recording is running, which is when the estimates stop being estimates.
Four steps. You have probably already done the first one.
See How Sentinel WorksSentinel reads recorded calls from whatever system you have, ours or anyone else's. If you are not recording yet, start there and we set it up.
All of them, once each call ends. Reviewing by hand reaches a fraction of them, and that gap is the whole product. Nothing installs on a truck.
Rebid signals, angry customers and overdue arrival promises get emailed to whoever you name. Nobody has to log in for the findings to land.
We go through what fired, what it missed and what was wrong, and rewrite the rules that need it. Then you coach off real calls instead of the two you overheard.
We do not publish a name, a number or a finding belonging to a business that uses Sentinel, and we would not publish yours.
The whole stack runs in Amazon Web Services in our own account. Your recordings and transcripts are not used to train any model.
Recordings 90 days, transcripts and analysis 180. If you need that in contract language, or you have a carrier questionnaire, let's walk through it together.
No. Any phone system will do, so long as it records. Plenty of contractors run Sentinel on the system they already have and never change phone companies at all. What Sentinel needs is the recording. Who provides the dial tone underneath it stays your business, on your timetable.
Yes, and there is no way around it. An unrecorded call leaves nothing to read. If you are not recording, we set that up first. Then we count how many of your extensions actually record, because half a dispatch desk recording is half a picture, and better known on day one.
No. Nothing installs on a truck, no technician logs into anything, and nothing changes about how a call gets taken. It reads recordings that already exist and emails findings to whoever you name. If your team notices it at all, it is because their manager started asking better questions in the Monday meeting.
It is separate software and we are not going to pretend otherwise. What it is not is a duplicate: your FSM records what got dispatched, invoiced and closed. It has no record of a call where nobody asked for the job, because no job was ever created. Sentinel does not write into your FSM and does not need a connector.
They stay in our own AWS account and Sentinel reads them there. Nothing is shared with another customer and no finding leaves your account. Get two things in writing rather than taking a web page's word for it: how long recordings are retained, which is a setting, and our commitment that your call content never trains a model.
It will be wrong sometimes; assume that going in. Every finding carries the quote that triggered it, so a human checks it in seconds rather than taking our word for it. Nothing is auto-sent to a customer and nothing changes in another system. On scoring, an item is only counted once its stated precondition matches what the call was actually about, so nobody is marked down for a call that never reached the situation. Wrong rule, we rewrite the rule.
No. Sentinel reads calls after they end, because the recording only reaches Sentinel once the call is complete. It is not live monitoring, it does not join calls and it does not answer them. Findings from a morning's calls are with you the same day.
Both read the same recorded calls, so there is nothing further to connect, and both are priced on top of your tier. Customer health is available at any tier and ties calls together by who was on them, so you see a pattern across a customer's calls rather than one call at a time.
You already record these calls and nobody has the hours to listen. Sentinel reads all of them and hands you the ten things that cost you money, starting with the callers who were ready and never got asked.
Sentinel works on recordings from any phone system. If your phones are already on TeleCloud, we can pull your recording coverage before you commit to anything.