Customer notifications and self-service account settings

Prerequisites and authority

Use the official organization interface. Customer procedures need account ownership; provider configuration and manual grants need authorized operator access.

Notifications and account settings

Open the in-app notification history to review notices, unread count and available read controls. A supported notification action may open the associated device/setup workflow.

In-app notices are available through the application. This scope does not promise browser or operating-system push while the app is closed. Telegram delivery is a separate channel and can arrive independently when supported/configured.

Review active/expiring/expired subscription notices, device/account notices and supported Wi-Fi or maintenance events. A notification describes an event; check the authoritative subscription or connection record before treating it as the current status.

There are no customer per-category notification opt-out controls in the agreed scope. Do not add preference instructions or implied push permissions to the guide.

Use account settings to review profile and supported password/session controls. Complete password changes through the official form and keep recovery information current. Phone-number self-service is not established; contact support rather than creating a second identity.

If Telegram delivery fails, in-app history may still contain the notice. That failure does not reverse a successful payment or subscription. Keep the event time and contact support using Notifications or email not delivered when needed.

Do not share full screenshots containing passwords, one-time codes or unrelated personal information.

Related guides

Related guides: Purchase a plan and understand activation, Credentials, devices and concurrent logins, Telegram customer onboarding and commands, Website registration account linking and recovery, Payment succeeded but internet did not activate.