Instagram DM automation for restaurants

What does a restaurant's Instagram inbox look like on a Friday at 6pm?

Service is starting, the phone is ringing, and the Instagram inbox has fourteen unread messages. Nine of them are one of five questions: what time do you close, can I book for four tonight, is the menu online, do you deliver, and do you take walk-ins. Nobody in the kitchen or on the floor can stop to answer them, so they get answered at 11pm, after the person has eaten somewhere else. The questions are not hard. They are just badly timed.

The other kind of message is the one you do want to read personally: a private-hire enquiry for a fortieth birthday, a supplier, a food writer, a complaint. Those get buried under the "are you open today" messages. Automating the repeat questions is not about replacing the host; it is about clearing the inbox so the host sees the enquiry that is actually worth a call back. That is what DMPilot is for on a restaurant account.

Four automations that suit a restaurant

DMPilot has three triggers: a keyword comment on a post or Reel, a reply or reaction to a story, and a keyword in a DM. Each automation sends one message, with an optional link shown as a button. These are written the way a front-of-house person would say them; swap in your own dishes, times and links, and keep each to three or four sentences.

Which questions is it safe to answer with an automated DM?

A good rule: automate anything with an answer that is true for everyone and changes rarely. Hours, the menu link, the delivery apps you use, the walk-in policy, and where to book. Do not automate anything that depends on tonight, such as "do you have a table for six at eight". Send the booking link and let the booking system say no.

• Hours: keyword "hours". Reply with the week's hours and the kitchen close time, which is the one people actually need.
• Menu: keyword MENU, on comments and DMs. One line of description and a See the menu button.
• Ordering: point the menu button at your online ordering page if you have one.
• Delivery: keyword "delivery". Name the apps you are on, or say plainly that you do not deliver.
• Booking: keyword BOOK, with a separate automation for "table" if your regulars say that instead.

Where do email capture and tracked links fit into a restaurant's week?

Restaurants have a real reason to collect emails: a new menu, a Sunday roast, a Christmas booking window. DMPilot can ask for the email inside the DM thread, with your consent text, before it sends the link. Do not ask for an email in the hours reply; nobody wants to sign up to find out when you close. Ask in a private-hire automation, and in the specials-story reply for people who want to hear about the next one.

Tracked links are the other half. Every See the menu or Book a table button is a short link with a click count and a click-through rate, so you know whether the DMs are sending people to the booking page or just being read and ignored. DMPilot counts taps on its own links; what happens on the booking or ordering site is measured there. Read how to capture leads from Instagram for the email side.

What should a restaurant measure each week?

Keep it to numbers that change what you do next week. Click-through rates vary widely between venues and cities, so treat your own first few weeks as the baseline and compare against that rather than against anyone else's figures. Four numbers are enough.

• Story replies to specials, and the click-through rate on the booking button in the reply. If replies are high and clicks are low, the special is popular but the link is not.
• Menu-link clicks from Reel comments versus from DMs, which tells you where the menu question actually comes from.
• Private-hire enquiries that reached a person, and how long they waited. The automation should make this faster, not slower.
• Unanswered DMs left at the end of the night. The point of the exercise is that this number falls.

What DMPilot will not do for your restaurant

DMPilot does not take bookings, orders or payments. It sends the link to whatever booking or ordering system you already use, and the booking happens there. It does not check availability, hold tables, or know that the back room is full on the 14th. It cannot message anyone who has not contacted you first, so it cannot DM everyone who tagged you last month or everyone who follows the restaurant across the street.

There is no visual flow builder, so each automation is one trigger and one message with an optional button and email request, rather than a branching menu of "press 1 for hours". It does not run on WhatsApp or Facebook Messenger. Every automated message is text you wrote, so it sounds like your front of house. There are no multi-account workspaces, so a group with three venues sets up each account separately, and no product carousels.

Does this keep the account safe with Instagram?

Yes, provided the tool runs on Meta's official Instagram API, which DMPilot does through an approved tech provider. A restaurant account is exactly the kind of account that gets tempted by a cheap unofficial bot, and those are the ones that lead to action blocks and lost reach. The rules DMPilot follows: one private reply per comment, a 24-hour window after the person's last message, and one link DM per person, per automation, per day.

DMPilot is free for up to 100 people a month, then $9 a month or $81 a year, flat, however busy the account gets. Start free with no card, set up MENU on your next dish Reel, and see how many of Friday's questions answer themselves. More recipes for local businesses are in DMPilot for small business.

Frequently asked questions