# The operating system for a clinic's OPD. > Hally connects the patient conversation, appointments, registration, OPD queue, clinical context and follow-up in one operating workspace, under the hospital's brand. Product: Hally Built and operated by: 7Unit Softwares Pvt. Ltd. 7Unit: https://www.7unit.tech/products/hally Commercial site: https://gethally.com Canonical page: https://www.7unit.tech/products/hally Built and operated by 7Unit. Hally is a product built and operated by 7Unit Softwares Pvt. Ltd. The commercial site is gethally.com. ## The outpatient day already happens. It just does not stay in one place. The point is not that a hospital has no software. The patient conversation, the appointment, arrival, clinical context and follow-up often live on disconnected surfaces. - **Messaged. Never on the chart.** The conversation stayed on a phone the desk could not see. - **Booked. The queue did not know.** The slot lived somewhere else. Arrival was a surprise. - **Checked in. The doctor walked in blind.** No reason for the visit. No context from the morning. The room had to reconstruct it. - **Seen. The follow-up was a memory.** The consult closed. The next step lived in someone's head. ## Hally runs that day in one workspace. 01. **Patient conversation** — WhatsApp and voice become managed patient-entry surfaces, not side channels. 02. **Appointment** — A real doctor and branch slot is booked, and reminders stay connected to it. 03. **Registration** — Patient identity, demographics and the reason for the visit are available before arrival. 04. **OPD queue** — Booked and walk-in patients share one operational queue: check-in, nursing, waiting and the doctor room. 05. **Consultation context** — The clinician opens patient context that is already assembled. AI may draft or assist. The clinician reviews and decides. 06. **Follow-up** — Reviews, reminders, reports and next actions stay actionable after the consultation. 07. **Return** — The next interaction continues with the same patient context. ## The patient can write. Or call. The workflow stays connected. WhatsApp and voice should not create separate patient silos. They should feed the same operational context. ### WhatsApp - Runs on the clinic or hospital's WhatsApp number. - Handles enquiries and supports appointment booking. - Carries reminders and follow-up. - Staff can take over the thread when a person needs to join. - Complaint and ticket routing, where that is configured. ### Voice - An AI voice agent for inbound calls. - Can support a missed-call callback, where that workflow is configured. - Can be limited to selected hours or use cases. - Calls can be recorded, summarised and tagged, where that is configured. - Staff can take over. The conversation can feed the same operational workflow. Voice does not give clinical advice, and it is not offered here as coverage of every language. What a hospital turns on is part of deployment. ## Every enquiry becomes operational context. This is the patient journey the desk can work. It is not a generic sales CRM. - Source tagging - Patient and enquiry pipeline - Appointment state - Attended and not-attended state - Reminders and follow-up - Human handoff - Complaint and ticket routing, where configured - Campaign or reactivation workflows, where configured - Operational reporting ## The clinic stays in control of the record and the decision. Hally may assist with context, drafting, routing and workflow. It does not independently diagnose, prescribe or close a clinical decision. Human review belongs where clinical judgement is involved. - **Your number. Your brand.** The hospital's WhatsApp stays registered to the hospital. Hally does not insert a marketplace between the hospital and the patient. - **The clinician decides.** Drafts and suggestions wait for review. Hally does not diagnose, prescribe, or close a visit on its own. - **Roles, branches and auditability.** Desk, nursing, doctor and admin see different work. Access to patient records is logged. Each organisation stays isolated. - **Privacy-aware by design, not a certification.** Sensitive fields are encrypted at rest. That is a design choice, not a certification. What compliance requires still depends on how the hospital configures and operates Hally. ## Alongside the systems the hospital already runs. Hally does not require the hospital to throw away its existing HIS, HMS or EMR. It can sit beside them and integrate where that system exposes an interface. - Patient registration - Doctors and schedules - Appointments - Reports - Operational events - Patient communication Each of these is in scope only where the hospital system or its API supports it. Hally does not claim a connector for every product on the market. ## The clock starts when Hally is actually running. A form is not go-live. The operating team uses Hally on the hospital's own OPD before the deployment counts. 01. **Map the OPD** — How patients move today, across conversation, desk, queue and follow-up. 02. **Configure** — Doctors, branches, roles and the workflows the team will actually open. 03. **Integrate where required** — Only the boundaries the hospital system can support. 04. **Train the operating team** — Desk, nursing and clinicians, on the work they will do in Hally. 05. **Go live** — Hally runs inside the hospital, not as a demo beside it. 06. **Measure and refine** — Watch the workflow in use, then adjust what the operating team actually needs. ## Commercial scope follows the hospital. There is no single price on this page. Deployment depends on the hospital or clinic. - Hospital or clinic size - Number of locations - Workflows enabled - Integration requirements - WhatsApp and voice usage - Operational support Current plans and deployment options → https://gethally.com ## Built as an operating product, not a campaign bot. Hally is software 7Unit builds and operates. The public product is an OPD workspace with separate organisations, distinct roles, and a log of access to patient records. It is not a campaign bot parked beside the hospital. - Each hospital organisation stays isolated from the others. - Desk, nursing, doctor and admin see different work. - Access to patient records is logged. - AI may draft, route or assist. A clinician decides where judgement is involved. - WhatsApp and voice, where enabled, feed the same operational workflow. - An existing HIS, HMS or EMR is integrated only where that system exposes an interface. ## Questions ### What is Hally? Hally is an OPD operating system built and operated by 7Unit Softwares Pvt. Ltd. It connects the patient conversation, appointments, registration, the OPD queue, clinical context and follow-up in one workspace, under the hospital's brand. The commercial product site is gethally.com. ### Is Hally an HMS or HIS? No. Hally is not a replacement for a hospital information system. It runs the outpatient operating workflow and can sit alongside an existing HIS, HMS or EMR. ### Can Hally work with our existing HMS or HIS? Yes, alongside it, where the hospital system exposes an interface. Typical boundaries are patient registration, doctors and schedules, appointments, reports, operational events and patient communication. Hally does not claim to connect to every system. ### Does the hospital need a new WhatsApp number? No. WhatsApp runs on the clinic or hospital number patients already message. The number stays registered to the hospital. ### How does the voice agent work? Voice is a second way in. An AI voice agent can take inbound calls, and can support missed-call callback for selected hours or use cases, where that is configured. Calls can be recorded, summarised and tagged. Staff can take over. The conversation feeds the same operational workflow as WhatsApp. The agent does not give clinical advice or make a clinical decision. ### Does Hally make clinical decisions? No. Hally may assist with context, drafting, routing and workflow. It does not independently diagnose, prescribe or close a clinical decision. A clinician reviews where clinical judgement is involved. ### Can Hally support multiple branches? Yes. Doctors, branches and roles are part of the configuration. Desk, nursing, doctor and admin see different work, and access to patient records is logged. ### How is Hally deployed? 7Unit maps the OPD, configures the workflows, integrates where the hospital system supports it, trains the operating team and goes live. The deployment is real only once Hally is running in the hospital. Scope depends on locations, workflows and integration. ### Where can I see current plans? Current plans and deployment options are on gethally.com. This page does not publish a universal price, because scope follows the hospital.