Help

A new user finds or is given the bot's Telegram handle and taps "Start". The bot detects this is an unrecognized account.

Since the Telegram account isn't linked to any identity, the bot responds asking the user to identify themselves.

The user types their name. The bot uses smart extraction to parse it — so replies like "I'm Mike", "call me Sarah", or just "Mike" all work.

The bot saves a pending approval request and notifies the admin. The user gets a confirmation that they need to wait.

The admin opens the Approvals page in the dashboard. They see the pending request with the claimed name, Telegram contact, and can either link to an existing seat or create a new one.

On approval, the user's Telegram ID is automatically bound to the selected identity. Their role and permissions take effect immediately.

The bot sends the user a message confirming they're approved. From now on, all messages from this Telegram account are routed through the normal pipeline with proper identity and permissions.

The user sends the sandbox join code (e.g. "join gentle-government") to the Twilio WhatsApp sandbox number from their phone. This registers them as a sandbox participant.

Once joined, the user sends a message to the sandbox number. The bot detects the WhatsApp number isn't linked to any identity.

Same as Telegram -- the bot responds asking the user to identify themselves. Smart name extraction handles natural replies.

The user replies with their name, the bot creates an approval request, notifies the admin, and the admin approves via the dashboard. The phone number is linked to the identity.

Once approved, the WhatsApp number is bound to the identity. All subsequent messages flow through the normal pipeline with proper permissions.