---
title: "Free demo scheduling for individual sales reps"
url: https://meet.barq.dev/for/sales-teams
updated: 2026-11-17
author: "Hammad Ali"
---

# Free demo scheduling for individual sales reps

> **Short answer:** Barq Meet gives individual sales reps free Google Calendar demo links after your team assigns the prospect's owner. Use a 30-minute demo with preparation questions, buffers and email reminders. The booking page won't route leads, rotate meetings among reps or check a specialist's availability alongside the account executive's calendar.


## Where should an assigned rep's demo link enter the sales process?

Send the assigned rep's link once your team has decided who owns the prospect. It works in that rep's reply or follow-up message; an unassigned inbound lead needs an ownership decision before an individual booking page can point to the right person.


Assign, then invite. We collect the prospect's answers for the meeting, but those answers don't choose a rep, score a lead or move the reservation to a different calendar.


For example, a rep handling an existing account can send their demo link after agreeing the topic by email. A generic website inquiry that needs territory routing is a different requirement, and our individual pages don't supply that routing. The [customer-success setup](https://meet.barq.dev/for/customer-success) distinguishes onboarding from an account review with a different preparation requirement.


Name the host beside the link and in the event description. The prospect should know whom they're meeting before committing time, instead of discovering the owner from the final calendar invitation.


## What should a demo booking ask the prospect?

Ask for the information that changes the demo, such as the task the prospect wants to see and their company website. Keep qualification in your sales process, and use separate events when a technical discussion needs longer than a first demonstration. The [sales demo agenda](https://meet.barq.dev/templates/sales-demo-agenda) starts with the prospect's problem and preserves time for the next decision.


Keep it answerable. These are our suggested starting settings for an individual rep, with buffers expressed as before/after minutes and no promise about sales outcomes or conversion rates.


| Sales conversation | Preparation question | Duration | Buffer before/after | Notice | Link format |
| --- | --- | --- | --- | --- | --- |
| First demo | Which task should we demonstrate? | 30 min | 10 / 10 min | 24 hours | Rep's public event |
| Technical discussion | Which integration needs discussion? | 45 min | 15 / 15 min | 48 hours | Secret event, approval on |
| Follow-up | What remains to decide? | 20 min | 0 / 10 min | 12 hours | Direct event |

We allow these events to use different notice and availability settings. A prospect can therefore reserve a short follow-up without accidentally gaining access to the longer technical-discussion window you share only after agreeing the scope.


In the first-demo example, a call starting at 14:00 finishes at 14:30, but its full interval runs from 13:50 to 14:40. That's 50 minutes including preparation and notes, so a neighboring calendar event can remove an apparently open half-hour.


## How does a rep publish and test a demo booking page?

Create the first-demo event around the rep's own calendar and test the complete reservation before sharing it with prospects. Set the question and location first, then check that the reminder helps the prospect prepare for the demonstration they requested.


One test is enough to start. It should use the same event length, buffers and calendar selections that a real prospect will encounter, instead of a temporary event with easier settings.


1. Connect the rep's Google calendars and pick the writable calendar where demo bookings belong.
2. On the Events page, select Availability beside + Create, then reserve demo hours around prospecting and other commitments, using the rep's working time zone.
3. Add a 30-minute first-demo event, select that schedule under "When people can book", and enter ten-minute buffers on both sides.
4. Set "Minimum notice" to 24 hours, add the demonstration question, and choose Google Meet or the agreed location.
5. Configure the email reminder, book the event yourself, and verify the invitation before putting the URL into prospect replies.


Follow [the individual rep's Google booking setup](https://meet.barq.dev/guides/free-booking-link-google-calendar) and [the demo reminder instructions](https://meet.barq.dev/guides/send-meeting-reminders-free). For exceptional requests, "Requires approval" under "Booking page" lets you decide whether the proposed meeting should proceed; it doesn't assign another rep.


## Will demo bookings appear automatically in our CRM?

We don't provide a built-in CRM connector; a booking link pasted into a CRM message remains a link. Use the API and webhooks for a developer-built connection if your team needs booking activity written into another system, and define the updates it should handle.


Keep ownership in the CRM. We can record the booking's source and UTM information in [Insights](https://meet.barq.dev/features/insights), but that describes reservations instead of qualification or revenue. The [agency appointment setup](https://meet.barq.dev/for/agencies) keeps account-manager ownership clear when clients have several project contacts.


For a labeled example, append `?utm_source=outbound` to a rep's demo URL when using it in an outbound message. If the URL already has query parameters, append `&utm_source=outbound` instead; use a different source for another distribution channel so you can distinguish the resulting bookings.


When `utm_source` is absent, source aggregation falls back to `direct`. That label isn't proof that the prospect typed the URL, so don't turn it into a claim about where the buyer first heard of you.


The [API and webhook guide](https://meet.barq.dev/features/api-and-webhooks) explains the integration route. Choose the booking events your CRM should record and test changes as well as initial reservations before depending on a custom connection.


## Can the account executive bring a specialist to the same demo?

The rep can include an extra guest when that option is enabled, but the booking doesn't check the specialist's calendar for shared availability. Agree the specialist's attendance before offering times, or use collective scheduling when both people must be available for every appointment.


An invitation isn't a check. The same distinction applies when a colleague joins for one technical discussion, even if several Google calendars already block the rep's own booking page.


We include demo pages, questions and reminders without a paid tier; generous fair-use controls are there to stop abuse. Review [the rep account's included features](https://meet.barq.dev/pricing), then [create the assigned rep's demo link](https://meet.barq.dev/app/sign-in) when the owner and attendee arrangements are clear.

## Frequently asked questions

### Can a follow-up use a shorter booking page?

Yes. Give follow-ups their own event, duration and question so prospects reserve the next conversation you intended. A direct follow-up URL also avoids sending an existing prospect back through the first-demo description and preparation form. Keep a shorter follow-up offer when its preparation differs, with the assigned rep and intended next decision named in its description.

### Can I review an unusually long technical request first?

Yes. Enable Requires approval under Booking page for the technical-discussion event, and choose an approval timeout you can meet. Pending requests hold time until a decision or expiry, so tell the prospect to wait for confirmation before planning attendance. Use request approval for the unusual session and explain that the prospect should wait for acceptance before treating the time as confirmed.

### What if the rep has work commitments in two Google accounts?

Connect both accounts and select the calendars that should block demos. Choose the booking destination independently, so a commitment on the second account removes a conflicting time while the confirmed demo still lands on the rep's intended work calendar. Select each rep calendar that must block time and test conflicts from both accounts before publishing the replacement sales appointment link.

## Related pages

- [Booking insights: sources, attendance and record exports](https://meet.barq.dev/features/insights)
- [Booking API and webhooks for your own application](https://meet.barq.dev/features/api-and-webhooks)
- [How to create a free booking link for Google Calendar](https://meet.barq.dev/guides/free-booking-link-google-calendar)
- [How to send meeting reminders for free](https://meet.barq.dev/guides/send-meeting-reminders-free)
- [Free scheduling for agencies](https://meet.barq.dev/for/agencies)
- [Sales demo agenda template](https://meet.barq.dev/templates/sales-demo-agenda)

[Create your free booking link](https://meet.barq.dev/app/sign-in)
