Cadence Mandates
Control when, how often, and through which channels SI reaches out
What It Is
A Cadence mandate defines the rhythm of SI's outreach for a specific context. It answers the questions: How soon after a trigger event should SI make contact? Through which channel? How many times per day or week? What happens if the contact does not respond? When should SI stop?
Without a Cadence mandate, SI uses its own judgment to determine timing and frequency based on engagement signals. That works well in most cases. But some businesses have specific follow-up rhythms they need to enforce — a real estate agency that requires a call within two hours of a new listing inquiry, a SaaS company that limits outreach to twice per week during trial, or a financial advisor who must wait 48 hours between touchpoints for compliance reasons.
Cadence mandates give you precise control over these rhythms without removing SI's intelligence. SI still personalizes the *content* of each message — the cadence mandate controls the *when* and *how often*.
Why It Matters
Timing is one of the most sensitive aspects of business communication. Too frequent, and you annoy prospects. Too slow, and you lose them to competitors. The right cadence depends on your industry, your audience, the pipeline stage, and even the communication channel.
Consider a coaching business. During the discovery phase, a prospect expects quick responses — they are actively evaluating options. But once they have booked an initial consultation, daily emails feel aggressive. A Cadence mandate lets you define these rhythms explicitly: "After a consultation booking, wait 3 days before any follow-up. If no response, send one email. Wait 5 more days, then send one SMS. If still no response, create a task for the coach to call personally."
Without cadence control, you are relying entirely on SI's default timing — which is good, but may not match your brand's specific expectations or compliance requirements.
How It Works
When you create a Cadence mandate, Zyntro's AI structures your guidance into three components:
Triggers — The events that start the cadence sequence. A trigger might be a form submission, a missed call, a proposal view, or a pipeline stage change. Each trigger has conditions that must be met before the cadence activates.
Steps — The ordered sequence of actions SI should take. Each step defines the relative timing (e.g., "immediately," "after 2 days," "after 1 week"), the channel (email, SMS, phone, live chat), the action type (send message, place call, create task, update pipeline), a behavior hint for tone, and whether the step is mandatory or optional.
Global Rules — Overarching constraints that apply across all steps: maximum touches per day per channel, maximum total touches per contact, stop conditions (reply received, meeting booked, opt-out), and escalation logic (what happens when the cadence runs out without a response).
SI reads this schema before every outreach decision. If a Cadence mandate says "max 2 emails per week to nurturing contacts," SI will respect that limit even if its own engagement analysis suggests more frequent contact would be effective.
Examples
A real estate agency needs fast response to new listing inquiries
The mandate defines: Trigger = new form submission on listing pages. Step 1 = send personalized email within 15 minutes. Step 2 = SMS within 2 hours if no email open. Step 3 = phone call within 4 hours if no response to either. Global rule = max 3 touches on day one, then drop to 1 per day. Stop if the contact replies, books a viewing, or opts out.
A SaaS company limits outreach during free trials
The mandate defines: Trigger = trial activation. Step 1 = welcome email immediately. Step 2 = usage tip email after 3 days. Step 3 = check-in SMS after 7 days. Step 4 = upgrade conversation email after 10 days. Global rule = max 2 touches per week, stop if the contact upgrades or cancels. Escalation = if trial expires with no conversion, create a task for the account manager.
A financial advisor must maintain compliance spacing
The mandate defines: Trigger = any pipeline stage change. Global rule = minimum 48 hours between any outbound touchpoint, max 1 touch per channel per week, no phone calls after 6 PM in the contact's timezone. Stop conditions = DNC request, regulatory hold, or explicit opt-out. This mandate overrides SI's timing optimization to ensure compliance.
