The intended Telegram experience

A target user journey for a managed conversational agent.

Status: target experience, not a released feature set.

The planned interaction model starts in a Telegram conversation. A person should be able to state a task plainly, understand when the system needs more context or approval, and receive a concise final result.

Target journey

1. Start with one useful task. The first interaction explains a concrete example rather than presenting a wall of settings.
2. Acknowledge quickly. The system confirms that it received the request and names any immediate ambiguity.
3. Show meaningful progress. Status changes communicate a real stage, wait state, warning, or final outcome—not a stream of decorative updates.
4. Ask before external effects. If an action requires a source, permission, or change, the person sees the relevant scope before it happens.
5. Return a result that stands alone. The final message should remain understandable even if a richer interface is unavailable.
6. Extend context deliberately. Preferences and memory are proposed as specific, reversible additions rather than silently accumulated.

Mini App role

A future Mini App may provide a re-openable surface for task status, settings, consent, and complex artifacts. The chat remains the primary place to state intent and receive a handoff.

What this page does not promise

It does not assert that the described task states, integrations, consent controls, or Mini App routes are available today. Each must pass an implementation and release gate before it is published as a current capability.