WhatsApp Upgrade

What happens when group membership and message routing break?

• SBC's View

  You manage group memberships manually.
  As class offerings overlap, students end up in 4+ groups.
  Routing announcements correctly becomes a chore you have to think about.
  One wrong group assignment = student shows up to the wrong venue, wrong time.

  5

  min per announcement

  50+

  messages/week
• Students' View

  You're enrolled in Bachata 101, Sensual, and a workshop.
  Same venue info, different times, posted to multiple groups.
  You see the announcement for Bachata 101 in the workshop group too—same class, different time.
  You show up to Monday's venue on Wednesday.
  You miss the last-minute location change because it landed in a group you don't check.

  47

  messages/week

  4+

  overlapping groups
• The Breaking Point

  Every announcement requires you to decide which groups get it.
  Manual routing errors compound as enrollment grows.
  Students miss classes or show up to wrong venues.
  No visibility into what actually reached whom.

  Your system works now at small scale. But as SBC grows, manual group management becomes impossible—and every routing mistake costs you.

Stop routing announcements manually.
Enroll students once. Tier-based routing handles the rest.
Every student gets exactly the messages for the classes they're taking.

• Enrollment-based routing — Announce once. Cloud API automatically routes to the right groups based on student tier (Bachata 101, Sensual, Workshop, etc.). No manual group assignments per announcement.
• Scheduled messaging — Reminders fire automatically (1 day before, 1 hour before, morning-of). Set it once, system runs it forever.
• Visibility — See who got what announcement, who opened it, who responded. Know exactly what landed and what was missed.

Enrollment-based routing eliminates manual group management.
Cloud API handles the distribution—no new platforms, no friction.

How Henrique's day-to-day changes:

Right now, everything—pricing, schedule, policies, announcements, reminders—lands in a single WhatsApp message.
Students scroll past it.
Information gets lost.

A rebalanced communication strategy routes information by urgency and type:

• WhatsApp — Time-sensitive (class reminders, announcements, 1-hour-before notices). Immediate, mobile-friendly, always-on.
• Dashboard — Student view of their data (upcoming classes, attendance, progress). Opt-in, searchable.
• Calendar (.ics) — Fixed events (class dates, workshops, registration deadlines). Sent via WhatsApp, syncs to student calendar.
• Email — Reference material (enrollment confirmation, policy updates, receipts). Archival-grade, not urgent.

Each channel does one job well.
Students stop missing announcements because they're not buried in noise.

Long messages overwhelm.
WhatsApp isn't designed for walls of text.
Break information into single-idea messages, sequenced for clarity and action.

Result: Each message has one purpose.
Students don't skip them.
They know: what, when, where, why, and what to bring.
Fewer "where is class?" questions.
Higher show-up rate.

• ~Week 1–2
  • Enrollment-based routing live
  • Stop making manual group routing decisions
  • Students get right messages for classes they're in
• ~Week 3–4
  • Scheduled reminders running (1 day, 1 hour, morning-of)
  • Show-up rates climb (students know exactly where to be)
  • "Where is class?" questions drop sharply
• ~Week 5+
  • Visibility into what reaches students (open rates, response rates)
  • Identify at-risk students (low engagement, cooling off)
  • System scales with SBC growth—no new overhead

You save ~3 min per announcement (~2.5 hours/week).
No routing confusion. Students show up to the right class. You focus on teaching and community.