How to Automate Alora

Respite is sold by the hour and delivered in somebody's house

Alora, from Alora Healthcare Systems in Atlanta and acquired by LivTech in 2026, is software for care delivered at home: home health, home care, hospice, pediatric homecare, private duty, personal care and companion care.

Respite sits inside that last group and has a logic of its own. The client is the person receiving care, but the customer is usually the family carer, and what they are buying is time. A daughter needs Thursday afternoon. A husband needs four days while he has surgery. Somebody needs a caregiver tonight because the arrangement that was holding collapsed this morning.

That makes the agency's product a scheduled hour with a specific person in it, in a specific house, verified as having actually happened. Which is why electronic visit verification carries so much weight here. A visit that was delivered and not verified is, to a payer, a visit that did not happen.

A missed clock-out becomes a payroll problem and a billing one

The scheduler's week is a series of small facts that each have to be true.

A caregiver forgot to clock out, so a two hour visit reads as eleven. A client's authorised respite hours are nearly used up and nobody has told the family. A certification expired last week and the caregiver has been working since. An emergency request came in on Sunday and there is nobody free within thirty miles. A visit was transmitted to the state aggregator and quietly rejected there. An invoice went out for hours that were never verified.

None of those is difficult. Each is somebody opening a screen, comparing two numbers and acting on the difference, and there are dozens of them every week. They get missed not because they are hard but because there are so many of them.

Alora

Certifications checked at the source State registries read directly, so a lapsed credential surfaces before a caregiver is scheduled against it.

Authorised hours watched to the last unit Payer portals compared against scheduled and delivered visits, with clients near their limit raised early.

Rejections worked the same week Aggregator returns reconciled against what was transmitted, so a rejected visit is fixed while it still can be.

Alora flags the visit before it reaches the aggregator

The platform covers a great deal of this already, and it would be wrong to imply otherwise.

EVV runs from a mobile device with GPS, with telephony as a fallback when there is no smartphone or no signal, and the system automatically transmits visits completed as planned to the aggregator, with connectivity built to Sandata, Netsmart, HHAeXchange and CareBridge. Visits with a discrepancy, such as a caregiver forgetting to clock out, are flagged for manual review before they are transmitted. Live Monitoring shows delayed visits and no-shows as they happen. Caregiver Credential Tracking, Prior Authorization Tracking, All-Payer Eligibility Verification, Open Shift Notification, Billing for All Payers and Payroll Management are all in there too, along with offline documentation for the field.

Which makes the line a precise one, and worth drawing carefully. Alora tracks the credential expiry date somebody entered and the authorisation somebody recorded. The registry that decides whether a certification is genuinely still active is a state website. The remaining units on a waiver authorisation live on the payer's portal. And a visit rejected after transmission is rejected on the aggregator's own screen.

An expired certification is found before the shift, not after

Overnight the comparisons get made, and the caregiver drives to a visit that will actually be paid for.

Certifications checked against the state registry that issues them rather than against a date typed into a profile, so a lapse is caught while there is still a week to fix it. Authorised hours read from the payer's portal and set against what has been scheduled and delivered, with any client inside a fortnight of running out raised to whoever calls the family.

Transmitted visits reconciled against what the aggregator actually accepted, so a rejection is worked this week rather than found at month end. Invoiced amounts matched to verified hours in both directions, because hours delivered and never billed cost the agency as much as hours billed wrong. Emergency requests arriving out of hours picked up and put in front of the on-call scheduler with the client's plan of care already pulled.

The line in home care holds. A person is not needed to fetch the figures, cross-check them and raise what does not match. No clinical documentation is written, no visit is verified on a caregiver's behalf, and anything going to a family carer or a payer is drafted for a person at the agency to send.

The scheduler stops being the person who checks

An agency's scheduler is the person who can find somebody for Thursday. A morning spent comparing an aggregator report against a payroll export is the least valuable thing they will do all week.

WebRun is an AI agent that works a real Chrome browser, using the same logins your office staff use. It opens the state registry, the payer portal or the aggregator, reads what is on the screen, and brings back a list with the client, the caregiver and the date attached.

It runs on your schedule in your own private environment, sessions are not shared between workflows, and a workflow can be restricted to an explicit list of sites. You can watch a run and stop it.

The workflows below are already built, and each one names what it opens.