genusAI
How genusAI supports the work
Sometimes the useful next step is finding a resource, putting a thought into words, or making sense of a busy day. Within configured genusConnect® experiences, genusAI can help with those tasks. People check the information, choose what to use, and remain responsible for decisions.
What genusAI is
Help within the work you are already doing
genusAI is the name we use for AI assistance across genusConnect experiences. The assistance available to a content author, a day-center team, or a family member is not necessarily the same. It depends on the product, the task, the information provided, and the permissions and configuration in place.
In the Partner Portal, Companion can explain a page, help find a workflow, prepare a draft, or propose a supported action. It is not a human coach, an independent care professional, or permission to act outside your role. AI can be wrong, including when an answer sounds confident.
Guidance
Find a resource or understand a workflow
A team member can ask what a supported page is for or how to begin a task. Portal Companion can use the available page context and configured knowledge sources to offer an explanation or a step-by-step guide. Where supported, guidance can point to the relevant control or page.
For example, a new coordinator might ask where to review a reservation. Guidance helps them find the workflow; it does not decide who should attend or give them access they did not already have. Staff should check that any explanation fits their current screen and local practice.
Content drafts
Turn an idea into something people can review
An author can work from a purpose and audience, clarify a resource goal, and prepare a draft genus Tile. Supported editing tools can suggest changes to text, questions or media. The author reviews the proposed changes and chooses what to apply.
A draft is not a published resource. Your team still checks accuracy, language, accessibility, source material and any clinical content. Organization-specific guidance can inform the work when configured; it does not guarantee that every draft reflects your mission or that every media format can be produced.
Review & insights
Review the recorded day with more context
In supported Day Center workflows, staff can work with selected attendance, activity and observation records to prepare a day review or family-summary draft. The system can surface recorded signals for attention and help organize the account. Staff check what was included, what is missing, and whether the wording is supported.
A repeated observation may be a reason to ask a better question, not a diagnosis. A single day cannot establish a trend. Participation counts, completed activities and family responses describe parts of the program; they do not show, by themselves, that genusConnect caused a better health outcome.
Summaries depend on the records available and the configured workflow. Private notes and family-facing information have different audiences. A reviewer must correct omissions, remove unsupported conclusions and choose the appropriate next step.
Supported actions
Prepare a specific action for approval
Authorized staff can use natural language to prepare supported Day Center actions, such as a reservation change, an attendance entry, an activity note, or a family-report preview or draft. Companion asks for missing details when needed and presents the proposed action for review.
The staff member checks the person, date and details, then approves or rejects the proposal. Approval does not bypass permissions or make every action available. The interface reports the result; if an action fails, staff need to resolve it rather than assume the record changed.
Ask and clarify
Say what you want to do. Resolve missing or ambiguous details before continuing.
Review the proposal
Check the intended person, action and information in the context of your responsibilities.
Approve or reject
An authorized person decides whether the supported change should happen.
Check the result
Confirm the reported outcome and any follow-up needed in the underlying workflow.
People decide
People decide what is appropriate
A useful AI feature needs a clear purpose and a person who can check its work. Before using it in a program, agree which tasks are enabled, which information may be used, who can review an output, and how mistakes or concerns will be handled.
Source selection, permissions and review matter as much as the wording of an answer. Do not put private participant information into general content prompts or product-knowledge stores. Shared learning between organizations is not shared access to private records or automatic cross-partner AI training.
- Check source information and correct or reject unsupported statements.
- Keep internal notes, family communication and other sensitive records within their approved audiences.
- Use established clinical, incident and emergency procedures when they are needed. AI assistance is not an emergency service or an autonomous care decision-maker.
- Confirm available features, configuration and responsibilities for the intended deployment.
An illustrative Day Center example
Small tasks within a human-led day
An activity coordinator prepares a discussion resource and checks an AI-assisted draft. A facilitator uses the approved resource with participants in a shared activity. Staff record what actually happened, then review a proposed family summary against those records.
An authorized family member receives the approved report through the channel configured for the program. Their question or home update goes back to staff for follow-up. AI can assist at particular steps; the activity, relationship and decisions remain human.
This is an example of how capabilities may be combined, not a customer result or evidence that every connection is enabled.