Ana içeriğe atla
All posts
Restaurant

How does a restaurant / café use intusell? A daily operations guide

Training is done; now it's about operations. From a DM reservation or takeaway request to the table, from reminders to reducing no-shows and handing off to a human — a restaurant's daily flow with intusell.

intusell team
Author
June 5, 20269 min read
Restaurant

In the main article, you trained the intusell AI: you uploaded your menu and knowledge base, set up working hours and table capacity, and configured the persona and response rules. Training was a one-time setup. Now the real work begins: how does a restaurant or café use intusell, that is, how does restaurant intusell usage work in daily operations? This article shows, step by step, what the assistant you trained actually does in the field over a working day — from the incoming DM to the table reservation, from a takeaway order to a reminder, to reducing no-shows and handing off to a human.

This article is the second part of the restaurant section of our sector-based "how to train your AI" series. The first part, how to train the intusell AI, covered the setup; this one covers turning that setup into daily operations. We've written the same series for the tour agency and clinic sectors too.

Quick answer

Özet

A restaurant uses intusell to respond 24/7 to the reservation and takeaway requests guests send via Instagram DM and WhatsApp, to create reservations based on working hours and occupied tables, to reduce no-shows by sending automatic reminders 1 day and 2 hours in advance, and to re-offer a no-show reservation's freed table to suitable customers in follow-up. The AI never invents something not on the menu, a price, or stock; it says what it doesn't know and hands off to the live team. The business is always the one providing the service.

A day in the flow

A restaurant that has set up intusell has a typical day that looks very different from before. In the past, the owner or the floor manager would, at every spare moment between service, sift one by one through unread DMs, unanswered WhatsApps, and "are you open today?" comments. Now the messages that come in overnight and during service are already answered, reservations are created, and reminders are scheduled. The backbone of a day works like this:

TimeGuest sideWhat intusell does
01:40"Is there a table for 4 on Saturday evening?"Suggests a suitable time, creates a reservation from an open table
09:00The team logs inThe reservations accumulated overnight are ready in the single inbox
12:30Lunch rush, takeaway orderCollects the items from the menu, clarifies the order
17:00Guest with an evening reservationA reminder is sent automatically 2 hours in advance
19:20Request for a private event for 30The AI doesn't confirm on its own; it escalates the conversation to the live team
23:30A guest who has gone quietProactive follow-up message keeps interest alive

The team is no longer busy sifting through messages, but instead deals with conversations that genuinely require a decision — a private event, a large group, a complaint. They no longer have to stand by the phone keeping up with DMs during service.

Who is it for?

This usage model makes the most sense especially for these businesses:

  • Restaurants that receive heavy reservation demand via Instagram and WhatsApp — those who can't keep up between service with dozens of "is there a table?" messages a day.
  • Venues that suffer from no-shows — businesses where tables left empty by reservations that don't turn up turn directly into lost revenue, especially on weekends.
  • Cafés that lose after-hours and in-service demand — those losing guests because questions that come in during the evening rush or while closed are answered late.
  • Businesses with high takeaway / pickup volume — those who have to take orders constantly via WhatsApp and note them down one by one.

If you have a volume of demand that a single person can't keep up with between service, intusell works like an experienced floor manager that handles that demand.

Incoming demand: the guest asks, the AI gives the right answer

The flow starts when the guest sends a message. Imagine someone writing on Instagram DM, "We're coming as 6 on Saturday evening, is there a spot on the garden side?" The AI reads this message, scans the working hours, table layout, and venue rules in your knowledge base, suggests the option that fits the guest's need, and steers toward a reservation.

There are two important points. First: the AI does not invent something that isn't on the menu or in the knowledge base. To "Do you have gluten-free pizza?" it doesn't guess if it isn't sure; it says what it doesn't know and hands off to the live team or the business. This is the most important trust message — rather than giving the guest wrong information and creating disappointment at the table, it's safer to hold the right answer. Second: whatever language the guest writes in, the AI replies in that language; for a café in a tourist area this is critical, and no extra setting is needed.

If during training you added the response rule "before the reservation, clarify the party size, date, and time," the AI asks those three things first; the offer isn't random but based on the real request. We cover separately how all these channels come together in a single inbox in the Instagram and WhatsApp automation article.

