Solace Caregiver Hub — Product Concept

I was looking at Solace Health, a company that matches patients with a dedicated human care advocate, and went through their actual product to understand it. I noticed something specific: Solace names family caregivers as a supported persona in its own materials, but its "For Caregivers" page is marketing-only. There is no actual tool. Caregivers managing a loved one's care are left reconstructing what is happening from scattered calls and texts. That gap, a named persona with no product behind it, is what I wanted to explore: what would Solace build for caregivers if they built something?

A caregiver-facing dashboard that gives family members a single, plain-language view of what their loved one's advocate is doing: the care plan and its status, upcoming appointments, insurance authorizations, and a summary of every advocate call.

I started from one question: what does a caregiver actually lose today? The biggest gap is the advocate call. If you miss it, you miss the update entirely. So the centerpiece is a call-summary feature, a missed call becomes a plain-language summary with action items that automatically populate the care timeline. That is the one feature that removes work rather than just organizing it.

From there, each feature answered a real caregiver question. "What is being handled?" became the care-plan timeline with clear statuses. "What is coming up?" became an appointments view with confirm-and-reschedule states. "Is insurance going to cover this?" became an authorization tracker. And because the update should reach the caregiver rather than wait for them to check, I added a proactive notification the moment new information lands.

Two principles shaped every decision. First, realism over cleverness: I modeled features the way Solace's actual advocate-driven model would really work, not the way a flashy demo would. Insurance status comes from the advocate checking and logging it, not a fictional insurer API, because most payers do not expose one. Visit outcomes come from advocate follow-up, not an automatic medical-record feed. Second, honesty about the hard parts: I included a Risks section naming what would actually make this difficult, PHI protection, consent granularity when multiple caregivers share access, and the danger of an AI-hallucinated item in a care plan, because those are the things that separate a real healthcare product from "AI-powered" hype.

A multi-caregiver permission model for siblings sharing care of one parent, with granular consent, plus deeper integrations modeled realistically against what advocates can actually access.