Skip to main content

​
Manage Your ATS Integration Workflow

From within the Admin page, under the ATS Integrations → Configuration tab you may configure policies for when to engage applicants, which actions to perform after interviews, and which interview results to write back to custom fields in your ATS. Settings below use the same labels shown in the Admin UI. Some fields only appear for specific ATS providers (for example Workday workflow steps or Bullhorn tearsheet sync).

​
Available Settings

​
Candidate Flow Stages

  • Start Stages Which stages or statuses applicants must be in for Tenzo to sync them from the ATS and begin outreach. Once applicants are moved out of this stage, outreach will end. For integrations that display this setting, selecting no start stages stops Tenzo from pulling new applicants from the ATS (Workday integrations can still match configured Start Workflow Steps). Status-based integrations without a Start Stages setting use their ATS’s supported applicant status to determine which new applicants to pull. Candidates already in Tenzo, and people you add yourself (for example a CSV upload), are unchanged.
    • Paycor: stages are shown by Paycor’s numeric stage code (for example Stage 1) until the code-to-name mapping is confirmed; the list covers the standard codes plus any stage already seen on your synced candidates.
  • Resume Review: Above Threshold / Below Threshold If an initial resume review of applicants is configured, applicants can be moved to different stages based on the resume review result before the interview is conducted.
  • AI Interview: Above Threshold / Below Threshold Which stages to move applicants to when the interview is complete, based on score and completion rate. No movement will occur if a field is left blank.
  • AI Opt Out Stage Which stage to move applicants to when they opt out of the AI interview for human review.
  • Interview Accommodation Requested Which stage to move applicants to when they request an interview accommodation — an accessibility change needed to complete the interview itself (for example a sign language interpreter or a slower pace). Job-related work accommodation disclosures do not trigger this move; those are handled by the work-accommodation review flow below. No movement will occur if this field is left blank.
  • Work Accommodation Requested (optional) Which stage to move applicants to when a completed interview has scored answers flagged for work-accommodation review. Normal interview-result actions still run, and the applicant remains here until every flagged item is reviewed. Two cases skip this move: a candidate whose score already meets the passing threshold on their raw answers, and flagged Info questions, which surface for reviewer awareness without holding the stage. No movement will occur if this field is left blank; the candidate stays in their current ATS stage while the interview is under review.
  • Cooling Down Stage Which stage to use while a candidate is in cooldown before further outreach.
  • Outreach Stage / Outreach Paused Stage Optional stages that reflect when Tenzo is actively outreaching or when outreach is paused.
  • Max Attempts - No Interview / Max Attempts - Interview Not Completed When outreach attempts are exhausted, configure two targets. Each applies only to its corresponding outcome. The legacy single Outreach Attempts Exhausted Stage is deprecated: it does not fill in unset Max Attempts fields, so set the new fields before relying on ATS moves for those outcomes. Set the matching Workday workflow steps too when your integration uses steps.
  • Invalid Contact Stage Which stage to move applicants to when Tenzo cannot reach them (invalid phone number, carrier invalid-number on SMS, or missing email for a web-call invite). No movement will occur if this field is left blank. Invite send failures after retries cancel the invite call; they do not move the applicant to the Invalid Contact stage — only unreachable contact (missing email / bad phone / SMS carrier invalid) does.
  • Wrong Number Stage Which stage to move applicants to when the person at the phone number confirms via text that Tenzo reached the wrong person, or says so explicitly during a voice call (including hanging up after an identity denial without confirming the candidate can be reached there, before the interview continues). If someone confirms the candidate is reachable at this number but unavailable (e.g. at work), Tenzo does not treat it as a wrong number. No movement will occur if this field is left blank.
  • No Consent Stage / Consent Revoked Stage Optional stages for candidates who have not consented, or who had consent and later revoked it.
  • Stage Routing Rules (when enabled for your org) Conditional routing that can override the default stage moves above based on interview outcomes and other signals.

​
Scoring & Thresholds

  • AI Interview Above Threshold Score Minimum interview score required to use the AI Interview: Above Threshold stage.
  • AI Interview Completion Rate Threshold (%) Minimum completion rate required alongside score for the above-threshold path.
  • AI Interview Proctoring Score Threshold Optional proctoring score gate used when proctoring is enabled for video interviews.

