What it is
Honeit tracks the IP address a candidate is using at each stage of the interview process — when they schedule a call, when they open the call link, and when they join the call itself. Each of those IP addresses is used to estimate a location, giving you a location trail for the candidate across the whole scheduling-to-interview journey, not just a single snapshot.
How it works
Honeit captures location at three points:
Scheduling — when a candidate uses a scheduling link to book a call, Honeit reads the IP address they scheduled from and estimates their location. This also sets the time zone shown on the contact's Details tab, so calls and reminders display correctly for them. This event is recorded in the contact's Activity Log.
Opening the join call link — when a candidate clicks the link to the call, that IP address and estimated location are captured too, and also recorded in the Activity Log.
Joining the call — when the candidate actually enters the interview, Honeit captures their IP address and location at that moment. You'll see this in real time as a "Call Participants" popup on the interview dashboard (e.g., "Jamie is joining the call · US United States · IP address: 66.249.83.70").
You can see the full picture in one place by clicking the IP Activity location pin, available both on the contact record and on the live Interview Dashboard. It opens the candidate's activity location history: scheduling, link-open, and join events for that call, each with its location and IP address.
Why it matters
This gives you multiple independent checkpoints to verify who you're actually talking to, not just one. Compare the locations across scheduling, link-opening, and joining, and against whatever the candidate has told you about where they're based. If those locations are consistent with each other and with the candidate's stated time zone, that's a good corroborating signal. If they don't line up — for example, a candidate who says they're in the United States but whose IP consistently resolves elsewhere — that's worth a closer look.
A mismatch on its own isn't proof of anything — VPNs, travel, and shared or corporate networks can all cause a candidate's IP location to differ from where they actually live. Treat it as a signal to investigate further, not a verdict, and weigh it alongside your other verification steps.