Book a demo: how to set up a demo flow with a calendar and one meeting link (2026)

"Book a demo" is the button on a software vendor's site that schedules a guided walkthrough of the product with a person, at a time the visitor picks. It is the opposite of a free trial: instead of the visitor exploring the product alone, someone shows them the parts that matter for their situation and answers questions as they come up.

This page is for both sides of that button. For a buyer: what booking a demo gets you, how it differs from a trial, and how to ask for one. For a team that needs the button on its own site: how to run the whole flow — scheduling, the call, the write-up — with the calendar you already use and one meeting link, and without buying a sales-development stack first. Our own Book a call page is the worked example, because it runs exactly this way.

What "book a demo" means

A demo is a scheduled, live, person-led walkthrough of a product. Three things sit behind the button:

1. A scheduler — the visitor picks a slot and it lands on someone's calendar, with a confirmation email.
2. A meeting room — where the walkthrough happens, at the booked time.
3. A write-up path — what the team keeps afterwards: who the visitor was, what they asked, what was agreed.

Vendors differ mostly in how much they put between the visitor and the slot. Some ask for a form and route it to a sales-development rep who then proposes times; some open the calendar directly. The second is shorter for the visitor and has fewer moving parts for the team — which is why the flow below uses it.

Demo vs free trial vs discovery call

A demo is not a trial: nothing is set up in your name, and you leave with notes rather than an account. It is also not a discovery call — discovery finds out what to show; the demo shows it. For simpler products the two collapse into one thirty-minute call.

How to ask for a demo

If the vendor's site has no button, or you want the demo to cover something specific, a short email does it:

Subject: Demo request — [your company], [the problem]

Hi,

We're looking at [product] for [one line: the problem]. Before a trial, I'd like a 30-minute demo focused on [the two or three things that matter]. [Names/roles] would join from our side.

Would [date option 1] or [date option 2] work? We'd want to see [specific scenario] rather than a general tour.

[Your name]

The specific scenario is the part that gets you a useful demo instead of a tour.

The demo flow, in three steps

The rest of this guide is for the team. The setup uses the calendar you already have, one meeting link, and no code.

Step 1 — A booking page in your own calendar

Google Calendar's appointment schedules produce a public booking page: the visitor picks a slot and it lands on your calendar. Google documents that a personal Google Account or a Workspace account can create one; that the schedule's description "displays: on your booking page, in confirmation emails, in event descriptions"; and that the conferencing options are "Google Meet video conferencing, in-person meeting, phone call, none / to be specified later" — with the note "to use a third-party conference service, select None / to be specified later" (checked September 2026).

Put the booking page behind the Book a demo button. Any scheduler with a description field that travels into the confirmation email will do; the recipe does not depend on Google's.

Step 2 — One reusable InterMIND link in the description

Create one ad-hoc meeting in InterMIND and copy its link — it looks like intermind.com/abc-def-ghi. Paste it into the booking page description, so it arrives in every confirmation email and calendar invite the scheduler sends.

One link serves every demo, permanently. When a session ends, the next visitor who opens the same link starts a fresh session on the same URL. Two properties make it safe to put on a public page:

• Nobody walks in. An anonymous visitor lands in a waiting room and joins only when you approve them. There is no setting that turns the approval off, and an unanswered request is denied automatically after 5 minutes.
• Nothing carries over. Ad-hoc rooms delete their chat when a session ends and keep only the latest session's recap — one visitor's demo leaves nothing for the next one to find.

Step 3 — Each side picks its own language

The visitor opens the link in a browser, types a name, picks their language and knocks; you approve and pick yours. From then on each participant hears the others in their own language, and chat messages are translated per participant. Voice and chat cover the same 23 languages: English, Russian, Spanish, French, German, Italian, Portuguese, Polish, Dutch, Czech, Hungarian, Danish, Finnish, Icelandic, Norwegian, Romanian, Swedish, Ukrainian, Japanese, Korean, Turkish, Chinese (Simplified) and Hindi.

For a demo flow this is the step that widens the funnel: a visitor from Warsaw, São Paulo or Seoul books the same slot, from the same page, and asks questions in the language they think in. The visitor installs nothing, creates no account and pays nothing — only the host's side of the room carries a plan.

What the visitor sees

From the visitor's side, the whole flow is four screens:

1. The booking page. Pick a day and a slot. Enter a name and an email.
2. The confirmation email. The time, the calendar invite, and — in the description — the meeting link.
3. The link, at the booked time. A browser page: type a name, pick a language, knock.
4. The room. Once approved: the walkthrough, in their language.

