RC Open Jio

Problem Statement

There are many Interest Groups (IGs) in RC that are dying due to a lack of participants.
Additionally, RC life feels segregated, with students mainly mingling within their own RC circles.
A key reason is the absence of a shared platform for students from different RCs and interests to connect.

We propose a low-entry-barrier, easy-to-use platform with a comprehensive feature set to encourage inter-RC connectivity and help students with similar interests find one another.

Solution

Build a low-friction, Telegram-based “RC Open Jio” platform where students can:

Discover events by category and audience
Create and manage events easily
Join/leave events in one tap
Subscribe to categories for proactive notifications
Maintain profiles (name + RC) for better matching and relevance
Share events to other chats via inline Telegram sharing
Keep shared event cards synchronized across chats when participation changes

This lowers barriers to cross-RC interaction and helps IGs attract participants faster.

How It Works

Current prototype stack:

FastAPI webhook + cron endpoints
Telegram Bot API integration
Core conversation/state logic in bot workflows
PostgreSQL persistence and business rules
Notification outbox + async dispatcher
Schema for users, events, participants, subscriptions, and outbox
Shared-message tracking for cross-chat synchronization

System Flow

User message/callback arrives via Telegram webhook.
Bot normalizes input and routes to guided flows (create, edit, delete, list, profile, subscribe).
Data is written/read from Postgres (events, participants, RC profile, subscriptions).
Reminder jobs (24h/1h) are queued in the outbox and dispatched asynchronously via cron.
For sharing:
- users share event cards to other chats,
- shared message instances are tracked,
- join/leave updates can propagate across tracked shared copies for consistent state.

Privacy & Trust

In direct creator view, creators can see participant handles.
In shared event cards, participant handles are never exposed.
Participants generally see display names only.

Impact

More cross-RC mingling through discoverable, open events.
Faster group formation and better IG survival through visibility + shareability.
Reduced coordination overhead (one-tap participation + reminders).
Better event propagation: share-to-chat enables organic discovery beyond creator circles.

Feasibility

Core end-to-end workflow is already implemented (Telegram + FastAPI + Supabase).
Adoption friction is low (Telegram-first, no new app install).
Share + sync capability is already integrated and extensible.
Practical near-term enhancements are straightforward:
- analytics dashboard
- moderation tools
- smart recommendations
- user validation