---
title: "Free scheduling for virtual assistants managing clients"
url: https://meet.barq.dev/for/virtual-assistants
updated: 2026-11-17
author: "Hammad Ali"
---

# Free scheduling for virtual assistants managing clients

> **Short answer:** Scheduling for virtual assistants managing clients starts with a separate, client-owned host account for each person being booked. Barq Meet can check several Google calendars for one host and offer 30-minute client appointments. Those calendar connections don't establish delegated assistant access or turn one account into independent client booking identities.


## Whose account should own a client's booking link?

The client who attends the meetings should own the host account and booking identity. An assistant can prepare the proposed schedule and page copy, but access to the account needs an agreed, supported method before any management work begins. Don't assume a delegated assistant role exists.


Establish ownership first. A virtual assistants booking page for your own discovery calls is a different page from the booking link you help a client prepare for their customers.


We allow several Google accounts and calendars to inform one host's availability. Connecting them doesn't create several hosts, assign a different sender identity to each client or grant the assistant a separate administrative role.


The [individual-host feature inventory](https://meet.barq.dev/features) is the starting checklist for a client handover. If you need a portfolio dashboard with independent client permissions, confirm that requirement before choosing a scheduling product.


## What should I collect from the client before setup?

Ask the client to approve their meeting purposes, offered hours, conflict calendars and intended booking destination. Treat these as operational decisions that determine what guests can book, not cosmetic preferences to fill in after the page is live. Record the agreed settings for handover.


Keep the proposal concrete. The suggested starting settings below give the client something they can change before you prepare their booking page.


| Client appointment | Minutes | Buffer before / after | Notice | Intake prompt | Link choice |
| --- | --- | --- | --- | --- | --- |
| New customer introduction | 30 | 5 / 10 minutes | 24 hours | What should we discuss? | Public event link |
| Existing customer review | 45 | 5 / 15 minutes | 48 hours | Which decision needs the client's input? | Direct event link |
| Brief follow-up | 15 | 0 / 5 minutes | 24 hours | Which earlier call is this about? | One-off link |

Suppose a client offers 14:00 to 16:00 for introductions with no before buffer and ten minutes afterwards. Three 30-minute meetings occupy 120 minutes, starting at 14:00, 14:40 and 15:20, if the options are prepared on a compatible start-time grid.


Check the grid. The example uses a ten-minute step, and the last notes buffer ends at 16:00; a different step or an existing calendar conflict can change the offered starts.


## How can I prepare the page without assuming delegated access?

Prepare the configuration for the client to apply in their account, or work through the client's approved access arrangement once it has been established. Have the client apply the settings. This recipe doesn't grant access or prescribe sharing a Google password.


1. Let the host select conflict calendars.
2. Agree the destination calendar for new bookings and the location for each event.
3. Create the event with its description, duration and chosen "Schedule" under "When people can book".
4. In "Advanced", set the approved buffers, "Minimum notice" and "Start-time steps".
5. Before the URL reaches customers, have the client inspect the guest page and confirmation together, then agree where you are authorised to distribute their link.


We read scheduling fields from existing events: start and end, busy/free, status, event type and the host's own response. We don't read their titles, descriptions, locations or other attendees.


Google's consent screen still asks for broader calendar access because creating booking events requires it. Explain that distinction to the client; a privacy statement about what we read shouldn't be presented as the wording Google will show.


## Who receives replies to the client's appointment emails?

Replies go to the host through the email's Reply-To setting, while Barq Meet sends the appointment message. If the assistant needs to help handle replies, the client must arrange that access through their own communication setup. The booking link doesn't create a shared support inbox.


Review one real test message. We provide editable email content, so the client can approve the tone and instructions before the link reaches customers.


For multiple clients, keep a separate handover note for each host. Record which calendar receives bookings and which URL belongs in their messages, so a copied link doesn't send customers to the wrong person.


## Where should I place the approved client booking link?

Place the link in the channels the client has approved, with an anchor that names the meeting purpose. Test the pasted destination. A correct-looking button can still point at someone else's page when you've copied a previous client's message without changing the destination behind the appointment text. For the invitation itself, adapt the [meeting confirmation email templates](https://meet.barq.dev/templates/meeting-confirmation-email) to the purpose and preparation of this appointment.


The [guide to booking-link placement](https://meet.barq.dev/guides/where-to-share-your-booking-link) helps plan distribution. The [two-way calendar-sync definition](https://meet.barq.dev/glossary/two-way-calendar-sync) helps explain what the calendar connection does without promising general calendar mirroring.


For a virtual assistants scheduling app handling your own calls, use your own host account. Check [individual account pricing and features](https://meet.barq.dev/pricing), then [prepare your host booking page](https://meet.barq.dev/app/sign-in) with account ownership agreed.

## Frequently asked questions

### Can I connect every client calendar to my own host account?

Several Google calendar connections still belong to one host's scheduling setup. They don't create independent client identities. Have each client own their host account and agree who manages it through an access method your organization approves. Keep each client's host identity and calendar access under that client's agreed arrangement, so new invitations don't appear to come from you personally.

### Will guests know which client they are booking?

Make the host name, event description and location explicit before sharing the page. Review the guest experience with the client so the invitation identifies the person attending, instead of relying on an assistant's internal notes. Inspect the public profile and sample confirmation for each client before distributing the link, especially when preparing several similar appointment offers.

### Can I hand the link back when my contract ends?

A client-owned account makes the operational handover clearer because their appointments and booking identity already belong with them. Document the schedules and communication settings you've agreed, then follow the client's process for ending access. Leave the client a note covering active offers and calendar selections, with credential access reviewed through their normal handover process.

## Related pages

- [Scheduling features](https://meet.barq.dev/features)
- [Free scheduling, with every feature included](https://meet.barq.dev/pricing)
- [Where to share your booking link: 25 places that work](https://meet.barq.dev/guides/where-to-share-your-booking-link)
- [What is two-way calendar sync?](https://meet.barq.dev/glossary/two-way-calendar-sync)
- [Meeting confirmation email templates](https://meet.barq.dev/templates/meeting-confirmation-email)

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