Foundry Academy · Sales Development · Lesson 4 of 6

Ethical multi-channel cadence

Design a proportionate sequence that respects recipient choice, channel rules, timing, and human accountability.

Start the lesson

Your learning work, on this device

No signup, cloud storage, cross-device sync or verified completion. Saving is optional. This browser profile is shared with anyone who can use it; private mode, browser cleanup or storage limits may remove work. Use only fictional or non-sensitive material. Export a copy before relying on this device.

Not saved. Worksheets, answers and practice notes currently last only in this tab.

Practice markers are self-reported, never credentials.

01 · Explanation

Ethical multi-channel cadence

Objective: Design a proportionate sequence that respects recipient choice, channel rules, timing, and human accountability.

Define the cadence objective, approved audience, lawful and organizational basis, channels, sender, timing, frequency, content purpose, and maximum attempts before launch. Each step should add relevant information rather than repeat pressure. Coordinate email, phone, professional networks, mail, events, or referrals so a recipient is not contacted by several people without context. Apply time zones, business hours, account ownership, suppression, and current-customer rules. Test the actual system with internal records before activating prospects.

Stop or reroute the cadence after reply, opt-out, complaint, wrong person, legal restriction, closed account, active opportunity, or other defined event. CAN-SPAM applies to commercial email, including business-to-business email; calls and texts may implicate federal and state requirements that depend on technology, consent, number type, content, and context. This course cannot determine the legality of a specific campaign. Obtain qualified review and document the approved rules. Monitor delivery, replies, negative responses, opt-outs, complaints, and suppression failures—not only meetings. A high meeting count does not justify deception or ignored recipient choice.

Before you begin

  • Confirm the proposed fourteen-day cadence contains six emails, four calls, and two texts and lacks required operating controls.
  • Preserve the eight explicit prior opt-outs and quarantine the nineteen unapproved personal mobile numbers; individual records are not supplied.
  • No channel permission, schedule, activation, negative-path test, reply, referral, handoff, or outreach result is supplied.

Original overview module anchor →

02 · Compare the artifacts

Supported work. Visible uncertainty.

This is a fictional, sanitized training case using fabricated organizations and contacts. It contains no real personal or confidential data and is not legal, privacy, employment, or sales-results advice.

ClearBench ethical outbound pilot

ClearBench is a fictional supplier of modular quality-inspection workstations for small manufacturers. Leadership wants a four-week outbound pilot aimed at 120 companies in Utah and neighboring states. The proposed ideal-customer profile is plants with 25 to 250 employees, repeat inspection work, and a recent expansion, quality issue, or hiring signal. Research confirms 74 accounts meet all three fit indicators, 28 meet two, and 18 have no traceable trigger beyond industry. The list contains 162 contacts: 46 quality leaders, 39 operations leaders, 31 owners, 22 procurement contacts, and 24 people whose role is unclear. Twelve contacts left their listed employer, eight have explicit prior opt-outs, and 19 personal mobile numbers came from an unapproved list vendor. A draft email states that ClearBench will cut inspection time 40 percent, but the only evidence is one internal demonstration showing a 17 percent reduction under controlled conditions. The sequence proposes six emails, four calls, and two text messages over 14 days. It lacks channel-specific consent review, weekend restrictions, reply handling, and a stop condition after referral to another contact. Sales considers a meeting qualified whenever a prospect accepts a calendar invitation. Delivery specialists want a written problem, current process, stakeholder, urgency, and agreed next step before handoff. The pilot budget is $6,000, capacity is eight discovery calls per week, and only two specialists can conduct technical discovery. Learners must build a responsible account field, role research method, evidence-based message, controlled cadence, qualification handoff, and learning scorecard. The exercise does not promise response rates, revenue, or regulatory compliance; applicable outreach rules require qualified review.

Supported example — reference only

Milestone or date
Day 1 preflight — proposed
Deliverable
Run suppression and contact-source review before any proposed first touch.
Evidence
M04-I01 (F05, confirmed: eight prior opt-outs); M04-I04 (F09, confirmed: control gaps)
Owner
Sales process owner and authorized legal or privacy reviewer
Dependency
Record identities, suppression output, permitted channel, timing policy, and reviewer decision: not supplied.
Review gate
Every selected record must clear current suppression, source, channel, and contact-state controls.
Exception
Any opt-out, reply, referral, wrong contact, disqualification, or accepted handoff stops the sequence.
Status
Learner proposal — not activated

