Who we serve overview

Care connects us. Start with your perspective.

Families, funders, community programs, care agencies, health systems, providers, device companies, and developers bring different needs and strengths to care. Explore how each can take part in one ecosystem, then go deeper into the section written for you.

Talk to the team

Common questions

For families and volunteers

Caring for someone you love shouldn't mean carrying it alone.

Maybe it is your mother at a day center, your husband home from the hospital, a neighbor you check on, or a volunteer shift you want to do well. This part of the page is written for you, not for buyers. You will find a few things worth learning today, how you would meet genusConnect, what it will and will not do, and where to start. No sign-up needed to read.

Start learning (no sign-up)

Already invited? Sign in

Family questions

Learn a few things that help

Short lessons you can read aloud or print for the sibling who will never open an app. General guidance, not medical advice.

Safe transfers

Before you help someone stand, bring the chair close, lock the brakes, and clear the floor.

Let them do as much as they can; count to three together and rise on three.

Bend your knees, keep your back straight, and hold them close to your body, never by the arms.

If they start to fall, do not try to catch them; ease them down and call for help.

If transfers are getting harder, ask the center or agency for a hands-on lesson.

Redirect, don't argue

When your person insists it is 1974, you do not need to correct the year.

Ask about the song on the radio.

Move toward the feeling behind the words, not away from the person.

If they want to go home while sitting in their own kitchen, ask what they miss about home.

Arguing rarely wins, and when it does, you both lose the evening.

What a good day at a day center looks like

A good day center is not babysitting.

It is a structured, person-centered day: meaningful activities, meals, companionship, supervision, and skilled observation.

Your person is known, expected, and gently invited into a day shaped by purpose.

Staff notice small changes in appetite, walking, or mood that a family often sees only in hindsight.

Ask any center you visit how they would spend an afternoon with your person, and listen for a plan.

Caring for yourself

You cannot pour from an empty cup, and nobody expects you to.

Sleep, a meal you sit down for, and one conversation that is not about caregiving all count as care.

Notice your own sleep, health, and mood the way you notice theirs.

If you feel angry or numb more days than not, tell someone: a friend, your doctor, or a caregiver group.

Relief and love can live in the same day; taking a break is part of keeping on.

How to ask for a break

Asking for a break is not giving up; it is how you keep going.

Pick one specific thing: Thursday afternoons, or the first Saturday of each month.

Ask a sibling, a neighbor, or your faith community by name, with the date and the hours.

Try a day center for one afternoon and notice how you both come home.

If the answer is no, ask the next person; the need does not go away because one person said no.

Learn a few things that help, with no sign-up

You will find five short lessons below. You can read each one aloud in under a minute, or print it for the sibling who will never open an app. Start with the one you need tonight.

If your person's center uses our Day Center Companion (our tools for adult day centers), a six-chapter Family Guide, with stories and tips, is inside your care app. The Day Centers Inspire white paper and the research behind it are public now, on our day center research page at /daycentercompanion/research.

These lessons are general caregiving guidance, not medical advice. For anything about your person's health, medications, or safety, call their doctor, or the center or agency you already work with.

How you will probably meet us

You will most likely meet genusConnect through a center, agency, or hospital you already know. It arrives with that organization's name and colors on it, not ours.

There is no app-store download and no price for individuals. Cost comes through the organization you work with, so ask them.

Someone already in your family circle invites you, and you open the care app from the link in the invitation.
The center or agency your person attends invites you when they start.
You scan a code or tap a link and read a public resource page, with no login and nothing to download.
A neighbor or volunteer joins the same way: by invitation from someone already in the circle.

Everyone in your circle reads the same page

When your brother is three states away and your neighbor drives on Thursdays, the hard part is keeping everyone current. One shared place does that, without a group text nobody can find later.

No family has to go it alone. You direct your data: you decide what you share, what stays private, and when.

A shared calendar, and a view of who was last in touch.
Tasks you can hand to a sibling, such as who is driving Thursday, that repeat when they need to.
Photos and moments the whole circle can see and comment on.
One health record: medications, allergies, doctors, and insurance, behind its own PIN.
An emergency card with the numbers and facts a hospital asks for first.
A key-papers checklist: living will, healthcare power of attorney, HIPAA release, where each one is, and when to review it.
If you get stuck, someone you trust can guide you through a screen from their own phone. Guiding you gives them no access to anything they could not already see.

If your person attends a day center

'How was the day?' gets a real answer

If your person's center runs our Day Center Companion and turns on evening notes, a note reaches you at the end of the day. It is drafted from what actually happened, and a staff member reads it before it reaches you.

It comes in four small parts: To talk about tonight, Ideas for home, Caring for yourself, For your next visit. The third one is written to you, not about your person.

A person on the center's staff approves every evening note. The AI cannot add a fact about your person, cannot invent an activity, and cannot skip that review.

Who can see what, in plain words

You direct your data. The family's private space for chat, photos, and notes stays private until you choose to share it. The health record sits behind its own PIN, separate from the lock on the app itself.

Your care app runs on a platform built for HIPAA-regulated care. Protected health information is encrypted in transit and at rest. Access is scoped to the organization you work with and to your own community. If your person's center turns on comments in its care app, what you write goes to the center's staff, not to a public feed.

We do not say that nobody else can ever see your information. We say what is true: access is scoped to the organization you work with and to your own community, and you choose what leaves the family's private space.

What it will and will not do

