Guide

Notifications

Watchlist.top has several notification surfaces. While the app is open, events can show an in-app toast in the lower-right corner and play a local sound. The local sound can also be a voice alert when the browser or device provides speech voices. A separate Settings toggle can turn these in-app toasts on or off. If OS notifications are enabled in Settings and the browser permission is granted, supported events can also create a native browser/desktop notification. Server-side price notifications can be delivered through Telegram or email according to the selected account channel. Fired events are also collected in the Notifications feed.

What this section covers

What in-app toasts deliver: while the application is open and the in-app notifications toggle is enabled, price and parameter events can show a toast in the lower-right corner. This includes By changes, Impulse, Print activity, and fired price notifications. Clicking the toast opens the coin. Sound plays locally if configured for that alert type.
How toast interaction works: moving the pointer over a toast pauses auto-hide, the copy button copies the ticker, and clicking outside the copy/close controls selects the related coin.
How the Notifications feed differs from toasts: the feed keeps fired events in a compact list with the newest rows at the top, so several alerts can be reviewed without covering the chart with the old settings form.
What delivered price notifications mean: price notifications created on the chart are monitored by Watchlist.top servers and sent via the selected channel (Telegram or email) even when the application is closed.
How optional OS/browser notifications work: enable the OS notifications toggle in Settings and grant browser notification permission. If permission was denied earlier, it must be reset in the browser site settings. These native notifications are separate from in-app toasts.
How to set up Telegram delivery: the Telegram account must be bound in Account settings, and Telegram must be selected as the delivery channel.
How to set up email delivery: the email address must be confirmed. Once confirmed, select Email as the delivery channel in Account settings.
What happens when the delivery channel is set but the prerequisite is missing: the application cannot use a channel that lacks its required condition (confirmed email for email delivery, bound Telegram for Telegram delivery). The notification can exist, but delivery is not possible until the requirement is met.
How sound notification settings work: open Settings to choose the default local alert sound and volume. Print activity also has its own sound selector in the alerts window; selecting a sound there previews it immediately and only affects print activity alerts.
How voice alerts work: choose Voice in the sound selector, then choose an available voice and speed. The app speaks a short alert phrase locally: for example the coin, event type, direction, price, percent, or print activity details depending on the alert type.
Why voice alerts are not the same as Telegram or email: the voice is generated on the current device while the app is open. It is not sent through the server and it does not work if the browser tab or mobile app is closed.

Key screens and controls

Account settings showing the delivery channel selector with Telegram and Email options and their current validation state.
Account settings showing the Telegram bind section with the link and the polling status indicator.
Account settings showing the email confirmation flow: email field, status badge, and the send confirmation button.
Settings with the sound selector and volume control for local in-app alert sound.
Settings with the OS notifications toggle, the in-app notifications toggle, and the browser permission state.
Notifications feed with recent fired alerts.
Event notifications → Print activity subtab with the separate sound selector.
Browser permission dialog that appears when OS notifications are enabled for the first time.
Settings with Voice selected as the alert sound, including voice and speed controls.

Step-by-step flow

To enable native OS/browser notifications, open Settings and find the OS notifications toggle. Allow the permission if the browser prompts you.
To enable or disable toast cards inside the app window, open Settings and use the "In-app notifications" toggle. This does not change Telegram or email delivery.
To add a local sound to in-app alerts, open Settings, find the sound selector, pick an alert sound, and set the volume.
For Print activity alerts, open Event notifications → By parameters → Print activity and choose the sound in that subtab. The selected sound previews immediately.
To set up Telegram delivery: first make sure a Telegram account is bound (Settings → Account tab → Telegram bind section). Then select Telegram as the delivery channel.
To set up email delivery: first confirm your email address (Settings → Account tab → send confirmation email and open the link). Then select Email as the delivery channel.
To switch the delivery channel, open Settings → Account tab (or the account area in the header) and choose between Telegram and Email in the delivery channel selector.
If Telegram delivery is not working, check: is Telegram bound? Is Telegram selected as the channel? Has the bot been started in Telegram (@WatchlistTopBot)?
If email delivery is not working, check: is the email confirmed? Is Email selected as the delivery channel? Is the email address correct?
If an in-app toast appears, click it before it disappears to open the related coin in the current list.
To review several fired alerts, open the bell and use the Notifications feed. On mobile, tapping a feed row closes the dialog and opens the chart for that coin.
If you need to copy the ticker from a toast or alert row, use the copy button. It does not close the toast and does not switch the current chart.
To use a voice alert instead of a short sound, choose Voice in the sound selector, then select the voice and speaking speed. Use preview to check how it sounds on the current device.

