Dockie-talkie Agent Whenever
Patient messaging channels · Pre-launch validation
Routine patient inquiries and appointment preparation continue automatically, while an authorized staff member accepts and takes over when human review is needed.
This is not a commercially operating service. We are preparing a controlled onboarding with our initial healthcare-institution customer. The WhatsApp Business Platform is the only connection under verification today.
01 · Guided demo
01The dermatology flow prepares a request from the visit reason and preferred time. The internal medicine flow also organizes the main concern, duration, medication, and allergy answers for staff.
Every message, status, and schedule below is synthetic. It is not a real patient conversation, hospital record, production interface, or clinical result.
English guided demo
Start
Current step
Try dermatology booking or internal medicine booking with intake.
Choose one of two care journeys.
Synthetic demo care team
Hello. This example shows how a synthetic demo care team could respond. Choose one of the two flows below.
Choose a reply
02 · Staff handoff control
02Exceptions alert authorized staff. One acceptance pauses automated replies, and the owner, resolution, and any bounded return remain explicit in the workflow.
This is under verification in a synthetic environment. No real staff alert, patient message, appointment, or medical record is created.
Synthetic environment
Handoff control flow
Watch the boundary
Routine inquiry in progress
Prepare staff alert
One staff acceptance
Record resolution
Explicit return
Staff control
Routine inquiry in progress. Automated replies: Active. Current owner: None. Handoff priority: Not applicable. Agent Whenever continues short routine inquiries and starts a handoff only when staff review is needed.
Agent Whenever continues short routine inquiries and starts a handoff only when staff review is needed.
Next action
These controls change synthetic browser state only. No alert, patient message, appointment, or medical record is created.
03 · How the workflow runs
03Agent Whenever shows the next short question and organizes each selected answer. Clinic staff take over when appointment confirmation or clinical judgment is needed.
The customer healthcare institution authorizes the connection from its own channel account. The connection under verification today is AetherHeal's Meta app against a WhatsApp Business Account.
In a patient-origin conversation, the flow checks the visit purpose, preferred date, and basic information needed to continue. Contact-list broadcasts are outside the current scope.
Short choices collect appointment information and pre-visit intake answers. The current live-connection validation is limited to institution-approved English replies; the guided demo is synthetic.
The workflow does not change or infer from the patient's selected words. Clinical questions, urgent signals, and work that requires confirmation are designed to reach authorized staff with the necessary conversation context and priority.
The first authorized acceptance becomes the owner. Automated replies pause and duplicate acceptance by another staff member is blocked by design.
The workflow is designed to record the owner and resolution. Only safe routine inquiries return through an explicit staff action, while urgent signals remain on the human follow-up path.
04 · Channel scope
04Each channel requires separate authorization from the healthcare institution. One channel connection does not grant permission to use data from another.
Connection status
The WhatsApp Business Platform is the only connection under verification today. Each channel in the designed scope requires its own authorization from the healthcare institution before connection. Platform Data from the WhatsApp connection is not merged with patient conversations on any other channel.
05 · Authority and control
05AetherHeal Global Inc. develops and operates the software as a technology provider. Each healthcare institution controls its account, approved information, staff permissions, and final decisions communicated to patients.
06 · Data use
06We process WhatsApp Business Platform Data on behalf of a connected healthcare institution. Processing scope, retention, and data-subject procedures are finalized before activation in the customer agreement and patient notice.
Message content; health information selected by the patient, such as visit purpose, symptoms, duration, medications, and allergies; WhatsApp identifiers and profile name; technical metadata such as message time and status; and customer-approved service configuration.
Receiving inquiries, preparing approved English replies, organizing appointment and intake information, routing unsupported languages and exceptions to staff, security, troubleshooting, and customer support.
Messages are processed in the service infrastructure. Necessary conversation context may be sent to contracted processing providers, and exceptions are sent to a staff communication channel authorized by the customer.
We do not sell Platform Data or use it for advertising or cross-customer profiling.
07 · Current status
07No customer Business Portfolio is currently connected for production operation, and we do not process real patient messages in a production environment. Real-patient processing will not start until verified retention and deletion procedures, customer notices, and technical controls are in place.
Pre-launch validation
Meta app identifier: Agent Whenever
We review the institution's account structure, approved information, staff authority, and patient notice before discussing the connection scope.
WhatsApp is a trademark of an affiliate of Meta Platforms, Inc. AetherHeal does not claim official Meta or WhatsApp partner status.