Friday, 7:10 p.m. The expo window is jammed, three handhelds are firing tickets, and the host stand phone is ringing while your host walks a four-top to table 12. Siya answers that call in one ring, takes the order off your live menu, and drops it on your order board with a printable ticket. From $29 per month.
Toast is strong where it lives: handhelds on the floor, coursing, the kitchen display, the checkout. The one job no point of sale does is pick up when every hand on shift is already full.
Here is the whole call. It rings once. Siya answers with your greeting and your restaurant's name, then asks what the caller would like. She works from the menu you upload, so she knows your sizes, your temps, your sides, your substitutions, and what each costs.
She asks the follow-up questions a good host asks. Which dressing. Medium or medium rare. Sub fries for the side salad, that is a dollar. When the order is finished she reads it back line by line with the tax-included total, quotes the pickup time or takes the delivery address, and gets a callback number before she hangs up.
Plenty of calls are not orders. Hours, parking, patio seating, gluten-free options, whether you can seat nine on Saturday: she answers those from the knowledge base you write, in the caller's language, switching mid-call the moment they do. Anyone who needs a person is transferred to the host stand, the bar, or your cell under rules you set. Robocalls never reach anybody.
Same room, same Friday, same Toast setup. The only variable is who picks up.
| Today, without Siya | With Siya on the line | |
|---|---|---|
| Who answers at 7:10 p.m. | Whoever is nearest the host stand, mid-task | Siya, in one ring, every time |
| The third call ringing at once | Voicemail, and most callers never leave one | Answered in parallel; there is no line limit |
| Order accuracy | Scribbled on a pad over kitchen noise | Read back line by line with the tax-included total |
| Where the order lives | A sticky note until somebody keys it in | The AskSiya order board, structured and timestamped |
| Time to get it into Toast | Two to three minutes, plus the callback to clarify | Under a minute of typing from a finished ticket |
| After close | A voicemail box you clear in the morning | Orders, messages, and full transcripts waiting on the dashboard |
Put your own call volume and average ticket into the missed-call calculator to price that middle column.
Know this before you sign up. AskSiya does not write orders into Toast. When Siya finishes a call the order appears on the AskSiya order board with a printable ticket, and a person keys it into Toast the same way they would key in an order taken on a pad.
That takes roughly as long as reading the ticket out loud. Nothing is missing and nothing has to be chased: items are priced against your menu, modifiers are spelled out, the address and callback number are on the ticket, and the caller already confirmed the total. Put the board on a tablet by the terminal and it joins the expo routine in one shift.
If you would rather nobody retyped anything, there is a route for that today. The AskSiya REST API and outbound webhooks are live, so every completed order is available at GET /orders and pushed as an order.created event to whatever endpoint you point us at. Read the API documentation, or wire it up without code through Zapier.
A direct connection that files phone orders into Toast with nobody typing is on our roadmap. It is not built yet, and we will not imply otherwise or promise a date. Toast is a good product our customers already run their floors on. We are the phone layer in front of it.
If order injection is the thing that decides it for you, tell us that. We build integrations in the order operators ask for them, and restaurants who register interest go first when it ships.
Plans run $29 a month for 150 included minutes, $99 for 500, and $199 for 1,000, with two months free on annual billing. Phone ordering is the restaurant order taking add-on at +$49/mo, included free on Pro and free on every plan during early access. Starter and Growth auto-upgrade at 110% of included minutes rather than billing overage, so a heavy Friday never sends a caller to hold.
See the full pricing page, tour the restaurant product, read the pizza shop edition of this workflow, or browse every integration including Square.
No. There is no native Toast integration today and we will not imply there is one. Siya takes the order on the call and it lands on the AskSiya order board with a printable ticket, priced against your menu, with modifiers, delivery address, and callback number already captured. A staff member keys it into Toast in about the time it takes to read the ticket back.
If you want the retyping gone, our REST API and outbound webhooks are live today, so a developer or an automation tool can pull every order or receive it as an order.created event. Native Toast sync is on our roadmap with no promised date.
No. You keep the number on your menus, your window, and your listings, and forward calls to the local number AskSiya gives you. Forward everything, forward only when your line is busy or unanswered, or forward only after close. Switch forwarding off any time and the host stand phone rings again.
Siya answers all of them. She is not a single phone line, so there is no second caller waiting on hold and no third caller dropping into voicemail. Each order lands on the board separately with its own ticket and timestamp.
Table reservations are a separate add-on at $29 a month, free on Pro and free on every plan during early access. Siya collects party size, date, and time on the call, the request lands on your Reservations page, and she tells the caller you will confirm. She does not hold tables in a third-party booking system.
An AskSiya plan starts at $29 a month for 150 included minutes, with $99 for 500 and $199 for 1,000, and two months free on annual billing. Order taking is a $49 a month add-on that is free on Pro and free on every plan during early access. At a $35 average phone ticket, a couple of saved orders a month covers the Starter plan.