Scope and Connect
We agree what the agent says, what it must never say, and what counts as a good outcome. Then we connect to the system it reads from and map the fields, because nothing can be built until we can see your data.
Certifications, TB tests and background checks chased on a 90, 60 and 30-day cadence,
logged back to the caregiver record, so nothing lapses without anyone noticing.
Credential lapses are the quiet kind of problem. Nobody notices an expired certification on a Tuesday. They notice it during a state audit, during an incident review, or when a payer asks for documentation you cannot produce. Home care licensing is a state-by-state patchwork with no national regime, which means the specific list you have to keep current is yours and it changes. What does not change is that tracking it in a spreadsheet works right up until the person who maintained the spreadsheet is busy. This workflow watches expiry dates across your roster and starts chasing at ninety days, again at sixty, and again at thirty, by call and by message, until the renewal is in hand and logged.
It is the least glamorous thing we build and one of the easiest to justify, because the downside it prevents is an audit finding rather than an inconvenience.
We start from the list you actually have to keep current, since that varies by state and by payer. Certifications, TB tests, background checks, driving records, immunizations, in-service training hours. Whatever is on your list goes into the watch, with the renewal path and the person responsible attached to each. One honest caveat: several scheduling platforms do not expose credential dates through their API at all. Where yours does not, this runs off a scheduled export or a shared sheet you keep current instead, and we confirm which applies to you in week one rather than after you have paid.
Chasing escalates rather than repeating. The first touch is gentle and informational, the last one goes to your administrator as well as the caregiver, because a credential thirty days from expiry is your compliance problem and not only theirs. Every touch is logged, which is exactly what an auditor wants to see.
A live view of every expiring credential across your roster, with an automated chase sequence and a complete log of who was contacted, when, and what came back.