← Back to library

Take food orders from Instagram DMs with an AI agent

u/timhartmann7 on r/AI_Agents put a Claude-based assistant in front of a sushi restaurant group with seven branches, where almost all orders arrive as Instagram DMs. It replies from a reference sheet of dishes, allergy notes and delivery rules, and a human still confirms before the kitchen runs.

  • OutcomeAnswer delivery customers in Instagram DMs instantly, using your menu, allergens and delivery zones, and pass each confirmed order on for preparation.
  • SetupAn afternoon+
  • LevelAdvanced
  • Creditu/timhartmann7 on r/AI_Agents
View original
Works with
ClaudeCustom agent

Published Oct 20, 2026Updated Oct 20, 2026AI dry run on sample input: passed Oct 20, 2026Source verified Oct 24, 2026

When should you use it?

  • Most orders arrive as DMs and replies are slow or inconsistent
  • One busy person is the bottleneck for taking orders

Not for: Phone orders, voice notes and photos of handwritten orders; the poster keeps those with staff on purpose

What do you need, and what do you get?

You need

  • Access to your Instagram business messages through Meta's official API
  • One reference document covering dishes, prices, allergy details, delivery areas, opening times and current deals
  • A hand-off from chat to your order system or kitchen screen

You get

  • Instant, on-brand replies that help customers choose
  • Agreed orders passed on for cooking, with a record kept
  • A full chat log the owner can review

How does it work, step by step?

  1. Build the knowledge basePut menu, allergens, zones and hours in one structured document and keep it current.
  2. Set the rulesUse our prompt as the system instructions, including when to hand off to a person.
  3. Read back before confirmingHave the agent restate the order, address and any allergy notes and wait for a yes before it reaches the kitchen.
  4. Review logs daily at firstRead conversations each day for the first weeks and fix the rules where it went wrong.

The prompt

Our own prompt, inspired by u/timhartmann7 on r/AI_Agents and written to work in Claude and Custom agent. Values in lime are placeholders.

Fill in the blanks (optional; the copied prompt uses your values)

Prompt2 variables
You take orders for {restaurant} in Instagram messages. Use only this knowledge base: {menu_allergens_zones_hours_promos}.
- Be warm and quick. Help customers choose, explain ingredients, and suggest one add-on only when it fits the order.
- Always ask about allergies. Never confirm an item that conflicts with a stated allergy; say why and suggest an alternative from the menu.
- Check the address is in a delivery zone and the location is open.
- Before confirming, read back the full order, total, address, and any allergy notes in plain language and wait for 'yes'.
- Hand off to staff for voice notes, photos, complaints, refunds, or whenever someone asks for a person.
If something isn't in the knowledge base, say you'll check with the team instead of guessing.

Inspired by u/timhartmann7 on r/AI_Agents: A Claude agent taking orders for a 7-location sushi chain. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.

What can go wrong?

  • Allergen mistakes are not like a wrong sauce. A commenter suggested a plain-language read-back of allergens before every kitchen push; do it.
  • Promos and hours change. If the knowledge base is stale, the agent will confidently quote old prices.

Our take

For many restaurants, Instagram DMs are the order line, and a missed or curt reply is lost revenue. This build is a good template because it is as clear about what the agent doesn't do as what it does. Text conversations, menu questions, allergens and add-on suggestions go to the agent; calls, voice notes and photos stay with people, and a customer can ask for a human at any time. The owner gets the full chat log for review. Two points from the thread are worth taking seriously. A single accuracy figure hides very different mistakes: a wrong sauce suggestion is minor, a missed allergy isn't. And the fix a commenter suggested, a read-back of the order and any allergens before it goes to the kitchen, costs one message and prevents the worst failure. We built that into our prompt. In our dry run with a made-up menu of 20 items and 8 sample conversations, the agent answered menu questions from the knowledge base, refused to confirm one roll for a customer with a sesame allergy, read back every order before confirming, and handed off a voice-note message and a refund demand to staff.

Where the time goes back: Orders stop waiting for a busy manager to check DMs, and staff only handle the conversations that need a person.

FAQ

Isn't it expensive to send the whole menu with every message?
The poster uses prompt caching so the large menu block is read from cache on most messages, which keeps the cost low.
When does a person take over?
In his setup: calls, voice notes, photos, and whenever a customer asks for a human.

Source and credit

Inspired by u/timhartmann7 on r/AI_Agents. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.

Inspired by
A Claude agent taking orders for a 7-location sushi chain
Creator
u/timhartmann7 on r/AI_Agents
Published on
Reddit
Original date
Jun 21, 2026
License
Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
Originally for
Claude
AI dry run
Oct 20, 2026: passed. Dry-run tested by our AI test agent on sample input. Allergen rule and read-back worked; hand-offs followed the rules.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails.
Verified
Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.

Are you the creator? Claim or correct this page.

More in Customer Support

All 27 Customer Support playbooks →

Related playbooks

Customer SupportWorkflow✓ AI dry run

Ground WhatsApp answers in your public site pages

Customers who message you on WhatsApp get quick answers based on your own website, and interested ones are offered a call.

Credit: David (@recap_david)

An afternoon+
Customer SupportPrompt✓ AI dry run

Find the bugs in your intake chatbot with one test chat per rule

Write a small set of test chats, each aimed at one rule in your bot's field spec with the stored values you expect written down first, and catch errors a large pile of happy-path chats misses.

Credit: Adam (Adam13y)

Under an hour
Customer SupportPrompt✓ AI dry run

Clean up saved support replies before your bot reuses them

Read every saved answer your support bot can pull from as if it were about to be sent to a stranger, rewrite the risky ones into generic answers and set rules so new ones are written that way.

Credit: Pierre-Laurent Medori

Under an hour
Customer SupportWorkflow✓ AI dry run

Gate sales and support phone calls with clear handoffs

A voice agent rolled out in the order that works: inbound support first, then cautious sales qualification, with clear escalation.

Credit: u/liit_upp on r/SaaS

An afternoon+