​
Feedback Actions

  • Thumbs Up Stage Stage to move applicants to when a recruiter marks thumbs up in Tenzo.
  • Thumbs down Configure whether thumbs-down should disposition the candidate or move them to a stage (Thumbs Down Disposition Reason / Thumbs Down Stage).
  • Not interested Configure whether a candidate not-interested outcome should disposition or move to a stage (Not Interested Disposition Reason / Not Interested Stage).

​
Candidate Disposition

  • Enable Auto-Disposition (Rejection) Allow Tenzo to disposition (reject) candidates in the ATS for configured outcomes.
  • Enable Auto-Reject Inactivity / Auto-reject after timeout Configure whether inactive candidates are auto-rejected, the inactivity window (Auto-Reject: Days of Inactivity), and the target stage / disposition reason.

​
Custom Field Mapping

  • Tenzo Job Link Custom Field A text field on the job where Tenzo will write a link to the job in the Tenzo App.
  • Tenzo Interview Link Custom Field A custom field on the applicant where Tenzo will post a link to the interview.
  • Tenzo Interview Application Score Custom Field Where Tenzo will write the score of the interview (on the applicant).
  • Tenzo Interview Candidate Score Custom Field Where Tenzo will write the score of the interview (on the candidate). Note: the score written to the candidate will be overwritten if the candidate interviews for other jobs.
  • Tenzo Interview Completion Rate Custom Field Where Tenzo will write the interview completion rate when your ATS supports it.
  • Provider-specific custom field IDs (for example iCIMS interview PDF / summary fields, or Workday job custom field report settings) appear only for those integrations.

​
Job Settings

  • Enable Interview Auto Activation When enabled, ATS-synced jobs (AI-generated or created from a script/hybrid template) are automatically activated after any configured delay so outreach can begin. When disabled, recruiters must manually activate each job.
  • Delay Interview Activation Time to wait after a job is created before auto-activation. Set both hours and minutes to 0 for immediate activation when auto-activation is enabled. Setting a delay gives time to review and modify the job after creation before outreach begins.
  • How auto-activation interacts with ATS job status When org auto-activation is enabled and a job still has auto-activation on:
    • If the ATS marks the job closed / covered / filled / cancelled (or otherwise not open), Tenzo pauses the job. Auto-activation stays on.
    • If the ATS later marks the job open again (for example Accepting Candidates), Tenzo resumes the job and outreach can continue.
    • If someone manually pauses the job in Tenzo (or turns auto-activation off on that job), auto-activation turns off. Tenzo will not auto-resume that job when the ATS reopens it until a recruiter turns auto-activation back on or resumes the job manually.
  • Manually activating, pausing, or resuming a job (and toggling auto-activation) requires the Manage Lifecycle permission. This is granted to the Admin and Editor roles by default; Recruiters do not have it unless an org explicitly grants it on the Role Permissions page.
  • Create ATS Application When Tenzo should create an application or submission in your ATS for candidates added from sourcing, uploads, or other Tenzo-only paths. Applicants already in your ATS are unchanged. This is a Job Settings control, not an Activity Feeds toggle.
    • If passed (default): create only after a passing interview.
    • Immediately: create when the candidate is added to the job.
    • No creation: never create an ATS application from Tenzo. Resetting ATS configuration in Admin clears this saved value. The control then shows the integration default that matches runtime (If passed for most integrations). A few customers still have a leftover Immediately fallback until that value is saved or backfilled; reset does not flip those to If passed.

​
Interview Results to ATS

  • Enable Interview Results ATS Notes (default on): When enabled, Tenzo posts AI interview summaries to the ATS as notes after a call completes (on the application when one exists, and on the candidate for sourced flows without an application). Call-stop and not-interested notes use the same setting. Interview Results Templates only control note content, not whether posting happens.
  • Enable Interview Results ATS PDF (default on): When enabled, Tenzo attaches the AI interview results PDF to the ATS after a call completes (application and candidate paths). When disabled, PDF writebacks are skipped; notes and other writebacks below are controlled separately.
  • Score, completion rate, and interview link custom field writebacks are not controlled by these toggles.

