Do I have to give up taking bookings by phone?

No. Phone bookings continue exactly as they are. Fork Time answers the calls your team cannot reach, and those bookings appear in the same book as the ones your host takes by hand.

Can I keep my restaurant's phone number?

Yes. Your number stays yours and forwards to Fork Time. Guests notice nothing except that somebody answers.

Do my guests need an app?

No. They call, text, message or use your website exactly as they would now.

Does this replace a staff member?

No. It covers the work that arrived with the extra channels: answering the phone, the email, the messages and the enquiries during service. Your team stays on the floor, and every decision that needs judgement still goes to them.

What if my team prefers the paper book?

Most keep both for a week. The live book is visible on any phone or screen, so the host can work the way they always have while the rest of the team can see what is coming.

How long does setup take?

Roughly half an hour. There is no migration, because there is nothing to migrate.

$99 per location per month for reservations, $199 with AI answering your calls and messages, $299 with phone ordering. No per-cover fees, no commission, no contract, and 14 days free.

FOR RESTAURANTS TAKING BOOKINGS BY PHONE AND PEN

Page role: first-system switchers, AU/UK "booking system" phrasing. Also owns the AI-modified variants: "AI restaurant booking system", "AI booking system for restaurants" (rising per Trends 3 Aug 2026; never target the generic "ai booking software", its SERP is appointment-scheduling intent). /restaurant-reservation-system owns the US "reservation system" head terms; this page must never target them. FAQ entry to add on this page (query pattern confirmed by Eat App's 20 Jul 2026 article):

What is the difference between a restaurant reservation system and booking software?

Nothing meaningful. "Reservation system" is the common US phrasing and "booking system" the common Australian and UK phrasing for the same category: software that takes reservations, manages tables and holds guest records. The real differences worth comparing are fee model (flat versus per cover), who owns the guest data, and whether the system also answers your phone.

Your staff are either in the kitchen or on the phone.

Guest enquiries now arrive across phone, email, SMS, WhatsApp, web chat and social, and none of those existed as a job when most restaurant teams were built. Somebody still has to answer them, and during service that means someone leaves the floor or the pass. Fork Time takes that work: it answers calls and messages on every channel, handles catering and function enquiries, checks what is actually free, and writes the booking into a live book your whole team can see. Your existing phone number stays yours. Nothing needs to be migrated, because there is nothing to migrate. Setup takes roughly half an hour with no hardware and no app for guests. Pricing starts at $99 per location per month with no per-cover fees and no contract, and every guest record belongs to your restaurant.

THE PAPER BOOK IS NOT THE PROBLEM

Plenty of good restaurants run a paper diary and run it well. It is fast, it never crashes, and the person holding the pen knows the room better than software does.

The choice was never paper against software. It is where your people stand.

A decade ago a restaurant answered a phone. Now it answers a phone, an inbox, a text thread, a WhatsApp, a web chat and a comment on social. That is a job, and in most independent venues nobody was hired to do it. So it gets absorbed by whoever is nearest, which during service means someone who was carrying plates a moment ago.

THE COST TURNS UP SOMEWHERE ELSE

This is why it never looks like a phone problem. The phone is answered, the booking is taken, the diary looks fine. What suffers is the room.

Food waits at the pass while the person who should be running it takes a booking. Tables are checked less often. Pacing slips, and pacing is what guests actually notice: 45% of diners say they would not return if their party's meals arrived more than ten to fifteen minutes apart, and 76% of diners are impatient if they wait more than fifteen minutes to be served.

Meanwhile one in three restaurant calls goes unanswered across the industry, most of them during peak service, and those never reach the diary at all. The function email that arrives at six on a Friday is read on Monday.

None of that is a discipline failure. It is arithmetic. Five channels, one team, and service happening at the same time.

THERE ARE TWO WAYS TO COVER THE WORK

Hire someone for it. That is the honest option and it works, if you can find them and carry the wage. Front of house roles are among the hardest to fill in hospitality, and the hours you most need covered are the hours everyone else needs covered too.

Or run it as a system. Fork Time answers every channel, takes and changes bookings against real availability, handles catering and function enquiries through the back and forth, and hands your team anything that needs a person, with the whole conversation attached. It costs a fraction of the wage, and it works the shifts nobody wants.

This is not about replacing anyone on your floor. It is about covering the job that was added to your restaurant without a person being added to your team.

WHAT CHANGES ON DAY ONE

Your phone number does not change. Calls forward to Fork Time, which answers the ones your team cannot reach, checks what is actually free, and writes the booking into the book your team is already looking at.

Guests can also book from your website, by text, on WhatsApp or through an AI assistant, without anyone picking up. All of it arrives in the same place.

Your team keeps a book, and it is still the thing they look at during service. It is simply live, visible on any phone or screen in the building, and it updates itself when a booking arrives at eleven at night.

WHAT YOUR TEAM KEEPS

The judgement. Fork Time recommends and your team decides: which walk-in gets the table that is about to turn, whether a booking needs a deposit, which cancellation is worth chasing. Nothing is seated, charged or refused without a person.

The guests. There is no marketplace between you and the people who already choose you, and nothing is charged per cover. Every booking, preference and visit history stays in your guest list and leaves with you if you go.

The way you run the room. This is not a new operating procedure. It is the diary you already keep, with the channels answered.

WHAT IT TAKES TO START

There is no migration, which is the part that stops most restaurants moving. Nothing has to be exported from an old system, because there is no old system. Fork Time reads your website for your menu, hours and details, you confirm what is right, you set your tables and your booking rules, and you forward the phone.

Roughly half an hour, no hardware, no app for guests to download. If it is not working the way you want inside the first fortnight, the trial ends and you have lost nothing.

WHEN A PAPER BOOK IS STILL THE RIGHT ANSWER

If your phone rarely rings out, if walk-ins fill the room without a waitlist, and if nobody on your team is choosing between a guest at the table and a guest on the line, the diary is doing its job and software will not add much.

The venues this helps are the ones where the room is busy enough that answering has become a job, and where the person doing it should be somewhere else.

EVERY CALL ANSWERED

See it working on your own service.

The demonstration uses examples based on your restaurant and service style.

Book a demo ↗ · Talk to it now →

REMOVED: /restaurant-answering-service. Same Ahrefs parent topic as /ai-phone-answering; two pages on one parent cannibalise the site's best cluster (~900 searches/month). Build instruction: 301 /restaurant-answering-service to /ai-phone-answering. The keywords it targeted (restaurant answering service, answering service for restaurant) are covered by /ai-phone-answering's H2 and FAQ layer.