Using Ashby? Evie handles the scheduling conversations Ashby can't.
Evie reads job and candidate data directly from Ashby via its API, then handles the full negotiation loop by email until every interview is confirmed. Your team keeps using Ashby's native workflow — Evie takes on the back-and-forth it doesn't.
Triggered from Ashby. Coordinated over email. Written back on confirmation.
Evie reads from Ashby.
The moment a candidate reaches the relevant interview stage in Ashby, Evie reads the job, candidate record, and interviewer details directly via the Ashby API — no recruiter email needed to kick things off.
It coordinates entirely by email.
Ashby's own scheduling tool shares availability links; Evie goes further. It manages outreach, negotiation, and confirmation entirely through email — proposing times, chasing non-responders, and confirming the slot through that back-and-forth. It doesn't have direct access to anyone's calendar. When a candidate doesn't click a link, or availability changes, or a slot falls through, Evie handles it without pulling anyone back into the thread.
Confirmed interview written back to Ashby.
Once confirmed, Evie updates Ashby with the interview date, time, format, and meeting link, and triggers Ashby's feedback and scorecard flow post-interview.
Exactly what Evie reads from Ashby, and writes back.
No broader data access. Field-level scope, documented.
Deploys in 48 hours.
From contract to live in two days. Total IT time: about one hour.
Generate an API key
Your Ashby admin generates an API key. Evie's team configures the connection.
Map interview formats
Map interview formats and SLA rules with the onboarding team.
Live test against a real req
Move a candidate to the relevant stage in Ashby. Evie runs the full coordination loop for sign-off.
Your team keeps using Ashby's native workflow. Evie handles the negotiation Ashby doesn't.
“Native scheduling gets us most of the way. Evie handled the rest — the reschedules, the non-responders, the exceptions.”
Using Ashby? Evie handles what native scheduling can't.
API connection. No changes to your Ashby workflow. Evie takes on the negotiation loop, nothing else.