Staff shortages: run your restaurant without hiring a front desk
200,000 unfilled hospitality jobs. See how an autonomous front desk follows up every missed call by message, recovers lost bookings and eases the pressure on your team.
"We miss calls on purpose. There's nobody free to take them." A restaurant owner told me that on a demo call, plainly.
It isn't negligence, it's a trade-off. Short-staffed, you choose the floor over the phone. And you're right to: the guest in front of you has already walked through the door.
Except the role that goes first is never in the kitchen. It's the one that answers the phone and confirms tables.
The vacancy nobody sees
The staffing shortage is no longer a passing crisis. It's the sector's new normal.
200,000 unfilled jobs in French hospitality. The first casualty: the front desk.
Sit-down restaurants account for 40% of the branch's business failures. You read it on your Friday rota already.
The phone rings. Messages pile up. Emails wait until tomorrow. And the guest books somewhere else.
Every missed call goes next door
A missed call isn't an inconvenience. It's a booking that changes address.
- 18% of phone bookings (lost without an immediate answer)
- 85% of missed calls (go to the nearest competitor)
- 70% of missed calls (land in the middle of service)
Ten missed calls a week means £1,700 to £2,600 in bookings gone every month. To put a number on it, see the real cost of a no-show.
The front desk isn't hired, it's deployed
The real shift of 2026 isn't yet another piece of software. It's a front desk that no longer depends on recruitment.
Before, a role to recruit, train, replace six months later. In between, the phone rings into the void and messages are read the next morning.
Now the recovery happens in writing. A missed call gets a WhatsApp message, an SMS if WhatsApp isn't available on that number, and the conversation carries on there, in under a minute. No payroll.
Worth saying, since the question comes up in every training session: this doesn't replace a host. It replaces the moment when nobody is free to reply.
Heep even catches what you can't see, and lets you reply to every request in under a minute.
Noto Paris: 1,600 bookings a month
Noto, Moma Group's Italian table in Paris. High volume, an international crowd, peaks no team holds on the phone. Every missed call goes back out as a message, with no extra staff.
- 1,600 bookings / month via Heep
- <1 min response time, 24/7
- 32 languages handled
Want to see what that looks like on your volume? See how many calls you're losing
How the autonomous front desk works
The guest gets in touch
SMS, Instagram, email or WhatsApp. A missed call gets an immediate WhatsApp or SMS follow-up.
Heep understands the request
In natural language, in the guest's own language, accents and typos included.
It checks availability
Live in your booking system, with no double entry.
It confirms and follows up
Table confirmed, reminder sent. You touch nothing.
What a voicemail will never do
A voicemail deflects. "Call back during opening hours." The missed call, on the other hand, gets a message, and the table is booked from there, in writing.
- It handles the peaks. 70% of missed calls land during service. It never gets overwhelmed.
- It speaks the guest's language. From Japanese to Italian, no script.
- It knows your menu. Allergens, terrace, groups, opening hours: it has the answer.
And it doesn't quit. Live in a few days, there every night, with zero turnover.
Tonight, run the test: ask someone to ring your line at 8:30 pm and count the rings. Tomorrow at open, check the date of the oldest unread message in your DMs. That is the size of the vacancy, without posting a job ad.
Frequently asked questions
Can an AI agent really run a restaurant's front desk?
Yes.
How long does it take to deploy Heep?
Deployment takes a few days. No heavy setup and no change to your booking system.
Does Heep work with my booking system?
Yes. Heep syncs with the main systems such as Zenchef and SevenRooms to read availability and write bookings.
What happens with a very specific request?
Heep handles the vast majority of requests on its own and passes sensitive cases to your team with full context. Nothing slips through.