It will not give you medical advice. Neither the app nor anyone behind it diagnoses, prescribes, or tells you what to do about a symptom. Those questions go to your person's doctor, or to the contact information your center or agency gives you.

Inside the app, genusAI (our AI helpers that draft and propose; a person decides) stays small. It can highlight the button you are looking for, or draft a caption for a photo that you review before it posts. It is not the place for health questions; those go to your person's doctor. AI drafts, people decide.

When AI drafts an evening note at your person's center, a person on the center's staff approves it first. The AI does not decide anything about your person's care; people do.

If you volunteer

Show up to your volunteer shift prepared

Every volunteer has something to offer, and most of us want to do the shift well, not just show up. If the center or agency you volunteer with runs volunteer rooms, you get coaching prompts and scripts for warm, confident conversations.

Live rooms (we call them Mingle) let you play games, keep someone company, and get coaching over video from wherever you are. Virtual volunteering counts.

Coaching prompts and scripts, so the first call is not the scary one.
If your center runs the training library, short practice scenarios and five- or ten-minute huddles with a colleague.
Healthy pacing, so nobody burns out.
Recognition of the good you did.

Where to start today

Read one lesson above, tonight if you can. Then ask the center, agency, or hospital you already work with whether they use genusConnect, and if they do, ask them to invite you.

If you are weighing a day center, find one near you and ask for one afternoon. If someone has already invited you, sign in. If you still have questions, the family questions page is next.

What we won’t claim

We will not tell you that going to a day center means your person will stay out of residential care longer. We would love to say it, and the studies we have do not support that claim, so we do not say it.
We will not quote you a percentage, a savings figure, or a study we cannot hand you.
We will not promise that a person answers the phone at nine at night or calls you back within the hour. Urgent questions go to your person's doctor or to the contact information your center or agency gives you.
We will not describe an app that answers your health questions. The AI inside highlights a button or drafts a caption for your review, and it does not give medical advice.
We will not say that nobody else can ever see your information. Access is scoped to the organization you work with and to your own community, and we say exactly that.
We will not sell you anything on this page. There is no price for individuals and no app-store download; you meet us through an organization you already know.

Questions we hear

Do I need to download anything?

No. There is no app-store download. A public resource page opens when you scan a code or tap a link, with no login. If someone invites you into a family circle, you open the care app from the link in your invitation.

What does it cost me?

There is no price for individuals, and the lessons on this page are free to read with no sign-up. Cost comes through the center, agency, or hospital you work with, so ask them what, if anything, families pay.

Who can see what I write?

You direct your data. The family's private space for chat, photos, and notes stays private until you choose to share it. The health record sits behind its own PIN. If your person's center turns on comments, what you write there goes to the center's staff, not to a public feed. Access is scoped to the organization you work with and to your own community.

Can we get fewer messages?

Ask the center or agency that sends them. Staff choose who receives the evening note, so fewer updates, or none at all, is a fair thing to ask for. If comments are off in your app, use the phone number or email address the center already gives you.

What if a note about my mother is wrong?

Say so. A person approved that note, and a person corrects it. At centers using our Day Center Companion, staff can edit the note and approve the corrected version, and earlier versions are kept. Tell the center directly, or through comments if your center has turned them on.

How do I volunteer?

Through an organization, the same way families arrive. Ask a center or agency near you whether they run volunteer rooms, or tell us where you are through our contact page. There is no public volunteer sign-up on this site.

More questions and answers

Want to volunteer? Ask a center or agency near you whether they run volunteer rooms, or tell us where you are. Tell us where you are.

Back to the doors

For funders and foundations

Fund the programs. See what the money did.

You do not deliver care. You fund the senior centers, faith programs, food programs, day centers, and family-support groups that do. Then you show a board what changed. When a program you fund runs on genusConnect, it keeps one plain, dated record of its work. You read that record in aggregate, without participant records and without becoming the operator. We state the limits up front, and we never quote a percentage we cannot hand you a study for.

Talk with us about your portfolio

Read the day-center white paper

Know whether it is working, from one plain record

Is it working? That is the question every funder asks, and the record answers it in aggregate.

Any community program running on genusConnect keeps a dated record of who came through the front door, what they asked for, and what was delivered.

The same record shows which requests went unmet. So the next program, and the next grant request, rest on what people actually asked for, not on a guess.

Who came in, by scanning a code, tapping a link, or using a shared tablet at the front desk
Warm check-ins and reminders that read like a trusted neighbor, not a compliance notice, with delivery tracked
What people asked for, and what the program delivered, in one shared view
A public resource page under the program's name that anyone can read; it carries no protected health information
Unmet-need trends, reported in aggregate, that justify the next program and the next grant request

See the portfolio without seeing anyone's record

The reports we prepare for you are de-identified and aggregate. You are not given participant records, and you do not become the operator.

Access is scoped to each organization and to each person's own community. What you see is how your portfolio is doing, not a window into one family.

genusConnect is built for HIPAA-regulated care. It runs on AWS under our Business Associate Agreement with AWS, and protected health information is encrypted in transit and at rest. We sign a Business Associate Agreement with partners who handle protected health information.

Know how far to trust each number

For day programs, we sort every measure below by how it was made, so a board can tell a count from a claim.

A roll-up across all the programs you fund is something we build with you during onboarding, not a button. Tell us what your board already asks for, and we shape the reports to match.

