The Customer Who'd Rather Type Than Call
Website chat for restaurants is the guest on your site at 9:40 with one question. Same menu, same limits, same ticket as the phone.
On this page
It's 9:40 on a Tuesday and someone is reading your menu in bed. They have one question — whether the gluten-free crust is made in the same kitchen as the regular dough — and the only way to ask it is to call you tomorrow at eleven. So they close the tab and order from the app that already has their address.
You paid to get that person onto that page. The phone number at the bottom of it is the only door, and it is shut.
TL;DR:
- Website chat is for the customer who would rather type: same menu, same limits, same ticket as the phone.
- The conversation lands in the same list as your calls, so the order and the transcript sit together.
- Close the tab halfway through an order and come back: the pizza is still there, at the price you set.
- Payment is the same as the phone — pay at the counter, or a link in the conversation — at 2.9% + 30¢.
- It draws on your plan minutes: $99 a month for 750, or $299 for 5,000, with no overage.
A text box that takes the order
Most chat on a restaurant site is a widget with three answers and a phone number at the end. It is there to get the visitor off the page, not to take an order.
The difference shows up at "large pepperoni, half mushroom". A scripted widget hands you a phone number. This one builds the line, asks about the crust, reads the order back the way it will print, checks the limit you set, and sends the ticket where your kitchen already reads tickets.
It quotes the same menu the phone quotes. One menu per shop, so the chat cannot offer a price the phone does not know. One set of order limits, one reservation book, one list of tickets. Change the price of a large on Tuesday morning and both channels say the new number by lunch.
It also knows what you are out of. Mark the short rib sold out on the menu board and it stops offering it, in the chat and on the phone, even when the menu it imported still lists it as available. A restock brings it back. That one habit saves more Friday arguments than any script.
What the customer sees
A small widget in the corner of the page, and a conversation that sounds like your counter:
Guest: do you have gluten free crust
Kovo: We do, on the 12-inch only. It's made in the same kitchen as the regular dough, so I can't promise it's free of cross-contact.
Guest: ok. large pepperoni, half mushroom, pickup at 7
Kovo: Large, half pepperoni, half mushroom, pickup at 7. That's $24.80. Pay at the counter, or I can send a link.
The allergen line is your own note read back with the disclaimer, the same script the phone uses, and it never tells anyone a dish is safe. The order is read back before it is placed, because a typed order gets misread as easily as a spoken one.
Close the tab, come back, the pizza is still there
That is the whole test, and it is worth running yourself before the widget goes on your site.
A guest adds a pizza, gets distracted, reloads the page, and adds a drink. If the pizza is gone, the chat is a demo. If it is still there, with the crust and the half-and-half attached, the thing works.
The order is kept line by line as it is built, so a reload, a dropped signal in a parking lot, or a trip to the payment page does not start anyone over. A guest who has to rebuild a four-item order does not rebuild it. They order from somewhere else, and the somewhere else is usually the app that takes a third of the ticket.
Where the chat earns its place
Three cases, and they are specific:
- The menu page with a question. Someone is reading the menu, has one question about a substitution, and will bounce to a delivery app rather than call during service.
- The office order. Twelve lunches is easier to type than to say, and a list pastes in faster than it reads out.
- The after-hours visitor. Your kitchen is closed and your site is not. A question, a table, or an order still has somewhere to go.
A site nobody visits has nothing for a chat box to catch, and a shop whose orders already arrive by phone at the volume it can cook does not need a third door.
| The phone | The chat | |
|---|---|---|
| Who it's for | the caller with both hands free | the customer who would rather type |
| Best at | a fast order, a table, a question answered now | a menu question, a list, a big order typed carefully |
| Where the ticket goes | your kitchen | your kitchen |
| Payment | at the counter, or the card you already have on file, charged on the call | at the counter, or a link in the conversation |
| What it draws on | your plan minutes | your plan minutes |
The phone is still the fast path for a caller with both hands free, and the card you already have on file is still what closes that call in one step. The chat is the other door on the same building.
What it costs
The chat draws on the same plan minutes as the phone, because it is the same thing taking the order. Starter is $99 a month for 750 connected minutes, roughly 300 calls, and Unlimited is $299 for 5,000. There is no per-minute fee and no overage: at the cap, calls forward to your own phone instead of being answered.
A chat order is a call that happens to be typed, which is the honest way to price it. There is a ceiling per conversation and per shop, so a copied widget cannot run up your minutes. If the guest pays by link, the processing is Stripe's standard rate of 2.9% + 30¢, the same as a phone order.
What to try before you put it on your site
- A menu question with a substitution in it, to hear whether the answer is in your words.
- Two items, a reload, then a third, with nothing missing at the end.
- An order past the limit you set, which should be refused and then kept alive for what fits.
- A table, if you run your own book.
- A payment link, paid, to watch the ticket print only after the money clears.
- The desk list, where the conversation should sit next to the calls with its transcript.
That is ten minutes on your own menu, and it tells you more than an hour of demo. If you want to see the far end of it, the Toast walkthrough shows where the ticket comes out.
FAQ
Is website chat a separate product from the phone agent?
No. It is the same thing taking the order, with a text box instead of a phone line: same menu, same order limits, same payment link, same reservation book. A guest who types is taking the same path as a caller, which is why the ticket prints in the same place and shows up in the same list at the desk.
What happens if someone closes the page halfway through an order?
The order is kept line by line as it is built, so they can come back to it. Add a pizza, reload the page, add a drink, and the pizza is still there with its crust and its half-and-half. A guest who has to rebuild a four-item order will not rebuild it; they order from somewhere else.
Can a guest pay in the chat?
Yes, in the same two ways as the phone. They can pay at the counter when they collect, or take a link in the conversation and pay it on Stripe's page. A chat has no number to text, so the link arrives in the thread itself. No card number is ever typed into the chat.
Does the chat use up my plan minutes?
It does, because it is the same thing answering: 750 connected minutes on the $99 plan is roughly 300 calls, and 5,000 minutes on the $299 plan is roughly 2,000. A chat order is a call that happens to be typed. At the cap the line forwards to your own phone, and nothing extra is billed.
Does chat replace the phone?
No. It catches the guest who is already on your site with a question or an order and would otherwise bounce to a delivery app. The phone still handles the caller who wants to talk. The two share one menu and one set of limits, so there is nothing to keep in step.
Final Thoughts
The chat is not a second product to run. It is the same menu, the same limits, and the same ticket, with a text box in front of it, for the customer who would rather type than call.
Open your own site on your own phone, ask it the question you get asked most, and type an order through. Take a test call with your own menu first; the chat is on the same plan, and the rest of our phone writing covers the other door.