Vetra for Restaurants & Cafés
A table held for a guest who never arrives, and a bad night that reaches your reviews before it reaches you — those are the two quiet leaks in an independent dining room. Vetra answers the phone with your real menu and hours, captures the enquiry as a lead, asks every guest how the visit went, and keeps the guest list that tells you who each one was. The same engine runs the café half of this page, asking the counter version of the same questions.
Independent restaurants and cafés, one to six locations. Square, Toast — or a register with no API at all.
The no-show
It starts as a phone call at the worst possible moment — mid-service, hands full, nobody free to pick up. The call goes to voicemail, the party books somewhere else, or they book with you and you never hear from them again. Vetra takes that call and gives you back the one thing voicemail does not: a name, a number and what they wanted.
Sample calls — an invented restaurant. A real call reads your real hours and menu.
It never says "confirmed".
Vetra holds no table inventory, so the agent takes the request and hands it to you. In every restaurant conversation it is held to the same instruction — never tell a guest a booking is confirmed — because the seat is a commitment only you can make.
The 86 list travels with it.
What the kitchen took off tonight is what the phone, the widget and the dashboard all say. A caller is never offered a dish you cannot serve.
You get the summary, not the voicemail.
Who called, what they asked for, and the transcript. It lands in notifications and as a text, so the follow-up happens the same night instead of the next morning.
The review
A guest has a poor night, says nothing, and writes it down three days later where everybody can read it. The gap between the visit and the review is the only place anyone can do anything about it — so Vetra sends a short text into that gap and asks how it went.
One text after the visit, in your name. A poor answer opens a private make-it-right conversation and alerts you the same day, so you hear it from the guest rather than from a stranger's phone.
Whichever way a guest answers, the same Google review link goes out. Nobody is sorted by what they said and nobody is skipped for it. That is not a setting you could switch — it is written into the engine, permanently, and it is the one thing here we would not change for a customer who asked.
The room, read back to you
The restaurant dashboard is the same engine as the café one with the vocabulary changed — covers rather than orders, average check rather than ticket, dayparts rather than the morning rush. Ask it in the words you would use out loud and it answers off your own sales.
Regulars, the ones who come back sometimes, the ones drifting away, and the first-timers — built from what they actually bought, not from anyone filling in a form.
Which service is quiet, on your own trading pattern rather than an industry chart — and the busy ones too, so nothing gets discounted into a full room.
A group view across your locations, and each room on its own page underneath it. Built for an operator with a handful of sites, not a franchise system.
The café half — the counter
And it has never once told you anything. Every order is in there, timestamped. Your item costs are in there. So is every regular, and the week each one quietly stopped coming. Vetra reads what you already pay to collect — and tells you what it means. Everything from here down is that, in full, for an owner who still works shifts and runs one to six shops.
The quiet number
There's no cancellation, no complaint, no exit survey. A regular comes in twice a week for a year, then doesn't — and the first time you notice is months later, if at all. It's already in your POS. Nothing has ever asked it.
Sample data — invented people at an invented shop. No real customer appears here.
Dana is worth reaching. Priya is a drop-in. Knowing which is which is the difference between a gesture and a giveaway.
One POS connection
It all comes off sales you are already recording. Open any card and use it — these are the real components, not screenshots of them.
Before you ask whether it works with your setup
Same engines either way. Only where the numbers come from changes — and if they come from the second path, we tell you exactly what that costs you in precision.
If you run Square or Toast
The promo is the one thing we write to your POS, and it only moves after you approve it. Prices we never touch.
If you run an old register
And the honest part: we do not see every cash sale. We see what comes through us. The analytics are directional, not your books — and we would rather say that now than have you find it in month two.
The everyday win
Insights answers the question you thought of. Today surfaces the one you did not. The composer turns either into something you can send.
Ask "what are my slowest hours?" and get back a chart, a ranked list or a written answer — with every figure tracing to a real calculation rather than an estimate.
Yesterday's revenue, lifetime repeat rate, average rating and a ranked action queue. Each card deep-links to the tool that acts on it with the message already written.
Type a goal — "dead Tuesday, send 10% off" — or pick a playbook. It counts your exact audience and checks the discount against a 20% margin floor, warning you before you cut past it. On approval the promo is written to your register as a real discount.
It proposes setting changes — catering lead time, say — as a before-and-after with Confirm and Cancel. Applied atomically, and written to the audit trail either way.
Make more per cup
Competitor scraping, your costs, the quadrant, and a tuner that does the what-if maths live. Advisory from end to end — the last step is always yours.
Market low, average and high as a band with a slider. Live margin, revenue and profit deltas at any price, with a 20% margin-floor warning before you overshoot.
On Square, approve a recommendation and it writes to your catalog. On Toast, we hand you the recommendation to apply. Either way you approve first — nothing moves on its own.
After a price change the dashboard tracks predicted against actual impact, with a lifetime profit-added total and a running accuracy figure. You see whether the calls were right, because a number you cannot check is not proof.
Paste your menu and it estimates the ingredient recipe and cost behind each drink, so everything downstream runs on profit rather than revenue. You correct anything it gets wrong, and it remembers.
Vetra does not change your prices. Not with a button, not overnight, not with permission given in advance. You get a recommendation and the reasoning behind it. The change happens in your POS, by you.
What the research actually found
Punch cards do work — and the research on what they actually do isn't the research the vendors quote. A discount is only an investment if it's aimed. Broadcast, it is margin handed to people who were already walking in.
Kivetz, Urminsky & Zheng · 2006
A real multi-location campus café, buy-ten-get-one, 949 completed cards across roughly 10,000 purchases. Regulars moved from about nine to eleven purchases a month.
The part the vendors never quote is in the same paper: purchase rates slow down again once the reward is earned. It isn't habit formation. It resets.
Leenheer et al. · 2007
Correcting for self-selection shrinks the measured share-of-wallet effect roughly sevenfold.
Which is the shape of every headline number in this category. Restaurants that bought marketing sell more. Customers who enrolled spend more. Both compare people who opted in against everybody else, and call the gap a result.
Sharp & Sharp · 1997
Loyalty schemes are "quite defensive in nature, encouraging buying by existing buyers."
In their data the scheme's share still fell from 32% to 30%, while a rival running plain price promotions went from 21% to 28%.
"A program that appears to drive visits while eroding 8-10 margin points through excessive discounts isn't driving ROI — it's subsidizing behavior you may have gotten anyway."
So the useful question is not how do I run a loyalty program. It is which customer, and which hour — because that is what turns a discount from a giveaway into an investment. Everything below is a way of answering it, off data your shop already has.
Keep them coming back
Messaging is enabled per shop and the campaign is yours — you write it, you confirm who it goes to, you press send. What Vetra brings is the aim.
Triggered texts for slow days, lapsed customers and birthdays, written per customer. Daily send caps and opt-out suppression are enforced in the send gate, not left to config.
Milestone lifecycle texts off order data — welcome on the first, win-back at N days lapsed, a reward every Nth visit. Frequency-capped and quiet-hours aware. Points and visits live in Vetra, not inside Square or Toast — if you already run theirs, this sits alongside it rather than replacing it.
A short text asking how the visit went. An unhappy answer opens a private make-it-right conversation and alerts you the same day, so you hear it from them rather than from a screenshot.
Customers with two or more visits who have not returned in fourteen days or more, with their own pattern attached, and one click to launch the win-back. Card 05 above is this. The revenue-at-stake figure beside each name is in build — the list is live now.
Compliance, stated precisely.
Messaging is enabled per shop. "Reply STOP to opt out" is appended by the send gate automatically, and opt-outs suppress every engine. Frequency caps and quiet-hours checks are enforced in the loyalty loop. Texts go from a single TCR-registered toll-free number, and consent is captured before anyone is messaged.
The front desk that never sleeps
The same front desk for both rooms — the restaurant's reservation enquiry and the café's "are you open" land in the same place. Not a hundred-dollar add-on at the bottom of an order form. It is in the price at every tier.
Answers calls, reads your menu and hours, captures a name and number as a lead. Transcript and recording land in notifications. Never offers an item you have 86'd.
Customer-facing chat on your own site — menu, hours, lead capture. The same brain as the phone, so the two never disagree. One snippet.
The high-ticket work most café and restaurant tools ignore. Public intake form, validated against your own rules, into a new / replied / won / lost pipeline. The phone honours those same rules.
Leads and converted revenue attributed by channel — voice, widget, catering, missed call — with a period-over-period trend, so you can see which one actually pays.
A code provisioned per location for the counter or the table. Whoever scans it links themselves to their own order history — no app, no punch card, no friction at the till.
Photographs of receipts read into purchase history — what was ordered, how often, which day — so the regular list builds itself without manual entry. The same reader runs on bar slips; the café and dining-room path is on the queue.
It gets better the longer it runs
Not a slogan — a consequence. Every one of these needs accumulated trading to work at all, and the dashboard tells you which ones are not there yet rather than pretending.
The dashboard shows what the system can and cannot yet do, and what unlocks next — "100 orders and it can recognise the usual." Visible progress rather than a black box.
Tomorrow's revenue and orders, weather-adjusted, carrying a live accuracy figure that improves as data accumulates — including learning that weather does not move your sales.
You against the average Vetra room of your own kind on list size and daily orders. It gets more useful as more shops join, which we would rather say than pretend it is already dense.
Every change logged with an AI-versus-owner tag, the before and after values, and a timestamp. If something moved, you can find out what moved it.
Published, because nobody else in this category publishes
Toast Loyalty, Thanx, Punchh, Paytronix, Ovation — every one of them gates the price behind a demo. Here is ours: $249 a month, per location, 400 voice minutes included, $0.20 a minute past them.
Vetra for Restaurants & Cafés
$249 / month
Minutes over the included 400 are metered and land on the following month's invoice at $0.20 each. Multi-location is coming and is deliberately unpriced until it exists.
Talk to Avi first.
Twenty minutes on your room, your menu and your POS — he built it and he is the person who will answer. Or skip it and start below; two fields and you land on Stripe.
Talk it through
The price is above and the checkout is real, so this is not a gate — it is for the owner who would rather watch it run against their own menu first. You get the founder's attention and a setup that bends to how your room actually runs; we get somebody telling us what is wrong with it.
Book the demo, or send this instead.
Not a sales team — there isn't one. He built it, and he is the person who will answer. Independent restaurants and cafés, one to six locations.