Questions dealers ask us.

It runs the first round of hiring for car dealerships. It reads and scores each applicant's resume against the job, invites them to interview the moment they apply, interviews them by phone or on the web whenever suits them (nights and weekends included), and gives your managers a scorecard, a recommendation, the full transcript and the recording. Your team decides who to meet.

As fast as they like. The invitation goes out automatically as soon as their resume is processed, usually seconds after they apply. They pick a time that suits them, any hour of the day or night, and the next open slot is usually only minutes away. A typical interview takes about 15 minutes, and the scorecard is ready as soon as it ends.

Yes. You can send applicants in from your ATS, careers page or DMS through our REST API and get results back automatically by webhook, so nothing about your current workflow has to change. Or use the Cenivoz hiring workspace on its own, or both.

We set it up with you: your open jobs, your must-ask questions, and your interviewer's name and voice. Most dealerships have real applicants being interviewed within a few days.

No. They either answer a phone call at the time they booked, or open a link in any browser on their phone or computer. A typical interview takes about 15 minutes.

Yes. Add screening questions to a job ("Do you have your own tools?", "Can you work Saturdays?") and the interviewer asks every one word for word. For yes/no questions you can set the answer you are looking for; the interviewer never reveals it.

No. It recommends; your team decides. It never discusses pay or makes promises about the outcome. Those questions are passed to your hiring team.

Every candidate for a role gets the same structured interview. Scores are based only on what the candidate said, and questions and scoring never touch protected characteristics. Every transcript and recording is there for your team to review.

They can pick a new time from their link, or simply say so during the call and the interviewer reschedules it with them.

It has interview playbooks for 28 dealership roles, from service technicians, advisors and sales consultants to BDC, parts, collision, F&I and office roles.

Data is encrypted in transit, each dealership's data is kept separate, every change your team makes is recorded in an audit log, and interview data is stored in the United States on AWS. You can export or erase an applicant's data at any time.

Yes, and with single stores too. Each rooftop has its own workspace, jobs, applicants and interviewer, and group executives see all of their stores from one login and switch between them. A group can connect its ATS with API keys per store.

Either, and they choose. For a phone interview, the interviewer calls their cell phone at the time they booked: any phone works, with no app or link. The web interview opens in any browser, including on a phone. Both run 24/7, and interviews can be held in English or Spanish.

No. We don't train AI models on your data or your applicants' resumes, recordings and transcripts, and the speech and language providers behind the interviewer process it only to run each interview: we use their business APIs and opt out of their model-improvement programs. It isn't sold or shared for advertising.

Simple monthly plans per rooftop. The best way to start is a 30-day pilot on your real openings. Book a demo and we will walk you through it.

No. You can add applicants or upload resumes straight into the Cenivoz panel and run the whole first round there. If you do have an ATS, careers page or DMS, it can send applicants in through our API and get the results back by webhook.

Your team can type or talk to it. It answers questions from your own data (how many applied, who scored highest, which interviews are tomorrow) and drafts work for you: creating or editing jobs and screening questions, adding applicants, sending interview links, scheduling or rescheduling interviews, and bulk status changes or notes. Nothing changes until someone presses Confirm.