Skip to content

Guests book on your site. You cook.

Glyde is the restaurant AI agent with full implementation. A web agent answers hours, menu, and tables on your website. A phone agent takes the call when nobody picks up. Bookings land in your inbox — not on TheFork, not in a DM thread.

Book on your website Web + phone agent Live in one week

Site bookings

38

+12

Questions answered

214

24/7

Overflow calls

17

covered

Bookings by hour

Website · chat · phone overflow

Peak 19:00
11am2pm5pm8pm11pm

Owner inbox

Live
  • Web · Site

    Tisch für 2 um 19:30 — booked

    Booked
  • Chat · Widget

    Are you open Sunday?

    Answered
  • Phone · Line

    Missed call → overflow agent

    Covered

Glyde agent

Line rang out. Overflow took name, party of 4, 20:00. Ping is in your inbox.

Built on a live diner group. Copied to the next kitchen.

Kullman's WürzburgKaiserslauternLintheLudwigsburgRegensburgKiln CafeCafesPizza countersBakeriesOne kitchen at a time
Dining room ready for service
Guests at a table booked on the site
Plate leaving the pass
Web agent and booking on a laptop
Phone overflow when the line rings out

0

Kullman's houses on one sheet

0

ways to book: site, chat, phone

0 days

typical implementation

0%

commission on a table

The product

Website bookings. A web agent. A phone agent. We install it.

Stop sending guests to a marketplace or a WhatsApp thread. Glyde is the restaurant AI agent — chat on the site, overflow on the line, tables in your inbox.

Book on your website

Guests pick a house, a slot, and a name on your page. You get a ping. No TheFork cut. No bio-link maze.

12:00Open
12:30Open
18:00Open
19:00Open
19:30Booked
20:00Booked
20:30Open
21:00Open

Web agent on the page

Hours, menu, address, delivery, book — from your sheet. Answers in German or English. Never invents a dish.

Open now?

Yes — door until 24:00

Table for 2 at 19:30?

Slot held. Name?

Gluten-free burger?

On the sheet. €14,90

Phone overflow agent

Their phones ring first. If nobody picks up, Glyde answers, books the table, and stamps the caller number.

Restaurant line · 4 rings · no answer

Forwarded to Glyde. Agent spoke German, took Eva · 2 · 20:00, wrote the ping.

Caller ID savedNo recording

Hours that stay true

One Closed-today switch beats a stale Google hour. Kitchen cutoff is per house, from the same playbook.

Door 11:00–24:00
Kitchen to 23:00
Closed today: off

Full implementation

We load the sheet, wire chat and booking, set the overflow forward, and train the owner. Week one, not a deck.

Day 1–2

Sheet

Day 2–3

Agent

Day 3–4

Site book

Day 4–5

Overflow

How it works

Four jobs. One agent. Installed.

Book on the website. Answer on the page. Cover the missed call. We load your sheet and go live.

glyde · website booking
Guests at a table they booked on the restaurant site

Book a table

  • WürzburgTonight
  • 2 guests19:30
  • NameEva
Confirm request

A table on your domain. Not a marketplace.

Party size, slot, name, phone. The ping hits the owner inbox. We never hold a deposit on our card.

  • Slots from your sheet
  • House picker for groups
  • Same booking as the chat agent
Why kitchens switch

Built for the way restaurants actually get booked.

Not a POS with a chatbot bolted on. Glyde answers, books, and covers the missed call — and we install it.

Guest booking a table on the restaurant website

0%

commission on a table

Guests book on your website.

QR on the table, widget on the page, same slots the agent uses. The reservation is yours. No marketplace owning the guest.

  • Book widget on your domain
  • Same inbox as chat and phone
  • No third-party book
A guest calling the restaurant

4 rings

then the agent answers

The phone still rings the kitchen first.

Staff picks up, nothing changes. If they are in the pass, Glyde takes overflow: hours, menu, table, caller number. Their published +49 stays put.

  • Forward on no-answer only
  • Spoken German, AI disclosed
  • Ping with caller ID
Kitchen plating during a booked service

7 days

to a live kitchen

Full implementation. Not a login and a PDF.

We type the sheet, train the agent, put booking on the site, and sit with their phone forward. Week one is a real inbox.

  • Playbook from what they already have
  • Owner Closed-today drill
  • Live kitchen you can call and chat
What operators ask for

Bookings, answers, overflow. Then we install it.

The live kitchen is Kullman's. The product is the same agent on your site and your missed calls.

Guests book on our site now. The chat answers Sunday hours while we are in the pass. When the line rings out, the overflow still takes the table. That is the product — not another dashboard.

Floor lead

Live kitchen on Glyde · Würzburg

Site

direct book

Line

overflow covered

We did not want TheFork owning the guest. Slot on the website, ping in the inbox. Same agent as the chat.

Owner

Independent diner

Closed today is one switch. Google can stay wrong. The agent is not.

GM

Full-service, one location

Phone overflow was the sale. Staff still answers when they can. Glyde only takes the miss.

Host stand

Friday service

Implementation was the sheet we already had. They did not ask us to redesign the food.

Chef-owner

Café / bakery

German first, English if they type English. No invented dishes. That is the only bot I will put on the door.

Operator

Pizza counter

Try the live kitchen before you buy. If the answers are wrong, we do not go live.

Group ops

Multi-house

Simple pricing

Setup, then a small monthly. No commission on a table.

Playbook numbers, not a SaaS grid. Half when we start. Rest when a real booking fires. Extra house or language is another line.

Replies

Web agent on one kitchen

150–400

20–60 / mo after

  • Web agent: hours, menu, address, book
  • QR on the door
  • Sheet you already have
  • German or English
  • Two rounds of answer edits
Recommended

Host

Book on the site + Closed today

400–700

40–80 / mo after

  • Everything in Replies
  • Book a table on your website
  • Owner inbox pings
  • Closed-today switch the agent reads
  • Live kitchen this week
  • Full implementation, one location

Overflow

Phone agent when nobody picks up

Custom

on top / mo after

  • Everything in Host
  • Call overflow on your existing +49
  • Spoken German, caller ID on the booking
  • EU hop + voice, no number port
  • On-site or remote phone-forward setup
  • Multi-house playbooks

We do not take guest deposits. Overflow voice is priced after the web agent is live. Questions →

FAQ

Questions? Good.

Ask the live kitchen or send a setup request. Real humans, not a ticket bot.

A web agent on your site that answers hours, menu, and booking from your sheet. A book-a-table flow on your domain. Owner inbox. Closed-today. If you want overflow, we set forward-on-no-answer from your existing phone to the voice agent. That is full implementation — not a login.

Full implementation

Name a kitchen. We put the agent on it.

Book on your website. Web agent on the page. Phone agent when the line rings out. Tell us the kitchen that already gets DMs.

  • Web agent + book on your site
  • Phone overflow if you want it
  • We install it on your sheet this week

Get a setup this week

No credit card. Name the kitchen.

We use this to start the first script. No spam.