The short version
A parent at home needs help with an errand. An adult child elsewhere needs to understand the request, and a relative nearby needs to know whether anyone has picked it up. Wrynkle brings these everyday tasks into a shared family workflow, without making every private conversation a family update.
Conceptual brand illustration
Product, owner and current status
Owned and operated by Datahase Dev Private Limited. Parents participate through WhatsApp; family members use the browser console. Standalone mobile apps are listed as coming soon.
Public sources checked on
The everyday problem
Living in another city or abroad changes how a family coordinates small tasks. A grocery item, an appointment to remember and a request for a lift can arrive across several conversations. The useful question is often practical: what has been shared, what needs attention, and who has offered to help?
Wrynkle gives the parent a familiar way to speak or type in their own language. Relatives use a separate browser console for the shared work. The product is a family companion; the coordination described here is not remote health monitoring or a substitute for speaking directly with a parent.
Who does what
- The parent chooses to participate
- The parent joins from their own phone and agrees to the consent notice. They can use WhatsApp voice notes, text or photos, decide whether to share messages with organizers, and send STOP. Entering their number in the console is not consent.
- An organizer manages the circle
- An organizer sets up the family and invites relatives with organizer, can-help or can-view access. The role is about managing a family circle, not granting every member access to every conversation.
- Relatives coordinate what is shared
- Family members see shared information according to their role: plans, check-in replies, lists and help requests. A relative nearby and an adult child overseas can participate in the same circle, with different responsibilities and access.
An illustrative workflow
Agree before starting
The organizer prepares the family circle and joining invitation. The parent joins from their own WhatsApp and accepts the consent notice themselves. Participation starts with that decision, rather than with a relative enrolling them silently.
Capture a small everyday task
The parent sends a voice note asking to add groceries to a list. They share the list with family. If they ask for a reminder, Wrynkle reads it back and waits for confirmation before setting it.
Coordinate in the console
Authorized relatives can view the shared list and edit it. A scheduled check-in can ask how the parent is doing, but its reply is conversation context, not a clinical observation or proof of safety.
Make a help request visible
If the parent asks the family for help, the console shows a help request. A family member can select “I’m on it” so the parent knows who is responding. Available notifications depend on settings and services; the family still needs a separate plan for urgent situations.
Three product decisions
- Use different interfaces for different jobs
- The public walkthrough puts voice and text on the parent’s existing WhatsApp, while the console gathers shared plans and requests for relatives. The design lesson is to start with each person’s task and familiarity, rather than require everyone to learn the same dashboard.
- Keep participation and sharing deliberate
- The privacy policy separates private conversations and remembered details from the shared dashboard. Roles govern family access, and the parent chooses message sharing. STOP ends new message processing and scheduled messages; deletion of earlier records is a separate choice.
- Distinguish a request from a response
- The messaging guide describes a help request followed by a family member’s acknowledgment. The terms also say alerts can be delayed or missed and cannot make someone respond. Showing who has taken responsibility is useful, but it does not turn a notification into an emergency service.
What the public evidence establishes
The official walkthrough describes lists, reminders, check-ins and help requests across WhatsApp and the console. The messaging guide explains reminder confirmation and the parent’s ability to stop. The privacy policy describes role-based sharing, processing by AI and speech providers, and controls for export and deletion. These are documented product behaviors, not independently measured family outcomes.
AI can mishear or misunderstand a message. The terms ask families to check important appointment or medicine information directly with the parent. Reported medicine records are records of what was reported, not independent confirmation that a dose was taken. Wrynkle’s servers and service providers process content; the privacy policy explicitly says it is not end-to-end encrypted.
Scope and boundaries
Wrynkle is not a doctor, medical device, medical service or emergency service. It does not diagnose, change treatment or doses, monitor health, or contact emergency services. An alert does not guarantee a response, and a missing check-in is not proof that someone is safe. In an emergency, contact the appropriate local emergency service directly. The browser console is available; standalone mobile apps and live voice calls are not currently available according to the public site. This study describes documented features, not clinical validation or a physical-device acceptance test.
Custom solutions for care organizations
Proposed adaptations · Discovery required
- Clinics: preparation and nonclinical requests
- A custom workflow could help people prepare appointment paperwork, confirm logistical requirements and send nonclinical follow-up requests to a named staff queue. The clinic would define approved content, who owns each request, and when a person must contact clinical staff through an established channel.
- Elder care: visits, errands and family updates
- A provider could explore visit planning, transport or shopping requests and consented updates to authorized family members. The reusable lesson is separating a person’s private conversation from an agreed shared update. Staff roles, caseload boundaries and handover responsibility would require a new design.
- Hospitals: patient-family logistics
- A discovery engagement could map transport, paperwork and family coordination, with clinician-approved instructions only where the organization defines and reviews them. This would be a new workflow alongside existing care processes, not a claim that Wrynkle connects to hospital systems or manages patient records.
What additional sector work requires
- Define the service and accountable owner
- Map consent, verified identity, family authorization, staff queues, caseload separation, operating hours and handovers. Specify who responds and what happens when a request is unanswered before choosing the interface.
- Design the technical connections
- Assess official business-messaging setup, message templates and delivery limits. Discover scheduling or system-adapter requirements with the organization; no adapter, EHR integration or access to an existing system is assumed.
- Review information handling and clinical boundaries
- Design access, audit and retention controls around the minimum necessary information. Any patient-record use needs an appropriately reviewed architecture. Jurisdiction-specific privacy, security and clinical review must shape the scope; compliance and delivery feasibility cannot be promised before discovery.
These proposals exclude diagnosis, treatment changes, autonomous triage and emergency-response guarantees. A family companion’s consent flow cannot simply be copied into an institutional service. Discovery must establish the organization’s obligations, approved workflows, human responsibility and whether the proposed system should be built at all.
Inspect the sources
- Wrynkle product and availability
WhatsApp entry point, family console, everyday tasks and mobile-app distribution status.
- How Wrynkle works
Family roles, parent consent, shared workflows and help acknowledgments.
- WhatsApp messaging guide
Joining, reminder confirmation, STOP and delivery limitations.
- Privacy and sharing
Private versus shared information, processing providers, retention and export/deletion controls.
- Product scope and terms
AI limitations, current exclusions and the absence of medical or emergency guarantees.