Watch Kalivant do a week of the job.
Each walkthrough is a screen recording of Kalivant connected to a lab Unified CM cluster and Unity Connection server, with a real Cisco 8845 on the desk. The customer is Tallmeadow Health, a made-up four-site health network.
The call report is already in your inbox.
A month of call records from all three sites, straight from Unified CM's CDR and CMR files. The library's voice-quality report shows Charlotte with five times the poor calls of the Raleigh HQ; the team saves it as their own and has it emailed every Monday morning.
- Open the library's voice-quality report.
- Chart the share of poor calls.
- Charlotte: one call in five sounds bad.
- Save it as the team's own report.
- Email it every Monday morning.
- Scheduled, with the next run shown.
A charge nurse says her phone is "doing something weird."
Alexis Holmes, a charge nurse at the Raleigh HQ, calls the help desk. They find her in People, open the 8845 on her desk and use remote control to see its live screen. Call forward all is on, set by accident. One press of Forward off from the browser clears it on the real phone.
- Search People for Alexis.
- Her record lists the 8845 on her desk.
- The phone's page: registered, with her name on it.
- Open Remote control from the phone's actions.
- The live screen from her desk. Call forward all is on.
- Press Forward off from the browser.
- A fresh capture from the phone: forwarding is off.
New starters, and their phones registered overnight.
An 8845 plugged in at the Raleigh HQ auto-registered on its own. The help desk gives it to Alexis Holmes on her own number, 1440, and Kalivant builds the phone and line from the self-provisioning templates the cluster already has.
- Pick the HQ cluster.
- Find Alexis by her user ID.
- Claim the phone that auto-registered.
- Give her her own number, 1440.
- Review the plan: profile, device and line templates.
- Provision. Every step succeeds and lands in the audit log.
Patch night, from one page instead of four SSH sessions.
A Tomcat security COP goes onto the Charlotte cluster: pre-checks first, then the publisher, then the subscriber once you approve, and the same checks again afterwards. This walkthrough runs against Kalivant's simulated platform so we don't patch the lab on camera; the screens are the real ones.
- Start a new run.
- Pick the Tomcat security COP.
- Choose BR2: publisher, then subscriber.
- Save the draft and start it.
- Pre-checks pass; the publisher installs.
- Approve stage 2: the subscriber installs.
- Completed. Every post-check passed.
The Denver office handled its own changes this week.
A site admin limited to Denver's phones and numbers, and the audit log of what they changed.
See it running against your own cluster.
It's a 30-minute call. We connect Kalivant to one of your clusters and show your team around.