Questions we expect

Answers for trust, setup, privacy, and club fit.

The FAQ keeps the public story honest about what RomrHQ does, what it does not do, and why Telegram-first is an intentional launch choice.

Trust and permissions

The bot only works inside explicit club context.

RomrHQ is designed around bounded Telegram groups, club-scoped records, and operator permissions rather than broad self-service access.

Can any rider change records?

No. Rider submissions can be captured, but official attendance, distance, and member changes depend on the configured workflow and operator review.

Does the bot decide membership?

No. Readiness summaries show evidence against club thresholds. Leadership keeps promotion and membership authority.

Can it act in the wrong chat?

Group binding is part of the setup story so commands operate in the intended club and chapter context.

Privacy and records

The public funnel separates marketing leads from club operating data.

The launch site captures qualification and referral data. Club runtime data belongs to the operational product and should be handled separately from the marketing funnel.

What does the site collect?

Demo requests collect contact and club basics. Rider referrals can include role, leadership contact, and the operational pain needed to route the nomination.

What does the bot record?

The product records the club-scoped member, ride, attendance, distance, and readiness facts required by the operating workflow.

Is this public by default?

No. The product story is built around club-scoped records and private pilot conversations, not public profiles.

Setup and culture

Telegram-first is a constraint, not a shortcut.

RomrHQ is not trying to replace club culture or turn the chapter into a generic SaaS workspace.

Why Telegram instead of a new app?

The first product works where the validated club workflow already happens, which reduces adoption drag for riders.

How much setup is required?

A pilot should start with group binding, operator roles, member records, ride workflow, and readiness thresholds.

What is out of scope?

Public pricing, dues, voting, discipline, broad ERP, and WhatsApp-first support are outside the launch product.