Practice Task

Practice: Design lead follow-up reminder rules

Use the supplied sales-lead sample to design reminder rules and message examples.

Back to practice tasksEnter task room
Practice typeRealistic client scenario · no cash reward
SubmissionsOpen practice; every contributor can submit their own version
Review outcomePass: +30 Trust Points. Revision or not passed: no points until fixed.
Current statusOpen
Practice boundaryRead the exercise here; submit and revise in the task room

The brief is not the submission area

This page gives the customer scenario, source material, deliverables, review criteria, and suggested format. Formal practice submissions, files, revision notes, and review outcomes belong in the task room so each attempt is auditable.

Exercise brief

Use this page to understand the scenario, assumptions, source material, deliverables, and pass/fail criteria before working.

Task room

Submit the completed result, upload supporting files, send clarification messages, and resubmit a new version if revision is requested.

Reusable practice

There is no participant quota. Multiple contributors can submit, and each version is reviewed against the same criteria.

Review record

Outcomes are pass, revision needed, or not passed. Only a passing version earns Trust Points or case-review eligibility.

Client Scenario

What problem are you solving?

A 12-person B2B sales team keeps leads in a spreadsheet. Reps often forget high-intent follow-ups after demos and proposals, so the owner wants to review the rules before connecting any real sheet or messaging system.

System Context

Use these assumptions

Assume the client may later use Google Sheets, Feishu Sheets, Excel, email, Feishu, or WeCom. Do not log into a real system or write automation code for this practice. Design the rules, fields, exception handling, and message copy.

Source Material

Base your work only on this material

lead,stage,last_contact_days,interest_signal,owner,next_step
Acme Parts,demo_done,5,asked for price,Alice,send quote
BluePeak,new,0,downloaded whitepaper,Bob,qualify need
Chen Studio,proposal_sent,9,asked for discount,Alice,follow up decision
DeltaOps,demo_done,12,no reply after demo,Chris,send recap
EastMart,qualified,3,asked integration question,Bob,answer technical question
Faro Lab,proposal_sent,1,waiting finance review,Chris,check next week
Deliverables

What to submit

  • Reminder rule table with trigger, recipient, timing, and message
  • Field explanations
  • At least four message examples
  • Exception handling for missing owner, blank last_contact_days, or unknown stage
  • Questions the client must confirm before automation is connected
Review Criteria

What makes a result pass review

  • Use only the supplied sample fields
  • Cover demo_done, proposal_sent, qualified, and new stages
  • Every rule must be triggerable from table fields
  • Do not claim a live CRM, email, or chat integration exists
  • Message examples must be client-readable
Submission Format

Recommended format

  • Start with the rule table
  • Then include message examples, exception handling, and confirmation questions
  • Markdown tables, CSV, or structured text are all acceptable