UX Notes: Matching Tea to State in a Telegram Bot

We built Tea Bro around one idea: people choose tea badly when they only chase taste notes. They choose better when they start from state — tired, anxious, need clarity, wind-down.

The flow

1. Name the state (or take a short test on the site).
2. Get a calm direction (softer profile, less leaf, not “max strength”).
3. Brew once. Optionally note one line after the cup.

No gamification. No 30-day streak. The win is a usable cup today.

Product decisions that mattered

• Softer beats stronger when the user is already exhausted.
• Evening ≠ morning — same leaf, different dose and timing.
• Deep links — bot points to concrete pages (bot hub, test, compass), not only the homepage.

Hub for the bot:

teabro-site.vercel.app/bot-tea-bro.html

State-oriented entry on the site:

teabro-site.vercel.app/kompas-sostoyaniya.html

For product people

Chat is a good trigger surface. A website is a good explanation surface. Split them on purpose. Keep the bot short; put the reasoning and guides on stable URLs you can link from every channel.

If you ship ritual tools, design for the tired evening version of the user — not only the motivated morning one.