Restaurant Social Media on Autopilot: What to Automate

The restaurant week, sorted

Three modes. Safe to automate: the post only uses facts that change rarely and that you have confirmed. Automate with an expiry: the post is fine, but it goes stale at a known time, so it needs an end date that stops it. Always a human decision: the post depends on a call made on the floor, a person's consent or a customer's feelings.

If you only take one rule from the table: anything with a price, a date or a dietary label needs a confirmed source, and anything with a date needs an expiry. The rest is detail.

Three questions that sort any new post

Your week will have posts that are not in the table. Run each one through these questions in order.

1. 1

   Does a person have to decide something on the day?

   Sold out, chef off sick, a complaint, a staff member who may not want to be shown. If yes, it is a human post. Automation cannot see your dining room.

2. 2

   Does it go stale at a known time?

   Specials, events, offers, holiday hours. If yes, it can be automated only with an end date that stops it and removes it from anything pinned or repeated.

3. 3

   Does it depend on a fact you have not confirmed in writing?

   A price you meant to change, an allergen in a new sauce, a booking link that moved. If yes, confirm the fact first. Once the fact is confirmed, the post can go into one of the other two groups.

A post that passes all three is boring in the best way: it uses settled facts and nobody has to make a call. That is the post to automate first.

The facts behind every food post

Automated posts are only as accurate as the facts they draw from. For a restaurant, four facts cause most of the trouble. Keep each one in a single place, with a person who owns it.

• Allergens. In the US, the FDA lists nine major food allergens: milk, eggs, fish, crustacean shellfish, tree nuts, peanuts, wheat, soybeans and sesame. Sesame was added by the FASTER Act and has had to be labeled on packaged foods since 1 January 2023. Your caption does not need the full list, but whoever wrote it must know where each one sits in the dish.
• "Gluten-free". The FDA's definition is under 20 parts per million of gluten, and it says restaurants making gluten-free menu claims should be consistent with that definition. State and local governments oversee restaurants. If your fryers or surfaces are shared, an automated post should never add the phrase on its own.
• Holiday hours. Google's help page says special hours are for a closure of up to 6 days in a row. For 7 days or more, it advises marking the business as temporarily closed instead. If your posts say one thing and your Google profile says another, guests will believe the one that turns out wrong.
• UK and elsewhere. The UK Food Standards Agency publishes allergen guidance for food businesses, including a matrix you can adapt. Check your own food authority for local rules.

For a fuller system for these facts, with owners and expiry dates, see Keep Your AI's Brand Memory Accurate.

Expiry dates: the rule most setups miss

Most automation mistakes in restaurants are not wrong facts. They are right facts that have run out. The Tuesday special was true on Tuesday. The October set menu was true in October. Three habits stop old facts from coming back.

• Every special, event and offer gets an end date when you enter it. Not later. If you do not know the end date, the post is not ready to automate.
• An approved caption is not a permanent fact. If you approve "two-course lunch for $22 this week", the tool should not learn that lunch is always $22. Check how your tool treats approved posts before you rely on it.
• Anything pinned or repeated needs a review date. A pinned post with last season's prices is the most common stale fact on restaurant pages. Put a calendar reminder on the day the offer ends.

What stays with a person, and why

Some posts look routine but carry real risk. Keep these out of any automated flow, however good the tool.

• Sold-out and "last tables" posts. They are only useful in the moment, and a late one annoys guests who come for something you no longer have. Post them live or not at all.
• Review replies. A reply is a conversation with one guest, often about something that went wrong. A person should read the review and write the reply. If you reuse a review in a post, it becomes a testimonial with its own rules; see reposting customer reviews and photos.
• Staff features. People leave, change roles or decide they do not want to be on your feed. Each feature needs a fresh yes.
• Answers to allergy questions. Whether a guest asks in comments or by message, a person who knows the kitchen answers. Never let a template promise something is safe.
• Anything after an incident. A food-safety issue, a bad night that went viral, a local tragedy. Pause automation first, then decide what to say.

Set it up in one afternoon

1. 1

   List your recurring posts (15 minutes)

   Write down every post you published in the last month and put each in one of the three modes from the table.

2. 2

   Fill in the four facts (30 minutes)

   Prices, allergens, hours and events, each with an owner and the date you checked it. Update your Google special hours for any closure you already know about.

3. 3

   Give every dated item an end date (10 minutes)

   Specials, events, holiday hours and offers. No end date, no automation.

4. 4

   Choose a modest rhythm (5 minutes)

   Automate two or three safe posts a week first, not seven. How often to post covers a realistic starting rhythm, and the restaurant week plan covers what to post on each day.

5. 5

   Decide who watches (10 minutes)

   Name the person who gets notified when a post goes live, who reviews anything held back, and who can pause everything on a busy night.

6. 6

   Run a supervised week

   Approve every post by hand for a week, even if your tool can post on its own. Note anything you had to correct. Fix the fact, not just the post.

If you use KeepsPosted, Autopilot is the opt-in version of this: an AI reviewer checks each post against your playbook, confirmed facts and offer dates, posts that pass go live and you get an email with links, and anything the reviewer flags waits for you. You can pause it any time. Approve-first is the default, which suits the supervised first week.

Before you switch any tool to posting on its own, run through the 10 guardrails for letting AI post for you. Photos with prices or dates on them have their own checks, covered in AI images with text.

Common questions

Sources

• FDA: FASTER Act, sesame as the ninth major food allergen (checked 12 Nov 2026)
• FDA: Gluten-free means what it says (checked 12 Nov 2026)
• Google Business Profile Help: set special hours (checked 12 Nov 2026)
• UK Food Standards Agency: allergen guidance for food businesses (checked 12 Nov 2026)

Written by the KeepsPosted editorial team from the FDA, Google and Food Standards Agency pages listed, read on 12 November 2026, with AI assistance for drafting. The three modes, the week table and the setup steps are our own suggestions, not measured results. Trattoria Lume is an invented example. This is general information, not legal advice.