Skip to main content

Documentation Index

Fetch the complete documentation index at: https://f4c7a9e2d8b1-docs.tenzo.ai/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

Tenzo enforces candidate consent before sending SMS or email messages. This ensures compliance with TCPA regulations and respects candidate communication preferences. Every outbound message passes through a consent check before it reaches the candidate. There are two levels of consent:
  1. All AI communications — a master switch. When disabled, outreach is not attempted with this candidate (call, SMS, email, etc.).
  2. Per-channel consent — SMS consent and email consent control whether each individual channel is available.

​
ATS Sync

Consent preferences are typically imported from the ATS when candidates are synced. For example, Bullhorn organizations can map opt-out fields so that SMS and email preferences reflect the candidate’s choices in the ATS. During a phone screen, Morgan reads a TCPA disclosure and asks the candidate for permission to send text messages. If the candidate opts-in Morgan enables SMS for the candidate. For Bullhorn organizations, verbal consent changes are written back to the ATS automatically. For other ATSes, verbal consent is stored in Tenzo and may be overwritten if the ATS syncs different values later.
Non bullhorn orgs should not use this feature until consent write back is built
Verbal consent only affects SMS. It does not change the candidate’s overall communication preference or their email consent.
When a candidate has not granted SMS consent, Tenzo falls back to email if all of the following are true:
  • The candidate has an email address on file
  • The candidate has granted email consent
  • Your organization has a connected email integration
If any of these are missing, the message is not sent. The email fallback itself is consent-gated — the system actively checks email consent before sending the fallback email. If the candidate has not granted email consent (or all-AI-communications consent is disabled), the fallback email is not sent either.
Email consent is a separate candidate field from SMS consent. It is typically imported from the ATS during candidate sync. There is no verbal consent flow for email — it can only be set via the ATS.
If no email integration is connected, candidates who have not granted SMS consent will not receive post-call follow-up communications.
If AI communication consent is disabled, no messages are sent via any channel.
Tenzo sends several types of email directly to candidates: thank-you emails, rejection emails, resume feedback emails, virtual interview links, job description emails, and job paused/resumed notifications. All of these check email consent before sending. When a candidate has not granted email consent (or all-AI-communications consent is disabled), the email is silently skipped — there is no fallback to SMS or any other channel.
For scheduled emails (rejection and resume feedback), a consent denial clears the scheduled send so it is not retried.

​
Line-Type Detection

Even when a candidate has granted SMS consent, Tenzo may still block SMS delivery based on the candidate’s phone line type. Before sending, the system checks the number against Twilio’s Lookup API and blocks messages to:
  • Landlines
  • Pagers
  • VoIP numbers (fixed and non-fixed)
  • Premium and shared-cost numbers
This check runs after the consent gate. If the line type is unknown or the lookup fails, the message is allowed through. Line-type results are cached for 30 days.
Line-type blocking does not trigger email fallback. It only affects the SMS send step. If a candidate’s number is a landline and they have no SMS consent, the email fallback logic (above) applies based on the consent check, not the line-type check.

​
SMS send (with email fallback)

Candidate SMS send requested
    │
    ├─ Overall communication disabled?
    │   └─ BLOCKED (no fallback)
    │
    ├─ SMS opted in?
    │   └─ Line-type check (landline, pager, VoIP, etc.)
    │       ├─ Blocked → SMS not delivered
    │       └─ Allowed → Send via SMS
    │
    └─ SMS not opted in
        │
        ├─ Web call?
        │   └─ BLOCKED (web calls have separate email flows)
        │
        └─ Phone call: attempt email fallback
            │
            ├─ Email not opted in?
            │   └─ BLOCKED
            │
            ├─ No email on file?
            │   └─ BLOCKED
            │
            └─ Email integration available?
                ├─ No  → BLOCKED
                └─ Yes → Send via email

​
Direct email send

Candidate email send requested
(thank-you, rejection, resume feedback, virtual interview,
 job paused/resumed, job description, no-answer)
    │
    ├─ Overall communication disabled?
    │   └─ BLOCKED (email not sent)
    │
    ├─ Email opted in?
    │   └─ Send email
    │
    └─ Email not opted in
        └─ BLOCKED (no fallback)
ATS activity logs reflect the channel that was actually used. If a message was sent via email fallback instead of SMS, the activity is logged as an email send.