Choose the right calendar type
Solo, service, group, round-robin, or collective.
Purpose
When to Use This SOP
- Creating a new booking link
- Rebuilding a messy appointment setup
- Deciding between solo, service, group, round-robin, or collective calendars
- Adding a new team member who takes appointments
- Setting up sales calls, consultations, demos, service visits, classes, or events
- Calendar bookings are not updating pipelines correctly
- Appointment reminders are going to the wrong people
- The team is experiencing double bookings
Before You Start
- Do not create the calendar first. Start by defining the appointment flow.
You should know:
- What the appointment is for
- Who owns the appointment
- Whether one person or multiple people need to attend
- Whether multiple attendees can book the same time slot
- How long the appointment should be
- What availability is realistic
- What reminders should be sent
- What pipeline stage should change
- What workflow should start or stop
Step-by-Step Procedure
- 1Define the appointment purpose
Write one clear sentence that explains the appointment.
Examples:
- This is a 30-minute consultation for new leads.
- This is a 60-minute onboarding call for new clients.
- This is a group training session with multiple attendees.
- This is a sales demo that requires both a rep and a technical resource.
- This is a service appointment assigned to the next available team member.
If the purpose is vague, the calendar setup will be vague too.
- 2Choose a solo or personal calendar when one person owns the appointment
Use a solo or personal calendar when:
- One person takes the appointment
- The appointment type is simple
- Availability depends on one calendar
- The booking should always go to the same person
Examples:
- Founder consultation call
- One-on-one coaching call
- Individual sales call
- Personal onboarding session
Do not use a solo calendar if bookings should rotate across a team.
- 3Choose a service calendar when the appointment is tied to a specific service
Use a service calendar when:
- Different services need different durations
- Different services need different intake fields
- Different services have different availability
- The appointment type affects follow-up
Examples:
- Website consultation
- CRM setup call
- Support session
- Estimate appointment
- Installation visit
A service calendar helps keep each appointment type connected to the correct form, reminders, pipeline, and workflow.
- 4Choose a group or class calendar when multiple people can book the same time
Use a group or class calendar when:
- More than one attendee can book the same time slot
- The appointment is an event, class, webinar, or training
- Capacity matters
- The same reminder sequence goes to multiple registrants
Examples:
- Webinar
- Group demo
- Training session
- Workshop
- Class or cohort event
Do not use a group calendar for private one-on-one calls.
- 5Choose a round-robin calendar when appointments should rotate across team members
Use a round-robin calendar when:
- Multiple team members can take the same appointment type
- Inbound leads should be distributed
- The team wants fair assignment
- The appointment does not require a specific person
Examples:
- Sales team consultation calls
- Intake calls
- Support callbacks
- Demo bookings
Confirm all assigned users have realistic availability and external calendars connected.
- 6Choose a collective calendar when multiple internal people must attend
Use a collective calendar when:
- More than one team member must be available for the same appointment
- A sales rep and specialist both need to attend
- A demo requires multiple roles
- Internal coordination matters more than rotation
Examples:
- Sales plus technical demo
- Client kickoff with account manager and strategist
- Complex consultation
- Implementation planning call
Collective calendars can reduce scheduling confusion, but only if every required attendee keeps availability accurate.
- 7Set realistic availability
Do not set availability based on what looks good on a booking page.
Set availability based on what the team can actually support.
Review:
- Working hours
- Lunch breaks
- Prep time
- Follow-up time
- Time zone
- Team capacity
- Internal meetings
- Travel time, if relevant
- Maximum number of bookings per day
A calendar that looks wide open may create a workload the team cannot handle.
- 8Add buffers and minimum notice
Add buffer time before and after appointments.
Buffers protect time for:
- Preparing for the call
- Reviewing the contact record
- Writing notes
- Moving the pipeline stage
- Sending follow-up
- Taking a break between calls
Set minimum notice so someone cannot book too close to the appointment time.
For example, a same-day appointment may be fine for some businesses but chaotic for others.
- 9Connect external calendars where needed
If users already use an external calendar, connect it where appropriate.
External calendar sync can help prevent double bookings.
Confirm:
- The correct external calendar is connected
- Busy events block availability
- The user understands which calendar controls availability
- Test bookings do not create conflicts
- The CRM appointment appears where the team expects it
Do not assume sync is working until it has been tested.
- 10Define the booking form fields
Only ask for information needed before the appointment.
Common fields:
- Name
- Phone
- Business name, if relevant
- Appointment interest
- One qualifying question
- Notes or context, if useful
- Consent language, if SMS or marketing follow-up may happen
Avoid long booking forms unless the appointment truly requires more information.
- 11Connect the calendar to pipeline and workflow logic
A booking should not live alone.
Decide:
- Should a new opportunity be created?
- Should an existing opportunity move to Appointment Booked?
- Should a tag be applied?
- Should a field be updated?
- Should a reminder workflow start?
- Should a pre-booking nurture stop?
- Should the team receive an internal notification?
The calendar is part of the operating system, not a separate tool.
- 12Test the booking flow end to end
Create a test booking as if you were a real visitor.
Confirm:
- The booking page loads
- Availability is correct
- Form fields work
- Confirmation appears
- Confirmation email sends
- SMS reminder sends if planned and consent exists
- External calendar receives the booking
- Opportunity is created or updated
- Pipeline stage changes correctly
- Workflow starts or stops correctly
- Internal notification reaches the right person
Do not publish the calendar until the full path works.
Checks Before You Finish
- ✓The appointment purpose is clear
- ✓The correct calendar type is selected
- ✓Appointment owner or assignment logic is defined
- ✓Availability is realistic
- ✓Buffers are configured
- ✓Minimum notice is configured
- ✓External calendars are connected where needed
- ✓Booking form fields are short and useful
- ✓Reminder plan is defined
- ✓Pipeline stage connection is defined
- ✓Workflow connection is defined
- ✓Test booking was completed end to end
- ✓Visitor and team experiences were both checked
Common Mistakes
- Treating the calendar as just a booking link
- Using a solo calendar when the team needs round-robin
- Using group booking for private calls
- Forgetting buffers
- Letting people book too close to the current time
- Not connecting external calendars
- Asking too many questions on the booking form
- Forgetting to stop pre-booking follow-up after someone books
- Not testing reschedule, cancellation, or no-show paths
- Publishing before confirming pipeline and workflow behavior