A clearer picture.
Before we begin.

Work is in development. You can explore the product through a guided demonstration with fictional records and discuss an early evaluation. Live customer deployment is a separate step that requires an agreed scope, appropriate controls and approved system access.

Home-care and community-based care teams coordinating recurring schedules and last-minute coverage, including supported living and services for people with intellectual and developmental disabilities. We explore fit around the actual visit, staffing and decision requirements of each organization.

We have not published standard subscription pricing. An evaluation starts with your workflow, organization size and system requirements. Any paid pilot or subscription needs its own written scope and commercial terms; a product conversation does not enroll your organization.

We do not promise a deployment timeline before understanding the source system and required approvals. The first conversation and fictional-data demonstration do not require a connection. A live timeline depends on vendor access, customer review and the agreed operating scope.

Scheduling compares a proposed plan against availability, qualifications, continuity and working-time constraints. Coverage recovery handles a change to that plan: an open visit, caregiver responses, questions, a human decision and confirmation of the result. Work is being built to keep those two workflows connected.

Our approach keeps coordinators responsible for the important decisions. The product is designed to organize context, suggest eligible options and carry the decision history forward. Missing information, timing questions and unsafe options remain visible for a person to resolve.

The current Work preview does not contact real caregivers. It illustrates inbound messages, scheduler-recorded callouts and controlled SMS outreach. Automated voice handling, call recording and transcription are not part of the current Work preview. Any live communication requires separately approved setup and operating rules.

The illustrated workflow stops and hands the case to a coordinator with the reasons visible. It does not relax a qualification, rest or service requirement to produce a match. The organization decides the appropriate next action through its own escalation process.

A reply records interest. Timing, qualifications, approval and the assignment recorded in the scheduling system still need to be resolved. Work’s development model keeps those steps separate so an unanswered question or unconfirmed change does not look complete.

No live vendor integration is announced. We are evaluating approved interfaces for operational schedules and staff assignments. Share the exact product and edition you use, and we can discuss documentation, permissions, customer sponsorship and a suitable evaluation path.

The intended approach is to work with an approved source system, rather than replace clinical, billing or care-record functions. Whether a particular workflow can be supported depends on the source system’s available interfaces and the permissions the vendor and customer authorize.

Please use general workflow descriptions only. The first demonstration uses fictional records and does not need patient information, staff records or account credentials. Any later data access must use an agreed, approved process.

We are not claiming a security or compliance certification, or readiness to process customer protected health information. The current Work application uses fictional records. Security, privacy, contractual and operational requirements must be addressed before any live pilot.

Bring the shape of the problem: your service model, the system you use, the people who make decisions, recurring constraints and one difficult day described without personal records. Our evaluation guide helps you organize those questions.

Agree on the workflow, the starting baseline and what counts as a verified outcome before a pilot. Useful measures include coordinator effort, unfilled visit time, unresolved questions and confirmation accuracy. We have not published customer performance results.

Yes. Email hello@blendwave.ai with the relevant product, interface and enrollment process, or reply to an existing inquiry. Our integrations page describes the operational schedule and staff-assignment information we are currently exploring.