Case Study
This technology staffing company manages hundreds of contract workers across multiple continents. Their scheduling operations team had built a fragile automation stack spanning Google Sheets, Monday.com, Calendly, Zapier, and manual phone calls. Vela replaced all of it - phone, email, and SMS - in a single deployment.
Company
National Technology Staffing Firm (anonymized)
Industry
W2 Staffing & Contract Workforce Management
Headquarters
New York, NY
Reach
5 continents
Clients Served
Fortune 500 technology companies, autonomous vehicle leaders, AI companies
Interview Volume
1,000+ per week
This company is not a traditional staffing agency. They operate as a W2 employer of record - sourcing, hiring, and employing thousands of contract workers on behalf of enterprise technology clients. Think autonomous vehicle test operators, AI training specialists, and technical operations teams deployed across multiple cities and time zones. The company processes roughly 2,000 hires per month, and every single one passes through an interview gauntlet before placement.
The scheduling operation behind those interviews had become one of the most complex parts of the business. Their operations team had stitched together 17 different tools and automations to keep it running: Google Sheets for interviewer availability, Monday.com boards for candidate pipelines, Calendly for booking links, Zapier automations for triggering emails and calendar invites, and manual phone calls to chase down unresponsive candidates. The system worked - barely - but it was fragile, opaque, and completely dependent on the one person who had built it.
The complexity started with the clients. Interviewer availability changed every single week. Hiring managers would claim interview slots for the coming week in a shared Google Sheet, and an account manager would manually transfer that availability into Monday.com. From there, the operations lead would manually input those times into separate Calendly events - one for each office location, typically three. A candidate clearing their background check would trigger a Zapier automation to send the appropriate booking link. When they booked, another automation populated their information back into Monday. Then a separate automation created double-blind calendar invites - one for the candidate, one for the interviewer - because the client required that candidates could never see interviewer information.
And that was just the happy path.
The real nightmare was rescheduling. On a bad day, half the candidates on the schedule needed to move. Sometimes half of their cancellations came in at the last minute - 15 minutes before the interview, with no alert to the operations team, making it look like a no-show. Filling empty slots required manually reaching out to replacement candidates, and the team had no automated way to do it. The operations lead spent 18 to 24 hours over a single weekend building a single reschedule workflow in Zapier - just for one client.
Meanwhile, every client had a different process. One wanted availability managed in a shared Google Sheet. Another required a separate tracking spreadsheet where the team had to manually log confirmations with a "C" in a column and update it multiple times a day. Some clients used their own applicant tracking systems, pushing candidates behind the scenes where the staffing firm lost all visibility. The CEO put it bluntly: every client had some unique process they had to follow, and he wished they could model all of it as one input-output system instead of having people track dozens of different styles.
Three people were spending roughly 60 hours per week combined on scheduling coordination. The operations lead described her world as being spread across 17 different systems, and joked that she hoped the Vela team had never used Zapier so they would not be horrified by what she had built. It was working - but just barely, and it was breaking in all the places that mattered most.
"Right now I have it across 17 different things. So to have it all come from one thing would be awesome."
Vela did not ask the team to rip out their existing tools or change how their clients share availability. It plugged directly into the systems that were already there - the Google Sheets, the Monday.com boards - and took over everything downstream.
Here is how it works: Vela connects to the client's Google Sheet where interviewers post their weekly availability and the Monday.com board where candidates move through the pipeline. When a candidate clears their background check and gets moved to the interview stage on Monday, Vela picks it up automatically. It scans the Google Sheet, identifies available interview slots, and calls the candidate by phone. If they pick up, it books them on the spot. If they do not answer, it sends an email. Either way, the candidate receives an email confirmation with a calendar invite.
Vela creates the double-blind calendar invites the client requires - separate events for the candidate and the interviewer, with no shared information between them. It reads interviewer availability directly from the source of truth and matches candidates to open slots intelligently, factoring in time zones, interview duration, and location.
The system is timezone-aware by default. It will not call a candidate in Hawaii at 6 AM their time because a team member in New York triggered the workflow at 9 AM Eastern. It formats everything for the candidate's local time and schedules outreach during appropriate hours.
Rescheduling - the single biggest time sink for the operations team - became fully automated. If a candidate declines the calendar invite, Vela emails them to offer new times. If they reply to the confirmation email saying they cannot make it, Vela continues the conversation. If they call back the same number that contacted them, Vela handles it over the phone. After multiple failed attempts, it escalates to a human on the team. The 18-hour weekend Zapier builds became unnecessary.
For bulk cancellations - like when inclement weather forced the cancellation of an entire afternoon of in-person interviews - the team can simply message Vela on Slack: "Cancel all afternoon interviews for today." Vela handles every outbound communication, crafting polite, empathetic messages for each candidate across phone, email, and SMS simultaneously.
The entire configuration is done in natural language. No code, no Zapier chains, no fragile automations. The team writes behavioral instructions like: "Ignore my personal calendar for this workflow - use the Google Sheet for interviewer availability." Or: "First-round interviews are 30 minutes. In-person interviews are 60 minutes." Or: "On rejection, immediately call the candidate back to reschedule without asking me for permission." A new client or role can be set up in roughly 15 minutes.
And critically, Vela works as a single system across every client - regardless of whether that client uses Google Sheets, Monday boards, or some other format for availability. The one input-output system the CEO had been wishing for.
"I just wanted to make sure we're not setting up a one-time thing. Vela's actually the full solution."
When a candidate clears their screening and gets moved to the interview stage on Monday.com, Vela detects the change automatically. No manual trigger needed. It pulls interviewer availability from the connected Google Sheet and identifies the best available slots.
Vela calls the candidate by phone first. If they do not answer, it follows up by email. The candidate receives time options in their local timezone, books a slot, and gets a confirmation with a calendar invite. The interviewer gets a separate, double-blind calendar invite with no candidate information exposed.
Vela sends reminders 24 hours and 2 hours before the interview. If a candidate cancels, Vela automatically attempts to reschedule - via phone, email, or SMS - without human intervention. If weather or emergencies force bulk cancellations, one Slack message handles all outbound communications.
17
Tools and automations replaced by one AI agent
60 hrs
Of weekly scheduling coordination eliminated
1,000+
Interviews managed per week across multiple clients
15 min
Setup time for a new client or role
3
Channels - phone, email, and SMS - handled simultaneously
17
Tools and automations replaced by one AI agent
60 hrs
Of weekly scheduling coordination eliminated
1,000+
Interviews managed per week across multiple clients
15 min
Setup time for a new client or role
3
Channels - phone, email, and SMS - handled simultaneously
The fragile automation stack that had taken months to assemble and an entire weekend to patch was replaced by a single deployment configured in natural language. The operations team went from monitoring 17 systems multiple times a day to checking one dashboard. Rescheduling - the task that consumed more time than anything else - became fully autonomous. Bulk cancellations that used to require a scramble of manual emails, texts, and phone calls could be triggered with a single Slack message.
The operations lead no longer needed to spend her weekends building Zapier automations. And when hiring volume spiked for a new client or location, spinning up a new workflow took 15 minutes instead of days.
"Especially when you're doing interview stuff, man, it's just - sometimes it's got to happen on the weekends."
"I got called out once for calling someone who was in Hawaii at 9 AM Eastern, and they were like, do you know what time it is here?"
"We recently had to cancel 60 interviews set for Saturday, and then the afternoon interviews all needed to get canceled because of inclement weather. We had to send out bulk emails and bulk texts and probably calls."
"Every client is kind of different. They all have some unique process that we have to follow. And that's why we have people doing it."
Vela replaces the duct tape - Zapier chains, manual phone calls, spreadsheet gymnastics - with one AI agent that handles phone, email, and SMS.