Counted for you: who came in, messages delivered, days booked, closeout state, family notes reviewed
You measure it with the record: no-show rate, days delivered, time from intake to first day, and whether each incident was closed out
Measured locally, no claim from us: time staff spend on documentation, caregiver strain, and participant retention over time
The software does not time itself. A program runs it for two weeks and does the timing, and the result is theirs to report

If you fund adult day programs

How participation reconciles with the invoice

Ask a center for one week of its closeout and lay it beside the invoice. When a center bills from this record, the closeout and the invoice draw on the same figures.

Every day carries a state: open, in review, or finalized. A manager's PIN authorizes the change, and a "Finalized by" name is kept for audit.

In what we publish about our own software, null results appear beside wins. What you read from us is the whole record, not the flattering half.

Scheduled, showed, no-show, and no record, reconciled against billed, not billed, waived, and late fee
A single day or a Monday-to-Friday week, exported as PDF or CSV, ready to attach to a renewal
Caregiver strain asked at intake, so the program holds a baseline before it claims relief
Retention over time, measured by the program from its own record; we make no claim about it
No participant-level export across a date range today; every activity export is a single date

Write these four things into the award

Grants end. Directors leave. Software companies get bought. Before you fund a program on any platform, including ours, write down what happens then.

For day centers, we recommend pausing a rollout if duplicate after-hours work for staff rises, and we build the reports so that can be seen. Documentation gaps are shown by site and shift, never by a named person.

The decision to pause belongs to the program, not to us, so if you want a pause clause, write it with them.

What the software costs the program per year after the grant ends
What leaves with the program if we stop operating or are acquired
Whether the record survives when the director who championed it moves on
Who decides to pause the rollout, and on what evidence

The training is already built and runs again for every new hire

New hires arrive every year, and the training has to run again each time. Here it does, without the program writing it.

As of the current library: 18 branching simulations, 18 huddles, 10 activity plans in three formats, and 76 reviewed resources. There are 18 courses, 16 of them ready, with a pass mark of 80.

Each learner can export a certificate. Said plainly, there is no report yet that adds up completions across a whole center, so do not plan around one.

Two ways to fund it: place it, or co-apply with us

Place the platform at a program you already fund, so its record starts on day one. Or co-apply with us and write the method into the proposal.

carePhysics (our method: ten evidence-based principles about how people stay engaged) draws on named engagement-design and behavior-change models with a reviewer bibliography. Cite it in a proposal as a design lens, not as clinical proof.

The nonprofit lane runs through genusCommunity Foundation; commercial licensing runs through genus Inc. Both carry the label Core company on our Companies page, and the two lanes do not blur.

Place it: the program you fund gets its own care app under its own name, and its record starts on day one
Co-apply: cite the method and its named models as a design lens in the proposal, never as clinical proof
Lessons shared forward: an outreach sequence or lesson one program builds can be adapted for another you fund, set up with you during onboarding
Planned: a shared knowledge commons across grantees, credited and dated; it is a design today, not a product

If you fund adult day programs

Where the money already comes from, dated and sourced

Funding for a day program is a braid, not a single payer. Every figure below carries its year and its source. One rule sits above every stream: families are protected first.

We do not publish a cost-savings or return figure. The strongest economic study to date found savings estimates that were not statistically significant (Pizzi et al., 2025).

GUIDE: Medicare's GUIDE model gives eligible families of people living with dementia a respite allowance of $2,625 in the 2026 performance year. That is about $104 per day at the CMS base rate. It is paid through the participating GUIDE program. Source: CMS GUIDE Payment Methodology Paper, version 3.0, effective June 1, 2026.
Medicaid: about 79 percent of participants had some or all services paid by Medicaid in 2022. Source: NCHS Data Brief No. 502 (2024), from the CDC's 2022 National Post-acute and Long-term Care Study.
Older Americans Act: adult day care is a named Title III-B service, and Title III-E funds respite in adult day settings. Both reach centers through Area Agency on Aging contracts.
Family fees: the national median adult day rate is about $95 per day. Source: CareScout Cost of Care Survey 2025.
Respite is not metered here, meaning the software does not track or bill it. The participating GUIDE program holds the allowance, and the allowance belongs to the family.

What we won’t claim

We will not hand you a return-on-investment figure; the strongest economic study to date found savings estimates that were not statistically significant (Pizzi et al., 2025).
We will not claim that attending a day center keeps a person out of residential care longer. The studies we have do not support that claim, and we cite them on the research page (Udeh and Menne, 2025).
We will not quote an outcome percentage without a dated, named source you can read yourself.
The Scoring Certificate and the cross-grantee proof pack are planned, not shipped, and they carry that label until they ship.
We will not call carePhysics proven; it organizes established models into a design lens, and each program's results are measured locally.

Questions we hear

Do we see participant data as a funder?

No. The reports we prepare for you are de-identified and aggregate; you are not given participant records. Access is scoped to each organization and to each person's own community, and public resource pages carry no protected health information.

Who owns the record?

The program's staff write it, day by day, and it is their working record; you read aggregate reports drawn from it. If the program stops using us, what leaves with it is a question we answer in writing before an award. That answer does not come from a feature list. Ask for it, and write it into the award.

What does a program pay in year three?

We do not publish a price list here, and we would rather you asked than guessed. For day programs, pricing follows how the program is funded, for example per enrolled participant per month or per site. Ask for the year-by-year cost, including the years after the grant ends, before the award is written, and write it in.

Can we pause the rollout?

