How ATS integration 2.0 (beta) works – Tezi

For 💼 Starter, Pro, Business, and Enterprise using Tezi’s 🔗 ATS integration 2.0

With Tezi’s ATS integration 2.0 (beta), Max automates top‑of‑funnel work in Tezi and syncs candidates to your ATS when they’re ready for interviews or deeper evaluation. The integration helps you:

Fold Tezi-sourced and Tezi-screened inbound candidates into your existing process seamlessly

Track Tezi’s sourcing directly in your ATS

Avoid Max duplicating outreach to candidates who are already in your pipeline

Keep ATS inbound screening on autopilot with Max

Add new roles

Add new roles that are linked to your ATS through the following steps:

Select the Roles tab.

Select Add new role.

Enter a candidate-friendly job title. Tezi will use this title in sourcing outreach, scheduling emails, etc. if you enable those features.

Select the appropriate ATS role to link to.

(Optional) If available, provide the URL to your job description. Tezi will attempt to scrape your JD’s content from the URL as part of Tezi’s AI Max gathering context on the role. Tezi will also link to it in sourcing outreach.

Add the role.

After the role has been created, click ATS settings on your Role Setup page to configure how sourcing and inbound screening should sync with your ATS. See sections below for context on configuration.

👉

If your ATS integration 2.0 has just been set up, you may need to wait a few minutes to 6+ hours before adding roles so that Tezi can complete the initial data sync from your ATS. Initial syncs take longer for larger ATSs with more roles, candidates, etc.

Sourced candidates

Tezi automatically exports sourced candidates to your ATS once they’ve expressed interest.

In your role’s ATS settings, set an ATS stage that interested sourced candidates should be exported to. Note that, if you use Tezi for screening inbound candidates (see next section), Tezi-recommended inbound applicants will be synced to this Export stage as well.

After a sourced candidate responds with interest, Tezi automatically syncs them to the ATS Export stage. In Tezi, exported candidates are tracked in the Pipeline tab in the Exported stage.

Tezi’s export includes full context on the candidate—profile and contact info, all emails with Max, and the chat screen transcript when applicable—so you’re equipped to manage next steps in your ATS after the export.

With ATS integration enabled, Max also checks your ATS during sourcing and, to prevent redundant outreach, won’t contact any candidates already associated with the role.

⚠️

When selecting an Export stage, keep in mind any ATS automations (e.g., scheduling requests, emailed forms, etc.) that may get triggered when Tezi exports a candidate. To avoid unwanted automation behavior, you may want to create a new ATS stage for Tezi’s exports or disable existing automation rules.

Exceptions to automatic export behavior

While Max typically exports interested sourced candidates automatically, there are two exceptions:

If agentic replies are disabled for your role, Max won’t automatically detect interest from a candidate’s reply and therefore won’t automatically advance interested candidates to export. Instead, Max flags replies in Tezi, and you can review the message to decide whether the candidate should be exported.

If you’ve turned on chat screening for sourced candidates, the sync happens after they both express interest and complete the chat screen.

See the flowchart below for when interested sourced candidates are exported, depending on your configuration.

Click to expand

Inbound applicants

For inbound screening, Max imports applicants in your ATS, evaluates in Tezi, and then syncs evaluations back to ATS.

In your role’s ATS settings, set:

Inbound application stage: the ATS stage where Max should import inbound applicants from.

Export stage: the ATS stage where Max should advance recommended applicants after evaluation.

Note: If you use Tezi for sourcing (see prior section), interested sourced candidates will be synced to this Export stage as well.

After Max has evaluated applicants against your criteria:

Max advances good fits to the Exported stage in Tezi and to the ATS Export stage defined in your Tezi ATS settings. This happens within ~15 minutes of evaluation or, if you’ve configured chat screening for inbound, after the candidate submits the chat screen. When the candidate is advanced, Max also syncs all information on the candidate—its evaluation, any emails exchanged, and the chat screen transcript when applicable—so you have full context to manage next steps in your ATS.

For applicants who are not a fit, Max logs its evaluation to the candidate’s ATS activity feed, but does not move or reject them. Evaluations typically sync to the ATS within ~15 minutes of application, unless Max is working through a backlog. You can review Max’s recommendations in your ATS and take next steps as needed.

See the flowchart below for when applicants are exported, depending on your configuration.

Click to expand

You can still personally screen applications alongside Max. If you move an applicant to a new ATS stage (including rejecting), the candidate will advance to Exported in Tezi for tracking.

⚠️

If chat screening is enabled for inbound, use caution when screening applications. Applicants that Max invites to the chat screen remain in the ATS application review stage until they finish. Advancing or rejecting them during this window can conflict with Max’s chat screen.

Comparison with legacy ATS integration

Tezi’s ATS integration 2.0 dramatically reduces complexity for both users and Tezi, enabling streamlined, self-serve ATS integration and role setup. With these improvements, some legacy functionality is no longer available. See below for a detailed comparison.

Dimension	Legacy Integration	Integration 2.0
Sync behavior	- All candidates, stages, stage changes, and most relevant information (e.g., resumes, emails, etc.) are synced between Tezi and ATS, other than unresponsive sourced candidates for some ATSs - Two-way syncs happen on an ongoing basis with a delay of up to 30 minutes	Targeted syncs for specific candidates and stages: - Sourced: Sync from Tezi → ATS after an interested reply or, if enabled, after the chat screen. - Inbound: Imported from ATS → Tezi, evaluated in Tezi, then re-synced into ATS after evaluation or, if enabled, after the chat screen. All relevant information (e.g., resumes, emails, etc.) exported to ATS when the Tezi → ATS sync occurs
Visibility into Max’s automations	Full visibility into what Max is doing in both Tezi and ATS	While candidates are in top-of-funnel stages (i.e., outreach, inbound evaluation, chat screening), Max’s actions are visible only in Tezi Once candidates are synced from Tezi → ATS, Max’s historical candidate interactions and all other relevant information are available in ATS
Where you decision candidates	Lack of clarity on where to decision candidates. Decisions in either Tezi or ATS sync to the other, but some decisions are best made in Tezi due to limited information syncs, e.g., chat screen transcripts only available in Tezi.	Decision candidates in your ATS when they’re ready to advance to interviews. One exception: If you have disabled agentic replies, work with Max to respond to sourced candidates and advance them to chat screen in Tezi.
Interview scheduling with Max	Supported	Not supported because interview stages are not synced between Tezi and ATS
ATS integration setup	Typically a multi-day process for both the user and Tezi’s team	Self-serve using these instructions
Role setup	Adding new roles and activating Max (”go live”) requires Tezi team involvement, resulting in lags and slowness	Adding new roles and activating Max (”go live”) is self-serve and immediate

FAQ

Can I manually export candidates into my ATS?

Tezi automatically syncs candidates to your ATS as described above. To sync additional candidates manually, you can change the candidate’s stage to Exported, and then select any stage in your ATS to export to. The export will happen within 15-30 minutes.

All Tezi automations stop for a candidate when they are exported.