Vela - The AI Recruiting Coordinator

by•
Vela is an AI recruiting coordinator. Cc it on any email thread and it takes over: candidate screens, multi-round loops, and full panels. It offers times, chases people who go quiet, handles reschedules, sends the resume with the invite, books prep calls, and collects feedback. Email, SMS, WhatsApp, Slack, and phone, every time zone, 24/7. No links, no logins, nothing new for your team to learn. Trusted by The World's Best Recruiters, and backed by YC, CRV, and other incredible investors.

Add a comment

Replies

Best
Hey Product Hunt 👋 I'm Gobhanu, co-founder of Vela. Vela is the only scheduling agent trained specifically on recruiting scheduling data. The problem If you have ever run an executive search, you know the drill. One placement means six-plus rounds: a hiring committee, a board member three timezones away, a candidate who can only talk at 7am before their current job notices. Every round is a new permutation. And here is the part that breaks every existing tool: you have read/write access to exactly zero of those calendars. You are not scheduling for yourself. You are brokering between parties who have never met. So you live in the reply-all thread. Propose, get declined, repropose, chase, repeat. Most firms solve this by hiring coordinators. Scheduling links do not work, because the person you need to book is not your user. What Vela does You CC Vela on the email thread. That is the whole onboarding. No new tool, no workflow change. From there Vela: Runs the back and forth exactly like a professional coordinator would, in your firm's voice Handles the edge cases: reschedules, no-shows, "can we push 30 minutes," five people across three timezones Sends the calendar invite with the resume attached and the right video link Works across email, SMS, and WhatsApp, 24/7

 From the hiring side, scheduling eats more of my week than actual interviewing. The failure mode I'd worry about is candidates feeling handled by a bot before they meet a human. How does Vela keep touchpoints personal, and where does it hand off to a real person?

 We built Vela to emulate human behavior. Most folks can't tell the difference between whether it's AI or human.

Beyond that, candidates would much rather, in my personal experience, have a response in 5 minutes from someone who is able to do and achieve the same outcome than wait for a human for many hours because they're busy or they might be sleeping if they're across different time zones. Most candidates have actually preffered interacting with Vela and frequently compliment it on how smooth the interview proccess was!

the cc it and forget about it approach is genuinely brilliant, no new dashboard to babysit when the rest of the recruiting stack already feels bloated. love that it just lives where the work already happens.

 Thank you!

Finally something that actually just works from your inbox instead of forcing a whole new login. Loved that it just chased my no-show candidate without me lifting a finger.

 Thank you!

Love how it just lives inside the email thread, no new dashboard to babysit. Chasing candidates across SMS and Slack while the rest of us sleep feels like actual leverage, not another tool to maintain.

 Thank you!

'write access to zero of those calendars' names the real problem. with no calendar access either side, how do you avoid offering a slot that's already gone?

 we are able to mimize these types of errors by simply passing on the availability as fast as possible!

   fast narrows the race condition window, it doesn't close it. neither side has write access, so the underlying slot can still get taken in the gap between offering it and someone accepting it, however small that gap is. what happens when it actually collides, does a human get flagged that a slot got contested, or does vela just start renegotiating on its own without anyone finding out a collision happened at all

The tool seems quite interesting. Do you support integrations with the most common ATS? Thanks!

 hey Daryna! Yes we do! What ATS are you using?

the part I'd want to understand is the feedback collection step, not the scheduling. scheduling mistakes are annoying but recoverable, you just repropose a time. "collects feedback" and talks to candidates in the firm's voice is a different category, if a candidate asks "how did it go" or "am I moving to the next round" mid-thread, does Vela wait for an explicit decision from the hiring team before it answers, or can it infer an answer from the tone of the feedback it collected and relay that as if it were settled? that's the kind of thing that's hard to walk back once a candidate has heard it.

 In the above situation yes! It would stand down and wait for the human descion or nudge as a reminder to the Human if needed to make sure the proccess keeps going!

 good to hear, but that raises the follow up: standing down is fine internally, the question is what the candidate actually sees while it's waiting. the pitch elsewhere in this thread is a reply within 5 minutes, faster than a human who might be asleep, that's the whole value prop. so on the one question that matters most to the candidate, does the fast reply disappear and they wait like they would with a human, or does Vela send some kind of holding message? if it's the second, what does that message say without accidentally implying an answer either way?

 This really depends on the situation. Certain situations, Vela is smart enough to make the right judgment call because it's been through 'this' common question all the time!

In other situations, the best possible outcome may be simply to wait.

 that split is the part I'd want pinned down before trusting it at scale. "been through this common question all the time" sounds like it's learned from volume, which is fine until a firm's first ever candidate asks something Vela hasn't seen a hundred times yet - does it default to waiting when a question is unfamiliar, or is there a real risk it treats novel-but-confident-sounding as familiar and answers anyway? the failure mode I'd worry about isn't the known cases, it's the one where the model is wrong about which bucket a question falls into.

Does it have its own dashboard or it works in email threads only?

 It has its own dashboard too! Vela was dubbed the best ai search coordinator!

This is awesome! Who is this built for?

 Thanks Gary! We support exec search firms and recruiting agencies!

I love the idea. How do you handle hallucination? Whats the error rate?

12
Next