The program can, at any point. We recommend pausing a rollout if duplicate after-hours work rises, and we build the reports so that can be seen. Those reports show it by site and shift, never by a named person. The decision sits with the program, not with us or with you. If you want a pause clause, write it into the award with the program.

What is the pilot evidence so far, and whom may we cite?

Small, and we say so. The day-center evening note was shaped in pilot use with The Helm. The Day Centers Inspire white paper and research report grade every claim we make and name the study behind each grade. Our earlier work with Henry Ford Health System and the University of Michigan is described on our research pages. You may name those collaborations; ask us for the study design behind each before you cite a result. The pages describe the work; they are not proof of outcomes, and we do not have an outcome percentage to give you.

More questions and answers

Back to the doors

For community programs

"How was the day?" Now every family gets a real answer.

Community centers, faith groups, senior centers, and food programs are the real front door for many families. Adult day and respite programs hold love and structure together every working day; that is your craft. Ours is smaller: a warmer way in and less paperwork behind it. For day programs, one workflow runs from intake to the evening note. Your staff approve that note, written from what actually happened, before it carries the day home.

Walk through a day with your team

See GUIDE Companion

Walk the whole day

For every community program

Neighbors get in with a scan, a tap, or the tablet at your desk

You hear about food stress, caregiver burnout, and isolation long before a hospital does. So the door should be easy: a neighbor scans a code, taps a link, or uses the tablet at your desk, and help starts in a few steps. Families can also text a word your center chooses to 211-411, and a phone becomes the door.

Message and data rates may apply. Message frequency varies. Text STOP to opt out, HELP for help.

Behind the door, your logo, colors, and words are on the public resource page and on the reminder a neighbor gets on Tuesday. All of it works alongside what you already use: text, email, QR codes, and your website reach people today, with nothing to download.

A public resource page under your name that anyone can read, with no login needed
Reminders and check-ins shaped by carePhysics (our method: ten evidence-based principles about how people stay engaged), so they read like a neighbor, not a notice
Outreach campaigns to the people you serve, with delivery you can see
Live rooms where volunteers offer coaching, games, and company
Training and help sheets your staff and volunteers can print and use
What people asked for, reported in aggregate, to shape your next program and your next grant request

For day programs

Run the whole day in one place, with less typing on the floor

Your intake, roster, reservations, activities, incidents, evening note, closeout, and reports run as one day in one place. On the floor, an aide selects everyone at the table, picks one activity, and taps a button that reads Save for 14. At 3:45 staff open a readiness check that shows what is still unwritten while the person who was there can still write it.

Intake taken with the family, with care cues for allergies and medication support carried onto the roster
Reservations with capacity and a waitlist, so a full Friday cannot be quietly overbooked
Activities, observations, and mood captured close to the moment, with time presets
An emotion dial with an Unable to tell choice that stores nothing rather than a guess
Incidents with an owner, a due date, and a status; locking or resolving one is a human action
Reservations and attendance kept separate, so what happened never writes over what was planned

For day programs

Tonight's note goes home after a person on your staff approves it

At pickup, every family asks how the day went. From the day's record, genusAI (our AI helpers that draft and propose; a person decides) drafts a note. It follows the style the family chose at intake: warm, brief, or clinical. A person on your staff approves every evening note, and the AI cannot add a fact that is not in the day's record.

A section called To talk about tonight
A section called Ideas for home
A section called Caring for yourself, written to the family caregiver
A section called For your next visit
Private staff notes stay out of the family note unless a staff member unlocks them

For day programs

Closeout you can hand to a payer or a grant committee

Your closeout lines up scheduled, showed, no-show, and no record against billed, not billed, waived, and late fee. You settle each no-show one of three ways, with the reason recorded, and every finalized day keeps a Finalized by name for audit. Export a day or a Monday-to-Friday week as PDF or CSV and attach it without retyping a figure.

Every day carries a state: open, in review, or finalized
A waived fee posts as a zero line with its own marker, so a fee you let go is still a line you can show
Reports cover the day-center summary, participant activity, billing summary, and family communications
You bill a documented day only where a payer's rules allow it; eligibility, contracts, and payer rules decide payment

For day programs

Turn on the family loop, and families send drop-off context and read the reviewed note

Your center chooses what families see. In the morning a daughter sends drop-off context: how her father slept and who is driving. In the evening the reviewed note arrives. Reservation requests wait for your staff to approve, waitlist, or decline, and each secure comment goes to a person on your staff who owns it.

Reviewed updates go out; drop-off context and comments come in
Family requests stay pending until a person on your staff resolves them
Comments can be switched on or off at each site
Care-circle sharing follows consent and role controls, so a son nearby and a daughter three time zones away read the same reviewed note

If you run an adult day program

Where the money comes from, with a year and a source on every figure

Funding for adult day comes from several payers at once, not one, and every figure here carries its year and its source. Respite under the CMS GUIDE model is paid through the participating GUIDE program, and the allowance belongs to the family.

The Day Center Companion page walks the whole day in order, from intake to closeout, and says where each step stops.

Medicaid paid some or all services for about 79% of participants in 2022 (NCHS Data Brief No. 502, 2024, from the 2022 NPALS wave)
The Medicare GUIDE respite allowance is $2,625 for the 2026 performance year, about $104 a day (CMS GUIDE Payment Methodology Paper v3.0, effective June 1, 2026)
Through your Area Agency on Aging, adult day is a named Older Americans Act Title III-B service, and Title III-E funds respite there (CRS R43414 and ACL budget documents)
Family fees remain most centers' baseline: the 2025 CareScout Cost of Care Survey places the national median adult day rate near $95 a day

