How to answer Instagram DMs for a restaurant without living on your phone

A guest opens Instagram, sees your latest dish, and taps the message button. "Any table for two tomorrow at 20:00?" It takes her ten seconds. If nobody answers, she asks the next restaurant on her screen.

For many small restaurants the owner's phone is now the front desk. It buzzes during service, at midnight, on a day off. This article is about getting that under control: a few rules, a few templates, and an honest line for when software should take over.

Why DMs feel harder than email

Email is slow by nature. A guest who emails expects an answer today. A guest who sends a DM expects an answer in minutes, because the app feels like a conversation.

That expectation is the problem. You cannot leave a DM until Monday the way you can leave an email. But you also cannot answer every one while plating food.

The cost is real if you think about one message. Take a table for four at €35 a head: that is €140 sitting in one unanswered DM. We wrote about the same arithmetic for phones in what a missed call costs a restaurant, in euros. The DM version is quieter, because nobody sees the guest leave.

Rule 1: decide when you answer, and say so

Pick fixed windows. For example: before opening, after the lunch rush, and once late in the evening. Three short sessions beat constant glancing.

Then tell guests. Set an Instagram quick reply or an away message that says when you usually answer and where to book if it is urgent. A guest who knows she will hear back by 15:00 is far more patient than one who hears nothing.

Rule 2: one person owns the inbox

If three people can reply, guests get three tones and sometimes two different answers. Name one owner for the DMs each day. Everyone else leaves the threads alone.

If you do share it, write down what a reply may promise. A manager who says "we will find you a table" without checking the plan creates a problem for Saturday.

Rule 3: move the booking out of the chat

DMs are a poor place to keep a reservation. They scroll away, and the booking exists only in someone's memory. Whatever you agree in the chat, enter it in your reservation system straight away, with the guest's phone number.

Ask for the phone number in your first reply. You need it for the booking anyway, and it gives you a way to reach her if something changes.

Rule 4: know what never gets a quick answer

Some messages should not be answered from a phone on the pass. Write the list and keep to it:

• Allergies and dietary needs.
• Complaints.
• Large groups and private events.
• Discounts, press and partnership requests.

For these, send a short holding reply and come back properly. A rushed answer about an allergy is worse than a slow one.

Templates that sound like you

Templates are not cold if they are short and specific. Keep three or four in your notes and change the details each time.

A table is free. "Hello Marta, yes, we have a table for two tomorrow at 20:00. Could you send me a phone number for the booking? We will see you then."

The time is full. "Thank you for writing. 20:00 is full tomorrow, but we have 18:30 or 21:15. Would either suit you?" Always offer two alternatives, not a flat no.

A group enquiry. "Thank you, we would be glad to host you. For groups this size I will check the table plan and reply properly by this afternoon. Which date and how many guests?"

Opening hours and menu questions. Answer in one line and give the link. Do not paste the whole menu into a DM.

Reply in the guest's language where you can. A guest who writes in Polish and gets a Polish answer remembers it.

Where the manual method breaks

These rules work until volume grows. The usual breaking points are:

• Messages arrive at 23:40 and you are asleep.
• During Friday service nobody can touch a phone.
• The same guest writes on Instagram, then emails, then calls, and nobody remembers what she asked last time.

At that point you have two choices: hire someone to sit on the inbox, or let software answer the routine messages and keep the hard ones for you. See also why restaurants lose bookings after the kitchen closes for the late-night side.

What letting software reply should look like

A generic chatbot is the wrong tool. It cannot check your tables, and it makes up answers. What you want is something that reads your live availability, books into your system, and stops when a person is needed.

That is what Nomi, our AI host, does on Instagram. She replies within about a minute, in the guest's language, signed as your restaurant. She checks live availability in Tableo, creates the booking with the guest's phone number and confirms it. She does not invent prices, dishes or free tables.

You keep the controls. Each action has its own switch, including replying on Instagram and creating bookings. You set the largest group she may book alone (the default is 8) and how far ahead she books. Allergies, complaints, private events and discounts always go to a person. If you step into a thread, she stops in that thread.

A sensible way to start is to have everything wait for your approval, read what she would send, and loosen one switch at a time. Every reply shows what it was based on, so you are not trusting a black box.

She also remembers. If a guest asked for the terrace in June and writes again in September, Nomi knows. She never stores health, diet or allergy information.

Nomi is in testing with pilot venues in Lithuania, and early access is by request. Setup takes about ten minutes. A reply costs 4 credits and a booking 6, with 1 credit at €0.10, so a reply and a booking together come to €1.00. Details are on the pricing page.

A simple starting point this week

Whether or not you use software, do these three things in the next few days. Set an away message with your answer times. Write your four templates. Write the always-ask list. That alone will cut the time you spend on DMs, and it makes any later handover to software much easier, because the rules already exist.