Each rep's own calendar

With Each rep's own calendar as the playbook's calendar, every tour is booked on the calendar of the rep who gives it. Each rep connects their own Google or Microsoft 365 calendar once, under Personal settings → Calendar, and the assistant only offers times they are free. Your CRM stays the CRM.

Info

A rep who connects a calendar in Personal settings → Calendar has their tours booked on it whatever calendar the playbook uses: on a WelcomeHome or shared Google calendar playbook too. The playbook's calendar only books the reps who have not connected one. Each rep's own calendar as the playbook's calendar means reps who have not connected one are not offered at all.

Set it up#

Invite your reps
On Settings → Team, invite each rep. Choose the Sales rep role for people who only give tours: they see their own tours, tasks and booking pages, and their own calendar and hours, and nothing else. Anyone with another role can connect their calendar too.
Link each rep's login on the staff list
On each community's Staff section, choose each rep's Login in their entry, from the people on your Team, and leave Gives tours on. The entry then shows whether they have connected a calendar, and Hours opens their hours (to change as an owner or admin, to read as a group manager). It warns when an entry is not linked to a login, and when a deactivated login still has tours to come. The Contact email is only for reaching them.
Have each rep connect
Each rep signs in and connects their calendar under Personal settings → Calendar (the account menu, top right).
Add the connection
On Connections, under Add a connection, add Each rep's own calendar. There is nothing to paste: each rep has signed in for themselves.
Use it in a playbook
In the playbook editor, on Integrations, choose it as the calendar. A community that keeps a shared calendar can still use Google Calendar or Microsoft 365 Calendar through a community customization.

Who is offered#

Your booking rules decide who can take a tour: a named person, a job title, round robin, or anyone at the community. Of those, the assistant offers only reps who:

have a staff entry linked to their login, with Gives tours on,
have connected a calendar that works, and
have an AnswerStack login that is active.

A rep missing any of these is not offered. If nobody is left, the assistant takes a callback request instead of guessing, and the call is marked for follow-up. Check each community's staff list before you switch a playbook over.

What happens on a booking#

The event is created on the rep's own calendar with them as the organizer, and the booking notes in the description. The caller is not invited unless you turn on Send the caller a calendar invitation on the connection; then the notes are left off, because every invited person can read the description. Your own confirmation email or text goes to the caller either way.

Limits#

A CRM is still needed. Every booking belongs to a contact in your CRM.
One calendar per rep, their main one.
No attended rate from the calendar. Neither Google nor Microsoft records whether someone attended.