Technical brief: seven days of silence as a leading indicator in paid cohort groups

Abstract

Course companies that run cohorts in WhatsApp groups learn about dropout late, usually when the access period ends. This brief examines a single, cheap signal available during the course: the list of members who sent no message in the previous seven days, as exposed by 9bot Reports. It argues the signal is useful only when joined with course platform progress and when it triggers a staged response (group first, person second). It reports no original data. Operational detail is in the 9bot article on student community retention. 9bot is a commercial, paid product with a seven day trial, unaffiliated with Meta.

Problem statement

Completion is a lagging outcome: it is known only after the course closes. Teams need a leading indicator that is (a) observable weekly, (b) available per cohort group, and (c) cheap enough to review by hand. Group silence meets all three. Its weakness is specificity: a student may be silent and progressing.

Signal properties

Property Seven day silence Course platform progress Combined
Frequency Weekly Depends on platform export Weekly
False positives High (quiet but studying) Lower Low
Cost to review Low Medium Medium
Who can act on it Community manager Coordinator Both, then tutor

Architectural controls

  1. Join before acting. Silence alone never triggers private contact.
  2. Stage the response. First an easy milestone in the group (for example a ten minute exercise) and a poll on blockers; then, for those still silent and stalled, a tutor's private message.
  3. Keep the human step human. 9bot does not message inactive students privately; it covers the group side (messages, commands, moderation, reports, timed access).
  4. Close with notice. Before anyone is removed, the timed access feature sends a warning, which preserves a renewal or extension option.

Strategic decisions from engagement data, 9bot

Operational checklist

  1. Same weekday, same hour: pull the seven day inactive list per cohort.
  2. Join with progress; discard students who are advancing.
  3. Post the group nudge on the scheduled slot.
  4. After a week, assign remaining cases to a named tutor.
  5. Log exits before the end from Reports.
  6. At close, compute completion (finishers divided by enrolled) and compare with a cohort that ran without the routine.

Evidence and limits

Evidence comes from one paper (Frontiers in Education, 2024) whose 309 respondents, all near graduation, used groups their institution administered. Satisfaction there rose with reciprocity, with the quality of information and with the quality of service, and it was the strongest companion of wanting to continue. Completion was outside its scope, so the indicator in this brief is a monitoring aid, not a validated predictor.

References to the 9bot ecosystem