Foundry Academy · CRM Operations · Lesson 3 of 6

Tasks, sequences, and follow-up

Operate timely follow-up without concealing automation, overriding recipient preferences, or creating unowned task noise.

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

Tasks, sequences, and follow-up

Objective: Operate timely follow-up without concealing automation, overriding recipient preferences, or creating unowned task noise.

A task should name the desired outcome, due time, owner, relevant context, and completion evidence. Define which events create a task, when ownership transfers, how overdue work escalates, and which outcomes close or reschedule it. Sequences can support consistent reminders, but every step needs an approved purpose, audience, channel, timing, sender identity, stop condition, and exception path. Test automation in a sandbox and prevent duplicate tasks when records re-enter a stage.

Respect consent, opt-out, do-not-call, frequency, time-zone, and channel rules that apply to the organization. Commercial email is subject to CAN-SPAM requirements, and calls or texts may be subject to federal and state requirements; obtain qualified legal review for the actual outreach program. Stop automated outreach when a recipient replies, opts out, becomes a customer under a different workflow, or raises a complaint. Human owners remain accountable for accuracy and tone. Measure useful outcomes such as time to first response and next-step completion, not activity volume alone. Retain enough history to explain actions without keeping unnecessary personal information indefinitely.

Before you begin

  • Confirm the missing reply, opt-out, disqualification, and opportunity stops plus integration-owner and token issues.
  • Treat the full-overwrite request as provisional and outside the automation test itself.
  • No task due dates, test execution, consent result, suppression result, or production activation is supplied.

Original overview module anchor →

02 · Compare the artifacts

Supported work. Visible uncertainty.

This fictional training case uses fabricated company and contact records. It contains no real personal or confidential data and does not provide privacy, legal, employment, or technology-vendor advice.

OrbitWorks CRM repair

OrbitWorks is a fictional business-to-business maintenance software company with 14 sales and service users. Its CRM holds 8,420 company records, 11,780 contacts, and 1,360 open opportunities. An audit sample finds 23 percent of open opportunities have no dated next step, 18 percent lack a decision-role contact, and 11 percent are assigned to former employees. Two pipelines use different meanings for qualified, yet both feed one forecast. Sales moves opportunities forward when a meeting is scheduled; customer success uses the stage only after a written problem and buying process are recorded. A marketing import of 2,100 contacts is waiting. The source contains 430 probable duplicates, 280 records without a documented marketing basis, 17 personal notes copied into a free-text field, and country values in nine formats. The proposed automation sends four emails and creates a call task, but it has no stop rule after opt-out, reply, disqualification, or opportunity creation. A dashboard reports a 72 percent win rate because it excludes closed-lost records older than 30 days. A regional manager requests administrator rights for all representatives to fix records faster. The CRM also has three integrations whose owners left the company; one export token has not been rotated in 19 months. Leadership wants a clean forecast by Friday and suggests overwriting all records from the import. Learners must design a controlled repair that improves lifecycle clarity, data standards, follow-up, stage evidence, reporting, permissions, and change management. They must minimize unnecessary personal data, preserve auditability, and avoid claiming that a configuration alone establishes lawful processing or accurate forecasts.

Supported example — reference only

Step or milestone
Stop sequence on recipient reply
Trigger or date
Any recorded reply event; event schema and timing not supplied.
Evidence and source ID
M03-I01 (F09, confirmed: no reply stop condition)
Owner
CRM process owner and data steward
Gate or threshold
Sequence must stop before another automated outreach action and create an owner review task.
Dependency or gap
Reply event mapping, task due rule, test result, monitoring, and activation approval: not supplied.
Status
Learner-proposed control — production blocked

A well-handled evidence gap

Step or milestone
Integration-owner-loss exception
Trigger or date
Integration owner departs or credential exceeds approved age.
Evidence and source ID
M03-I02 (F11, confirmed)
Owner
Authorized system owner
Gate or threshold
Automation pauses or routes safely until ownership and credential review are complete.
Dependency or gap
Integration identities, owner assignments, credential policy, token rotation, and test evidence: not supplied.
Status
Security and ownership gap open

Flawed approach — do not copy

Marking this automation specification “approved and complete” without the required evidence or reviewer is a flawed submission. Stop production activation if any consent, suppression, reply, opt-out, disqualification, opportunity, error, or owner-loss path lacks a passing test.

