An AI agent helps a café or restaurant owner with the writing and sums that pile up around service: specials from what's in the walk-in, plate costs, rota drafts, supplier emails, review replies and the week's numbers. You paste in the material, it drafts, and you check it before you send or post anything yourself.

It has no connection to your till, booking system or suppliers, and it never talks to guests. It should never have the last word on allergens, food safety or who works when.

Between the pass and the paperwork: a day with and without an agent

Six moments from a Thursday at a 40-cover café, first as they usually go, then with an agent on your phone.

07:30, the prep list. Without: it goes on the whiteboard, where the two people starting at nine won't see it. With: you message the day's prep needs, get back a list in the order the kitchen works, and put it in the staff chat.

09:15, the veg invoice. Without: prices are up again, and working out what that does to the menu goes under "later". With: you paste the invoice lines, and two minutes later you know which dishes now lose money and the new plate cost of your three best sellers.

10:30, a birthday for 25. Without: you tell yourself you'll reply properly tonight. With: you paste the enquiry and get a draft reply with what you can offer, the questions you need answered and a holding line on price. You change the price line and send it before lunch.

14:30, next week's rota. Without: it's written from memory of who asked for what, and you hope nobody's down for six days in a row. With: it's drafted from pasted availability and contracted hours, with gaps marked. You move two shifts and publish it.

16:00, specials. Without: you decide three in your head and tell the kitchen verbally, and by service one has changed. With: four costed ideas using what needs eating first. You pick two, because the third needs an ingredient you haven't got.

22:30, Saturday's review. Without: you reply tired, it comes out slightly defensive, and it's posted before you think better of it. With: a calm, specific draft is waiting. You change one line and post it yourself.

Specials usually start in the walk-in, whatever the menu plan says. Before you order, or at the end of the night:

What's left in the walk-in: [list]. Needs using by Friday: [list]. Suggest four specials using it, with a cost per portion from these prices and a selling price.

You get four costed options and choose the ones the kitchen can turn out at speed on a Friday night.

Costing a dish properly is where margin leaks get found. Give the agent the recipe for eight portions and the invoice price of each ingredient, then ask for the cost per portion, the price at a 70 per cent gross margin, and what happens if the cheese goes up 15 per cent. It shows the arithmetic so you can check it. If a number looks wrong, it usually is, and an ambiguous pack size is the commonest reason.

The same habit catches supplier price creep. Paste the last three invoices from the veg supplier as text and ask which line items went up, by how much, and what that does to weekly spend if nothing changes. Rises hide in lines nobody reads, and this gives you the list you need for the supplier conversation further down.

Menu descriptions sell dishes and usually get written in a rush. Ask for lines under 20 words each, plain English, with "succulent", "artisan" and "deconstructed" banned: say what the dish is and why it's good. You'll reject a couple and keep the rest.

Can an AI agent do your allergen matrix?

It can draft one, and the draft is where its job ends. Paste the recipes with their ingredients and ask for a table of the 14 allergens against each dish, marked contains, may contain or needs checking, with every ingredient it's unsure about listed separately. The FSA's allergen guidance for food businesses sets out the 14 allergens you must declare and includes a downloadable allergen matrix you can use for the final version.

Then someone who knows the kitchen checks every line against supplier labels and the recipes as they're really cooked. Substitutions are the usual trap: the agent only knows the recipe you pasted, so it can't know the bakery changed the bun last week. The signed-off sheet is your legal responsibility. The agent saves you the typing and the first pass.

Rotas, briefings and new starters

Nobody should be solving the rota from memory at half two. Paste everyone's availability, contracted hours and the shifts you need covered, then ask for a draft that covers every shift, keeps people within their hours, marks where you're short and shows anyone working more than five days in a row. You check it against working time rules and your own sense of who's reliable on a Friday night, then publish it.

Verbal briefings don't survive a busy service. From yesterday's notes and today's bookings, ask for five lines: two things to watch, one dish to push, one thing that went wrong and how you're fixing it. Read it out in ninety seconds or post it in the staff chat.

New starters learn whatever the busiest person remembers to tell them. A day-by-day induction checklist for a kitchen porter, or a one-page card for the coffee station (what good looks like, the five commonest mistakes, the opening checks), lets a supervisor train someone without you standing over them.

Suppliers and the weekly order

Suppliers quote in different pack sizes, and not by accident. Paste three quotes and ask for a line-by-line comparison, cost per kilo, on the six items you buy most. The cheapest supplier is rarely the one the headline prices suggest.

For the order, give it your par levels, what's in stock and this week's menu, and ask for an order sheet by supplier, rounded to their pack sizes, with any par level that looks wrong for the week flagged. You check it and place the order yourself.

When the invoice check turns up a rise, a short, specific ask works better than a complaint:

Draft a reply to our dry goods supplier asking them to hold prices for six months in exchange for a larger weekly order. My voice: direct, friendly, no long justification.

Reviews and enquiries: drafts you post yourself

A defensive reply to a two-star review costs more than the review did. Ask for a calm reply under 90 words, signed by the owner, that doesn't argue with the facts and doesn't offer a free meal. For good reviews, ask for a short reply to each that mentions something specific the guest wrote, with no "thanks for your feedback" and no exclamation marks.

