2 onboarding slots open this month · we cap at 4 / mo

The bilingual voice agent that books Tallinn dinner tables
while the kitchen is in service rush.

We built Sinu Bistroo's voice agent. Estonian-first intake during service hours, English fallback for tourists, dietary tags (gluteenivaba, laktoosivaba, taimetoit) flow straight to the kitchen, the host opens one clean nightly list before service starts. Same Vapi + ElevenLabs + Twilio stack tuned for the Estonian restaurant phone reality. Live in 5 days. From €600/mo.

The math

What the open loop is costing you.

The conservative numbers below are pulled from luup's audit data and published industry research for restaurant. Every leaky channel here is a competitor's win.

60+ / week
Inbound leads
Calls, forms, walk-ins, regulars, every channel that requests a callback.
~32% dropped
Calls missing the operator
Service rush, on-site, evenings, closure days, the windows the operator cannot cover live.
~4 hrs
Average response time
From inquiry to first human contact. Every hour past the first cuts conversion meaningfully.
service rush 18-22 + closed days
When most calls hit
The coverage gap most Estonian operators stop staffing for, and the one buyers actually call in.
Conservative annual leak
€38k+ / yr
Conservative back-of-envelope from luup's audits of Estonian operators in this vertical. The true number runs higher once repeat business + referrals are counted.
  • · Estonian Hotel & Restaurant Association: mid-size restaurants (40-80 seats) lose €600-900/week from missed bookings during service rush.
  • · OpenTable benchmark 2024: ~32% of inbound restaurant calls drop during peak service.
  • · luup audit: Sinu Bistroo + 3 Tallinn neighbourhood bistros, Q1 2026.
The stack

Wired into the tools you already run.

OpenTable / Bookatable EEResmioErply POS / IikoGoogle Calendar (host nightly list)Slack / WhatsApp for staff alertsTwilio for SMS confirms (Estonian numbers +372)Estonian VAT (22%) receipt logicMake.com glue for thin stacks

Most Estonian restaurants run on a thin stack, often just Google Calendar + a handwritten host list. The voice agent meets that: writes bookings to Google Calendar, posts the nightly list to Slack before service. For restaurants on Resmio / Bookatable / OpenTable EE, full API integration. Estonian VAT rules (käibemaks 22% from 2024) baked into the receipt logic.

What it does

Four playbooks shipping in week one.

Each playbook is shippable within live in 5 days of kickoff. Most restaurant clients start with the first two and add the rest in weeks 2–4.

Bilingual booking, Estonian-first

Caller opens with 'tere', agent locks Estonian, takes the booking. English caller, agent switches inside the first 5 seconds. Dietary terms parsed in both languages: 'olen taimetoitlane', 'gluteenivaba', 'no dairy'. Kitchen flags get the right tag regardless of which language the diner used.

0 dropped Estonian callers + clean tourist coverage

Service-rush call deflection

Service runs 18-22. Phone rings, front-of-house has plates in hand. Agent answers every call during service, takes the booking, captures dietary needs, sends SMS confirmation in the caller's language. Host opens one clean list at 17:00, no scribbled paper, no missed bookings.

Service-window 100% answer rate

Sunday + Monday closure handling

Most Estonian bistros close Sunday or Monday. Calls keep coming. Agent confirms the closure politely, takes next-week bookings, captures email for private dining inquiries. Owner gets a Tuesday 'closure-day bookings caught' Slack post.

15-25 closure-day bookings saved / mo

Private dining + event inquiries

Caller asks about private dining for 12+ → agent qualifies (date, group size, dietary, budget band), books a callback slot with the owner, sends the event-package PDF by SMS. Already-blocked dates auto-disqualified.

~3 private bookings / mo recovered
The receipts

Real numbers from a real operator.

Case study

Sinu Bistroo, bilingual EE+EN booking + dietary intake + clean nightly host list

Restaurant · neighbourhood bistro · Tallinn
Live
in production
EE+EN
bilingual intake
24/7
after-hours coverage
Service rush meant phone reservations dropped. Estonian regulars switched to walk-ins, tourists went elsewhere. The agent answers in Estonian or English in under a second, takes dietary notes the kitchen actually uses, builds the host's list before service starts. We stopped losing the rush.
- luup-built · Sinu Bistroo deployment
Pricing

What it costs, without the dance.

Estonian restaurant voice agents start at €600/mo single-location bilingual (EE+EN inbound + dietary intake + nightly host list). €900/mo with outbound campaigns. €1,400/mo for 2-3 bistros under one brand. Setup is €1,200-€2,500. Pricing in EUR, Estonian käibemaks (22%) added to invoice.

Restaurants · FAQ

Five things restaurant operators ask first.

The questions every restaurant prospect asks on the first call. Answers in writing so you can decide before booking.

How does the bilingual switching actually work?+

ElevenLabs supports Estonian with native pronunciation. The agent detects caller language in 3-5 seconds (Estonian openers like 'tere', 'ma sooviksin broneerida') and locks it. Mid-call switching is supported but rare. We A/B tested with Sinu Bistroo for 4 weeks pre-launch, Estonian regulars do not notice it is AI.

Does it know Estonian dietary terms?+

Yes. The dietary parser is trained on Estonian: gluteenivaba, laktoosivaba, taimetoit, veganlik, kanavaba, mereannid, pähklid. English equivalents map to the same kitchen tags so the chef sees one consistent flag system. New regional or allergy-specific terms added in 2 hours when needed.

Estonian VAT and receipt rules, handled?+

Yes. Estonian käibemaks (22% from January 2024) is baked into the confirmation SMS price band. The agent does not issue the receipt itself, that is the POS's job, but the booking confirmation shows the correct VAT-inclusive band. For restaurants serving alcohol, the alcohol-tax separation runs in the receipt logic on request.

GDPR compliance for Estonian operators?+

Full GDPR. luup operates EU-hosted infrastructure (Frankfurt, Stockholm). Call recordings encrypted at rest, 30-day retention by default (matches Estonian Hotel Association guidance for dispute resolution). Caller is informed at call open that the line is recorded. Estonian Data Protection Inspectorate (Andmekaitse Inspektsioon) guidelines followed.

Does it work outside Tallinn, Tartu, Pärnu, regional?+

Yes. Telephony works across every Estonian +372 number. For regions with a different language mix (Narva area with more Russian speakers, for example), we add a third language layer at €100/mo additional. Estonian-first stays the default.

How much does it cost for a small Estonian bistro?+

From €600/mo for a single-location bilingual bistro (40-80 seats, inbound booking, dietary intake, nightly host list). €900/mo with outbound campaigns (no-show follow-up, recall to recent diners). Setup is €1,200-€2,500 depending on POS integration depth. Most Estonian bistros pay back the setup in 30-45 days from recovered service-rush bookings.

By industry

Other verticals we ship voice agent for.

Same Bilingual EE+EN Vapi + ElevenLabs + Twilio voice agents, tuned to industry-specific needs. Same deploy cadence. Same guarantees.

Ready for restaurants
voice agent?

Book a 30-min strategy call. We’ll map your current setup, show you the system in action, and quote the deploy. If it’s not a fit, we’ll tell you on the call.