This guide explains why escalation routing matters for home-based care agencies delivering Medi-Cal personal care and home health services, how an agency can build its own routing procedure, and how IT Total Care handles the first look for agencies across the San Francisco Bay Area.
1. Why Does Knowing How to Escalate EVV Issues Matter for a Home-Based Care Agency?
Knowing how to escalate EVV issues matters because a live EVV failure is a routing problem before it is a technical one. The first question is whose problem it is, not how to fix it. Our post on EVV IT support lays out the division: the vendor supports the platform, the IT provider supports what the platform runs on, and the agency’s EVV administrator owns the data. Escalation is how an agency applies that division under time pressure.
The 6:50 a.m. call is the standard case. The scheduler cannot fix the phone, cannot see inside the platform, and cannot reset a portal account she does not administer. What she can do is capture what the caregiver is seeing and send it to the one party that can act on it. How to actually resolve a lockout is a separate topic.
Where Poor Routing Shows Up
- Misrouted tickets cost both sides time. A vendor ticket for a device problem, or an IT ticket for a platform outage, gets read, investigated, and sent back. Each round trip is measured in hours, and the visit is unrecorded for all of them.
- Unresolved failures become manual entries. When a clock-in cannot be made to work, the visit gets keyed in later by hand. California has not set a compliance threshold, but DHCS’s CalEVV FAQ is clear that outside emergencies the state expects visits to be captured electronically, not entered manually.
- Manual entries accumulate faster than anyone expects. In HHS-OIG’s audit of Colorado’s Medicaid personal care EVV program, issued July 17, 2026, 62 of 160 sampled claim lines included manually entered visits. In some cases most or all of an enrollee’s EVV records were manual entries. That is Colorado, and the findings were directed at the state agency, which disputed them; the pattern of manual entries piling up unexamined is what an agency should take from it.
- Routing produces the correction record. A ticket that captures the caregiver, the client, the visit time, and the cause is also the documentation the EVV administrator needs to correct the visit afterward. Bad routing loses the fix and the paper trail at the same time.
- Repeat failures stay invisible. Without a log of what was routed where, the same caregiver’s phone can fail four Mondays in a row and be treated as four new problems.
2. How Can a Home-Based Care Agency Escalate EVV Issues on Its Own?
An agency can build its own EVV escalation procedure in six steps: pick one internal intake point, capture the facts before calling anyone, sort the issue into one of four buckets, route each bucket to its owner, write the ticket so it does not bounce, and close the loop with the EVV administrator. None of it requires new software. All of it requires being written down.
Step 1: Pick One Internal Intake Point
Caregivers should report EVV problems to one place, and that place is usually the scheduler or the office manager. One intake point means one person hears every failure, which is the only way patterns become visible. It also means the vendor and the IT provider each deal with a single agency contact who knows the history, rather than six caregivers describing six versions of the same problem. Name the intake point and a backup, and put both on the caregiver-facing contact sheet.
Step 2: Capture the Facts Before Calling Anyone
Before the intake point opens any ticket, capture seven facts: the caregiver, the client, the scheduled visit time, the device (make, model, and whether it is agency-issued or personal), the EVV app version, the exact error message, and whether the phone had cellular signal or Wi-Fi at the client’s home. Most of the device details should come from the agency’s device inventory rather than from the caregiver on a stressed phone call; our guide to creating a device inventory list at a home care agency covers building one.
Then check whether the vendor has posted an outage or service notice. If the platform is already known to be down, there is nothing to escalate, and the intake point can tell the caregiver what to do instead of opening a ticket that will be one of a hundred.
Step 3: Sort the Issue Into One of Four Buckets
Every live EVV issue falls into one of four buckets, and the bucket decides who gets the call:
- Platform: the app, the portal, or the transmission of visit data is failing, typically for more than one caregiver.
- Device or connectivity: the phone, its operating system, or the connection at the client’s home is the problem, and the app is a bystander.
- Account: the caregiver cannot authenticate, and the account in question either lives inside the EVV portal or lives in the agency’s directory and email system.
- Data correction: the visit happened, but the record is wrong: a missed clock-out, the wrong client selected, or the wrong service.
The facts from Step 2 usually make the bucket obvious. One caregiver, one phone, no signal is device or connectivity. Every caregiver, every phone, same error is platform. When the bucket is still unclear after the facts are in hand, treat it as device or connectivity first, because that is the bucket that can be ruled out fastest.
Step 4: Route Each Bucket to Its Owner
Platform issues go to the EVV vendor’s support channel. That covers app errors hitting multiple caregivers, a portal that will not load, and visits that are not transmitting. For the agencies we work with, that channel is typically HHAeXchange, AxisCare, Axxess, or WellSky support.
Agencies on CalEVV route platform issues to Sandata’s CalEVV customer support at (855) 943-6070 or CACustomerCare@sandata.com. Agencies on an Alternate EVV system have two possible owners: problems inside the Alternate EVV app itself go to that vendor, and problems with the connection between the Alternate EVV system and the state’s Aggregator go to Sandata’s AltEVV support team at (855) 943-6069 or CAAltEVV@sandata.com.
Device, connectivity, and non-EVV account issues go to the IT provider. A phone that will not update, a caregiver with no signal at a client’s home, or a Microsoft 365 login that fails are all IT tickets, whatever app was open when the problem appeared.
Data corrections go to the agency’s EVV administrator, not to either outside party. A missed clock-out, the wrong client, or the wrong service is corrected inside the agency, because the administrator is the person DHCS holds responsible for the record.
Questions about what EVV requires, rather than about a failure, go to DHCS directly: the EVV inbox at EVV@dhcs.ca.gov, or DHCS’s weekly CalEVV drop-in hours every Wednesday from 10 to 11 a.m. Pacific time, on Microsoft Teams with no registration required.
Step 5: Write the EVV Support Ticket So It Does Not Bounce
An EVV support ticket that does not bounce contains three things: the facts captured in Step 2, the bucket the agency assigned, and what has already been ruled out. “Caregiver cannot clock in” is a symptom. “Caregiver on an agency-issued Samsung A15, app version 4.2.1, error ‘session expired’ at 6:48 a.m., full cellular signal, other caregivers clocking in normally, phone restarted with no change” is a ticket the vendor can work on the first read.
When an issue crosses buckets, open a ticket with each party and cross-reference the ticket numbers in both. A phone that needed an OS update before the new app version would install is an IT ticket and a vendor ticket at once, and each party should be able to see what the other found.
Step 6: Close the Loop and Track Repeats
Close the loop by logging the ticket numbers and the outcome, then handing the visit to the EVV administrator for any record correction. The fix and the correction are two different events, and the second one is the agency’s alone. A resolved ticket with an uncorrected visit is not resolved.
Track repeat issues by caregiver and by device. Three lockouts on the same phone point at the phone. Three lockouts across different phones at the same client’s address point at the address. A pattern points to the right bucket faster next time, and it is the evidence an agency needs when it asks either outside party to change something.
Limitations: An escalation procedure only works if the intake point actually captures the facts before dialing, and at 6:50 a.m. with a visit starting at seven, the temptation is to call whoever answered last time. The procedure also depends on a current device inventory, which drifts the moment a phone is swapped without anyone updating the record. And cross-bucket issues, the ones that need a vendor ticket and an IT ticket at once, are the ones most likely to stall, because each party can reasonably wait for the other. Agencies rarely fail to write the procedure. They fail to follow it during the exact minutes it was written for.
3. How Does IT Total Care Help a Home-Based Care Agency Escalate EVV Issues?
As a Bay Area MSP focused on home-based care, IT Total Care takes the first look on EVV issues that could be the device or the platform, so the agency’s intake point is never guessing at the bucket alone. We do not support the EVV platform and we do not touch visit records; we make sure what reaches the vendor and the EVV administrator arrives with the facts attached.
Our EVV Escalation Support Includes
- First Look on Unclear Buckets: When the intake point cannot tell whether a failure is the device or the platform, they call us first. We rule out device, operating system, and network causes before the issue goes to the vendor, so a vendor ticket is only opened when it belongs there.
- Device and Network Details for Vendor Tickets: We supply the device model, OS version, app version, and connectivity details a vendor asks for on an EVV support ticket, so the agency is not relaying questions between two parties.
- Current Device Inventory: We keep the agency’s device inventory current, so fact capture in Step 2 takes minutes rather than a search. Our device inventory guide describes what that record holds.
- Repeat-Issue Tracking: We track repeat EVV issues by device and by caregiver and review the pattern with agency leadership during the Technology Business Review, so a phone that fails every Monday gets replaced rather than re-ticketed.
- Data Corrections Routed, Never Edited: When an issue turns out to be a record problem, we route it back to the agency’s EVV administrator. IT Total Care does not edit visit records.
“The ticket that bounces is the one that costs the visit. Most of the vendor tickets we see get sent back because they say ‘caregiver can’t clock in’ and nothing else. Send the phone model, the app version, the error text, and whether she had signal, and the vendor can actually fix the issue. Send ‘can’t clock in’ and you are three back and forths away from the issue being started to get worked on. Meanwhile visits don’t stop and manual entries begin to become the norm.”
Brendan Duebner, President, IT Total Care
Ready to Route EVV Issues to the Right Party the First Time?
IT Total Care partners with home care and home health agencies across the San Francisco Bay Area, from San Mateo County to Santa Clara County, to take the first look on EVV failures, keep device records current, and get platform problems to the vendor with the facts attached. If your scheduler is still deciding who to call by memory, we can help routing EVV issues at your agency.
Contact Us to talk through where your agency’s EVV issues are stalling today.
