Does it replace CoverManager?

No. CoverManager still runs the room. digafood is the one who answers the phone and writes into it.

Can it sell the same table twice?

No. It checks availability at the moment of the call, so it will not offer a table that has just been booked online.

Does it respect the sittings and the capacity?

Yes. It reads how you have set up each sitting and each room, and only gives what you can genuinely serve.

Does it take allergies and special requests?

Yes. It asks about them and leaves them written on the booking, so they are there before the guest arrives.

And if I change booking system one day?

You connect the new one and digafood carries on the same. The system is replaceable; the phone is not.

CoverManager, now on the phone too

It checks availability by sitting and room, books, changes and cancels. heydiga answers the calls and the WhatsApp messages CoverManager does not pick up, and writes into CoverManager before hanging up.

Talk to us

The phone rings exactly when service is on

CoverManager runs the tables and the sittings. The problem is that half the bookings still come in by phone, and they come in at half past two.

Today

The online booking drops into CoverManager by itself. The phone one has to be taken mid-service, with a full dining room.
A table is written on paper and moved into the system at the end of the sitting. Sometimes that table had already been sold.
They ask about the set menu, whether there is a terrace or whether dogs are allowed, and that call takes somebody three minutes.

With digafood

It answers and writes the booking into CoverManager without anyone leaving the floor.
It checks real availability by sitting and by room at that instant. It only offers what is left.
It answers the usual questions and, if there is intent to book, closes the table in the same call.

What it reads and what it writes

The connection runs both ways: digafood checks CoverManager before promising anything and writes into CoverManager the moment it closes.

Reads from CoverManager

Real availability by sitting, room and number of covers.
Opening hours and closing days.
Booking conditions and deposits where they apply.
The customer record and their previous visits.

Writes into CoverManager

New bookings with sitting, covers and room.
Changes of time, of party size and cancellations.
Allergies, high chairs, celebrations and other 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 the sittings you already have set up in CoverManager.

You authorise access

From the CoverManager account itself, with a permission you can revoke whenever you like.

digafood reads the room

Sittings, tables, capacity, opening hours and conditions. Nothing has to be loaded by hand.

You divert the phone

And it starts answering and booking on the same floor plan as always.

If you have CoverManager, you have this

Every trade has its own casuistry, with its own day, its own integrations and its own questions.

Restaurants that take bookings

The calls arrive right at peak time, when the team is serving.

It handles sittings, rooms and groups without anyone putting the tray down.

Restaurant groups and chains

One number for many sites and no consolidated data.

It routes each call to its site and gathers what happens across all of them.

Delivery and takeaway

The order comes in by phone and has to be taken in full, fast and with no mistakes.

It takes the whole order, repeats it back to confirm and sends it to the kitchen.

Bars and cafés

Few bookings and a lot of questions: hours, terrace, whether the kitchen is open at that time.

It answers instantly and lets the team serve without interruptions.

Catering and events

The call is not a booking, it is a quote that has to be taken properly.

It captures covers, date, menu and contact, and hands it to the salesperson.

Hotel restaurants

Resident guests and outside diners, with different rules and different hours.

It tells them apart and applies the terms that belong to each.

What changes in a restaurant with CoverManager

The same booking system, with the phone answered mid-service.

30%

3 out of 10 calls come in mid-service, when nobody can take them.

70%

7 out of 10 bookings are closed end to end without anyone on the team stepping in.

45s

How long it takes to give an appointment, from the phone ringing to the calendar entry.

At two in the afternoon nobody can pick up the phone. Now everything gets answered and the table is booked without stopping service.

Market cuisine restaurant · Madrid

We stopped choosing between serving a table and picking up the phone. Now both happen.

Group of 6 restaurants · Barcelona

What 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.

Calls a month600

Average spend per customer€28

Calls that go unanswered today30 %

Money lost every month

€2,016

€24,192 a year

180

unanswered calls a month

customers who were going to book

Fixed with Diga Growth, 169 €/month.
You are losing 12 times what it costs.

Get that money back

What everyone on CoverManager asks

The five questions of someone whose dining room is already organised 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.

Talk to us

It gets on with more things

If the restaurant uses another booking system, it works too.

TheFork

Syncs marketplace bookings with your own channel, without double bookings.

Restoo

Handles tables, sittings and the waiting list straight on the floor plan.

WordPress

Captures the bookings and enquiries that arrive through the business's website.

Shopify

Checks the status of an online order and resolves the question without going through anyone.