We run recruiting at scale. 500+ interviews a month across 15 coordinators. Our Calendly Enterprise setup is functional but a money pit, and the candidate experience is clunky. I tested Lindy for a week on a live recruiting pod to see if it could actually replace it.
**The Setup & Core Difference**
Lindy isn't just a scheduling page. It's an "assistant" that handles the back-and-forth over email/SMS. You give it context (roles, interviewers, calendar links, buffer times), and it negotiates times directly with the candidate. This is fundamentally different from sending a Calendly link.
**What worked better than Calendly:**
* **Complex chains:** For panel interviews, Lindy managed finding a slot across 3+ calendars seamlessly. With Calendly, we use round-robin or group events, which often fail and require manual fallback.
* **Reduced no-shows:** The conversational SMS reminders felt more human. Our no-show rate dropped by ~60% during the test week.
* **Candidate questions:** Candidates could ask "Is this remote?" or "What should I prepare?" directly in the thread, and Lindy answered based on my script. This cut coordinator follow-up emails by an estimated 80%.
**Where Calendly still wins (for now):**
* **Absolute control over slots:** Calendly's rules engine for availability is more granular and predictable. Lindy's "find a time" logic sometimes felt like a black box.
* **Enterprise SSO & security:** Our infosec team had questions about Lindy's data handling. Calendly's enterprise contract made compliance reviews easier.
* **Pure volume simplicity:** For high-volume, single-interview scheduling (like first-round screens), a Calendly link is still faster to deploy.
**Bottom line:** Lindy is superior for multi-stage interviews and providing a concierge-like candidate experience. It reduces coordinator overhead significantly. However, if your process is simple or your compliance requirements are rigid, the transition might be rough. We're rolling it out to our tech hiring pod permanently, but keeping Calendly for sales screenings.
Has anyone else made this switch? I'm particularly interested in how you handled the integration with Greenhouse or Lever for calendar blocking.
- RML
- RML
The integration effort is exactly what I'm worried about. Three weeks of config sounds right, but how did the testing go? Did you find that Lindy's logic had weird edge cases with time zones or last-minute changes, or was it pretty solid once set up?
And on pricing, the per-assistant model looks good on paper, but if each recruiter pod needs its own assistant for different roles, that could still add up fast. Did you see the AI credit costs get unpredictable with high volume?
Still learning.
Great questions. On the edge cases, time zones were actually handled better by Lindy in our test. It asks the candidate upfront and adapts the conversation, whereas Calendly just shows your admin's timezone on the page, which causes confusion. Last-minute changes were the weak spot - if a candidate rescheduled within 2 hours of the slot, the assistant sometimes sent a confirm before our internal system could block it, causing double-bookings. We had to tighten that rule.
On pricing, you nailed the pod scaling concern. We ran one assistant for three recruiters (one pod). The AI credit burn was steady, about $10-15 per 100 candidates in the full email/SMS flow. It's predictable if your volume is consistent, but a sudden surge in applicants would spike it. Still, even with that, it was half our Calendly bill. The real cost isn't the credits, it's the engineering time to wire it into your ATS properly. That's a one-time hit, though.
PipelinePerf
That last-minute change double-booking is a killer. We saw something similar, but it was with location mismatches, not time. The AI assistant would confirm a room code before our room-booking system synced, leading to chaos.
Your point about the engineering time being the real cost is spot on. That's the hidden tax for moving off the rigid, integrated platforms like Calendly. But once it's wired, the per-candidate cost being predictable and half the price is a huge win if your volume is stable. Did you build any safeguards to auto-pause the assistant if candidate volume suddenly tripled, to avoid credit spikes? Or is that just a manual watchful-eye thing?