Integrations — ATS
Twynit + Zoho Recruit
Zoho Recruit runs a lot of agency desks. Twynit doesn't ask you to leave it — it adds the layer Zoho doesn't have: a Twin that reads every candidate against each client's scorecard, prepares evidence-backed submittals, and writes everything back.
Your consultants spend their day on client calls and closings, not on data entry.
What your Twin does with it
- Imports candidates and jobs from Zoho Recruit, de-duplicated into one agency-wide talent memory
- Ranks every candidate per client scorecard, with the evidence a client can be shown
- Prepares branded submittal cards clients can respond to in one tap
- Writes decisions and stage changes back to Zoho Recruit with named receipts
- Keeps each client's learnings walled off from every other client's — by design
Every write-back is named, logged, and undoable for 72 hours. If one fails, it surfaces as a warning with a retry — never silently.
How the connection works
01
Connect and import
Connect Zoho Recruit from Settings in about a minute. Your Twin imports your existing candidates and open roles in the background, narrating progress as it reads. People are matched and de-duplicated, so the same human across two systems becomes one person with one history.
02
Confirm the mapping
Before anything goes live, your Twin shows you how Zoho Recruit jobs map to Twynit searches and asks you to confirm — one review card, not a settings maze. Nothing syncs until you approve the mapping.
03
Work anywhere, both systems agree
From then on, sync runs both ways. A stage change in Zoho Recruit appears in your Twynit timeline as a receipt; a decision in Twynit writes back to Zoho Recruit and names its destination: "Updated Zoho Recruit: Sarah → Onsite." Conflicts follow the policy you set, and every resolution leaves a receipt showing both sides.
Questions
Does Twynit replace Zoho Recruit?
No. Twynit works alongside Zoho Recruit. Zoho Recruit stays your system of record; Twynit is where the judgment work happens — reading, ranking, evidence, decisions. Everything you decide writes back, so your team and your reporting keep working exactly as before.
We run multiple clients. How does Twynit keep them separate?
Clients group searches. Your talent memory is agency-owned and spans clients, but knowledge is client-scoped: one client's outcome learnings never inform another client's scorecards. That wall is structural, not a setting.
What exactly gets written back?
Stage changes, decisions, notes, and scheduling updates — each one recorded with a visible receipt that names the destination. If a write-back fails, it surfaces as a warning with a retry, never silently.
What if a sync does something I didn't want?
Every action your Twin takes is undoable for 72 hours from its receipt. Undoing an automated action also demotes that action type back to ask-first mode — your Twin asks what went wrong, and the answer becomes a remembered preference.
Keep Zoho Recruit. Add the judgment.