Every guest who opens the app, sees no 7:30, and decides to ask anyway picks up the phone. In a 44-seat room at 7:30 on a Friday, nobody can answer it. Siya does, in about one ring, and the request is on your dashboard before the next table is seated.
Think about who calls a restaurant that is already booked. The notify list is full and they want to know if waiting is worth it. The online form caps at four and they are six. A regular wants the chef's counter for a birthday and would rather ask a human. Someone rings at 4 p.m. because a guest at tonight's table has turned out to be celiac. Another cancels at 9 p.m. Sunday, and if nobody takes that call the table sits empty while your notify list waits.
None of that is a symptom of a weak book. It is overflow from a strong one, and it is the highest-intent phone traffic a restaurant gets. The problem is where it lands. Your room seats 40, there is no phone person, and every pair of hands is committed from first seating to last. So the call rings out into a voicemail box, and the numbers below are what that costs.
Work out what a cover is really worth after food cost in the food cost calculator.
Configured once, in plain English, in her instructions.
A party of nine or a Tuesday buyout is not a two-top question. Siya takes the date, headcount, budget range and contact, then hands it to whoever you label for events.
Celiac, shellfish, a nut-free table, a 40th, a proposal at 8:15. Siya writes it word for word onto the request and the transcript, so nothing depends on someone remembering a phone call three hours later.
The 6 p.m. that becomes 8 p.m., the five that is now three, the guest who cannot make it. Siya takes it at midnight on a Sunday and it is on your Reservations page when you open the room, early enough to release the table.
Visiting guests, out-of-town parents, a concierge calling on someone's behalf. Siya changes language the moment the caller does, at no extra cost on any plan.
Transfer routing to up to five labeled numbers: chef, GM, events, host stand, your cell. When a caller genuinely needs a human she hands off; when nobody picks up she takes a message.
Linen sales, delivery-app cold calls, warranty spam. Screened before they interrupt anyone, so what reaches your dashboard is guests.
Resy owns the book. Siya owns the phone. Today they stay two separate places, and you should plan service around that. The call produces a structured request on your AskSiya Reservations page: party size, date, time, name, callback number, notes, transcript. Whoever runs your book enters the table in Resy.
That handoff is typing, not detective work, which is the whole difference from a voicemail. The record is complete before anyone touches it, and Siya has already told the guest the restaurant will confirm, so nobody arrives at 7:30 expecting a table that was never entered. Same pattern on our sushi page and across the restaurant product.
We do not write a single cover into Resy, and we cannot see your availability. There is no connection today, and you should not buy this expecting one. Resy is a good product your team already knows. Siya is the phone layer standing in front of it.
Automation does exist today, just not the kind with a logo on it. The AskSiya REST API and outbound webhooks are live on every plan, so your own tooling can pull records or receive them as calls end. The endpoint list, webhook events, signature headers and retry schedule are in the API documentation.
If native Resy sync is what would decide it, tell us how your book runs and we will put you on the list. No dates promised.
Phone reservations run on the table reservations add-on, +$29/mo, over a plan of $29, $99 or $199 for 150, 500 or 1,000 minutes: roughly 20 cents an included minute, 2 months free billed annually. Add-ons are free on Pro and free on every plan during early access. See pricing, browse every integration page, or compare notes with the OpenTable guide.
No. There is no native connection today, in either direction. Siya answers the phone and captures a structured request on your AskSiya Reservations page with the caller's number and the full transcript; whoever runs your book enters the table in Resy. That is a few seconds of typing against a complete record. Native Resy sync is on our roadmap and is not built yet.
Exactly what you tell her to. You describe your usual patterns in her instructions, for example that late seatings are easier midweek or that parties above six need a manager. She takes the request, records how flexible the party is, and says the restaurant will confirm. Nobody is told they have a table, so your book stays the single source of truth.
Yes, and she keeps it out of the reservation queue. Siya collects the date, headcount, budget range, and contact details, then transfers to whichever of your five labeled numbers handles events, or takes a message with a callback number when nobody picks up. The whole call is transcribed, so you quote from what was actually said.
She answers those too, at no extra charge, on every plan. Cancellations, date changes, and next-week requests arrive overnight and are waiting when you open the room, which is often early enough to release a table rather than eat the no-show.
You pay for a plan plus the +$29/mo table reservations add-on. Plans are $29 for 150 minutes, $99 for 500, and $199 for 1,000, which works out around 20 cents an included minute, with 2 months free on annual billing. Every add-on is free on Pro and free on all plans during early access. The 7-day trial includes 30 minutes and needs no card. Full numbers are on the pricing page.
