Technical offboarding – Tezi

For 💼 Starter, Pro, Business, and Enterprise only

First, we’re sorry to see you go. If you have any feedback, we would love to hear it. Our team will ask for feedback live or over Slack during the offboarding process, and we greatly appreciate any thoughts that you share. We hope to reconnect in the future.

To begin offboarding, please reach out to Tezi Support. Our team will work closely with you to ensure a smooth offboarding experience that does not negatively impact your recruiting efforts or candidate experience.

When requested by Tezi Support, complete the following steps:

(Requires DNS admin permissions) Delete the DNS records that you added during Tezi onboarding. Exact records can vary by organization (confirm with Tezi Support), but typically, the relevant records are:

DMARC record for the hey.[yourdomain] subdomain: TXT record with the name _dmarc.hey or _dmarc.hey.[your domain]

MX record for the hey.[yourdomain] subdomain

Three CNAME records for the hey.[yourdomain] subdomain

(Requires Google Workspace admin permissions) Delete the max.tezi@[yourdomain] user in your Google Workspace

Google instructions

(Requires Google Workspace admin permissions) Revoke access for Tezi's Google Workspace app.

Go to Security -> Access and data control -> API controls -> Manage third-party app access.

Find the Tezi app and select Change access

Follow the Google instructions to revoke access

(Requires ATS admin permissions) If relevant, disable the ATS API key that you provided Tezi. It is most likely labeled "Max by Tezi (autonomous AI recruiting)" or a similar name.

Ashby instructions

Greenhouse instructions

⚠️

Do not complete these steps until requested by Tezi Support. Completing them early can disrupt active candidate communications and may cause Tezi to fall out of sync with your ATS while automations are still running.