VETRA
Log in Book a demo

Restaurants & Cafés

The questions restaurants and cafés ask first.

Restaurants and cafés run one engine and share one page, so they share one set of answers. Four rules sit underneath all of them, and none is a soft answer: the agent never confirms a table, it never answers an allergy question, every guest gets the same review link, and nothing sends itself.

What is on this page, and what is not.

These are the answers that belong to this trade. Anything true for every Vetra customer — what Vetra is, how cancelling works, where your data lives, how to get help — is on the platform FAQ. The product itself is on Vetra for Restaurants & Cafés.

The table

It takes the request and hands it to you. It never says “confirmed”. Vetra holds no table inventory, so the agent cannot commit a seat — only you can.

You get the name, the mobile number, the party size and what they asked about, in notifications and as a text, so the follow-up happens the same night instead of the next morning.

It does not answer allergy questions. Not a hedged version, not a “the kitchen usually” — it hands the call to a person, every time.

An allergy is a health decision and it belongs to your kitchen, not to a phone agent working from a menu file.

Yes. What the kitchen took off is what the phone, the widget and the dashboard all say, so a caller is never offered a dish you cannot serve.

On Square or Toast the 86 flows through from the POS; on an old register you set it by hand and it persists everywhere.

Guests & reviews

Everyone, and everyone gets the same link, whichever way they answered the check-in. Nobody is sorted by what they said and nobody is skipped for it.

That is written into the engine permanently rather than exposed as a setting, and it is the one thing here we would not change for a customer who asked. The link points at Google.

The check-in still does its job: a poor answer opens a private make-it-right conversation and alerts you the same day. What it never does is decide who is offered the link.

No. Messaging is enabled per shop, you write the campaign, you confirm who it reaches, and you press send. What Vetra brings is the aim. You decide, we aim it.

The send gate appends the opt-out line, suppresses anyone who has opted out, and holds frequency caps and quiet hours — those are enforced, not left to a config screen.

Then keep it. Points and visits live in Vetra rather than inside Square or Toast, so this sits alongside what you already run instead of replacing it.

The argument we would make is about aim, not about swapping vendors: an untargeted program mostly discounts the people who were coming anyway.

Your numbers

Never. 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.

On a connected POS the one thing Vetra writes is a campaign promo you already approved. Prices we never touch.

The POS has a reports tab. It will show you last week’s total; it will not tell you that the 2pm hour is dead, that your best-selling latte earns the least, or that a twice-a-week regular has not been in for three weeks.

A report is a number. This is the question you would have asked if you had had time to ask it.

Setup & sign-up

That path is built. Orders through voice, the widget and catering settle to your bank, the menu can be built from a photo of the one you already have, receipt capture reads paper into the same tables, and an 86 you set by hand persists everywhere.

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.

Yes. Restaurants and cafés are one vertical on one page, restaurants named first. The pilot form on the cafés page asks which room you run and takes restaurants, and onboarding forks to the restaurant build at step one.

The seating side is the part still being finished, and we would rather name it here than have you discover it in month two.

Price

$249 a month, per location. That is the whole list price for restaurants and cafés — one plan, not a ladder.

  • 400 voice minutes are included every month.
  • Minutes past the first 400 are metered at $0.20 each and appear on the following month's invoice.
  • Multi-location is coming, and deliberately not priced. We are not going to invent one.

Billed monthly, and it runs on any POS. Auto repair keeps its own Core/Pro plan prices — those are on the platform FAQ and none of them is yours.

The same terms, and the checkout, are on the pricing section of /cafes.

Next step

Book a demo, or start today.

The price is published above and the checkout on the restaurants and cafés page is real, so nothing here is a gate. Twenty minutes with Avi first if you would rather see it against your own menu. Independent operators, one to six locations.

Book a demo Twenty minutes with Avi, on your room and your POS. Start — $249/mo Two fields on the restaurants and cafés page and you land on Stripe. Rather talk it through? One application form, both rooms. Pick which you are at the top of it. Still have a question? Not a sales team — there isn’t one. Avi built it and he is the person who answers.