DEV Community

Hostly
Hostly

Posted on

We let an AI answer a Limerick restaurant's phone for six months. Here are the real numbers.

Most of what is written about AI phone answering for restaurants is a vendor quoting a survey. This is different: it is the record of one phone line in Limerick, Ireland, taken from the database, including the parts that went wrong.

I am the founder of Hostly (hostly.ie), an AI host that answers the phone and WhatsApp for Irish restaurants. From 15 April to 19 October 2026 our host answered every call to a busy restaurant and lounge in Limerick city centre. The venue uses OpenTable for its diary and has a small front-of-house team.

The short version

Measure Result
Calls answered 2,332
New bookings taken by phone 249
Covers booked 761
Changes and cancellations handled 166
Calls passed to a person 299 (13%)
Median call length 55 seconds
Busiest single day 83 calls (20 June)

About one call in nine ended in a new booking. The average booking was for three people.

The phone rings when nobody can answer it

This was the finding that mattered most to the owner.

  • 52% of bookings were taken between 4pm and 8pm. That is evening service, when every member of staff is on the floor.
  • The peak hour for calls was 4pm to 5pm, followed by 5pm to 6pm.
  • 7% of calls came outside 10am to 10pm, and 27 bookings were taken in those hours, when the building was empty.

Before the AI host, a call during service was answered if someone could reach the phone. Otherwise it rang out. Half of the bookings in this record came from exactly those hours.

Month by month

Month (2026) Calls answered Bookings by phone
April (from the 15th) 124 11
May 104 7
June 361 34
July 327 40
August 527 70
September 452 53
October (to the 19th) 437 34

Volume more than quadrupled between May and August. Two things happened: the venue moved the line over fully, and the summer season arrived.

What the AI did not handle

13% of calls (299) were passed to the team. These were private hires, complaints, deliveries and anything the host is told not to decide. Each one was logged with the caller's number and the reason. Since October, each one is also sent to every manager on WhatsApp, and one of them marks it as handled.

I think 13% is a healthy number. An AI host that never hands over is making decisions it should not make.

No-shows

Of the 249 bookings, 50 were later cancelled and 17 were no-shows. That is a no-show rate under 7% on bookings the host confirmed by SMS.

What went wrong

  • In the first months the host sometimes told callers there was less availability than there really was, when the connection to the diary was slow. We fixed the cause in October and now audit every availability check.
  • A handful of calls were dropped when callers rang during a software update. We now only update when no call is in progress.

Every one of these is visible in the venue's dashboard and was reviewed with the manager.

What I would tell another restaurant owner

  1. Count your evening calls first. If your phone rings most between 4pm and 8pm, that is where the bookings are being lost.
  2. Test on a live line, not a demo. Ask for a table at a time that is full. Ask to change a booking. Ask for a person.
  3. Ask the vendor for their record, not their statistics. Calls answered, bookings taken, calls handed over, and what went wrong.

The full breakdown is on the Hostly site: Six months of an AI host on a Limerick restaurant's phone. You can also ring the demo line on 061 788 376 and talk to the host yourself. Nothing is booked on the demo line.

Daniel Silva is the founder of Hostly, an AI host for restaurants and service businesses in Ireland, built in Limerick. hostly.ie

Top comments (5)

Collapse
 
hitensethiya profile image
Hiten Sethiya •

the 13% handed to a person is the number id look at first, an ai host that never hands over is making calls it shouldnt. same thinking behind searchspot, the ai helps you decide but you still book where you prefer

Collapse
 
hostly_2f8dbc7924ab663d71 profile image
Hostly •

Agreed. Handing over is part of the job, not a failure of it. Our rule is simple: the host decides nothing it was not told it can decide.

Collapse
 
hitensethiya profile image
Hiten Sethiya •

that boundary is the important part. do you make the handoff condition visible to the caller, or does it route to staff when the host hits it?

Collapse
 
wbcomdesigns profile image
Wbcom Designs 💡 •

Publishing the 13% handed to a person is what makes this credible; most write-ups hide that number. Which kinds of calls made up most of the handoffs: allergies and special requests, complaints, or large group bookings? That split would tell other owners where staff time still goes.

Collapse
 
hostly_2f8dbc7924ab663d71 profile image
Hostly •

Thanks. I went back through the 299 and grouped them from the call summaries, so treat these as rounded:

  • About a third were group bookings of seven or more, parties and private hire. That is by design: the venue wants a person to confirm those.
  • About a third were ordinary bookings where the caller wanted a person. Mostly the time they wanted was full, a change could not be made, or a booking could not be found.
  • Around 9% asked for a person or a named member of staff without saying why.
  • Around 5% were practical things at the venue, such as a locked door or lost property.
  • Around 3% were complaints about food or a bill.
  • The rest were job enquiries, sales calls, wrong numbers and calls too short to classify.

Allergies and dietary requests almost never appear in the handoffs. So staff time still goes to groups, and to callers who hear "that time is full" and want a person to check.