Skip to main content
bthebigclass
Back to home
Real-time updates

Three channels. One pipeline.

Every meaningful event — a student tagging you, a new lead landing on your contact form, a recording finishing — fans out across in-app bell, email, and WhatsApp automatically. No webhooks to wire, no Zapier zaps to maintain, no missed notifications.

@-mentions that pull people into the conversation.

Tag a student or co-instructor in a batch post or reply. They get a louder "X tagged you in Cohort 7" notification — in-app, email, and WhatsApp — even if they weren't already in the thread. Click the chip in the published post to open their profile in a new tab.
  • Tag picker shows teachers first, members below — alphabetised
  • Tagged user gets a louder cross-channel ping than the regular broadcast
  • Clicking the chip opens the profile in a new tab
  • Self-mentions are silently filtered — no "X tagged themselves" noise
  • Tagging in replies works too — pulls a new person into an active thread
Notification bell

🔔 Dinesh tagged you in Cohort 7

"@Renu can you weigh in on this question? It's right up your alley."

Fanned out across · 🔔 In-app · ✉️ Email · 📱 WhatsApp

Broadcast notifications on every cohort post.

Drop a post in a Batch Common Room and every member gets a notification — in-app + email + WhatsApp (where they have phone numbers on file). Replies notify the post author plus everyone already in the thread. Tagged users get a separate louder ping so we don't double-notify them.
  • New post → notify every batch member except the author
  • Reply → notify post author + all prior commenters in the thread
  • Tagged users get the louder "X tagged you" notification, not the broadcast
  • Email goes via your SMTP; WhatsApp via the same transport as other workspace messages
  • Disable per-channel via the recipient's notification preferences
Broadcast

Dinesh posted in Cohort 7 · 12s ago

24 members will be pinged across:

🔔

24 in-app

✉️

22 emails

📱

18 WhatsApp

Mentioned users get a separate louder notification — no double pings.

Recording-ready emails — automatic.

Stop recording → LiveKit finishes encoding → file uploads to R2 → backend poller detects the URL → instructor gets a workspace-branded email titled "Recording ready — {class title}" with a Watch button. No manual share. No "hey did the recording come through?" chat-group message.
  • Polls every 15 seconds — instructor sees the email within a minute of stopping
  • Email is workspace-branded (your logo, your reply-to, your tone)
  • Watch button links to the inline player dialog on the class detail page
  • Same notification fans out to students if you opt-in
  • Failure → email surfaces the error message + a manual retry link
Email preview

Subject: Recording ready — Vedic maths · Squares

The recording for Vedic maths · Squares has been uploaded and is ready to watch.

Watch recording →

cdn.thebigclass.com/recordings/tbc-abc123/...mp4

Lead capture, instant alert.

A visitor fills your public contact form. The lead lands in the dashboard. You get an in-app + email + WhatsApp notification within 10 seconds — with the lead's name, message, and a one-click Reply button that opens the inbox composer. New leads are accent-bordered in the inbox so the eye lands there first — they're the most revenue-sensitive signal in the workspace.
  • Lead lands → workspace admins notified across all 3 channels
  • Accent-bordered row in the inbox surfaces it above routine items
  • Reply from the inbox auto-bumps status to "contacted"
  • Per-form routing — different forms can notify different admins
  • Webhooks (roadmap) for forwarding to your CRM
Inbox · new lead
New lead10s ago

Riya reached out

Hi — interested in your IGCSE Computer Science cohort. Is there an EMI option?

riya@gmail.comReply
Free to start

Ready to launch your own?

Pick your subdomain, drop in your logo, and you're live. No demo call. No credit card.