Interview times that are actually free.

How it works

1. Connect your calendar. A recruiter authorizes Scout Scheduling from the settings page in Headhunt.AI. The connection is per person and entirely optional — colleagues who do not connect an account are unaffected.

2. We read your existing events’ times to work out your real availability, within the working hours, buffers, minimum notice and daily interview limits you configure.

3. Candidates choose from times that are genuinely free. Slots already taken on your calendar are never offered, including anything booked after the invitation was sent.

4. We create the interview on your calendar, invite the candidate, and attach a video-meeting link. Reschedules and cancellations update the same event, so your calendar stays accurate without manual mirroring.

Supported providers

Google Calendar · Microsoft 365 and Outlook Calendar, with Microsoft Teams meetings · Zoom Meetings

Connecting a video provider is optional. Without one, interviews are booked using the calendar’s own native meeting room.

What we access — and what we do not

We read the times and busy/free status of existing events in order to compute availability. We create, update and cancel only the interview events that Scout Scheduling itself books — never events created by you or by another application.

We do not read event titles, descriptions, attendee lists or attachments for any purpose beyond determining whether a time is free, and we do not store the contents of your calendar. We do not use this data for advertising, to build or enrich our candidate database, or to develop or train any generalized artificial-intelligence or machine-learning model.

Authorization tokens are stored in encrypted form and are accessible only to the components of the Service that implement the features described above.

Staying in control

You can disconnect at any time from the settings page in Headhunt.AI. You can also revoke our access directly in your Google, Microsoft or Zoom account settings, independently of us. On disconnection or revocation, we delete the authorization tokens for that account.

Data handling and terms

The data items collected from each provider, the exact authorization scopes requested, the purposes they are used for, and our commitments regarding Google user data — including the Google API Services User Data Policy Limited Use requirements — are set out in full in Article 18 of our Privacy Policy. Integration-specific terms are in Article 24 of our Terms of Service.