For every community program

Training you did not have to build

Your staff and volunteers turn over, and every new hire needs the same lessons. As of the current library, there are 18 branching simulations, 18 huddles, 10 activity plans in 3 formats, 76 reviewed resources, and 18 courses, 16 of them ready. Every lesson runs again for each new hire. We say plainly that managers get no roll-up report, so nobody plans around a report that does not exist.

Simulations: three decisions each, with coaching on every branch; ratings are words like strength or practice, never numbers
Huddles: five or ten minutes with a colleague, in five steps: Prepare, Read, Discuss, Practice, Commit
Courses: pass mark of 80, with a certificate each learner can export
The record is the learner's own; a manager cannot open it
Big Screen: games, music, and prompts on a shared display, while the console stays with staff
Pretty Paper: printable bingo cards, matching games, and caller keys for the screen-free tables

How we work with you

What we hold ourselves to while we work with you

We recommend pausing a rollout if the software adds duplicate after-hours work for your staff, and we build the reports so that can be seen. Where documentation varies, the report shows it by site and shift, never by a named individual. When AI drafts something on your behalf, such as an evening note or a lesson, a person on your team approves it first.

All of this is built for HIPAA-regulated care. It runs on AWS under our Business Associate Agreement with AWS and encrypts health information in transit and at rest. Access is scoped to your organization and to each person's own community, and we sign a Business Associate Agreement with partners who handle protected health information.

Staff single sign-on and any connection to your records system are scoped with your IT team during onboarding; no partner runs single sign-on today. Your logo, colors, and words go on the app and the public page, and texts and emails go out under your name; we set that up together during onboarding.

How a program starts

Start with one call and a week of your closeout

One 30-minute call, then a working preview in your brand within 24 hours, with sample people and sample notes. No real health information is entered during the preview. A self-serve path for smaller organizations is coming; today every preview starts with a call.

Bring one week of your current closeout, however you run it today, and your intake form. Tell us how families hear about the day now, and bring the question you most want answered. Come with the people who will use it: a program director and one floor lead, if you can.

What we won’t claim

We do not publish a return-on-investment figure or a savings figure; when a number appears here, it carries its year and its source.
We do not claim that attending a day program postpones a move into residential care; the studies we have do not support that claim.
We do not meter respite; the participating GUIDE program holds the allowance. GUIDE documentation written when a covered day is confirmed is planned, not shipped.
There is no participant-level export across a date range; every activity export is a single date.
There is no training roll-up for managers; each learner's record is their own, with a certificate they can export.
Nothing is sent back to a referring practice automatically.

Questions we hear

What do families see?

Only what your center switches on. When the family loop is on, a family sees the reservation calendar, requests or cancels a day, and reads the account statement. In the morning they can send drop-off context; in the evening they read the note a person on your staff approved. Secure comments go to a staff owner. Private staff notes stay out of the family note unless a staff member unlocks them, and care-circle sharing follows consent and role controls.

What if a note is wrong?

A person on your staff reads every evening note before it goes home and can edit, reject, or route it. The AI drafts only from the day's record and cannot add a fact that is not there. If something wrong still goes out, your staff correct it, and every note keeps its version history, so the correction is on the record rather than quiet.

What does it cost?

The preview is complimentary: the Preview Edition is a branded preview at no cost, with the day-center workflow on sample data. After that, pricing is set with you to fit how your program is funded. It includes the closeout and reporting exports your payers audit. We do not quote a savings figure to justify it. Ask us on the call what a program pays in year three, after a grant ends; we would rather you knew now.

Is this only for GUIDE programs?

No. GUIDE Companion is built for dementia programs and adult day partners in the CMS GUIDE model. The same day workflow keeps the attendance record, whoever pays for the day. That can be a Medicaid waiver, an Area Agency on Aging contract, VA adult day health care, or a family fee. Eligibility for each of those stays with the payer and its case managers. Respite under GUIDE is paid through the participating GUIDE program; we do not meter it. If you already partner with a GUIDE program, bring them to the call.

Is this only for day centers?

No. Senior centers, faith and food programs, and family-support groups use the front door, the public resource page, outreach, live rooms, and training without ever running a day program. The day workflow, from intake to the evening note and closeout, is switched on only if you run one. You pick the pieces your community needs, and everything runs under your name.

More questions and answers

Message and data rates may apply. Message frequency varies. Text STOP to opt out, HELP for help.

Back to the doors

For care agencies and community partners

Keep care connected, wherever people call home.

Home care agencies, independent living and assisted living communities, and community service partners share a need: keeping people, families, and teams connected. Shape an environment around your audience, with your name, your resources, and the tools that fit. Bring updates, shared calendars, and useful information together so residents, participants, and families know what comes next.

Book your call

Talk to the team

Bring families into the circle of support.

Care continues between visits, activities, and conversations with staff. Give residents, participants, families, and the people supporting them one place to keep what matters, under your name.

No family has to go it alone. They stay in touch with your team and know what comes next. Chat, photos, and notes live in the family's own community space inside the app.

Health information sits behind its own lock inside the app, apart from chat and photos.

Medications, allergies, doctors, and insurance in one health record
Observations and vitals, with target ranges and charts
A care report the family can share as a PDF
Emergency information and contacts, ready before anyone needs them
Shared tasks, and a shared calendar with tomorrow's visit
Chat and photo moments, so the good days get shared too

