Telegram Platform Reference¶
UCCA Knowledge Base | External Services | Messaging Version 1.0 | 2026-03-05 | Confidential
1. Account¶
UCCA operates a single Telegram account registered via Hush US number (+1 646-809-3511). The account was created 2026-03-05 specifically to manage UCCA bots. BotFather is used to create and manage all bots.
| Field | Value |
|---|---|
| Account Phone | +1 646-809-3511 (Hush US number) |
| Account Type | Personal account — used as bot owner only |
| BotFather | t.me/BotFather |
| Created | 2026-03-05 |
Note
Telegram requires a personal account to own bots. Hush number was used to keep Tim's personal AU mobile off Telegram entirely. Bot tokens are the only credentials that matter — the account phone is just the owner identity.
2. Bots¶
| Bot Name | Username | Purpose | Entity | Wrangler Secret | Status |
|---|---|---|---|---|---|
| UCCA Platform | @UCCAPlatformBot | Ops/admin alerts, deployment notifications, internal team comms | UCCA Inc | TELEGRAM_PLATFORM_BOT_TOKEN | Created 2026-03-05 |
| RTOpacks | @RTOpacksBot | Customer interactions, credential delivery, admin/power user queries | UCCA Australia | TELEGRAM_RTOPACKS_BOT_TOKEN | Created 2026-03-05 |
3. Wrangler Secrets¶
| Secret Name | Worker | Status |
|---|---|---|
| TELEGRAM_PLATFORM_BOT_TOKEN | ucca-ops | Set 2026-03-05 |
| TELEGRAM_RTOPACKS_BOT_TOKEN | ucca-ops | Set 2026-03-05 |
Note
Bot tokens are not stored anywhere except wrangler secrets. If a token needs to be rotated, use /revoke in BotFather then run: npx wrangler secret put <SECRET_NAME> --name=ucca-ops
4. Security Note¶
Telegram regular chats and bot interactions are NOT end-to-end encrypted by default. Only 'Secret Chats' are E2E encrypted. Bot API traffic is server-side encrypted (Telegram servers can read it).
This is acceptable for UCCA's use case because:
- Platform bot — ops alerts only, no sensitive personal data
- RTOpacks bot — credential delivery uses cryptographically signed PDF, not plaintext message
- Customer identity verification uses OTP via separate SMS channel, not Telegram
5. Outstanding Tasks¶
| Task | Priority | Owner |
|---|---|---|
| Build UCCAPlatformBot webhook handler in ucca-ops worker | P1 | Alex |
| Build RTOpacksBot webhook handler in rtopacks worker | P1 | Alex |
| Set Telegram webhook URLs via Bot API after workers deployed | P1 | Alex |
| Implement ops alert integration (deployment, health, billing alerts) | P2 | Alex |
| Implement RTOpacks credential delivery flow | P2 | Alex |
Version History¶
| Version | Date | Change | Author |
|---|---|---|---|
| 1.0 | 2026-03-11 | Converted from telegram-reference-v1.0.docx | Claude Code |