Using Call

Keeping Up with New Releases in Call: The Update Bar and Release Notes

How Call tells you a new version is live, what the update bar does, how to read What's new, and a simple routine for sharing changes with your team.

Call editorial team · Published · 6 min read

Cloud software changes under your feet. That is a strength, because you get improvements without an upgrade project, but it can also be a surprise when a button moves or a new option appears in the middle of a shift. Good change management in a call centre is mostly about two things: making sure the app updates at a safe moment, and making sure people know what changed.

A team lead reading a list of recent changes on a screen at their desk
Illustrative image

Call handles the first for you and gives you the tools for the second. This guide explains the update bar, the release notes page, and a small routine to turn notes into team habits. If your team is bigger and changes are frequent, Change Management in the Contact Centre covers the people side in more depth.

The update bar: how a new version reaches you

The app checks for a new version every few minutes, and again when you come back to the tab. When one is available, a bar appears at the top of every signed-in screen. It says that a new version of the app is available, shows the version number and when it was built, and lists every change since the version you opened, newest first. A button folds or opens that list.

What happens when a new version is live

  1. The bar appearsIt names the new version and asks you to save any unsaved changes first.
  2. You carry on workingNothing reloads by itself while you are on a page, so what you are typing is safe.
  3. You open another pageThe next time you open a different page in the app, it opens on the new version.
  4. Or you reload nowPress Reload the page to move straight away.
  5. What changed stays visibleAfter the switch, a panel headed What changed in this version stays at the top until you close it.

The panel has an Open the page link on each change, so you can go straight to the screen it concerns. The Close button hides the panel until the next version, and the app remembers that choice in the browser you are using.

When the app waits

The switch is deliberately cautious. The app does not move you to the new version while the browser phone is on, while you are signed in to take calls or on a call, while you are listening in to a live call, or while audio or video is playing. The bar simply stays until you finish and press Reload the page. This protects calls in progress, which are the one thing you cannot afford to interrupt.

What's new: reading the release notes

The full history lives under Settings, then What's new, and the bar's View release notes button opens it at the right version. Without signing in, the same notes are on a public page, which is handy for someone who is deciding whether to adopt Call or for a manager checking from a phone.

How to read an entry

  • BadgesNew, Improved or Fixed, each as an emoji plus a word, so the meaning does not depend on colour alone.
  • NEW markerMarks changes added since you last saw them in this browser, so repeat visitors see only what is fresh.
  • Version linksPress a version line to put its link in the address bar, then share it with a colleague.
  • Open the pageJumps from a note to the screen it describes, so you can try the change straight away.
  • LanguagesNotes are written in English and Japanese; in other languages, a note without a translation appears in English.

A tip for scanning: read the Improved and New items first, as they are the ones that give you something to try. Fixed items are useful when you have been living with a problem and want to know whether it has gone.

Turning notes into team habits

A release note that nobody reads changes nothing. In a small team, one person can own the task. In a larger one, a supervisor per shift can do it. Whoever it is, aim for a short, regular rhythm.

  1. Once a week, open What's new and read everything since your last visit.
  2. Pick the two or three changes that affect your team's daily work, such as a new option on a screen they use.
  3. Write them down in plain words, with the path to the screen, and post them where agents already look.
  4. Try each change yourself first, so you can answer the first question.
  5. Ask for feedback after a week: did it help, did it confuse?

Passive and active ways to follow changes

Wait to be surprisedFollow the notes
When you learn of a changeWhen someone stumbles on itIn a weekly review
TrainingAd hoc, mid-callShort, planned, with an example
RiskAgents lose time and confidenceLow, issues surface early
EffortNone up frontA few minutes a week

When a change affects what customers hear or how calls are routed, treat it as more than a note: test it in a practice call, tell the team, and keep a record in your own documentation. Contact Centre Documentation suggests a light way to do that.

Setting expectations about change

Frequent small releases are different from a big upgrade every year. Nobody schedules a training day, so the responsibility for noticing falls on the team. Be clear about three things. First, which screens your agents rely on every day, so the person reading the notes knows where to look hardest. Second, who may decide to adopt a new option, since an enthusiastic agent who changes a shared setting can surprise everyone. Third, how a problem is reported if a change causes one: a named person, a channel and a short description are enough.

It also helps to separate reading from adopting. Reading about a new option does not oblige you to use it; decide whether it suits your team on your own timetable.

If something looks wrong

A short release-day checklist for a supervisor

  • Read the new items in What's new
  • Open the changed screens and try them
  • Warn the team about anything that moves or renames a button
  • Check that the browser phone is off before reloading
  • Note any change that affects scripts, menus or reports

Doing it in Call

Open Settings, then What's new whenever you want to catch up, or press View release notes in the update bar. The page you are reading now works on a phone too; see Using Call on a Phone Browser. If you cannot find where a changed feature lives, the help centre's search will, and Finding Answers in Call's How-To Guides shows how to use it.

Frequently asked questions

Will I lose my work when a new version is released?

No. The app never reloads the page you are on by itself. It switches when you open another page, so save your work before you press Reload the page.

Why does the update bar not go away?

The app does not switch while the browser phone is on, while you listen in to a live call, or while audio or video plays. Finish that and press Reload the page.

Can I read the release notes without signing in?

Yes. The same notes are on a public what's-new page. Signed-in users find them under Settings, then What's new.

What do New, Improved and Fixed mean?

They label each entry: something added, something made better, or a problem corrected. Each badge is an emoji and a word, so it does not rely on colour.

How do I know which changes I have not seen?

Changes added since you last looked in that browser are marked NEW.

Are the release notes available in my language?

They are written in English and Japanese. In other languages a note without a translation is shown in English.

Open What's new in Call and read the latest changes

In the demo console you can try incoming calls in a simulation.

Related guides