Repair: Rework the automation specification as an evidence-backed draft, not an approved result. Define the automation entry event, eligible population, owner, purpose, and data prerequisites. List reply, opt-out, disqualification, opportunity creation, error, and owner-loss as mandatory stop or exception conditions. Specify task creation, due-date logic, monitoring queue, and fallback for every stop condition. Check the revision against this requirement: All required stop and exception conditions appear in the specification. 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 automation specification.

Redesign the sequence so work stops or changes when the record state changes.

Deliverable: An automation specification with triggers, stop rules, owners, and test cases.

Complete a bounded starter and gap analysis using only CB01, F09, F11, F12, 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
  • M03-I01 · F09 — The follow-up automation has no reply, opt-out, disqualification, or opportunity stop condition.
  • M03-I02 · F11 — Three integrations have departed owners and one export token is nineteen months old.
  • M03-I03 · F12 — Leadership proposes a full overwrite to produce a clean forecast by Friday.
  • M03-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.
  • M03-S01 · F09, F11, F12 — Build a starter version of “An automation specification with triggers, stop rules, owners, and test cases.” 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. Define the automation entry event, eligible population, owner, purpose, and data prerequisites.
  2. List reply, opt-out, disqualification, opportunity creation, error, and owner-loss as mandatory stop or exception conditions.
  3. Specify task creation, due-date logic, monitoring queue, and fallback for every stop condition.
  4. Create negative-path tests for consent, suppression, reply, opt-out, wrong owner, integration failure, and duplicate execution.
  5. Keep all test results not supplied and block production activation until authorized evidence exists.
  6. Route departed integration ownership and aged token review to the authorized system owner.
  7. Quality-check trigger, source, owner, threshold, stop behavior, evidence capture, rollback, and no implied activation.
Field-by-field guidance
Step or milestone
Name one automation event or control, including entry, action, stop, exception, or review.
Trigger or date
State the observable trigger; mark due-date calculation not supplied when absent.
Evidence and source ID
Cite M03-I01 for missing stops or another scoped input for ownership/change risk.
Owner
Use CRM process owner, data steward, or authorized system owner.
Gate or threshold
Define the condition that stops, routes, retries, or blocks production.
Dependency or gap
Record missing policy, consent, suppression, due date, test evidence, owner, or token review.
Status
Use Proposed control, Missing stop, Test pending, Security review, or Production blocked.
Automation specification · learning draft
Step or milestoneTrigger or dateEvidence and source IDOwnerGate or thresholdDependency or gapStatus

Start with 2 rows; the complete workbook specifies 2 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 3 · 2-item formative check

Tasks, sequences, and follow-up

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 3 · knowledgeWhich follow-up automation is safest to activate in a governed CRM lifecycle?
Question 2 of 2 · MODULE 3 · scenarioHow should OrbitWorks address the proposed overwrite while its follow-up automation lacks stop conditions?

Answer either question to review its reasoning.

Inspect the artifact, not just your quiz answers

  • All required stop and exception conditions appear in the specification.
  • Task timing, monitoring, and negative-path evidence requirements are explicit.
  • No test, suppression, consent, or production result is fabricated.

Stop: Stop production activation if any consent, suppression, reply, opt-out, disqualification, opportunity, error, or owner-loss path lacks a passing test.

Go: Go to sandbox testing when trigger, stop logic, task, owner, evidence capture, and rollback are defined.

Escalate: Escalate consent, privacy, integration ownership, credential, and production activation to authorized owners.

04 · Evidence to keep

Leave with usable work.

Sequence brief, task-trigger map, approval record, test cases, suppression rules, opt-out handling, and monitoring dashboard.

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.

Customer operations team discussing data and lifecycle information in a meeting.
Learn the standard. Practice the work.
Revenue operations colleagues coordinating a shared customer workflow.
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.

nist-privacy-framework · Official guidance

NIST Privacy Framework

Primary voluntary framework for identifying and managing privacy risk, governance, data processing, communication, and protection.

Open reviewed external source ↗

ftc-can-spam · Official guidance

FTC: CAN-SPAM Act Compliance Guide for Business

Primary compliance guidance relevant to commercial email workflows and opt-out handling in CRM systems.

Open reviewed external source ↗

ws-crm-operating-standard · Academy internal operating standard

Wealth Synergy CRM operations internal operating standard

Academy-selected lifecycle, field, queue, stage, dashboard, change, and review 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.