A well-handled evidence gap

Milestone or date
Text-message gate — date not supplied
Deliverable
Determine whether any text channel is permitted before including it in a cadence.
Evidence
M04-I02 (F06, confirmed: nineteen personal mobile numbers from an unapproved vendor)
Owner
Authorized legal or privacy reviewer and Sales process owner
Dependency
Affected records, approved source, channel permission, jurisdiction, consent evidence, policy, and review result: not supplied.
Review gate
Qualified reviewer documents permission and approved source before any text can be proposed for activation.
Exception
Quarantine unapproved mobile data; do not test or contact the number.
Status
Blocked — channel review required

Flawed approach — do not copy

Marking this fourteen-day cadence map “approved and complete” without the required evidence or reviewer is a flawed submission. Stop activation when suppression, source approval, channel permission, timing, reply handling, referral stop, wrong-contact handling, or owner is missing.

Repair: Rework the fourteen-day cadence map as an evidence-backed draft, not an approved result. Capture the proposed touch count, opt-out condition, unsupported mobile-source condition, and missing cadence controls with exact module input IDs. Map fourteen calendar days as a learner proposal, leaving exact send times and channel permissions pending. Add state-based stops for opt-out, reply, referral, disqualification, wrong contact, and accepted handoff before scheduling any touch. Check the revision against this requirement: The cadence represents fourteen days and supplied touch counts without treating timing or activation as approved. If the required evidence is still absent, keep the decision blocked and identify the missing input or authorized reviewer.

Full case record, ambiguities and all assignments →

03 · Bounded practice

Build the fourteen-day cadence map.

Design a multi-channel sequence with channel approval, suppression, stop rules, and exception monitoring.

Deliverable: A fourteen-day cadence map and negative-path test checklist.

Complete a bounded starter and gap analysis using only CB01, F05, F06, F08, F09, and the assignment-scope record below. Populate supported fields, label every unavailable field “not supplied,” and cite the input ID for each material statement. You may design a proposed template, control, question, or decision rule, but must label it as a learner proposal rather than observed case evidence. Do not contact people, access live systems, run tests, sign records, claim approval, or invent names, dates, quotations, transactions, results, or source documents.

Exact supplied inputs for this assignment
  • M04-I01 · F05 — Eight contacts have explicit prior opt-outs.
  • M04-I02 · F06 — Nineteen personal mobile numbers came from an unapproved vendor.
  • M04-I03 · F08 — The proposed fourteen-day cadence includes six emails, four calls, and two texts.
  • M04-I04 · F09 — The cadence has no documented channel review, weekend rule, reply handling, or referral stop condition.
  • M04-B01 · CB01 — Use CB01, the full versioned case brief printed once at the start of this packet, as a citable narrative source for details not normalized into F01–F12. Preserve its uncertainty language and do not treat narrative detail as approval, complete operational records, or professional judgment.
  • M04-S01 · F05, F06, F08, F09 — Build a starter version of “A fourteen-day cadence map and negative-path test checklist.” from the listed case facts. Treat requested structures, controls, questions, calculations, and templates as learner-designed proposals. Where an operational record or result is absent, add a gap entry naming the missing evidence and authorized owner instead of fabricating it.

Operating procedure

  1. Capture the proposed touch count, opt-out condition, unsupported mobile-source condition, and missing cadence controls with exact module input IDs.
  2. Map fourteen calendar days as a learner proposal, leaving exact send times and channel permissions pending.
  3. Add state-based stops for opt-out, reply, referral, disqualification, wrong contact, and accepted handoff before scheduling any touch.
  4. Define permitted-channel, weekday, time-window, spacing, owner, and escalation fields, marking all unsupplied policy decisions pending.
  5. Build negative-path tests for suppression, unsupported mobile data, wrong contact, reply, referral, and handoff without claiming execution.
  6. Route telephone, text, purchased-data, suppression, privacy, and jurisdiction questions to authorized legal or privacy review.
  7. Quality-check that every milestone has evidence, owner, dependency, gate, exception, and non-activation status.
