Squawk audio isn't playing
The Helious squawk is a live, noise-cleaned audio feed on the paid tier. When it goes silent, the fix is almost always fast. Work these in order and you'll be back on the tape in under a minute.
1. On iOS/Safari, tap to unlock audio first
Mobile browsers block autoplaying sound until you physically interact with the page. If you loaded Helious and the squawk never started, that's the cause. Tap the squawk play control once, directly, to grant the audio gate. A single deliberate tap unlocks the stream; after that it stays live for the session. This is a browser rule, not a Helious setting, so it applies on iPhone and iPad even on the paid tier.
2. Confirm you're on the paid tier
Live squawk audio is a subscriber feature. If your card is on file but the feed shows locked, check that your subscription is active and not mid-dunning (a failed renewal charge). Open your account/billing panel and confirm the status reads active. If a renewal just failed, updating the card clears it immediately. Everything else on the desk: the news feed, release breakdowns, auction analysis, stays available regardless, but the squawk specifically requires an active paid subscription.
3. Refresh the stream
The squawk rides a live socket. If your machine slept, switched networks (Wi-Fi to LTE), or sat idle behind a corporate proxy, the socket can drop while the button still looks armed. A hard refresh of the desk re-opens the connection and re-authenticates the audio token. If you were away from the desk for a while, refresh first before assuming anything's broken.
4. Check output routing and volume
Sounds obvious, but verify the audio isn't muted at the tab, OS, or hardware level, and that output isn't parked on a disconnected Bluetooth device or a headset that walked off. The squawk is forced to mono through a clean worklet, so if other browser audio plays but the squawk doesn't, it's the tier or socket, not your speakers. If nothing on the machine makes sound, it's routing.
Still silent after all four? Note your browser and OS and reach out from your account panel. A token that won't re-arm on refresh is the one case we need to look at directly. For the rest of the desk, head back to the [live terminal](/).