# 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.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/telegram-menu-button-matches-the-user-state/
- Source: [core.telegram.org](https://core.telegram.org/bots/webapps)
- GrowthDex source hub: [Telegram Mini Apps](/sources/telegram-mini-apps-core-telegram-org/)
- Last checked: 2026-06-09T04:07:00.000Z
- Rarity: rare
- Budget: low
- Channels: Onboarding, Activation, Retention
- Stages: telegram mini apps, menu button, personalization, first-run UX


## Why this can grow

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.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where telegram menu button matches the user state can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Onboarding and Activation channel.
3. Use the evidence from core.telegram.org to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed 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.

## Adjacent tactics in the same lane

- [Notion post-install database seeding before manual sharing](/growth-ideas/notion-post-install-database-seeding-before-manual-sharing/) - 3 shared channels
- [Telegram group add link requests admin rights up front](/growth-ideas/telegram-group-add-link-requests-admin-rights-up-front/) - 2 shared channels, 1 shared stage
- [Suggested prompts in the empty AI state](/growth-ideas/suggested-prompts-in-empty-ai-state/) - 3 shared channels
- [Telegram attachment menu install before habit ask](/growth-ideas/telegram-attachment-menu-install-before-habit-ask/) - 2 shared channels, 1 shared stage

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The Telegram Mini App should open where the habit already lives](/blog/the-telegram-mini-app-should-open-where-the-habit-already-lives/) - product-led growth, onboarding, brand trust

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.