Field-by-field guidance
Milestone or date
Use Day 1 through Day 14 or a named preflight gate; label timing as proposed unless supplied.
Deliverable
Name the proposed touch, suppression check, reply review, referral stop, or handoff gate.
Evidence
Cite the applicable M04-Ixx input and distinguish a supplied condition from a learner-designed control.
Owner
Use Sales process owner and authorized legal or privacy reviewer; no individual operator is supplied.
Dependency
Record required channel permission, policy, suppression, source approval, recipient state, or capacity evidence.
Review gate
State the observable precondition for advancing, such as clear suppression and permitted channel.
Exception
Specify the stop, quarantine, or escalation path for opt-out, reply, referral, wrong contact, or unsupported data.
Status
Use Proposed, Blocked, Quarantine required, Review pending, or Not activated.
Fourteen-day cadence map · learning draft
Milestone or dateDeliverableEvidenceOwnerDependencyReview gateExceptionStatus

Start with 6 rows; the complete workbook specifies 14 stable rows for this artifact. Add rows here or use the full download. No action is saved until you explicitly choose saving above.

Download complete six-module workbook (.md) · Structured case packet (.json)

Keep private client data, unpublished inventions, personal identifiers and credentials out of these public learning tools.

Module 4 · 2-item formative check

Ethical multi-channel cadence

Choose an answer and request feedback. Read why each option does or does not fit the evidence. Answers stay in this tab unless you choose device-only saving; they are never submitted.

Question 1 of 2 · MODULE 4 · knowledgeWhat should a recipient's opt-out trigger across an approved outreach workflow?
Question 2 of 2 · MODULE 4 · scenarioWhich control turns ClearBench's missing cadence rules into an observable stop-or-rework signal?

Answer either question to review its reasoning.

Inspect the artifact, not just your quiz answers

  • The cadence represents fourteen days and supplied touch counts without treating timing or activation as approved.
  • Opt-out, reply, referral, disqualification, wrong-contact, and accepted-handoff stops are explicit.
  • The unapproved personal mobile data remains quarantined, and no test or outreach result is fabricated.

Stop: Stop activation when suppression, source approval, channel permission, timing, reply handling, referral stop, wrong-contact handling, or owner is missing.

Go: Go to a tabletop negative-path review when all stops, gates, exceptions, ownership, and evidence-capture fields are documented.

Escalate: Escalate telephone, text, purchased-data, privacy, consent, and jurisdiction-specific outreach questions to qualified reviewers.

04 · Evidence to keep

Leave with usable work.

Cadence brief, channel approval, suppression rules, test record, owner map, stop-event log, and monitoring thresholds.

Download your artifact CSV and, if wanted, export the learning-work JSON above. Neither export is a reviewed submission or certificate. Device-only saving is optional; you must press Save my work now after edits.

When all six artifacts are ready, compare the full packet against the track rubric. Qualified human review is still required before real-world decisions.

Sales team discussing account strategy and outreach during an office meeting.
Learn the standard. Practice the work.
Business development professional holding a focused conversation with prospective clients.
Leave with evidence you can inspect.

Sources, scope and review boundaries

Curriculum 2026.10.08-learning-paths-1. External source dates below are record checks, not continuing guarantees. Verify current requirements before consequential use.

ftc-can-spam · Official guidance

FTC: CAN-SPAM Act Compliance Guide for Business

Primary guidance on commercial email identity, subject lines, advertising disclosure, postal address, opt-out, and vendor accountability.

Open reviewed external source ↗

fcc-47-cfr-64-1200 · Current codified text

eCFR :: 47 CFR 64.1200 -- Delivery restrictions.

Current codified FCC delivery restrictions. eCFR is authoritative but unofficial. Technology, consent, number type, content, context, state, and jurisdiction affect the applicable rule; obtain qualified legal review before configuring outreach.

Open reviewed external source ↗

fcc-one-to-one-consent-vacatur · Context only—not a positive rule

Insurance Marketing Coalition Limited v. Federal Communications Commission, No. 24-10277

FCC-hosted Eleventh Circuit opinion documenting vacatur of Part III.D of the 2023 order. Legal-status evidence only; it is not a positive instructional rule.

Open reviewed external source ↗

ws-sales-operating-control · Academy internal operating standard

Wealth Synergy sales-development internal operating standard

Academy-selected evidence, research, message approval, suppression, cadence, handoff, and metric controls. This is an internal operating standard selected by Foundry Academy; it is not law, accreditation, licensure, or an external-standard requirement.

Version 1.0 · reviewed 2026-09-01 · owner: Foundry Academy curriculum owner

A future Wealth Synergy private professional-development certificate would be issued only after its assessment, capstone, identity, reviewer, retention, access, deletion, appeal, and issuance controls pass quality review. No credential is currently issued. Any future certificate would not be an accredited academic qualification, professional license, or government certification.