TheFork, now on the phone too
It syncs marketplace bookings with your own channel, without double bookings. heydiga answers the calls and the WhatsApp messages TheFork does not pick up, and writes into TheFork before hanging up.
The portal brings you tables, it does not pick up your phone
TheFork fills slots with people looking for somewhere to eat. The regulars, and anyone who wants to ask first, still call.
- TheFork bookings come in by themselves and the phone ones are written down separately. By the end of the day there are two lists.
- Somebody books the same table through TheFork that another person is asking for on the phone. And there are two bookings for the same hour.
- Whoever calls to change the booking they made through the portal finds the line engaged mid-service.
- It writes them all in the same place: the portal's and the call's end up in the same room.
- It checks real availability at that instant, whether it comes from the portal or from the phone.
- It answers, changes the time or the number of covers and leaves it synced.
What it reads and what it writes
The connection runs both ways: digafood checks TheFork before promising anything and writes into TheFork the moment it closes.
- Availability published by sitting and by number of covers.
- Opening hours and closing days.
- Promotions and conditions live on the portal.
- Bookings the caller has already made.
- New bookings with sitting and covers.
- Changes of time, of party size and cancellations.
- Allergies, high chairs and special requests.
- Notes on what was discussed, for whoever greets them at the door.
Fifteen minutes and it is done
Nothing to install, no technical help and no touching what you already have published on TheFork.
If you have TheFork, you have this
Every trade has its own casuistry, with its own day, its own integrations and its own questions.
What changes in a restaurant with TheFork
The portal keeps bringing new customers. The phone stops losing the regulars.
People call us in Portuguese, Spanish and English. It answers in each person's language and the booking still lands in the system.
Chef-led restaurant · LisbonOne number for every site and each booking ends up in the right dining room. That used to need a person all to itself.
Group of 4 restaurants · ValenciaWhat not answering costs you
The calls you miss and the ones that interrupt your work both have a price. Find out how much you could save with digafood.
Rough figures for a restaurant:
- 600 calls a month, 1.2 min each on average.
- €28 average spend per customer.
Money lost every month
€2,016
€24,192 a year
180
unanswered calls a month
72
customers who were going to book
Fixed with Diga Growth, 169 €/month.
You are losing 12 times what it costs.
What everyone on TheFork asks
The five questions of someone who already lists on the portal and just wants to know whether this fits.
Connect it this afternoon
Fifteen minutes to connect it and it is answering tonight. If it does not convince you, it disconnects just as fast.
It gets on with more things
If the restaurant uses another portal or its own book, it works too.
