A linked calendar and a conflict calendar serve different purposes. Confirm both before publishing booking availability.
Before you beginConfirm the intended CentriCRM business, your permissions and feature availability. Use controlled records while learning; obtain authorization before live changes.
Step by step
- Identify the staff member, Google account and calendar that should receive new appointments.
- Review Settings → Calendars → Connections with the authorized calendar owner. Confirm access to the intended account.
- Check the linked calendar used for CRM events and the calendars used to detect conflicts. Writer access is needed to push events.
- Arrange a controlled appointment and confirm its date, timezone, participant and appearance on the linked calendar.
- Add an approved external Busy event and inspect whether the corresponding time becomes unavailable. Free events do not necessarily block bookings.
- Check the booking page on desktop and phone. Confirm the displayed timezone and clean up controlled test appointments.
Expected result
The intended calendar receives appointments and known Busy conflicts block the expected times.
Troubleshooting
- If events do not appear externally, check linked-calendar selection and write access.
- For double bookings, inspect conflict calendars and whether the external event is Busy.
- Do not reconnect a different Google account merely because its calendar is easier to find.
Supporting documentation
These links open the provider’s documentation. Availability and permissions depend on your account.
More guides
Create and verify a contactKeep a single useful customer record, check the business context, and confirm your changes saved.
Review and respond to a conversationFind the right thread, review its history, and check the channel and recipient before responding.
Check a website lead form before launchFollow a controlled submission from the public form to the correct contact and follow-up process.
Prepare an authorized private integrationDefine the business, owner and permissions before an administrator grants a developer access.