See who needs a check-in or extra support.

Check-ins, notes, and surveys help your team see who has responded and who has gone quiet. Staff decide who needs a conversation, a visit, or another kind of support. In home care, that can help care managers decide which homes need a nurse today.

When a daughter is stuck on a screen, a nurse or volunteer can guide her to the right place from the office. The helper follows the same taps and scrolls, and sees only what the helper was already allowed to see.

One organization, many teams, with access matched to their roles.

Your care agency or community partner is set up as one organization. Each site or branch, and each family's community, sits inside it. Branch roles see their own families.

Access is scoped by organization, site, and community; we walk your IT team through exactly how during onboarding. Reports across regions and for each branch are set up with you at the same time, not switched on from a menu.

Your name on the app, the public page, and the messages it sends.

Your logo, your colors, and your typography carry across the app, the public resource page anyone can read, and the texts and emails it sends. Texts and emails go out under your name; we set that up together during onboarding.

A daughter who never downloads anything still gets a text with a link to a page in your name and colors.

For home care: help families learn between visits.

Safe transfers, medication routines, the hard conversation: your clinical lead writes them, with drafting help from our AI. When our AI drafts a lesson, a person on your team approves it first.

Your existing PDFs, videos, and FAQs become short check-ins and lessons families can read on a phone. A six-week new-caregiver sequence is the kind of program you build here, not a course we ship in the box.

AI drafts, people decide.

Your team gets help writing, finding, and preparing from genusAI (our AI helpers that draft and propose; a person decides). When it drafts a lesson, a check-in, or a suggested reply for your team, a person on your team approves it first. A drafted change waits for that yes; it does not change a record on its own.

Inside the family's app, the AI does two smaller things. It highlights the control a person is looking for, and it drafts a photo caption for them to review first.

Identifiers are removed or minimized in prompts wherever feasible. Sensitive exchanges run on models we train and host ourselves; general tasks use leading frontier models. We go through which providers process which prompts, and under what agreements, with your IT team during onboarding, not on this page.

Built for HIPAA-regulated care, said in specifics.

Your care app runs on AWS under our Business Associate Agreement with AWS. We sign a Business Associate Agreement with partners who handle protected health information. Health information is encrypted in transit and at rest.

Access is scoped to your agency and to each family's own community. Staff sign in with multi-factor authentication; families can sign in with a one-time code sent by text, no password to remember. Access is logged.

That phrase, built for HIPAA-regulated care, describes how it is built, not a certification we hold. Your IT team's questions about logging, keys, and backups get specific answers in the onboarding conversation, not on a web page.

Keep the texts, emails, and website you already use.

Your care app works alongside what you already use: text, email, QR codes, and your website reach families today. Your records system might be a scheduling and EVV system or a home-health EMR. Staff single sign-on and any connection to your records system are scoped with your IT team during onboarding; no partner runs single sign-on today.

A family that will never download anything can still scan a code or tap a link and land on a resource page with your name on it.

No connection to a scheduling, EVV, or EMR system is shipped today, and we would rather say so before your IT team asks.

Days 1 to 90: what we do together, starting with your preview.

Day one: after a 30-minute call, a working preview in your brand within 24 hours, loaded with sample people and sample notes. No real health information is entered during the preview. Bring a scheduler, a nurse, and a family member if you can; they are the people who will tell you whether it works.

Days 1 to 30: brand, setup, guardrails, and staff sign-on scoped with your IT team. Days 31 to 60: your existing PDFs, videos, and FAQs become check-ins and lessons, with your reviewers' approval. Days 61 to 90: training, a soft launch with one program, and rollout. A group of newly admitted families works well as the first program.

The preview is complimentary; we call the tier Preview Edition. A self-serve path for smaller organizations is coming; today every preview starts with a call.

What we won’t claim

We will not put an outcome percentage on this page; the only numbers we publish carry a date and a named source.
We will not say the app keeps anyone out of the hospital or out of a care facility. The studies we have do not support that claim.
We will not name an agency or quote a result here; this page describes what your families and nurses get, not who already did it.
We will not describe the platform as certified; it is built for HIPAA-regulated care, and we say what that means in specifics above.
We will not promise an assistant that answers a family's caregiving questions at nine at night. What we describe above is the in-app help we have verified.

Questions we hear

Will the AI give medical advice?

No. Our AI drafts lessons, check-ins, and suggested replies for your team, and a person on your team approves them first. Health questions belong with your nurses, not with software.

Do families need to install anything to start?

No. A text or an email with a link, or a code they scan, opens a resource page under your name in any browser. The care app comes next, by invitation, when a family is ready for it.

Who owns our content?

Ask us before rollout and we answer in writing: what is yours, what leaves with you if we part ways, and in what format. We do not answer that question from a web page.

Can a family turn messages down?

Yes. Replying STOP to any text ends the texts. Which messages a program sends is set when you build the program with us. How a family asks for fewer is something we settle with you during onboarding.

How does a wrong note get corrected?

A person on your team wrote or approved the note, and a person on your team edits it. How a correction is shown to the family is something we settle with you during onboarding, not something the AI decides.

Can each branch see only its own families?

Yes. Access is scoped by organization, site, and community; we walk your IT team through exactly how during onboarding. Branch roles see their own families, and regional roll-ups are set up with you.

More questions and answers

Message and data rates may apply. Message frequency varies. Text STOP to opt out, HELP for help.

Back to the doors

For health systems, providers, payors, and partners