Table reservation: slot, capacity, and conflict prevention

When the guest asks for a time, the AI doesn't pull a time out of thin air. It looks at the three things you defined during training: your working hours, your table capacity, and whether that slot is taken. If it finds a suitable slot, it creates the reservation.

Here the most critical safeguard is conflict prevention: a reservation cannot be entered above capacity. Before creating a reservation, intusell checks your working hours and existing reservations; if a full slot or an over-capacity request comes in, it doesn't open that time and suggests the nearest available time. Cancelled or no-show (missed) reservations free the table again in this check. So the nightmare that venues working with a manual reservation book experience most often — booking two groups for the same table or exceeding the room's capacity — disappears.

Every reservation has a status, and its lifecycle is clear:

scheduled (planned)
  → confirmed (confirmed)
  → attended (turned up / seated)
or
  → cancelled (cancelled)
  → missed (didn't turn up / no-show)

You'll find detailed instructions on how to set up the reservation flow, table layout, and calendar sync in the restaurant reservation automation article.

Takeaway and pickup order routing

Alongside reservations, the second main flow is the takeaway / pickup order. Imagine a guest writing on WhatsApp, "2 lahmacun, 1 ayran, takeaway." The AI reads the menu from the knowledge base, clarifies the order items and quantities, asks for the missing information (address, pickup time, note), and compiles the order in one piece.

Here the boundary is clear: the AI never invents a price or stock. It quotes the price of an item defined in the menu from the knowledge base; if it isn't defined, or a real-time stock question like "is it available today?" comes in, it doesn't guess — it routes to the live team or holds by saying "let me confirm this with the kitchen." Once the order is compiled, the payment and delivery step is up to your flow — the AI summarizes the order in a single message, and the team sees it at a glance.

So on the takeaway side, intusell works like a front step that takes the order and compiles it neatly; carrying the result to the kitchen or the courier stays under the business's control.

Reminders and reducing no-shows

The most expensive thing in a restaurant is a reservation that doesn't turn up: an empty table is both lost revenue for that evening and a missed chance for another group you could have seated at that time — especially on a full Saturday night. intusell reduces this with automatic reminders.

For every reservation, two reminders are scheduled:

  • 1 day in advance: a message along the lines of "You have a reservation for [party size] tomorrow at [date time]".
  • 2 hours in advance: a short reminder along the lines of "You have a reservation today at [time] — 2 hours to go".

The reminder goes through the channel the guest wrote on; if that channel is unreachable, SMS kicks in, and if that fails too, email. The message contains a one-tap cancel/reschedule link, so the guest can let you know in advance that they can't make it and the table doesn't go to waste. The guest manages their own reservation from the /manage-appointment/{token} page in the link; there's no need to call your team. If you want to turn off the reminder for a specific reservation (reminders_enabled), you can do that per reservation too.

If the guest still doesn't turn up, you mark the reservation missed; intusell automatically re-offers the freed table to suitable ones among the most recent interested or in-follow-up WhatsApp customers (unlike the multi-channel reminders, this re-offer currently goes via WhatsApp) and triggers a follow-up flow. There is no managed waiting list here; the system makes an opportunistic re-offer to suitable WhatsApp guests in follow-up. So a no-show becomes not a lost table but an opportunity that gets reassessed.

Instagram comments: a channel that opens gradually

In a restaurant, the flow often starts with a comment under a post: "What are the prices?", "Do you take reservations?", "Are you open today?". intusell's first step is on the approved channels, WhatsApp and Instagram DM; these two work live today. Instagram comment automation, however, opens gradually depending on Meta approval — the DM gate (instagram_dm_enabled) and the comment gate (instagram_comments_enabled) are controlled separately in the system.

When the comment channel is enabled for you, the flow works like this: the AI gives a short public reply to suitable comments ("Of course, let's share the details by DM") and moves the conversation to private; topics like price and reservations get clarified there. Until it's enabled, it does this job fully on the DM and WhatsApp side. The channel order and approval process are detailed in the Instagram and WhatsApp automation article.

Following up a quiet guest: proactive follow-up and CRM

In a restaurant, most reservations are lost with guests who say "let me check and get back to you" and disappear. intusell doesn't forget these guests. A proactive follow-up message goes to a guest who got the information and then went quiet; interest is kept alive. Every conversation is logged to the CRM, so the guest's history, which date/event they were interested in, and what stage they're at stay on record.

This way, when the team starts a new day, it's clear which reservation is confirmed and which request is waiting on follow-up. There's no need to keep a manual reminder list; a returning guest is recognized along with their past preference.

Handing off to a human: working modes

You decide how autonomously the AI works. There are three working modes:

ModeBehaviorWhen
ai_onlyThe AI handles all conversationsBusy service, when you want fully autonomous
hybridThe AI runs the normal flow, escalates when neededIdeal for most businesses
human_onlyAll conversations go to the live teamSpecial night, large event, sensitive case

In hybrid mode, the AI hands a request for a private event for 30 or a complaint off to the live team. At the moment of handoff, the entire conversation history is in front of the team; the guest doesn't have to explain from scratch. You can change the mode at any time — for example ai_only on a quiet lunch, human_only for large groups on a full Saturday night.

What it isn't

To put intusell in the right category, let's clarify what it isn't:

  • It isn't a chatbot. It's not a flow bot answering from canned templates; it's a fully autonomous AI sales assistant that works with the menu, knowledge, and sales techniques you trained.
  • It isn't a POS / check system. It doesn't open tables or close checks, doesn't drive a kitchen display; it's the reservation, order-taking, and guest-communication layer.
  • It isn't a food marketplace / courier platform. It has no inventory of its own; it uses your menu and your rules, and leaves delivery to your flow.
  • It isn't a restaurant-specific priced product. The pricing model is based on messages and voice minutes, and doesn't change by sector. The reservation and order module can be enabled on any plan.

So you don't start with the wrong expectations, let these boundaries be clear from the outset. For product and pricing details, you can check the solutions and pricing pages.

Frequently asked questions

Does the AI book the table on its own?

Yes. The AI suggests a suitable time and reserves the table based on your working hours and open slots. Double-booking the same time is prevented by the system. For a large group, a private event, or an unusual request, it hands the conversation off to the live team.

How are no-shows (reservations that don't turn up) reduced?

For every reservation, an automatic reminder goes out 1 day and 2 hours in advance; the guest can cancel or reschedule with a single tap. When a no-show reservation is marked "missed", the freed table is automatically re-offered to suitable WhatsApp customers in follow-up, and a follow-up flow is triggered.

Does the AI take takeaway / pickup orders?

The AI reads the menu from the knowledge base, clarifies the order items and collects the order; it then routes the payment/delivery step to your own flow or the live team. The AI never invents a price or stock; it says an item not on the menu isn't available.

Which channel does the reminder go through?

First through the channel the guest wrote on (WhatsApp, Instagram, Telegram, Messenger); if that's unreachable, then SMS, and if that fails, email. The guest doesn't need to install a new app; they receive the reminder on their existing channel.

Can the guest be connected to a human?

Yes. In hybrid mode the AI runs the normal flow and escalates to the live team when needed. In human_only mode all conversations go straight to the team, and in ai_only mode the AI handles everything. You can change the mode at any time.

Do reservations land in Google Calendar?

Yes. When a reservation is created, it's copied to Google Calendar as "Reservation — guest name"; reschedules and cancellations are reflected too. The sync is one-way (intusell → Calendar); the team sees the reservations in their own calendar.

Next step

If you haven't trained your assistant yet, start first with the how to train the intusell AI article — the foundation of this operation is set up there. If you want to go deeper on the channel side, you can move on to the Instagram and WhatsApp automation article, and for the details of the reservation engine, the restaurant reservation automation article; you can see the restaurant solution page and the whole series on the all articles page. You can review the price on the pricing page.

To see live how it would work in your own venue, request a demo or write directly to hello@intusell.com. In a 20-minute session, we open your inbox together and test the first reservation in the system.

intusell team
The intusell team distills this content from real field practice and user feedback. Questions? hello@intusell.com
Try intusell

You read the blog — now see it live.

Test intusell live with your own sector scenario in a 20-minute demo.

Get a demo
Buradayım! 👋