Telegram menu button matches the user state
Change the menu button text or destination by language and user state, so the default entry point points at the next job instead of one generic webview.
Why this can grow a startup
Telegram gives bot owners a persistent launch surface beside the text input field. The docs go further than most teams do: they describe customizing that menu button for all users or specific users, changing the text by language, and linking different Mini Apps based on user settings. That turns the menu button into an onboarding and retention surface, not just a shortcut. A first-time user may need setup. A returning user may need the main workspace. One fixed button makes both groups do extra work.
Company example
Telegram's Mini Apps documentation says the menu button can be customized for all users or specific users, including changing button text by language or linking different Mini Apps based on a user's settings.
Source and metric
Source: Telegram Mini Apps
Telegram documents per-user menu-button customization, including language-specific text and settings-based destinations.
When to use it
Use this when Onboarding, Activation, Retention is relevant to telegram mini apps, menu button, personalization and you can run a bounded test with a low budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
Founder checklist
- Read Telegram Mini Apps and identify what is directly supported.
- Choose one channel context: Onboarding, Activation, Retention.
- Define the test around Telegram documents per-user menu-button customization, including language-specific text and settings-based destinations..
- Set an owner, evidence window, and stop condition before launch.
Explore the context
Apply this with an operator
Choose product surfaces that compound distribution without hiding weak activation or retention.