Telegram Concept Mockup

Make the bot feel like a place, not a pile of buttons.

The problem is no longer the wording. It is the surface. Inline keyboards still force the user to scan too many rows, remember which upload they opened, and mentally reconstruct state from scattered messages. The cleaner direction is a Telegram Mini App workspace, with a lighter hybrid fallback for moments that should stay casual in chat.

Best for
Dense review flows
Casual fallback
Chat + quick chips
Recommended path
Hybrid first

Basic Chat

Current direction

Mini App

Cleanest flow

Hybrid

Recommended

Richer Telegram options that still feel casual

Chat-only

Inline Keyboards, But Smaller

Keep chat native, but only show one upload card at a time and edit that message in place instead of stacking new ones.

  • Good for quick confirmations.
  • Still weak once mapping or split-account review gets dense.
Chat-only

Reply Keyboard As A Mode Switch

Use temporary bottom-sheet style reply buttons like “Newest upload”, “Review next”, “Ask advisor”, then remove them after the action.

  • Feels lighter than command lists.
  • Still not enough for multi-card workflow.
App entry

Menu Button / Attachment Mini App

Keep the bot conversational, but open a proper workspace when the user taps “Workspace” or “Review uploads”.

  • Best for mapping, status, and account separation.
  • Lets you design a real stepper, sheet, and queue.
Best mix

Hybrid Narrative + Workspace

Chat delivers the story and alerts. The Mini App handles anything with more than one decision, more than one file, or more than one data object.

  • Feels casual until the user needs depth.
  • Prevents the “button spreadsheet” problem.