Nothing else. No account creation, no download, no "an SDR will reach out to confirm".

What your team sees

1. A calendar event at the booked time, with the visitor's name and email.
2. A knock when they arrive — approve it, pick your language.
3. The demo.
4. A recap by email when the session ends: a title, an overview, key takeaways, sectioned points with timestamps, action items, open questions and topics. If the conversation produced nothing summarizable, no email is sent.
5. The same recap on the CRM record, if the CRM's inbound address is in the meeting's Recap copy field. The visitor's address stays in the To field, which is what the CRM matches against; the CRM address is BCC'd. Up to 10 confirmed addresses can live in your address book, and each is confirmed once by a test email opened inside the CRM. Available on every plan.

One boundary to state plainly: a visitor who joined without an account receives nothing after the demo — no recap, no history. There is no delivery channel for them. Your follow-up email is what they keep, and a separate guide covers the sales follow-up email with templates.

The worked example: our own Book a call page

InterMIND's contacts page has a Book a call card. It opens a Google Calendar booking page; the description of that booking page carries one InterMIND meeting link; a visitor who books gets the link in their confirmation email, joins at the booked time in whatever language they choose, and the team gets the recap afterwards. There is no form in front of the calendar and no SDR between the visitor and the slot.

Next to it sits the other half of the answer to "book a demo": a live demo that needs no booking. Anyone can open the demo in a browser, without signing up, and hear the translation working. A visitor who wants to see the product does not have to wait for a slot; a visitor who wants to talk about their situation books one.

Where the flow stops

The setup above is deliberately small, and it is worth being precise about what it does not do:

• No routing. One booking page, one calendar, one link. Assigning demos round-robin across a team, or by territory, is a scheduler feature, not part of this recipe.
• No lead scoring or enrichment. The team learns who the visitor is from the booking form and from the call.
• No history in the room. Ad-hoc rooms are designed to leave nothing between sessions. A prospect you will meet repeatedly belongs in a channel, where every session's recap is kept.

And the plan limits that decide whether the free tier carries the flow:

The window is a rolling 30 days and the voice-minute pool belongs to the host's account, so Basic covers about four 30-minute demos a month. A team running demos weekly starts on Pro.

FAQ

What does "book a demo" mean? It is the button on a software vendor's site that schedules a live, person-led walkthrough of the product at a time the visitor picks. Behind it are a scheduler, a meeting room, and a path for the write-up afterwards. It differs from a free trial, where the visitor explores the product alone in their own account.

Is a demo a free trial? No. A demo is guided and scheduled: a person shows you the parts of the product that matter for your situation and answers questions live, and you leave with notes and a next step. A free trial is self-serve: you get your own account and explore at your own pace. Many vendors offer both, in that order.

How do I ask for a demo? Email the vendor with the problem you are trying to solve, the two or three things you want the demo to cover, who will join from your side, and two date options. Ask for a specific scenario rather than a general tour — that is what turns a demo into a useful one.

Do we need SDR software to offer "book a demo" on our site? No. A booking page in the calendar you already use, with one reusable meeting link in its description, covers scheduling, the call and the write-up. Routing across a team, lead scoring and enrichment are separate tools, and a small team can add them later if the volume justifies it.

Does the visitor need an account or an app to join the demo? No. They open the link from the confirmation email in a browser, type a name, pick a language and knock. Nothing to install, no account to create, nothing to pay — the host's plan covers the room. A visitor who joins without an account does not receive the recap afterwards; the follow-up email is their record.

Is it safe to put a permanent meeting link on a public booking page? Yes, because the link is not the door. Anyone arriving anonymously waits for the host's approval, no configuration turns that approval off, and an unanswered request expires after 5 minutes. Ad-hoc rooms also delete their chat when a session ends, so nothing from one demo is visible in the next.

Can we run demos for visitors who speak a different language? Yes, from the same page and the same link. The visitor picks their language when they join and you pick yours; each side hears the other in their own language across 23 languages, and chat is translated per participant. Nothing about the booking flow changes.

Try it

• How to schedule a meeting from Google Calendar or Outlook — the calendar half of New meeting, the permanent link, the recurrence.
• Book a call with us — see the flow from the visitor's side, end to end.
• Try the live demo — the no-booking half: hear the translation now, without signing up.
• Start a meeting and copy its link — the link you would paste into your own booking page.

Sources: Google Calendar Help, Create an appointment schedule — account eligibility, where the description displays, and the conferencing options including "None / to be specified later" for third-party services. checked September 2026.