Club
Create or select the club context.
The bot knows which club and chapter a command belongs to before operational workflows begin.
Workflow overview
Telegram stays the surface. RomrHQ keeps the record.
The operating model starts with the club's existing Telegram groups, then adds scoped commands, operator review, and structured records for members, rides, attendance, distance, and readiness.
Setup
The club context is explicit before commands matter.
RomrHQ does not infer public chats or let a random message mutate records. A president or operator binds the club and Telegram groups first.
Groups
Bind member and prospect groups.
Commands inherit the correct scope from verified Telegram group binding rather than brittle chat assumptions.
Roles
Delegate operator work safely.
Presidents keep visibility while trusted operators run the command-heavy parts of the workflow.
Workflow
Member and ride records move through reviewable steps.
The product is useful because it keeps operational facts structured while still respecting club judgment.
Members
Identity links and status changes are club-scoped.
Road names, Telegram identities, prospect status, and role history stay attached to the right club record.
Rides
RSVP and attendance belong to the ride.
Operators can announce rides, collect RSVPs, review attendance, and keep distance corrections visible.
Readiness
Progress is summarized from approved facts.
Readiness views use approved rides and distance totals without claiming promotion authority.
Workflow proof
See the Telegram operating loop before the demo.
The mockups focus on the records presidents ask about first: bound groups, member status, ride RSVP, attendance approval, and readiness evidence.
Proof block A
Club onboarding and group binding
Shows how a president binds the Telegram groups the chapter already uses.
/club_create iron-legacy Europe/Riga Iron Legacy MC
Club created. You are linked as PRESIDENT.
/chapter_bind members
Send /bind_chat K7Q4D2 in the members group.
Telegram binding code expires in 15 minutes
Members group Bound
Prospects group Waiting
Founder role President
- No public chat is guessed
- Same admin confirms in group
- Later checks trust the binding
Use on homepage setup proof and president-page trust section.
Proof block B
Member and prospect directory
Makes searchable member status, identity links, and role history feel concrete.
/member_review prospects
3 prospects need review. Ghost is missing Telegram link.
/member_link Ghost | provider=telegram | user_id=118245
Identity linked. Group check is now available.
Operators see the next safe action
Prospects 3
Linked identities 18
Role history Immutable
- Search by road name
- Profile facts stay club-scoped
- Role changes leave a trail
Use on buyer page where the story shifts from memory to trustworthy records.
Proof block C
Ride creation and RSVP flow
Shows ride planning without implying riders need a new portal.
/ride_create title=Coast Run | starts_at=2026-06-06T09:00:00+03:00
Ride scheduled. Members and prospects can RSVP.
/ride_rsvp Coast Run | status=yes
RSVP saved for Ghost.
Prospects allowed, 180 km, 2 points
Yes 18
Maybe 4
Pending 7
- Ride facts are structured
- Reminder target comes from bound groups
- RSVP is linked to member status
Use where the sales page explains Telegram-native ride coordination.
Proof block D
Attendance and distance approval
Proves the product protects records from unreviewed rider submissions.
/ride_attend Coast Run | note=rode sweep
Attendance submitted. Operator approval required.
/ride_distance Coast Run | distance_km=196
Distance override submitted for review.
Operator decisions before totals become official
Approved attendance 16
Pending reports 3
Distance overrides 2
- Rider facts stay pending
- Operators approve exceptions
- Totals update only after decisions
Use on president page where trust and record quality need visual proof.
Proof block E
Readiness summary
Shows progress toward local thresholds without pretending the bot approves membership.
/ride_history Ghost
Status: close. 26 approved rides, 2310 approved km.
Remaining: 4 rides, 190 km, 0 points.
Readiness is separate from final approval.
30 rides, 2500 km threshold
Ride progress 87%
Distance progress 92%
Approval state Not automatic
- Thresholds are club-scoped
- Progress is evidence only
- Promotion remains a leadership decision
Use anywhere the pitch needs to show readiness without overclaiming governance.
Operating principle
The bot records the workflow; the club keeps the judgment.
RomrHQ is deliberately not a governance engine, dues system, or broad club ERP. It handles the core operating trail for the pilot product.
No forced member portal
Riders can stay where the club already coordinates instead of adopting a separate application.
No automatic promotion
Readiness is evidence, and the final decision remains with leadership.
No self-serve pricing posture
The public funnel qualifies fit before a pilot conversation and packaging discussion.