Why the Client Scheduler Shows a Consultant as Free Over Personal Holds

The client opens Outlook Scheduling Assistant or Google Find a time. They see empty white space across your schedule. They enter your assigned client email address to locate an open slot. The tool checks your client mailbox and finds zero appointments during that one hour. To your client, you look unoccupied and ready to talk.

Your client clicks the open space and sends a calendar invite. They do not know about your existing commitment on another calendar. They followed company protocol by using their internal calendar picker. You decline the invite later, which creates immediate friction.

The client scheduler only reads records stored inside the client Microsoft 365 tenant directory. You might manage your workday on an external Google Workspace account. Your client account sits empty until someone schedules an internal meeting. The scheduling interface assumes that an empty mailbox means an open person.

Colleagues inside that client organization rely entirely on these visual cues. Project managers place meetings directly over your schedule because no block stops them. They do not know you have two calendars open in separate windows.

Declining a meeting that appeared open looks disorganized to stakeholders. Accepting the meeting forces you to reschedule another paying client. The problem comes from the false availability displayed to the organizer.

The client calendar never received the hour because cloud tenants enforce strict boundaries. A Microsoft 365 tenant blocks unauthenticated external queries to protect user data. Internal scheduling tools query the local directory rather than external domains.

Your personal calendar lives in a separate directory with its own permissions. The client tenant cannot inspect your external availability without an administrative link. The client system treats your account as an isolated mailbox.

Adding a hold to your primary calendar updates only that specific database. That record stays inside your own account. Your client account receives zero status updates. The local free/busy table for your client profile remains clear.

Directory federation between separate organizations requires enterprise coordination. Client IT administrators rarely configure trust relationships for external contractors. Compliance controls prevent cross-tenant sharing to protect internal privacy.

Your client identity and your primary identity remain separated. You hold a commitment on one calendar, but the second calendar receives no signal. The scheduling tool displays the local state, which shows you as completely free.

Sending a booking link does not stop a corporate client from scheduling internally. Corporate teams work inside their native tools every day. An internal manager will not leave Outlook to load a booking URL for an onboarded team member. They use Outlook Scheduling Assistant because internal workflows direct them there.

Booking links work best for external contacts without access to your directory. A client provisions an internal email address for your consulting role. Team members then expect to book your time directly inside their system.

Subscribing to an internet calendar feed through an ICS URL also fails to protect the hour. Google Calendar and Outlook store subscribed feeds in secondary display layers. The software displays external entries on your screen so you can view your schedule.

Calendar servers exclude secondary web feeds from enterprise free/busy calculations. An ICS feed functions only as a personal visual layer. Colleague queries through Google Find a time or Outlook Scheduling Assistant ignore secondary subscribed feeds.

Subscribed feeds also update slowly. The host calendar controls the refresh schedule. Changes on your primary calendar do not appear immediately in the subscribed view.

Relying on external booking links and secondary feed overlays leaves your availability unprotected. The client system requires real calendar entries on the primary calendar to change availability state. Empty time slots invite conflicting meeting requests.

Fixing the client view requires writing native calendar events onto your client calendar. The event must sit on the default primary calendar of that client account. When an event occupies that primary calendar, the directory registers that time as Busy.

You do not need to share sensitive client details across organizations. The native block on the client calendar requires only the Busy status. A placeholder event titled Busy protects the hour without exposing private details.

Automated calendar synchronization creates these placeholder events across your accounts. When you place a hold on your primary calendar, a background process creates an identical Busy block on your client calendar. When you move the hold, the placeholder updates.

Outlook Scheduling Assistant and Google Find a time read native primary calendar blocks. The client tool encounters an authentic busy marker during that hour. The organizer sees that you are unavailable and selects another time.

As of 3 October 2026, OnlyBusy lists Free at $0 with up to 2 calendars and no scheduling links, Standard at $6 a month or $50 a year with up to 4 calendars and 4 scheduling links, and Premium at $12 a month or $99 a year with unlimited calendars and scheduling links. Teams is arranged by email at privacy@onlybusy.com.

Genuine Busy events bridge tenant boundaries without exposing private data. You keep your detailed notes on your main account while maintaining accurate availability across client organizations. Both calendars stay aligned, and the scheduler protects your reserved time.