Takes the booking during service, when nobody can reach the phone.
The phone rings hardest exactly when your team is least able to answer it. Orastra takes the booking, the questions before it, and the changes after.
Four jobs, in a venue.
Takes the table during the rush
Name, number, time, how many. Booked against real availability while the floor is flat out.
Answers what's on the menu, and what isn't
Allergens, vegan options, corkage, when the kitchen shuts. From your menu, in any language.
Handles the change of plan
Six became four. Eight o'clock became nine. They're running late. All sorted without a call.
Catches the enquiry worth having
Private hire, big groups, parties. Written down in full and put in front of a person.
From first contact to done.
- 01
A guest calls or messages, usually mid-service.
- 02
It answers the question or takes the booking.
- 03
Changes and cancellations happen without stopping the floor.
- 04
Big groups and events go to your team.
What venues ask first.
Can it tell someone a dish is safe for their allergy?
It only repeats what your own material says, and it will not work its way to an answer you haven't written down. Where your material doesn't cover it, it says so and offers to have someone check. That is the only safe way to handle this.
Does it work with my bookings system?
It books into calendars you connect. If your system shares availability that way, it fits. If it doesn't, tell us before you buy and we'll say so honestly.
How does it know our opening hours?
You set them during setup, and it uses them for every answer and every booking. Holiday closures go in the same place.