Clients as cases, not rows.
Intake, preferences, documents, authorizations, proof of care, complaints and family. One record, and the preferences on it decide who may serve.
What a case holds
A row gives you a phone number. A case gives you the answer.
Eight sections on one record, and the Receptionist, the Coordinator and Nessa all read this one.
One record. No second copy in a spreadsheet.
On the record
Everything the office asks about is already here.
Money, history and family live on the case, not in three tabs and someone's memory.
The money is on the case
Authorizations, units drawn down and the signed plan, on the client you're looking at.
Complaints stay attached
Every issue keeps its date, its outcome and who closed it, for as long as the case exists.
Family, with scopes
Each contact gets only what you give them: visit notes, billing, or emergency only.
Every visit lands back here
The proof-of-care record grows itself from verified visits. Ready to hand over at audit time.
The phone knows who's calling
An inbound number matches the case, and the Receptionist answers from it.
Guardrails
What it will never do.
Preference gates enforce who may serve a client; the record keeps the complaint and proof-of-care history in one place. How we handle data
Built into the engine, the same for people and agents
Required means required · No agent can propose someone who fails a gate.
One client, one record · No shadow copy in a spreadsheet.
Never drops a complaint · Resolved issues stay on the case.
Family sees only its scope · Each contact is granted separately.
Who reads this record
Three of the staff work from it.
The Receptionist identifies callers against the client record; the Coordinator uses preferences in ranking; Nessa reads the record with @-mentions.
- Inbound callMatched to #C-1042
- “Her next visit?”Fri 8a · R. Doyle
- New referralIntake started
- Hoyer required8 filtered out
- Cat in the homeAllergies checked
- Ranking6 of 14 offered
Nessa · Just ask.
Meet Nessa- “@Margaret Alvarez”Reads the case
- “Any open issues?”1 · since Mar 2
- “Who's her daughter?”Elena · visit notes
How does Nestaid manage home care clients?
Nestaid treats each client as a case rather than a row: intake, required preferences that gate which caregivers may serve them, documents, authorizations, the care plan, the proof-of-care record, complaint history and family contacts live on one record, the same record the Receptionist, Coordinator and Nessa use.
Frequently asked questions
Can I import clients?
Yes, clients import from CSV during switching.
How do preferences affect scheduling?
Required preferences gate who can be scheduled or proposed for that client; soft preferences influence ranking.
How does intake work?
A referral arrives by phone, text or a website form. The Receptionist identifies the caller, logs the inquiry and starts the intake record; a website form becomes a lead in the same system. Your staff complete the assessment, the required preferences that gate who may serve the client, and the documents, and the care plan is then seeded from the authorization's service code for a person to review and sign.