Is Joresay a full ATS, or a screening tool?
A full ATS. Jobs and requirements, clients and delivery, the candidate database, pipeline and stage history, sourcing and bulk resume parsing, client and vendor portals, invoicing and collections all ship as standard. The AI screening round is one stage inside that system, not a separate product bolted on.
Can we migrate from our current ATS?
Yes. Bulk import jobs, clients, candidates and stage history from CSV or Excel, or sync through the scoped REST API. Resumes come across with parsing intact, and most teams run Joresay alongside their existing system through the switch.
Does this replace our technical interview?
No. Joresay runs the screening round — the first conversation that decides who is worth a panel slot. Your technical round, system design round, and culture rounds stay exactly where they are. They just run on a shorter shortlist, with evidence already attached.
Can candidates tell it is an AI interviewer?
Yes — candidates are told explicitly before anything begins, in your own brand voice. Consent is captured upfront in line with US EEOC, EU GDPR, UAE DIFC, and India DPDP standards.
What happens on a weak connection or without a camera?
There is an automatic audio-only fallback. Answers are banked on every turn, so a dropped connection never loses an answer already recorded.
Who owns the recordings and transcripts?
You do. Recordings and transcripts are written into your own storage bucket (AWS S3 in your chosen region, Azure Blob, or Cloudflare R2) and accessed via short-lived signed URLs.
Is the score explainable to hiring managers?
Yes, and the model never sets it. Each competency is recomputed from its own question scores weighted by question, so the number always reconciles with the evidence beneath it. Every question score carries verbatim candidate quotes, and the report is a searchable PDF with the full transcript attached.
Do we have to use your AI account?
No. Connect your own OpenAI, Gemini, Claude, Qwen, DeepSeek, Groq, NVIDIA NIM or Moonshot account — or any OpenAI-compatible endpoint. Usage bills to you at provider rates and we add no markup. Resume and JD parsing also run on a built-in rule-based engine, so the desk keeps working with AI switched off entirely.
Can our clients and vendors log in?
Yes, and both are included. Clients get a branded portal for their own mandates, candidates and interviews, with granular permissions over what they may do. Vendors get assigned jobs, a submission form and their own performance and invoices — with placement credit attributed to the vendor rather than the last recruiter who touched the record.
Can we use our own domain and branding?
Yes — across client portals, vendor portals, candidate interview links, login screens, email notifications, sender identity, and legal pages.
How fast can a team go live?
Import your jobs and candidate records, connect your AI key, set your brand colour, and point your CNAME. Most teams run their first live AI screening the same day.
Where does data reside?
Company data is tenant-isolated with row-level separation. Files, audio and video reside in your chosen regional bucket — AWS US-East, Frankfurt, UAE Central, or Mumbai.
What happens if we leave?
Export all candidate profiles, transcripts, recordings, jobs, and billing history to CSV or Excel at any time, or sync continuously via the scoped REST API.
Does it handle high-volume campus and drive hiring?
Yes. Drive plans, bulk resume parsing, and parallel AI screening rounds are built to handle 500+ candidates at once without calendar bottlenecks.