Anu Agency
Playbook
Work with Anu
07.03 Connect booking, calendars and confirmations

07.03

Connect booking, calendars and confirmations

Make every booked appointment land on the right contact, the agent's own calendar, and the lead's phone with a confirmation and reminder.

40 minNeeds verificationChecked 2026-10-20

Video walkthrough

Coming soonBooked, synced, confirmed: the appointment chain
It will cover
  1. Who owns the appointment: the calendar the lead booked in
  2. HighLevel: connect each agent's Google Calendar, linked vs conflict calendars
  3. HighLevel notifications: booked, reminder, follow-up
  4. Follow Up Boss: calendar sync and appointment outcomes
  5. Book as the test lead and check four places
This chapter is complete without it. Every step is written out on this page.

What you're building

A booking chain where one appointment shows up in four places that agree: the lead's contact record, the booking calendar, the agent's Google or Outlook calendar, and the lead's phone (confirmation, then reminder). After the meeting, the agent marks it held or no-show so your scorecard in Part 08 can count it.

Why it matters

Most lost appointments are not lost in the conversation. They are lost when the meeting never reached the agent's personal calendar, the lead forgot, or nobody recorded whether it happened. Each of those is a connection, not a sales skill.

What you need

  • HighLevel: a calendar under Calendars, and each agent able to sign in to their own Google account
  • Follow Up Boss: each agent's Gmail or Google Workspace (or Microsoft 365) connected in their own settings
  • Your test lead's email and your own phone

Time and cost

Time
40 minutes plus 10 minutes per agent
Cost
$0 within your CRM plan

SMS confirmations use your CRM's texting, which is billed per message by your provider and requires a registered number (A2P 10DLC) in the US.

Step by step

  1. HighLevel: each agent connects their own Google Calendar

    Each agent signs in as themselves, clicks Connect beside Google Calendar, picks their Google account, and allows all requested permissions (Calendar, Profile, Email). Calendar connections belong to the individual user and cannot be shared, so you cannot connect them on an agent's behalf.

    Set the agent's main calendar as the Linked Calendar (where bookings are written) and any other calendars (family, personal) as Conflict Calendars so those hours show as busy.

    Check: An event the agent adds in Google makes that time unavailable on the HighLevel booking page within a few minutes.

  2. HighLevel: turn on booked and reminder notifications

    HighLevel has six notification types per calendar: Appointment Booked (Unconfirmed), Appointment Booked (Confirmed), Cancellation, Reschedule, Reminder, and Follow-Up. Turn on the booked notification and at least one Reminder for the Contact, and the booked notification for the Assigned User.

    Email and in-app are on this tab; SMS and WhatsApp have their own tabs with Contact, Assigned User and extra numbers as recipients.

    Check: Booking as the test lead sends you (as the contact) an email or text right away, and the agent gets the assigned-user notice.

  3. HighLevel: make no-shows count

    Agents set each appointment's status after it happens: Showed or No-show (other statuses are New, Confirmed, Cancelled and Invalid). Build a workflow with the Appointment Status trigger filtered to No-show that creates a task for the agent to rebook.

    Check: Setting the test appointment to No-show creates the rebook task on the test contact.

  4. Follow Up Boss: connect calendars and appointment outcomes

    Each agent connects Gmail or Google Workspace in their own settings. Appointments created in Follow Up Boss go to their Google Calendar, and Google events show in Follow Up Boss with a Google icon. Only the primary calendar syncs, and Focus Time, Out of Office, Tasks and Appointment slots do not.

    An account owner sets appointment types and outcomes (for example Met, No-show, Rescheduled) under Admin > Appointments. Agents set the outcome on the appointment from the lead's profile or the calendar.

    Check: An appointment created on the test lead in Follow Up Boss appears on the agent's Google Calendar.

  5. Use one booking link per purpose and put it in your follow-up

    Give each appointment type its own calendar or booking type ("Buyer consult 30 min", "Listing appointment 60 min"). Your scorecard can then count them separately. Put the link in your first follow-up message and in your email signature.

    Booking must happen with the same email or phone the lead used on the form, or you get a duplicate contact. HighLevel booking widgets can be embedded on your site with the calendar's embed code.

    Check: Booking from the follow-up link attaches the appointment to the existing test contact.

What success looks like

  • One test booking appears on the contact, the booking calendar and the agent's Google calendar, at the same time and time zone.
  • The test lead gets a confirmation immediately and a reminder at the time you set.
  • Each appointment ends with a status (HighLevel) or outcome (Follow Up Boss) the next morning at the latest.

Copyable templates

textConfirmation text (for leads who gave text consent)

Merge field names vary by CRM and version; insert them with your CRM's merge-field picker rather than typing them.

Hi {{contact.first_name}}, you're booked with {{user.first_name}} from Coastal Key Realty on {{appointment.start_date}} at {{appointment.start_time}}. Need a different time? Just reply here. Reply STOP to opt out.
textReminder text, sent the day before
Reminder: {{user.first_name}} will meet you tomorrow at {{appointment.start_time}}. If the time no longer works, reply and we'll find another. Reply STOP to opt out.

Try it

Lead bookssame email/phone as form
Booking calendarowns the appointment
Contact recordappointment + status
Agent's Google calendarlinked calendar
Confirmation + reminderconsent required for SMS
Scorecardbooked, held
  • Lead bookstoBooking calendar
  • Booking calendartoContact recordsame contact
  • Booking calendartoAgent's Google calendartwo-way sync
  • Booking calendartoConfirmation + reminder
  • Contact recordtoScorecardstatus after meeting
One booking, four places that must agree

How to test it

  1. Open your booking link in a private window and book tomorrow as Jordan Testlead.
  2. Check the contact record: one appointment, no duplicate contact.
  3. Check the agent's Google calendar: same time, same time zone.
  4. Check your phone and inbox: confirmation now, reminder at the set time.
  5. After the slot passes, set the status to No-show and confirm the rebook task appears. Then cancel and tag the contact test-lead.

Troubleshooting

HighLevel: sync stopped or shows a permissions warning.

The agent did not grant full calendar access. Go to Settings > Integrations > Google, look for the missing-permissions warning, and click Reconnect, granting every permission.

Appointment time is off by one or more hours in Google.

The calendar's time zone and the agent's profile time zone differ. Set both to the agent's actual zone, then book a fresh test.

Follow Up Boss: a Google event does not show on the lead's profile.

Appointments created outside Follow Up Boss do not appear on the lead's profile, though they still count in the appointment report. Create client appointments from the lead's profile.

The lead booked with a different email and a second contact appeared.

Merge the two contacts, then add the booking link to messages so it is pre-filled from the CRM, or ask the lead to use the same email.

Advanced technical details

Optional. You can follow every step above without these.

Technical detailsAppointment events for automation and reporting

HighLevel: the Appointment Status trigger fires on status changes (New, Confirmed, Cancelled, Showed, No-show, Invalid) and can feed an outbound Webhook action or a Google Sheets row. Appointment data is only included in an outbound webhook payload when the workflow trigger is appointment-related.

Follow Up Boss: register appointmentsCreated and appointmentsUpdated webhooks to receive changes. These fire only for appointments created in Follow Up Boss, not for events synced from Google or Office 365. The payload carries a resource URI; your receiver must GET it to read the appointment.

Sources

Written from the best available information. One or more steps could not be confirmed; see the notes in the chapter. Last checked 2026-10-20.