Most of the pain in a multi-cohort WhatsApp operation is not "which feature to turn on." It is "what state is this person in, and who is allowed to change it." A buyer who paid five minutes ago, a student in week four, a person whose access ends tonight, and a former student who should already be out are four different states. If the team treats them as one list of names in a group, the wrong action looks reasonable.
This piece walks through a practical state model and maps each transition to something a person does or something 9bot can apply. The surrounding product guidance is the 9bot page on automation for course creators. You evaluate 9bot for seven days on a paid plan. The company is independent and has no official relationship with Meta or WhatsApp.
A state model you can actually operate
Keep the names boring and visible in your support board:
| State | Meaning | Who may enter this state |
|---|---|---|
awaiting_payment |
Interested, not entitled | Checkout, not the group |
entitled_not_in_group |
Paid (or complimentary access granted), still outside | Checkout or support |
active |
Inside a cohort room, access still valid | Admission rule |
notice_pending |
Still inside, expiry notice already due or sent | The access clock |
removed_expired |
Taken out because the period ended | The access clock |
removed_other |
Taken out for a refund, chargeback or policy breach | Support or moderation |
excepted |
Admin or allowlisted, skipped by automatic removal | Named owner of the list |
Launch groups sit to the side. They are for people who have not bought yet, so they should never be the place where paid material and classmate numbers live. Renewal communities are a later state of entitlement, not a leftover seat in the old cohort room.
Transitions and owners
Payment confirmed to entitled, not yet inside. The source of truth is the checkout. The group should not invent a seat because someone sent a screenshot. Automatic admission in 9bot can approve join requests with filters and a daily cap, which is how you keep a launch rush from becoming an open door. The daily cap is a safety valve, not a sales tactic.
Entitled to active. A standard welcome should carry the rules of that room. This is also the moment to make sure the person landed in the correct shard of the cohort, not in last season's group that was never closed.
Active to notice_pending. Timed access in 9bot can warn before the period ends. The copy should say what happens on the last day and where renewal is handled. Put payment questions on a private support channel. The cohort is a classroom, not a billing desk.
Notice_pending to removed_expired. After the period you configured, 9bot removes the member and skips admins plus anyone on the exception list. The panel looks for overdue access every five minutes, so "tonight" means the job will run shortly after midnight plus that cycle, not at an exact second. Tell support that, or they will think the tool failed.
Refund or chargeback. This is removed_other. Do not wait for the original end date. A person who is no longer entitled should leave the room the same day the finance team records the reversal.
Exception list. Keep it short. A teaching assistant who needs to stay after the cohort closes should be an explicit exception, reviewed when the intake ends. An exception that nobody owns becomes a permanent seat.
What the bot should not do
The bot should not invent an entitlement, extend a deadline or decide a refund. Those are human decisions that then update the record. Custom commands such as .classes and .certificate can answer logistics. Scheduled and recurring messages can carry live-session reminders and cart-opening notices. Antispam, the link filter and banned words can keep a launch room from becoming a noticeboard for other people's offers.
When a command needs a system you own, 9bot may call that system with an outbound HTTP method (GET, POST or PUT) toward a checkout, a CRM, or an orchestrator you already use. Validate input on your side and never echo a payment status that includes personal data back into the shared chat.
A last-day runbook in six lines
- Confirm that the access window set in the panel is still the window you sold, including any extensions already granted.
- Confirm the notice went out (or go out now, if this intake was configured late).
- Confirm two company admins are still in every shard, and that the ops line used by the bot is separate from the creator's everyday handset.
- Review the exception list and remove names that were only needed during the intake.
- After the cycle, sample a few expired people and confirm they are no longer in the room.
- Export the period report (entries, departures, who was active in the window, who went quiet for a week) and keep it with the cohort record.
If a shard still holds people whose access ended, treat it as a broken transition, not as "we will clean it later." Later is how last year's buyers keep watching this year's live links.
The state model is useful only if the team can point to a person or a job for every arrow. 9bot covers the arrows that should not depend on memory. The rest stays with support, finance and the community manager.

Top comments (0)