An illustrative three-calendar setup
You have a personal Google calendar, Client A on Google Workspace, and Client B on Microsoft 365. Each client sees only the calendar issued by their organization. This example is a workflow you can adapt, not a reported customer outcome.
Start by deciding what each client is allowed to receive. A client calendar usually needs a Busy block for another engagement, not the other client's name, meeting notes, location, or attendees. Your personal overview may also need busy-only copies if a client's policy forbids exporting meeting details.
Send originals straight to the calendars that need them
- Personal → Client A and Client B: private busy blocks for personal commitments.
- Client A → Client B: private busy blocks for Client A's original meetings.
- Client B → Client A: private busy blocks for Client B's original meetings.
- Client A and Client B → Personal: optional copies for your own overview, with only the detail each client permits.
Don't rely on Personal as a relay between the two clients. Managed copies never become sources. Direct rules keep each original's route clear and avoid sending copied events around a loop.
For three selected calendars, the five-calendar Pro plan has room. Count calendars rather than connected email accounts, and check current plan limits before adding more clients.
Check the block from the receiving side
Use a neutral busy label. A custom label that names the other client defeats the purpose of hiding the meeting title. Check the destination calendar's sharing permissions and avoid copying into a calendar shared more widely than intended.
Busy-block presets skip all-day and declined events. Decide whether an all-day workshop, travel day, or appointment outside your usual working hours should reserve time too. Filters should reflect your availability, not just your preferred view of it.
Client administrators may need to approve access. Confirm that before relying on the setup; connecting your own account doesn't override a client's policy. The security overview explains access and data handling.
Test one pair before adding the rest
Follow the Google–Outlook guide or the multiple-Google guide. Create, move, and delete a disposable event on each source, checking the native destination calendar after each change.
When a contract ends, review every direction involving that client and use the app's rule and connection removal controls. Follow any cleanup warnings while access is still available. Revoking provider access first can prevent removal of copies on that calendar.
If your booking service already checks all the relevant calendars, a sync service may add little. Verify the scheduling path before introducing another set of copies.