The symptom
You’ve just rolled out a new Chime for Teams build and the UI still looks like the old one — a missing button, a stale icon, or layout that doesn’t match the release notes. Before opening a support ticket, almost always the answer is your browser is showing a cached copy.
Why it happens
The Chime agent and admin consoles are static web apps — just HTML, CSS, and JavaScript files served by the Chime server. Browsers cache those files aggressively so the app feels fast between sessions, which is great until the server-side version changes and the browser is still happy to reuse what it had yesterday.
The fix is a hard refresh: tell the browser to ignore its cache and ask the server for the freshest bundle.
The shortcut, per browser
Windows
- Chrome / Edge / Firefox:
Ctrl+F5
macOS
- Chrome / Firefox:
Shift+Cmd+R - Safari:
Option+Cmd+Eto empty the cache, thenCmd+Rto reload
What you won’t lose
A hard refresh only invalidates cached assets — it doesn’t touch localStorage. Anything that lives there survives the reload:
- Agent dashboard column choices and column widths
- Sound and notification toggles
- Saved filters and queue selections
If you land on an Unauthorized page
Occasionally the hard refresh races the auth handshake and you get bounced to an “Unauthorized” page. The fix is to browse directly back to the Chime root:
https://<your_chime_server>.com/ChimeThat re-runs the sign-in flow and drops you back into a working session.
Make this part of your release checklist
If you support a team of agents, add “hard refresh your browser” to the change announcement you send out after every Chime update. It is the single most effective way to head off false-positive bug reports right after a release.