Guide
Notifications
There are three ways a notification can reach you in Watchlist.top: as a browser toast inside the application, as a Telegram message, or as an email. Each channel has its own requirements. Browser notifications depend on the device and browser permission state. Telegram delivery requires a bound Telegram account. Email delivery requires a confirmed email address. This section explains how to set up and verify each channel, and what to check when a channel appears configured but delivery does not work.
What this section covers
- What browser (in-app) notifications deliver: a toast appears in the lower-right corner of the application when a parameter-based notification fires. Clicking the toast opens the coin. Sound plays if configured in settings.
- What server-side delivery means: price notifications created on the chart are monitored by the backend and sent via the selected channel (Telegram or email) even when the application is closed.
- How to enable browser notifications: the application must be granted notification permission in the browser. The permission prompt appears the first time the user enables browser notifications. If previously denied, it must be reset in the browser settings.
- How to set up Telegram delivery: the Telegram account must be bound to the user's account (see 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 is saved but delivery is not possible until the requirement is met.
- How sound notification settings work: open Settings, choose an alert sound from the available options, and set the volume. The sound plays locally in the browser tab when a browser notification fires. It does not affect Telegram or email delivery.
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 browser notification sound.
- Browser permission dialog (browser-native) that appears when the user enables browser notifications for the first time.
Step-by-step flow
- To enable browser notifications, open Settings and find the browser notifications toggle. Allow the permission if the browser prompts you.
- To add a sound to browser notifications, open Settings, find the sound selector, pick an alert sound, and set the volume.
- 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?
Screenshots
Screenshot placeholder
Delivery channel selector — Telegram selected
Show the channel selector with Telegram chosen and its bind status indicator visible.
Screenshot placeholder
Delivery channel selector — Email selected
Show the channel selector with Email chosen and the email confirmation status visible.
Screenshot placeholder
Sound settings for browser notifications
Show the sound selector dropdown and volume control inside the settings dialog.
Screenshot placeholder
Browser toast notification triggered by a parameter alert
Show the in-app toast in the lower-right corner that appears when a notification fires.
Operational notes
- Browser notifications play sound and show toasts only while the browser tab is open and the page is loaded. They do not work if the tab is closed.
- If the browser permission for notifications was denied at the permission prompt, it cannot be re-requested by the application. The user must manually change the permission 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 only server-side price notifications. Parameter-based (by changes, impulse) notifications always show as browser toasts regardless of the 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.
- Switching the delivery channel takes effect immediately. Future notifications from that point use the new channel.
When to use it
- When you need to understand how browser, Telegram, and email alerts work as separate channels.
- 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 channel is ready without verifying your email or connecting Telegram.
- Thinking browser notification permission and the server-side delivery setting are the same thing.
- Expecting all three channels — email, Telegram, browser — 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 always appear as browser toasts regardless of the Telegram/email channel setting