The phone rings during service, nobody leaves the floor
Reservations, groups, takeaway: Tanevo turns each request into a ticket. By phone, allergy questions go to your team.
- Table reservations: Ticket “Reservation Sat 7pm, 4 people, Gerber” with callback number; you confirm.
AI demo
Tanevo on the phone
Set up your business and call your own agent (it speaks German)
Every request
a ticket
Of course. What name shall I put it under?
Gerber.
Thank you. Saturday at seven, four people, under Gerber. The restaurant will get back to you to confirm the reservation.
Table reservations
Ticket “Reservation Sat 7pm, 4 people, Gerber” with callback number; you confirm.
What it takes down for you
The agent records the name and the request, and with your instruction also party size and time. You confirm the booking yourself.
Birthday, company dinner, drinks reception: the agent records occasion, date, number of guests and wishes, so you can call back prepared.
Lunch menu, closing day, parking, dogs allowed: what you store, the agent says.
How a call to your restaurant works
Restaurant name and notice: AI, call recorded. Can be turned off.
Reservation, group, takeaway or question. It answers what you've stored straight away.
By default the name; party size and time only on your instruction.
Nuts, gluten, lactose: never the menu. Handover per settings, else a ticket.
Name, number, preferred time in the dashboard. You confirm or call back.
Allergies and intolerances
On the phone, never answered from the menu. It hands over if your settings currently allow, otherwise records a ticket.
What else it handles
On the phone, never answered from the menu. It hands over if your settings currently allow, otherwise records a ticket.
A day in your restaurant
Example · translated from German
- 10:30A company wants a Christmas dinner for 25 people in December.
- 12:15A guest asks whether there is a vegetarian lunch menu today.
- 18:05Two pizzas to take away, collection at 6:45 pm.
- 19:30A guest booked for 7 pm and is stuck in traffic.
- 23:40A reservation request for Friday, four people at 7 pm.
- 10:30→ Records the occasion, date and number of guests. You call back with an offer.
- 12:15→ Answers from your stored weekly menu. If it says nothing, the agent says so.
- 18:05→ Creates a ticket with name, number and collection time.
- 19:30→ Records name and new arrival time as a ticket. The floor team needn't answer.
- 23:40→ Records the request as a ticket, due the next working day. You confirm.
A ringing phone during service versus Tanevo
Someone puts the plate down, or it just rings out.
Five voicemails in the morning, two of them without a number.
Whoever answers deals with the allergy question from memory.
On your closing day, nobody finds out when you reopen.
How to set it up for your restaurant
Examples. Instructions, off-limits topics and what it asks go under Behaviour, facts under Knowledge.
Instructions
- Always ask for party size and time for reservations.
- Groups of twelve or more: record occasion and preferred menu.
- Never promise terrace seating; only note it as a wish.
Never says
- Who has a reservation with us today
- Discounts or a free dessert after a complaint
- The kitchen's recipes and suppliers
Asks before handing over
Fact sheet
- Closing day
- Closed on Mondays and Tuesdays.
- Lunch menu
- Weekly menu, new on the website every week.
- Parking
- Three spaces behind the building.
- Dogs
- Welcome on the terrace.
Your systems
What works today and what doesn't yet. No reservation book is connected.
Menu and websiteToday
As a link or PDF. Re-import it when the weekly menu changes.
Pop-up agent on your websiteToday
Answers questions from your knowledge. The allergy rule applies only by phone.
Your own system with an MCP serverVia MCP
Connect it yourself, enable each tool. Changes only after read-back and yes.
Reservation book (e.g. aleno, foratable)Not yet
Not connected. The agent can't see whether a table is free.
Till systemNot yet
Not connected. Takeaway orders become dashboard tickets, not till entries.
What the agent never does
No allergen information by phone; even “gluten-free” or “without nuts” goes to your team.
Gives no advice on special diets; it notes the question.
Never confirms a reservation itself; you do.
No text message or email about new tickets; you see them in the dashboard.
Frequently asked questions
Not yet. It records the reservation request, and you confirm it. There is no connection to reservation systems yet.
Then the agent answers and records the request as a ticket. If a guest asks for someone from the restaurant, it puts them through to your number if you allow it: never, always, or only during opening hours. Otherwise it says you will call back.
Because on the phone every question mentioning gluten, lactose, nuts or an allergy goes to your team, even if the answer were in the fact sheet. The kitchen knows today's ingredients; a stored menu doesn't.
It records the order as a ticket, with name, number and preferred collection time. There is no confirmation to the guest, no link to your till and no text message to you.
Yes, if you forward your number to your Tanevo number. Outside opening hours it doesn't hand over by default; it creates a ticket due on the day you have it promise, otherwise on the next working day.
Not on the phone yet. The phone agent speaks Standard German; how well it understands Swiss German is still being measured with real recordings.