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:- All AI communications — a switch that gates AI-driven calls. When disabled, calls are not attempted with this candidate. It does not gate SMS (controlled solely by SMS consent) or email (controlled solely by email consent).
- Per-channel consent — SMS consent and email consent control whether each individual channel is available.
How Consent Is Set
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.Verbal Consent (SMS Only)
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. Verbal consent gathering is gated per organization: it only happens when theON_CALL_SMS_CONSENT feature flag is enabled for the org (off by default, so it is off for all orgs until explicitly turned on). It also only applies to phone calls — Morgan never gathers verbal SMS consent during web call interviews, even for orgs that have the flag enabled.
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.
Verbal consent only affects SMS. It does not change the candidate’s overall communication preference or their email consent.
What Happens When SMS Consent Is Missing
When a candidate has not granted SMS consent, SMS messages are not sent. There is no automatic conversion of SMS content into email. Email outreach to the same candidate uses dedicated email tasks instead — for example voicemail/no-answer template emails (failedCallEmail), virtual interview invites, companion first-touch outreach emails, or email-only outreach when call and SMS consent are both missing.
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.
What Happens When Email Consent Is Missing
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, the email is silently skipped — there is no fallback to SMS or any other channel. Email is not gated by all-AI-communications consent; only email consent governs whether these emails send.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
- Fixed VoIP numbers (non-fixed VoIP, e.g. Google Voice, can receive SMS and is allowed)
- Premium and shared-cost numbers
Line-type blocking only affects the SMS send step. It does not trigger email delivery.
Consent Decision Flows
SMS send
Direct email send
Related Pages
- SMS Registration — A2P 10DLC registration for SMS compliance
- Email Integration — connecting your email for candidate communication