Enquiries reach your hospital from every channel, but the routing still happens on the phone.

No. Your hospital information system, laboratory and imaging platforms keep running in parallel, and the patient chart, test results and clinical record stay there. Rocketly manages what happens before and around an admission: enquiries from connected channels, department routing, booking and check-up tracking, family communication and process reporting. The two systems work at different layers and neither substitutes for the other.

Routing is defined as a workflow rule: a trigger (a new conversation on a connected channel or a form submission), a condition (department selection, tag or message content) and an action (move to the department queue, assign an owner, prepare a draft). Workflow Builder ships with 46 trigger types, so you can shape different rules for the number of departments and the shift pattern you run.

Yes. Even when a relative writes from a different number you attach the conversation to the existing record and note the relationship and the contact consent on the card. Admissions, clinical and finance teams then see one history, and the same question does not receive two different answers in two departments. Who may see which detail is limited by role-based access.

You build the check-up process with your own stages: enquiry, package information, booking, tests, results consultation and follow-up. The package scope is prepared as a PDF in the quote module and shared through a link, with view and approval status visible on the record. Test results themselves remain in the hospital information and laboratory systems; Rocketly tracks the process steps and the communication.

AI can prepare a reply draft from the current contracted-institution list and process steps you wrote into the knowledge base. That is pre-information only: definitive coverage, pre-authorization and out-of-pocket decisions belong to the institution and to your admissions or finance desk. The team edits the final wording and the team decides whether to send it.

Yes. With an AloTech or Bulutfon switchboard integration, calls attach to the patient record and call analysis produces a summary and tags. A phone enquiry and a WhatsApp enquiry sit in the same history, enter the same routing rules and are measured in the same reports. Rocketly does not provide its own telephony; it works with the switchboard you already run.

The interface is available in 3 languages — Turkish, English and Russian. For enquiries from abroad you run the thread in the patient language, note the conversation language and time zone on the record, and plan travel and appointment steps as tasks. Your international patient desk sees its own queue and its own report.

Access is role-based: you define which user sees which patient record, conversation and report, activity history is retained, and the infrastructure is built to operate in line with data protection requirements. Permission distribution across departments, units and branches, along with retention periods, remains a decision for your organization.

There is a permanently free plan and no credit card is requested; there is no trial-period concept. AI features, advanced workflow rules, the call-centre connection and some channel integrations sit in paid plans. The pricing page shows which feature belongs to which plan, and enterprise rollout needs can be discussed with the team separately.