Screenshots

Delivery channel selector — Telegram selected

The channel selector shows Telegram and the current bind status.

Delivery channel selector — Email selected

The channel selector shows Email and the current email confirmation status.

Sound settings for local alert sound

Sound and volume are configured from the settings dialog.

In-app toast triggered by an alert

In-app toasts appear in the lower-right corner when a notification fires.

Print activity sound selector

Print activity has its own sound dropdown, and selecting a sound previews it immediately.

Operational notes

In-app toasts and local sounds work only while the browser tab is open and the page is loaded. They do not work if the tab is closed, and toasts can be hidden with the in-app notifications toggle.
Native OS/browser notifications require both the Settings toggle and browser permission. If permission was denied at the prompt, it cannot be re-requested by the application; change it manually in browser site settings.
Telegram delivery works even when the application is closed because price notifications are monitored on the server.
The delivery channel setting affects delivered price notifications. Parameter-based notifications (By changes, Impulse, Print activity) use in-app toasts and local sound regardless of the Telegram/email channel setting.
Sound plays only in the browser tab. If the tab is muted or the device volume is zero, the sound will not play even if a notification fires.
In-app toast notifications are short-lived and keep only the most recent events visible. They are a working aid, not a permanent alert archive.
The Notifications feed is more suitable than toasts when you need to review several fired alerts one by one. It does not replace Telegram or email delivery for server-monitored price alerts.
Hover pause is meant for reading and copying a recent alert. It does not turn the toast into a permanent history item.
In the Android app, supported in-app alert events can also be routed to Android system notifications when notification permission is allowed.
Switching the delivery channel takes effect immediately. Future notifications from that point use the new channel.
Voice alerts use the browser or device speech engine. Available voices differ by browser, operating system, installed language packs, and Android WebView. If no voice is available, choose a normal sound or install/enable a speech voice in the operating system.
Browsers can restrict autoplay and speech until the user interacts with the page. If a voice alert does not speak right after opening the app, click inside the app once and test the sound again.

When to use it

When you need to understand how in-app toasts, OS/browser notifications, Telegram, and email work as separate notification surfaces.
When an alert fired but you did not receive it and need to trace what went wrong.
When you want to verify that your account state and channel setup actually allow delivery.

When not to rely on it

If your question is purely about metric formulas or chart interaction — those are covered elsewhere.
If you have not set up any alert yet — start with the alerts section first.

Typical interpretation mistakes

Assuming a configured delivery channel is ready without verifying your email or connecting Telegram.
Thinking browser notification permission and the delivery-channel setting are the same thing.
Expecting email, Telegram, in-app toasts, and native OS/browser notifications to fail or recover for the same reasons.

Algorithms and formulas to understand

Why the delivery channel check happens at the time of notification dispatch rather than at configuration time
Why browser notification permission denial at the prompt level cannot be overridden by the application
Why parameter-based notifications use in-app toasts regardless of the Telegram/email channel setting
Why in-app toasts and native OS notifications have separate toggles
Why the Notifications feed is used for reviewing fired events while Settings remains the place to configure alerts
Why toast copy/select/close actions are separated so copying a ticker does not accidentally open the coin
Why Print activity has a separate sound setting: it can be tuned independently from the default local alert sound and previews the chosen sound immediately
Why voice alerts depend on browser/device speech voices and can behave differently on desktop browsers, mobile browsers, PWA, and Android WebView

Related sections

Event notifications Account, subscription, trial Common problems