Squawk audio isn't playing
The Helious squawk is a live audio feed with the background noise stripped out, and it comes with the paid tier. Silence is usually quick to fix. Work down this page in order and you are normally hearing audio again inside a minute.
1. On an iPhone or iPad, tap the control once
Mobile browsers will not play sound until you have touched the page, so if you opened Helious and the squawk never started at all, that is almost certainly it. Tap the squawk play control itself, once, rather than tapping somewhere else on the page. That one tap opens the audio gate and the stream stays live for the rest of the session. Nothing in Helious can do it for you. The rule belongs to the browser, which is why it still catches paid subscribers on an iPhone and iPad.
2. Is the subscription still active?
Live squawk audio only runs for subscribers. If your card is on file and the feed still shows locked, the subscription may be mid-dunning, meaning a renewal charge that failed. Open your account panel and check that the billing status reads active. Updating the card clears a failed renewal straight away. The rest of the desk keeps working either way, including the news feed, the release breakdowns and the auction analysis. The squawk specifically needs an active paid subscription.
3. The connection may have dropped
The audio rides a live socket, and a socket is easy to lose without noticing. Sleeping the machine will do it, and so will switching from Wi-Fi to LTE or sitting idle behind a corporate proxy. The awkward part is that the button still looks armed afterwards. A hard refresh of the desk reopens the connection and re-authenticates the audio token, so if you have been away for a while, refresh before you assume anything is broken.
4. Everything between the tab and the speaker
Start with the obvious mutes, at the tab, in the operating system, and on the hardware itself. Then check where the sound is actually going, since output can sit pointed at a Bluetooth device that has disconnected or a headset that walked off with someone. The squawk is forced to mono through a clean worklet, so if other browser audio plays and the squawk does not, the problem is the tier or the socket rather than your speakers. If nothing on the machine makes any sound at all, it is routing.
If it is still silent, note your browser and OS and get in touch from your account panel. A token that will not re-arm on a refresh is the one case we have to look at ourselves. The rest of the desk is back at the [live terminal](/).