Every other CRM (HubSpot, Salesforce, Pipedrive) collapses the caller and the recipient into one record. Home care doesn't work that way. CareRM is built around the real shape: one care recipient, multiple contacts, consent that lives where it belongs.
In a typical CRM, the person who calls is the person you sell to. In home care that's wrong before the call even ends. The daughter on the phone isn't the patient. The POA isn't the billing contact. The hospital discharge planner isn't the family. You end up with five spreadsheets, a kanban tool with custom fields nobody fills in, and a back-office system that thinks one phone number equals one human.
The vertical CRMs that ship inside WellSky-style systems aren't much better. They're intake forms with kanban bolted on. No consent model. No notion that one recipient can have three decision-makers. No way to text the daughter without touching the patient record.
home care inquiries come from a family member, not the person who will receive care.
family decision-makers are typically involved in a single adult-child inquiry. POA, billing, sibling.
generic CRMs that model this correctly out of the box. You end up rebuilding it as custom fields.
Field-research observations from home care intake interviews. Not survey data.
The person receiving care and the people you talk to are two different things. CareRM models them that way at the schema level, not as a custom field.
Three surfaces, one underlying record. Move a deal, the conversation moves with it. Send a sequence, the consent check is automatic.
Pipeline kanban for clients, caregivers, and referrals. Stage changes can fire a nurture sequence (with consent checks attached).
One thread per contact. Every channel in one place. PHI stays out of subject lines.
Outbound steps check consent before they fire. Blocked steps stay visible, never silently sent.
Sarah said yes to SMS for care-coordination, no to marketing. Linda is email-only. CareRM enforces that at the message layer, not in your team's memory. Every outbound carries a consent_id that proves which grant authorized the send. Quiet hours by state. Withdrawal preserves the original grant (you keep the receipt) and blocks the next send.
WellSky stays your scheduling, billing, and back-office system of record. CareRM owns the part WellSky was never built for: the messy front end. The phone call, the four family members, the consent tracking, the pipeline of leads that haven't converted yet.
The moment a lead qualifies, CareRM creates the client (and related contacts) in WellSky. Idempotent. Audited. Reversible if you misclick. Field-level mappings are documented per resource so you can see exactly what crosses the boundary and which side wins on conflict.
care_recipient maps to WellSky Patient (Prospect or Client state).contact (client_contact) maps to RelatedPerson.Those CRMs assume the caller is the customer. In home care, the caller is almost never the patient. They're the daughter, the POA, the discharge planner, the doctor's office. CareRM separates the care recipient from the people you talk to, links them with roles (POA, billing, emergency), and puts consent on the contact where it actually lives. You can do this in HubSpot with custom objects, sure. You'll spend three months getting it wrong, then another six getting it right.
No. CareRM feeds WellSky. WellSky stays your scheduling, billing, and back-office system of record. We sync the client and related contacts the moment a lead qualifies. Idempotent, audited, reversible. You keep WellSky. We own the part it was never built for: the inquiry pipeline, the multi-channel inbox, and the consent layer.
That's the default case. Sarah calls about her mom Margaret. CareRM creates a care_recipient for Margaret and a contact for Sarah, linked through recipient_contacts with role flags (Sarah is POA, primary, decision-maker). Any consent Sarah gives is logged against Sarah, not Margaret. When Sarah's sister Linda calls a week later about billing, she becomes a second contact on the same recipient. No duplicate records. No "which Margaret is this" confusion.
Yes. Most home care agencies are coming from HubSpot, Pipedrive, Zoho, a spreadsheet, or some combination. Done-with-you onboarding includes the import. We map your existing contacts into the recipient + contact model, pulling apart fields that were collapsed together, and flag anything ambiguous for you to review. Notes, pipeline stages, and conversation history come along. Typical migrations are 7 to 14 days.
Yes. Every outbound carries a consent_id pointing to the exact grant that authorized it (channel, purpose, timestamp, disclosure text shown). Quiet hours are enforced by state. 10DLC brand and campaign registration is included for SMS. Email goes through Postmark with a BAA. PHI never lands in subject lines or logs. If a contact opts out, the original grant stays on file (you keep the receipt) and the next send is blocked at the dispatch layer.
The deal sits on the care recipient. All contacts linked to that recipient see it. The Unified Inbox shows the threads from Sarah, Linda, and David in one view, so whoever picks up the conversation has the full context. Stage changes log who moved the card and why. Nurture sequences run against the primary contact by default, with the option to fan out.