Recruiting panel scheduling
OneCal vs Microsoft Graph for Recruiting Panel Interview Sync
Recruiting panel scheduling fails in the gaps between companies. The candidate is on Gmail, the client is on Microsoft 365, two agency interviewers are on separate domains, and every manual hold becomes a source of drift.
Microsoft Graph app build: build the manual path first
This is the agency-owned build path: create a Microsoft Graph app, read busy time, and write masked holds to a calendar the panel workflow can trust.
Register an Azure application
Create an app in Azure, add redirect URIs, and request the narrowest delegated calendar scopes your flow can survive on. Application permissions may trigger a much heavier admin review.
Collect consent from each interviewer account
Each internal interviewer signs in and grants access. For client interviewers, expect consent to fail or route to their IT team. Plan for missing data rather than assuming every tenant cooperates.
Store refresh tokens outside code
Put tokens in a secret store with owner, tenant, scope, and expiration metadata. A spreadsheet of tokens is not an operating system; it is a future incident.
Read free busy windows for the next 30 days
Use Graph calendarView or getSchedule calls to collect start, end, showAs, event ID, and last modified time. Do not read subject or body unless the business has approved that data movement.
Write masked panel holds to a mirror calendar
Create Busy holds for every unavailable interviewer in a scheduling mirror. The recruiter sees the true booking surface without seeing client or candidate details they do not need.
Handle moves, deletes, and recurring interviews
Map every source event to a destination hold. Recurring events need instance IDs, not just the series master. Deletes need a cleanup pass or the agency loses slots for days.
Where the manual path breaks under operating pressure
Token refresh becomes production work
A revoked token during a final-round loop can make one interviewer look free when they are not. Recruiting teams need alerting, retry logic, and ownership.
Tenant consent is not predictable
Some clients allow delegated calendar reads. Others block them. A recruiter still has to present times without asking the client security team to debug Azure.
Panel edits create stale holds
Interviewers move holds, clients swap panelists, candidates reschedule. If the mirror does not shrink and delete fast, the agency burns both speed and trust.
Privacy risk spans candidate and client data
Interview calendars carry names, compensation notes, requisition details, and confidential backfill plans. Copying subjects across tenants is a mistake.
OneCal vs the manual path vs WonderCal
These tools solve different jobs. The manual path proves the data problem. OneCal helps with part of the scheduling workflow. WonderCal focuses on the underlying calendar truth that keeps teams from offering bad times.
| Vector | Microsoft Graph Build | OneCal | WonderCal |
|---|---|---|---|
| Latency | Can be fast with webhooks, but polling builds and failed subscriptions often drift under real agency load. | Good for personal multi-calendar visibility, less tuned for agency panel workflows across client tenants. | Fast masked sync keeps panel availability current across Google and Outlook without making recruiters own webhooks. |
| 2-Way Sync | Possible, but the agency owns ID maps, deletes, recurrences, token failures, and retry queues. | Useful calendar sync product, but agency operators still need to validate fit for client/candidate panel flows. | Two-way sync is product-owned, including update and delete handling for busy blocks. |
| Calendar Privacy | Safe only if the build copies busy state and strips subjects, bodies, attendees, and locations. | Can reduce manual copying, but configuration has to protect meeting details across accounts. | Masked Busy blocks are the default operating model for cross-domain availability. |
| IT Admin Blocks | Azure consent and Microsoft Graph scopes are common blockers in client tenants. | New app approval may still hit client or agency IT review. | User-scoped OAuth narrows the approval ask for distributed recruiting teams. |
| Team Pricing | Engineering time, monitoring, and recruiter downtime are the real cost. | Seat costs rise as recruiters and coordinators need coverage. | $4 per user per month keeps cost predictable across recruiters, coordinators, and interview teams. |
The WonderCal fix: sync the truth, not the secrets
WonderCal gives recruiting agencies the part they actually need: accurate cross-domain busy state with private details masked. Keep the ATS and interview workflow; fix the calendar layer that feeds it.
When the manual path is still fine
- The calendar does not touch revenue, hiring, legal, customer, or child privacy risk.
- A stale slot for 15 minutes will not hurt trust or create operational rework.
- One owner checks failures, deletes, and permissions every week.
When WonderCal is the better call
- Google and Outlook accounts both decide whether a person is actually free.
- Multiple people or domains must be correct before one meeting can be booked.
- Private details should stay inside the original calendar account.
- The team wants predictable pricing instead of maintenance surprises.
FAQ: OneCal vs Microsoft Graph for Recruiting Panel Interview Sync
Can a recruiting agency build panel scheduling with Microsoft Graph?
Yes, but it becomes a production integration. The agency must manage consent, token refresh, webhooks or polling, recurrence logic, deletes, and privacy rules.
Why is client tenant access hard?
Client Microsoft 365 tenants often block third-party app consent or require admin review. That can delay scheduling even when the hiring manager wants to move fast.
How should candidate privacy be protected?
Move only busy state, start time, and end time. Do not copy names, titles, notes, compensation references, or meeting links into another tenant.
Where does OneCal fit?
OneCal can help individuals manage multiple calendars. Recruiting agencies still need to check whether it fits panel interviews, client domains, privacy needs, and team pricing.
When is WonderCal the better fit?
When recruiters coordinate multiple interviewers across Google, Outlook, client domains, and agency domains, and speed plus privacy matter more than owning custom Graph code.
Book panels before candidates cool off
WonderCal keeps Google and Outlook availability aligned with masked busy blocks, fast updates, and pricing that does not punish growing teams.
Start with WonderCal