Turn a booking into a returning guest.

Anything with a calendar and limited capacity: restaurants & cafés (tables and seats), salons & barbers (appointments, chairs, specialists), beauty & wellness (rooms and practitioners), studios & classes (class spots and instructors), clinics & practices (appointments).

Different capacity, same guest journey: book, visit, remember, return.

One honest limit: G-Guest books within a day — slots, appointments, seats, class spots. Multi-night stays are not something it models today, so we don't sell it for that.

Three jobs that look alike from the outside and are not.

A form takes a request. Somebody still has to read it, check the book and write back, and that somebody is you, usually at eleven at night. Until you reply, the customer has nothing but hope.

A widget takes a booking and keeps it. The booking tools bolted onto site builders do confirm a slot, but your guest list lives in their system, and to software your booking page is just a picture. You are renting the tool and lending them your customers.

G-Guest is your own booking system, on your own site. Somebody picks a real slot and is confirmed on the spot. A taken slot can't be booked twice. Reminders go out by themselves. A cancellation goes to the waitlist instead of vanishing. Every visit — not every booking — grows a guest history that is yours, exportable any time.

And one thing none of the others do: it is open to software, not just to people with a mouse. An assistant can read your real availability and create a confirmed booking without ever touching the form. In our latest research on Amsterdam restaurants, not one of the 200 we tested published a booking interface an assistant could call.

Two things, both automatic.

The spot goes back on sale. If anyone joined the waitlist for that day, G-Guest works the queue — oldest request first, one person per opening, so a single freed spot doesn't summon six people to race for it. We don't hold the spot: it goes to whoever books first, and the message says so plainly.

The cancellation is not counted as a visit. They don't become a returning guest, and no post-visit follow-up is sent to somebody who never came.

Visits. A booking three weeks from now doesn't make somebody a regular, and a cancellation certainly doesn't.

G-Guest keeps them apart: future bookings, cancellations and no-shows on one side, real visits on the other — and it distinguishes a confirmed visit from a presumed one. Guest status (new → returning → regular) is built from the visits, so what you see is what happened.

Names, contacts, visit counts and notes are all yours, exportable in one click.

No — and this is deliberate.

Only with consent. Return messages go only to people who ticked the box, and only after a visit that actually happened. One unsubscribe ends it for good.

And there is a silence rule. Before any marketing message, G-Guest checks when that person last heard from you. If it was recent, the message doesn't go. Sometimes the right message is no message.

Confirmations and reminders are operational, not marketing — those always go through.

After a visit, G-Guest asks for the thing that makes a review useful: what the person experienced, and why they came. "Quiet enough to work in on a Tuesday" answers a question that "great place!" never will — for a human reading it, and for an assistant recommending you.

Requests rotate across the destinations you choose instead of pushing every single customer to one platform. You set the list; the rotation is automatic.

A day or two. Tell us your hours, days off and anything to block (holidays, private events) — one message is enough. We build your booking page and your capacity — tables, chairs, rooms, class spots — run a test booking, and you're live. Nothing for you to install.

The moment somebody books, you get the confirmation instantly — by email, by Telegram, or both at once. You pick; change it anytime.

It's built for a real team, not one login shared around:

• Booking alerts reach the phones that run the shift — owner, floor, front desk, as many as you need
• Staff get their own link to run the day — see today's bookings, seat, move or add somebody — without touching your settings or exporting your guest base
• The owner sees everything: the full guest base, settings, hours, reports, export
• Everyone works off one live view, so the floor and the phone never double-book the same slot

Honest answer: they're different tools. A marketplace is a demand channel — its app puts you in front of people who don't know you, and it charges for that: a monthly fee plus a cut of every booking, including the regulars who were already yours.

G-Guest is not a marketplace. It's your own booking system, on your own site:

• It converts the traffic you already own — Google, social, AI answers, regulars — at €49/mo flat, no per-booking fees, ever
• Your customers stay yours — names, visits and contacts belong to you, not to a platform
• AI-bookable — assistants book you directly through your site

If the marketplace genuinely brings you new customers, keep it — some places run both. What many discover is that most of their bookings were coming from their own name all along.

Yes — that's the point. G-Guest publishes live availability in a way assistants can read, so an AI acting for a customer picks a real slot and completes a confirmed booking end to end. As more people ask an assistant where to go and let it book, you're already the business it can act on.

Yours, always — export it anytime, no questions.

If you cancel: the live booking flow stops, but your data is preserved, nothing is deleted. Come back and it switches on again the same day. We keep clients with a system that works, not with locked doors.