LINE Chatbot for Restaurants (2026)

Because in these markets, a LINE account is often how a diner decides where to eat, not just how they book once they've decided. A ramen chain with locations across Tokyo that only takes phone reservations is invisible to the diner who wants to check wait times and reserve without calling.

The scenario that shows the value: a diner near a busy Tokyo location taps the rich menu's "Reserve a Table" button during their lunch break, sees the next available slot, and books it in under a minute - no call, no hold music. A regular customer instead taps "Pre-order Lunch Set" and pays through LINE Pay, then simply picks up the order and skips the queue entirely. Both interactions happen through the persistent rich menu at the bottom of the chat, not a typed conversation, which matches how these customers already expect to interact with a restaurant brand.

For a multi-location chain, this also solves a coordination problem - one LINE account per brand, with the rich menu routing each customer to their nearest location's actual availability.

Keep the automated scope reservation and menu-focused:

• Table reservation booking. Real availability by location and time, confirmed in-chat.
• Wait-list and queue notification. Let a customer join remotely and get notified when their table is ready.
• Menu and ingredient lookup. What's in a dish, grounded on the actual menu - not a judgment about whether it's safe for a specific allergy.
• Pre-order for pickup. Skip-the-queue ordering, with LINE Pay support where available.
• Loyalty stamp card tracking. Current stamp count and what it unlocks.
• Location and hours lookup. Via the rich menu, for chains with multiple sites.

The menu-lookup and allergy line matters enough to repeat: listing ingredients is fine; certifying a dish is safe for someone's specific allergy is not something the bot should ever imply.

A restaurant chain doesn't need approval to send a message the way it would on WhatsApp outside the 24-hour window - but push messages beyond the account's free monthly quota are billed by volume tier, and a chain tempted to broadcast a daily lunch special to its entire follower list will find that adds up quickly.

The rich menu is the more sustainable lever here, since viewing and tapping it doesn't consume the messaging quota. Putting today's specials, the reservation button and the loyalty card behind the rich menu means customers can check in on their own time, at no incremental cost, while the account's push-message budget stays reserved for things that genuinely need to be pushed - a reservation confirmation, a wait-list "your table is ready" alert.

Outside Japan, Thailand and Taiwan, none of this applies in practice - LINE has little presence with diners in most other markets, so a chain expanding into a new region elsewhere should not assume the same setup will translate.

The line is about health and safety, plus judgment calls with financial weight.

• No allergy severity judgment. The bot lists ingredients; it never tells a customer a dish is "safe" for a severe allergy. That confirmation has to come from kitchen staff who can verify the actual preparation.
• No food-quality or health-incident complaints. These need a manager, both for the response and for any required follow-up.
• No large group or private event menu negotiation. These involve custom pricing and menu decisions a flow shouldn't make.
• No food-safety incident reporting handled solely by the bot. Capture details, but route to a manager immediately - this needs a documented human response.

Get the allergy boundary right before launch - it's the single highest-stakes automation decision on this list, and worth testing deliberately rather than trusting a default script.

Four triggers should route to a person immediately:

1. Any severe allergy question. Route to kitchen or floor staff who can verify actual preparation, not the ingredient list alone.
2. Food-quality or health complaints. Escalate on sentiment and urgency, not wait for a formal complaint.
3. Two failed attempts at a reservation or pre-order. A booking flow that keeps failing needs a person to finish it.
4. A direct request for staff. Available from the rich menu at every step.

On Conferbot, the handoff moves the conversation into a shared agent inbox with the full exchange attached, so staff aren't asking the customer to repeat an allergy concern or complaint they've already described - see human handoff for how that transfer works.

1. Register a LINE Official Account per brand, even across multiple locations.
2. Build the rich menu around reservation, pre-order and loyalty - the three highest-value self-service tasks.
3. Push reservation and POS data in via webhook so availability and stamp counts are accurate in real time - neither is a native integration, so this is IT's build, not a settings toggle.
4. Set the allergy-question escalation rule explicitly and test it before launch, not after a real customer hits it.
5. Enable LINE Pay for pre-order pickup where your market and platform support it.
6. Pilot at one location for a month and track wait-time complaints before rolling out chain-wide.

Because the flow is built once and deploys everywhere, the same reservation logic can also run on the website widget for customers researching the restaurant before they're on LINE.

Track the numbers that reflect actual service, not just message volume:

• Reservation completion rate through the bot versus phone bookings still coming in.
• Pre-order pickup volume and its effect on in-store queue length.
• Loyalty stamp redemption rate, to see whether the program actually drives repeat visits.
• Escalation rate on allergy questions, tracked separately from general complaints - this one needs its own attention.

A shorter in-store queue at peak hours is often the clearest sign the pre-order and reservation flow is actually working, more than any single message metric.

Is a LINE chatbot worth it for a restaurant outside Japan or Taiwan?

Generally not. LINE's relevance is concentrated in Japan, Thailand and Taiwan, and it sees little everyday use as a dining channel elsewhere. A restaurant whose customers are mostly outside those markets will get far more engagement from a website widget or WhatsApp than from investing in a LINE Official Account.

Can a LINE bot tell a customer if a dish is safe for their allergy?

No. It can list a dish's ingredients grounded on the actual menu, but it should never confirm a dish is safe for a specific allergy - that requires kitchen staff who can verify how the dish was actually prepared, since cross-contamination risk isn't something an ingredient list captures. Route any allergy safety question to staff directly.

What is a rich menu and how does a restaurant use it?

A rich menu is a persistent, tappable visual menu fixed to the bottom of the LINE chat, letting customers reserve a table, pre-order or check loyalty stamps without typing. For a restaurant chain, it's typically the primary interface - viewing and tapping it doesn't count against the account's messaging quota, unlike a pushed broadcast message.

Can customers pay through LINE for a restaurant order?

Where LINE Pay is available - mainly in Japan, Thailand and Taiwan - customers can pre-order and pay for pickup directly in the chat, letting them skip the in-store queue entirely. Availability depends on the market and the restaurant's payment integration, so this needs to be confirmed before building a pre-order flow around it.

Does broadcasting a daily special on LINE cost extra?

Yes, once you exceed the account's free monthly quota of push messages, additional sends are billed by volume tier. A daily broadcast to the full follower list adds up quickly, which is why many chains put specials behind the rich menu instead - customers check it on their own time, at no incremental messaging cost.

What does a LINE chatbot cost for a restaurant?

Plans are $19, $39 and $59 a month, and the free tier covers 600 conversations on the website widget. LINE is not on the published plan comparison, so confirm availability with us first - the pricing page lists what each tier includes. LINE's own push-message fees beyond the free monthly quota are billed separately by volume tier, so a restaurant should budget for both the platform subscription and LINE's own charges.