Event enquiries tend to go to whoever answers first. Paste the message and you'll get a draft with what you can offer, the questions you need answered and a holding line on price until you've decided it.

Illness is the exception. If a guest says they were ill after eating, don't reach for a draft: it's a food safety matter with its own procedure, and it needs your full attention.

Every word in these replies goes out from your account, after you've read it. The agent never replies to guests for you.

Check-ins around service

A check-in is a message your agent sends you at a set time. Pick times that fit your service:

  • Daily at 16:00. It asks for today's covers, takings and anything that went wrong, and adds them to the week's notes.
  • Sunday at 18:00. It asks what's left in the walk-in and what needs using first, then suggests specials for Monday and Tuesday.
  • Monday at 09:00. It asks for next week's rota gaps and the order list, and reminds you to check the allergen sheet before service.
  • First of the month. It asks for last month's numbers and turns them into one page, compared with the month before.

Three or four is plenty, because beyond that you stop reading them. There's more on the habit in scheduled check-ins.

Skills for your kitchen

Your rota rules save the most time each week, so they're the ones to get exactly right: opening and closing times, minimum shift length, who can't do Sundays, how many days in a row is too many, who covers the pass. Once Able° has saved them as a skill, every rota draft starts from your rules. Agent skills explained covers how skills work.

Others worth saving:

  • Your menu voice. Length, the words you use and the words you ban, how you describe heat and texture, whether you name suppliers.
  • Your order sheet. Supplier names, pack sizes, par levels, the order of the sheet and the cut-off times.
  • Your review replies. Warm without gushing, specific, never defensive, no exclamation marks.

What stays with you (and with the EHO)

These carry personal and legal responsibility, and no draft transfers any of it.

  • Food safety. Allergen sign-off, temperature records, cleaning schedules, HACCP paperwork, anything an environmental health officer would ask to see. The agent can draft forms and team briefings. It can't verify a recipe, check a label or sign a record.
  • Who works when. A rota is a legal document as well as a practical one: working time, rest breaks, young workers and right to work all apply.
  • Hiring and letting people go. It can write the advert and help you prepare a fair, firm conversation about lateness. Who stays is your decision, and the conversation is yours to have.
  • Prices and promises. It does the arithmetic on a regular's discount or a refund, and you make the commercial call.
  • Anything live. Bookings, table plans, till counts, stock levels and card payments live in your own systems. The agent sees none of them, so it can't spot a double booking or a till discrepancy.

Allergies, staff details and card numbers

  • Health information. A guest's allergy or a staff member's medical note is health data, which is special category data under the UK GDPR and the EU GDPR. Keep it out of memory, and write "nut allergy, table 6" rather than a name.
  • Staff data. For a rota, availability and hours are enough. Leave out home addresses, phone numbers, dates of birth, disciplinary records and bank details, and use initials.
  • Card details. Never paste a card number, a receipt showing one or a screenshot of a payment. No task here needs one.
  • Commercial figures. Supplier quotes, margins and rent are nobody else's business. Paste the minimum and clear the thread afterwards.
  • Memory. Let it remember dishes, suppliers, par levels and your voice. Keep out staff circumstances, complaints with names attached and anything a regular told you in confidence. Once a month, ask what it remembers and delete what shouldn't be there. The wider picture is in what happens to your data.

What we set up with you, and your first week

We set Able° up for you on its own private server and guide you through connecting it to Telegram or LINE on your phone, the one step that needs you. After that, Able° customers get a monthly tune-up with us.

Your first week, fitted around service:

  • Day one. Pick ten dishes and ask for descriptions. Twenty minutes of this teaches you more than a week of reading, and your first week with an AI agent covers the wider habit.
  • Day two. Take the descriptions you kept, tell it what makes them yours, and ask it to save your menu voice. Then redo one you rejected and compare.
  • Day three. Cost three dishes from real invoice prices and check the arithmetic by hand once. If its figure disagrees with yours, you've found something about a pack size or a price.
  • Day four. Start the Sunday specials check-in and the Monday rota and order check-in, which between them cover most of the admin that eats your day off.
  • Day five. Tell it which drafts you changed and why, so the next ones land closer, and ask what it has stored.

Is it worth it for a small café?

Probably not if your menu never changes and your team is stable, because a folder of standard documents covers most of this. It's also the wrong tool if you need a live link to your till or bookings, which it doesn't have. And it needs about ten minutes of pasting around service. If the day is so relentless that nothing ever gets typed, that's the problem to fix first.

Common questions

Can an AI agent take bookings for my restaurant?

No. Able° is your own agent, with no connection to your booking system, phone or inbox, and it doesn't talk to guests. It can draft your reply to a booking or event enquiry, including the questions you need answered, and you send it from your own system.

Do I need to be technical?

No. If you can send a message and copy text, you can use it. The skill lies in deciding what to paste and checking what comes back, which is why the first week starts with something as low-stakes as menu descriptions.

Will it post to social media or update my website?

No. It can draft the week's posts, say one a day with different angles such as the dish, the person behind it and the quiet-day offer, and you publish them. That keeps you in charge of everything that goes out under your name.

What if it gets a price or a dish wrong?

It will sometimes, especially when an invoice is messy or a pack size is ambiguous. Treat every draft as coming from someone who's never been in your kitchen: check the numbers once, and tell it what was wrong so the next draft is closer.