Extend your team past the front door, under your own name.

Whether you are a provider practice, health system, payor, or care partner, connect people with support beyond the appointment. Discharge follow-up, dementia care under the CMS GUIDE Model, a department front door, member outreach: run each one in your brand, with your clinicians deciding what goes out. All of it is built for HIPAA-regulated care and reaches people by code, link, text, and web before they download an app. Here is what is built, what is scoped with you, and what we will not claim.

Book a 30-minute scoping call

Talk to the team

Read the security page

Start from a program that already exists.

You do not have to start from a blank page. Five programs exist today, and each one can carry your name. Reminders and check-ins carry the routine follow-up, so your clinicians spend their time on the people who need a clinician. That is how you reach more people without adding headcount.

Discharge Companion follows a person home. A patient scans the code on the discharge sheet, or texts one word to 211-411, and your unit's follow-up resources go to work. Texting the word is how a patient opts in to messages about the program.

Message and data rates may apply. Message frequency varies. Text STOP to opt out, HELP for help.

GUIDE Companion, for dementia programs under the CMS GUIDE Model and the adult day partners who provide respite.
Day Center Companion, for adult day centers: intake, arrival, activities, closeout, and an evening note a person on your staff approves before a family reads it. Read more at /daycentercompanion.
A department front door: a public page anyone can read and a code to scan, bringing a person to the right office under your name.
Member outreach campaigns: scheduled texts and emails to a member list, with a send history your team can inspect.

Your name on it, your reviewers behind it.

Your logo, colors, and typography carry across the app, the public pages, and every automated message. Families and members see your name and colors. Texts and emails go out under your name; we set that up together during onboarding.

Your designated reviewers approve content before it is published. When AI drafts something on your behalf, such as an evening note or a lesson, a person on your team approves it first. That rule runs through genusAI (our AI helpers that draft and propose; a person decides). AI drafts, people decide.

Built for HIPAA-regulated care, with the specifics.

Your programs and their data run on AWS under our Business Associate Agreement with AWS. We sign a Business Associate Agreement with partners who handle protected health information. No agency issues a HIPAA certificate, so we show you the controls instead.

SOC 2 Type II readiness: the architecture supports the criteria, and there is no report to hand you yet. The detailed control inventory, including logging coverage and recovery windows, is in the security overview we share under NDA. Here are the controls, by category:

Protected health information encrypted in transit and at rest
Managed key handling
Access logging with identifier redaction
Multi-factor authentication for staff
Access scoped to your organization, to each person's own community, and to the signed-in user
Backups

Works alongside what you already use.

It works alongside what you already use: text, email, QR codes, and your website reach families today. Staff single sign-on and any connection to your records system are scoped with your IT team during onboarding; no partner runs single sign-on today.

Live today: text, email, and push messages, an embeddable player and public pages you can place on your own site, and real-time team chat. Partner APIs are scoped with your team; there is no public developer program.

Planned: EHR, FHIR and HL7, and data-warehouse connections. There are no shipped connectors today, so we scope them with your IT team rather than promise them on a web page.

If you run a health plan

Members see a partner, not a payer.

If you run Medicare Advantage, Managed Medicaid, or employer group plans, you want members who stay engaged, not just claims that get processed. Reminders, check-ins, and a place to ask for help can help close care gaps and bring social needs into view.

You can list the local providers and community programs you trust, so each member sees your name next to help that is close by. Measures like HEDIS, Stars, and CAHPS are design targets your program tracks, not outcomes we claim. Ask whether it lifts a rating and we will say it plainly: the studies we have do not support that claim.

If you serve a member base or a county

One program in your name can serve a member base or a county.

An association rallies members around a cause. A county hears about missed rides in one office and food stress in another. Both can run one program in their own name, shaped to fit: a public resource page anyone can read, codes to scan, reminders, and campaigns in one voice.

Reports we prepare for a council or a board are de-identified and aggregate; you are not given resident records.

Planned: connected devices, so a reading from a scale or a wearable can lead to a check-in from a person. Device makers should ask us where that work stands before planning around it.

If you want the whole platform under your name

Go to market under your own name while we stay in the background.

As an enterprise licensee, you take the whole platform, white-labeled, and offer it as your own. You get one vendor, one support relationship, and one security review. Your customers see your name; we stay in the background.

genus Inc. is the company that licenses the platform commercially. How it relates to the foundation, the method, and the operating companies is laid out at /companies.

Days 1 to 90, together.

It starts with one 30-minute call. Then you have a working preview in your brand within 24 hours, with sample people and sample notes. No real health information is entered during the preview. A self-serve path for smaller organizations is coming; today every preview starts with a call.

Days 1 to 30: your tenant, your brand, the groups you serve, and your guardrails, with staff sign-on scoped with your IT team.
Days 31 to 60: your existing PDFs, videos, and FAQs become check-ins and lessons, published only with your reviewers' approval.
Days 61 to 90: training, a pilot cohort in one department or program, then go-live.
Throughout: we recommend pausing a rollout if duplicate after-hours work rises, and we build the reports so you can see it.

The science underneath, offered as a lens, not as proof.

Every reminder and check-in your program sends follows carePhysics (our method: ten evidence-based principles about how people stay engaged). The principles draw on named engagement-design and behavior-change models, with a bibliography your reviewers can read.

We offer it as a lens your clinical reviewers can use when they judge a check-in or a lesson, not as clinical proof. Our research pages describe studies and pilots with Henry Ford Health System and the University of Michigan. Ask us for the study design behind any result you read there. Research pages are not themselves validation.

