Sentinel is restaurant call analytics: AI reads every recorded call your host stand takes and shows you the event and catering inquiries nobody returned. 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, and your POS records none of them, because none of them became a transaction.
The most valuable call the business takes, most likely to be answered mid service by somebody carrying plates. No callback, and no record it ever came in.
No reservation exists, so there is nothing to report. They called the next place on the list, and your covers look like a demand problem.
Forty people at nine, or nine people at four. Nobody is sure, and the person who took the call went home.
Ten specific things that happened on your phones, ranked by what they are worth.
An event, catering or buyout inquiry.
A caller wanted a table and did not get one.
Party size, date and time from every event call.
A date held, a menu or a contract promised.
Someone asked about membership or a gift card.
A booking you could not take, and the reason.
Takeout order volume, and when it actually peaks.
A call asking what your website already answers.
An allergy or dietary need raised in advance.
Vendors and robocalls separated from real guests.
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 Host stand, main line
Call summary
Caller asked about a private party for about forty people on the Saturday after Thanksgiving, early evening. They were told somebody would call back with availability. No date was held and no callback was logged.
Triggered rules
Event inquiry, no date held
Analysis
New inquiry, taken at the host stand mid service. The most valuable call the business takes, and nothing about it exists in your reservation book or your POS. Trigger sentence: “It would be about forty people, we were thinking the Saturday after Thanksgiving, early evening.”
Sent by TeleCloud Sentinel · Conversational Insights
View call in SentinelAt a club this is measured. At an independent restaurant it is not, so check your own book against it. What the club data shows is that food and beverage does not pay for itself, which means a mishandled event inquiry costs you twice: once in the booking, and again in the subsidy that covers the shortfall.
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. No POS integration, no reservation system integration, nothing to configure at the host stand. 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 during service it reaches zero.
Event inquiries and unbooked tables get emailed to whoever you name, the same day. The rest builds the weekly picture of what the phone is doing.
We go through what fired, what it missed and what was wrong, and rewrite the rules that need it. Then you coach the host stand off real calls.
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. If the calls are recorded, Sentinel can read them, whatever system produced them. Restaurants and clubs run it on the phones they already have. Whether you ever change phone providers is a separate question on a separate timetable, and plenty of operators never do.
Yes, and there is no way around it. Sentinel has nothing to read if nobody captured the call, so recording comes first and we will set it up if you need it. Then we count how many of your extensions actually record. A host stand that records paired with a banquet office that does not is the most common gap we find.
No, and this is worth being straight about. A caller who abandons in the auto attendant never has a conversation, so there is nothing for Sentinel to read. That problem is real, and it is a telephony report built from call flow events rather than a call analysis product. Ask us for that separately and we will tell you what your phone system can show.
No. Nothing installs at the host stand, nobody 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.
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 guest 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 lunch service 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 guest's or a member's calls rather than one call at a time.
You already record these calls and nobody has the hours to listen, least of all during service. Sentinel reads all of them and hands you the ten things that matter, starting with the event inquiries nobody called back. It also separates vendors and robocalls from real guests, which is what finally makes every other number mean something.
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.