Instagram Automation for a Restaurant: Bookings, Menus and the 22:40 Problem

A restaurant’s Instagram inbox has a specific shape: a small number of questions, asked at exactly the moments nobody can answer them. Peak service is peak enquiry, and the person who could reply is carrying plates.

The six questions, in roughly the order of frequency: are you open now, do you take bookings, do you have a table tonight, where exactly are you, do you have vegan or gluten-free options, and can we come with a group of eight.

The four automations worth building

1. Open now, and the address. Sounds trivial; it is the most-asked question and the most annoying to answer at 20:15 on a Friday. An automatic answer that states today’s hours and gives a map link handles it in a second.

Write it with today’s hours, not the week’s. A grid of seven lines is skimmed; “Open until 23:00 tonight” is read.

2. Bookings, routed to wherever bookings actually live. The automation’s job is not to take the booking — it is to get the person to your booking system in one tap, with the group size already asked.

We do take bookings. How many of you?
[2–4] [5–8] [More than 8]

Split at eight because large groups usually need a human anyway. Routing them straight to a person rather than into a booking widget avoids the classic failure where a party of twelve books three separate tables.

3. The menu, as a link and not a photograph. Menu photographs in Direct are unreadable on a phone and go stale the week you change the wine list. One link, always current, and the dietary answer attached to it: “Vegan and gluten-free options are marked on the menu.”

4. After hours. Most restaurant enquiries arrive when you are closed — people plan the evening in the afternoon and the weekend on Thursday night. An away message that states when you reopen, plus the hours and booking link, turns a dead hour into a booking. The design detail is in after-hours auto replies.

What about the comment-to-DM route?

It works well for restaurants in one specific pattern: a post about a dish or an event with “comment MENU” or “comment BOOK” in the caption. The comment is public social proof and the reply is private and useful.

Where it works less well is on ordinary food photography, where the comments are compliments rather than requests. A rule that DMs everyone who says “looks amazing” with a booking link reads as a business that cannot take a compliment. Attach comment rules to posts where you actually asked for an action.

Should a restaurant automate story mention replies?

Yes, and for restaurants this is one of the better returns available, because customers photograph food without being asked.

Someone tags you from a table, the story is live for 24 hours, and an automatic reply arriving in the next minute reaches a person who is physically in your restaurant with a phone in their hand. Thank them, ask to reshare, and you have content and goodwill for the cost of one message. The mechanism is in story mention auto replies.

What must not be automated

• Complaints about a meal. Somebody had a bad night. A cheerful automated menu link on top of that is the screenshot that travels.
• Allergy questions. “Does the sauce contain nuts” is a safety question, and a confident automated answer that turns out to be wrong is a serious problem. The correct automated response is to get a person, fast.
• Same-day availability, if you cannot actually see the book. Telling someone there is a table when there is not costs you a walk-in and a review.

How do you handle the party of twelve?

This is where a restaurant inbox genuinely differs from a shop’s. Large bookings, private hire and events are high-value, low-volume, and they need a conversation.

The right design is to detect them early and get them out of the automation: a group-size button, a keyword like “event” or “private”, and an AI agent instructed to hand over immediately when someone mentions a date and a number. The goal is not to answer — it is to collect the date, the size and a phone number, and to tell the person when they will hear back.

Does the 24-hour window matter for a restaurant?

More than for most businesses, because of the weekend.

You may reply for 24 hours after a person’s last message. Someone asking about Saturday on Friday night, with no reply, becomes unreachable by Saturday night — and if the answer would have come on Monday, you cannot send it at all. That is not a missed reply; it is a permanently closed conversation.

Practical consequence: for a business closed on some days, an automated response that invites a tap is not a nicety. A tap is an interaction, and an interaction restarts the clock.

What to measure

• Bookings that started in Direct. Put a distinct link or code in the automated reply so you can actually count them.
• Enquiries answered inside an hour during service. This is the number the automation exists to move.
• How many conversations still need a person, and what they are about. That list is next month’s automation.

The broader pattern for businesses with premises and opening hours is in Instagram DM automation for a local business, and the method for picking which questions to automate is in the FAQ bot article. Chatonaut’s plans are on the pricing page.