Telegram Deep Linking in the restaurant business.

A table QR is not “just a PDF menu.” With a deep link like t.me/bot?start=table_12, the bot already knows the context: which table, which room, which offer. Offline venue and digital service meet in one tap.

Below are working scenarios for restaurants, cafés, and takeaway.

How the link works

Basic pattern:

https://t.me/your_restaurant_bot?start=table_5

The guest opens it, taps Start — the bot receives /start table_5. Keep the payload short and stable (table id, zone, campaign). Feature overview: useful Telegram bot features.

Menu and order from the table

Each table gets its own QR. After Start, the bot opens the menu (buttons or Mini App) already bound to that table. The kitchen ticket includes the table number; calling a waiter is optional.

Floor benefits: less bar queue, faster table turns, clear analytics on which tables order most. Café flows: café bot post.

Table booking with a seating QR

From the website or ads: ?start=book_terrace. The bot shows open slots, collects party size and phone, and confirms the reservation.

On the visit day, send a reminder plus a seating QR — host scans it or the guest opens the bot at the door. Fewer no-shows and name mix-ups.

Takeaway and delivery: separate entries

• start=pickup — takeaway menu and pickup time;
• start=delivery_zone_north — zone and minimum order checks;
• start=promo_lunch — lunch set without extra questions.

One bot covers dine-in, takeaway, and delivery; marketing sees which channel drove the order. Delivery automation: food delivery bot.

Payment and the check without friction

After dishes are selected, the bot can take payment in Telegram or send an invoice. For dine-in, split checks or add “one more pizza to table 5” via the same deep link.

Kitchen and cashier share one order id. Guests see “preparing / served” — fewer waiter interruptions.

Checklist before you print QRs

1. Every table has a unique, stable payload.
2. The link opens on a phone without a website login.
3. After Start, the guest sees menu or booking in under 10 seconds — not “write to us.”
4. Fallback exists: “Call waiter / manager.”
5. Admin view shows order with table number and kitchen status.

Do not put long text or personal data in the QR. Payload is a short key; details live on your server.

Need a bot with table QRs, booking, and takeaway? Get an estimate at botservice.biz.