What we won’t claim

We do not put outcome percentages on a web page; a number appears only with a date, a named source, and a qualifier.
We do not promise service levels, uptime, or response times here; those live in a contract.
We do not claim a SOC 2 report; the architecture supports the criteria, and there is no report to hand you yet.
We do not list single sign-on or records connections as features; they are scoped with your IT team, and no connector has shipped.
We do not describe our production security posture on a web page; the control inventory is in the security overview we share under NDA.
We do not put identifiers of any kind on a public page, and public resource pages carry no protected health information.

Questions we hear

Where does our data live?

On AWS, under our Business Associate Agreement with AWS. Store-by-store detail, including backups and recovery windows, is in the security overview we share under NDA.

Who can see whose data?

Access is scoped by organization, by community, and by the signed-in user. Your staff work within your organization, and a family member's view is scoped to their own community. Role names and the authorization detail are in the security overview.

How do we leave, and what comes with us?

The exit terms are set in the agreement before anything goes live: what comes with you, in what format, on what timeline, and what may remain in aggregate. We would rather write that down with you than promise it on a web page.

What does the AI touch, and who approves it?

Our AI drafts and proposes: a lesson, a check-in, an evening note, a caption. When it drafts something on your behalf, a person on your team approves it first. In the app it can highlight a control or draft a caption for a person to review. Any action it proposes waits for a person to approve or reject it before anything changes.

Which model providers see prompts, and under what agreement?

General tasks use leading frontier models. Sensitive exchanges and real-time analysis run on models we train and host ourselves. Identifiers are removed or minimized in prompts wherever feasible. Provider names and their agreements belong in the security overview, not on a public page.

Who signs a BAA with us, and which legal entity?

We sign a Business Associate Agreement with partners who handle protected health information. genus Inc. is the company that builds, operates, and licenses the platform, as described at /companies, and your agreement names the signing entity.

More questions and answers

Message and data rates may apply. Message frequency varies. Text STOP to opt out, HELP for help.

Back to the doors

For device and technology companies

Bring your innovation into the everyday work of care.

Building an IoT device, a monitor, a transportation service, or a robotics solution? Entering the care market means connecting your product to the people, teams, and routines it is meant to support. Genus offers an ecosystem to build around: a place to connect your technology with communication, resources, and coordinated support.

Discuss your device or service

Explore devices and integrations

A product is more useful when it fits the whole experience.

Help people understand what your product does, how to use it, and who can help. Bring onboarding, guidance, and family or staff communication around your device or service, shaped for the audience you want to reach.

IoT devices and connected home technology
Monitors, sensors, and wearable devices
Transportation and mobility services
Robotics and assistive technology

Start with a care need and a focused pilot.

Identify who will use your product and what should happen before, during, and after they use it. Work with care and community partners to shape a focused experience, learn from participants and staff, and refine the path to market.

Connect the right information to the right people.

Plan the connection around your product: the information it provides, the people who need it, and the actions they can take. Live device readings and service connections depend on a supported integration configured with your team.

What we won’t claim

A device category listed here does not mean every product in that category is already integrated. Compatibility and the connection are confirmed with each partner.

Questions we hear

Is this only for medical devices?

No. We welcome companies working on connected home devices, monitors, transportation, robotics, and other technologies that support everyday care. Start with the need your product addresses and the people you want to serve.

Can our product connect directly to Genus?

We review the available interfaces, information flow, permissions, and support responsibilities with your team. A live connection needs a supported, configured integration; it is not assumed from the device category.

How do we begin entering the care market?

Bring a product description, your intended audience, and one practical use case. Together we can define the care experience, integration needs, and a focused pilot.

More questions and answers

Back to the doors

For developers and product builders

Build in the ecosystem. Grow a product of your own.

Use Genus as a launchpad. Developer kits help your team add new functionality to an existing ecosystem, bring a product to market faster, and learn from the people it serves. Start connected to Genus, with a path to a product that can stand independently.

Discuss developer kits

Explore the ecosystem

Start with a foundation you can build on.

Use developer kits and reusable components to focus on the capability that makes your product useful. Build around communication, content, resources, and connected care experiences, with the components and integration approach selected for your project.

Launch, learn, and keep improving.

Introduce new functionality within a care experience that already has a purpose. Work with participants and partners to test the idea, learn what helps, and refine the product before expanding. Less work on the starting foundation leaves more room for your own innovation.

Plan for your own product from the beginning.

Your idea can begin as part of the Genus ecosystem and develop into an independently operated product. Plan your brand, product boundaries, ownership, licensing, and hosting with that direction in mind. Identify which components travel with your product and which remain connected to Genus.

What we won’t claim

A standalone product is a planned development path, not an automatic export. Component licensing, dependencies, and operating responsibilities are agreed for your project.

Questions we hear

What can we build with the developer kits?

Start with the functionality your audience needs: a new tool, a resource experience, a connection, or a service. We work with you to identify the kit components and integration approach that fit your product.

Can our product eventually operate independently?

Yes, that can be the direction from the outset. We plan the product boundaries, licensing, dependencies, hosting, and support needed for independent operation with your team.

How do we get started with a developer kit?

Tell us what you want to build, who it will serve, and whether you want to stay connected to Genus or work toward an independent product. We can then discuss the appropriate kit components, access, and a first development scope.

More questions and answers

Back to the doors