​
Activity Feeds

  • Enable Text Activity Feed / Enable Email Activity Feed Configure whether inbound and outbound messaging should be propagated as notes to the ATS during outreach.
  • Enable Stage Transition Activity Feed (default off): When enabled, Tenzo can post ATS comments when a candidate’s Tenzo pipeline stage changes (not your ATS job stage name).
  • Tenzo Stage Comment Aliases: Add stages where a comment should be posted. The default note is Tenzo is moving application to: <stage name> (call completed uses separate above/below threshold stage rows). Override with custom text per stage if needed.
  • Enable Sourced-by-Recruiter ATS Notes (when available) Controls notes for recruiter-sourced candidate flows.
  • Provider-specific note-type label overrides (Bullhorn, JobDiva, Jobvite) appear only for those integrations.
  • These comments are independent of AI Interview: Above Threshold / Below Threshold moves in the ATS.
Consent field mapping via the admin UI is supported for Bullhorn (candidate-level opt-out fields) and Workday (optional application questionnaire SMS consent). No other ATS provider — including RecruitCRM — supports writing consent / opt-out values back to the ATS.
Tenzo can map Bullhorn opt-out fields onto the candidate’s consent settings in Tenzo, so a candidate’s choices in your ATS govern what Tenzo is allowed to send. Three mappings are available:
  • Email consent field A single Bullhorn field controlling whether Tenzo may send email to the candidate.
  • SMS consent fields One or more Bullhorn fields controlling whether Tenzo may text the candidate.
  • Call consent fields One or more Bullhorn fields controlling whether Tenzo may place AI calls to the candidate (Bullhorn’s “all AI communications” preference).
Notes on behavior:
  • These are opt-out fields, following Bullhorn’s convention: a value of No means the candidate is opted in (consent granted) and Yes means they are opted out.
  • When you map several fields for one channel, every mapped field must indicate consent for that channel to be allowed.
  • The mapping works in both directions. Values are read from Bullhorn on candidate sync, and consent changes captured by Tenzo (for example verbal SMS consent on a phone screen) are written back to the mapped fields.
  • There is no self-serve Admin UI for these mappings. Contact Tenzo support to have them configured for your organization.
See Candidate Consent for how consent gates each outbound channel. Workday tenants that collect SMS consent on the application questionnaire can enable application-scoped SMS in Admin → ATS Integrations → Configuration:
  • Enable application SMS consent When on, Tenzo reads the questionnaire answer for each application and stores it on that candidate-job record. Candidate-level STOP still blocks every job.
  • SMS consent Yes answer ID / SMS consent No answer ID Workday Question_Multiple_Choice_Answer IDs for the Yes and No choices. Both are required when the toggle is on; ingest is skipped if either is blank.
This does not write consent back to Workday. Leave the toggle off to keep candidate-level SMS consent.

​
Sync Settings

  • Sync Applicants While Job Paused When enabled, Tenzo continues syncing applicants from the ATS even while the job is paused in Tenzo.
  • Default Candidate Source / Excluded Candidate Statuses (provider-dependent) Control which candidates are eligible during sync.
  • Bullhorn tearsheet controls are documented below.

​
Workflow Steps (Workday)

On Workday integrations, many Candidate Flow outcomes also have matching Workflow Step fields (for example Invalid Contact Workflow Step, Max Attempts - No Interview Workflow Step). Use these instead of or in addition to stage fields when your Workday process is step-driven.

​
Bullhorn Tearsheet Sync (Bullhorn only)

When tearsheet sync is enabled for your organization, Tenzo pulls candidates from Bullhorn tearsheets during ATS sync. Configure which tearsheets are included under Admin → ATS Integrations → Configuration → Sync Settings.
  • Tearsheet sync scope controls which tearsheets Tenzo queries from Bullhorn:
    • Public only (default): sync non-deleted public tearsheets only.
    • Public + private for selected owners: sync all public tearsheets, plus private tearsheets owned by users on the allowlist below.
    • Selected owners only: sync tearsheets (public or private) owned only by users on the allowlist.
  • Tearsheet owner allowlist: search and select Bullhorn users when scope requires owners. Private tearsheets are only included if your Bullhorn integration credentials can access them in Bullhorn.
  • Tearsheet name pattern (optional): regular expression matched against each tearsheet name. Only matching tearsheets are synced; leave blank to include all tearsheets allowed by the scope filter.
  • Eligible for Tearsheet Sync (per job, in job Caller Settings): even when a tearsheet matches these filters, candidates are added only to jobs that have this setting enabled.