Answers the question, then books the table.

It can't. You tell TableNote what tables you have and how many each one seats, and it only ever offers a time when a real table that fits the party is genuinely free. If two guests try for the last table at the same moment, the database itself rejects the second one — it's not a matter of timing or luck. Parties bigger than the largest table you've listed are handed to you instead of booked.

It answers only from the menu, hours, and policies you give it. If a guest asks something you haven't covered, it says so, apologises, and emails you the question rather than guessing. That restraint is the entire design — a confident wrong answer about a nut allergy is worse than no answer at all.

No. You paste one line of code into your existing site, wherever it's hosted. Nothing else about your site changes, and nothing moves.

You don't stop taking them by phone — this just covers the hours nobody can pick up. Most people decide where to eat in the evening, and a call that rings out at 9pm is a table that goes to whoever answered. Bookings taken by the assistant land on the same screen your staff already use.

Technically yes, but we'd tell you not to for the same tables — two systems that don't know about each other will eventually sell the same table twice. Where TableNote differs is that it answers questions too, and charges one flat monthly fee with nothing per cover.

Every confirmation email carries a private link to the guest's own reservation, where they can cancel in two taps. The table goes straight back into your book the moment they do — which is the whole point, since a guest who can't find how to cancel simply doesn't, and you lose the table to a no-show instead of reselling it. Changing a time or party size still needs a phone call.

Yes. Staff can seat, cancel, mark a no-show, or add a walk-in from their own screen, and you can cancel anything from your dashboard. You can also mark whole dates closed for holidays or private events, and it won't book through them.

$79 CAD a month, or $790 a year. One price, everything included — there is no higher tier and nothing is held back.

No. Whether the assistant books you four tables this month or four hundred, the price is the same. This is the main way it differs from the big reservation platforms, which typically charge a monthly fee and then again for every guest seated.

No — instead you get to see it working on your own restaurant before you pay. Send your website and you'll get a page back with the assistant already answering from your real menu and hours, so there's nothing left to take on faith. You can cancel any time, and you're never locked into a term.

Reservations already in the book stay valid and your staff screen keeps working until the end of the period you've paid for. After that the widget stops answering and stops taking new bookings. You can export or simply work through what's left first — nothing is deleted the moment you cancel.

Most of an evening's work is entering your menu, and you can import that from your existing site or photograph a printed one instead of typing it. After that it's listing your tables, setting the hours you seat, and pasting one line of code. Realistically under an hour.

Yes, and with anything else that lets you add a snippet of HTML. It's a single script tag and doesn't care what built the page around it.

No. If you can edit your own site, you can install it — and if you'd rather not, setup help is included in the price.

Almost certainly not. The widget renders in its own isolated container so it can't collide with your site's styling, however that styling was written.

A name and phone number, which the restaurant needs to hold a table and to reach someone who's running late. An email if the guest offers one, so they get a written confirmation. Nothing else, and no account for the guest to create.

You, through your own login, and your staff through a shared PIN you set and can change at any time. Reservations are scoped to your restaurant at the database level, so no other business on TableNote can reach them even in principle.

Up to 180 days after the sitting, then they're deleted automatically. Conversation transcripts follow the same 180-day schedule. The full detail is in our Privacy Policy.

It answers from what your menu says, and always adds a reminder that the guest should confirm with staff before ordering, because kitchen practice changes day to day. It never presents an allergen answer as a guarantee. If your menu doesn't cover it, it says so and passes the question to you.