Fast Launch Digital · Community Operations Manager · August 2022–May 2025

← Back to Bhagya Rathnasekara’s portfolio website

A privacy-safe reconstruction of the operating workflows I used while managing day-to-day community operations for a paid crypto and finance education community with more than 500 members across Telegram and Discord.

This sample demonstrates paid-access checks, onboarding, self-serve support, member communication, moderation, escalation, and retention work. It does not reproduce live community content or disclose member information.

Selected operating record

500+ paid members in the community I managed.

Helped maintain approximately 90% paid-member retention through the 2023 downturn.

Helped reduce repeated support requests by roughly 60% through self-serve onboarding and knowledge resources.

Member operating system

1. Verify access — Confirm payment or referral status and manually review edge cases.
2. Orient the member — Share the welcome message, rules, first steps, and core resources.
3. Enable self-service — Keep FAQs, pinned resources, and archived updates searchable.
4. Check early signals — Use participation and support needs to identify confusion or early drop-off.
5. Support and moderate — Apply documented rules, preserve human review for exceptions, and escalate based on evidence.

Routine welcome, CAPTCHA, rules-acceptance, and saved-reply steps were supported by Rose Bot. Member support, moderation decisions, payment exceptions, and trust-and-safety cases remained human-reviewed.

The member education library

The support queue kept asking the same thing in different words: how do I actually do this? Not what to think about a market, but which button, which screen, in which order. That is a documentation problem wearing a support problem's clothes.