Case study — ClaimYour.Gold
A programme inside the messenger, not beside it
- Scale
- A live Telegram mini-app and bot surface in continuous production.
- Identity
- Shared with the web product
- Channel
- Telegram, live
- Status
- Live in production
The challenge
The audience for this programme opens Telegram daily and installs almost nothing else. A mini-app that required a separate sign-up would have started most people over, and a bot with no state would have felt like a toy rather than the product.
The approach
Shared identity, not a parallel account
The mini-app authenticates against the same identity service as the web product, so a participant’s progress is one record regardless of which surface they opened.
Commands with real state behind them
Bot commands read and write the same engagement services the web product uses, rather than a simplified shadow of them.
Notification discipline
Lifecycle and re-engagement messages are rate-limited deliberately — the fastest way to lose a messaging channel is to abuse it, and this is the channel a licensee cannot easily replace.
The outcome
The surface has run in production without a second identity system appearing behind it, and the notification discipline has kept the channel healthy rather than triggering platform throttling.
The platforms this evidences
Considering something similar?
The capability above is licensable independent of this engagement — see the platform page for what is and is not white-labelled.