Schedule
Confirm an appointment using accurate information from the appointment system.
Support appointment coordination, service reminders and front-desk workflows with accurate messages and privacy-aware processes.
Clinics, diagnostic centres, hospitals and healthcare networks coordinate appointments, preparation instructions, service changes and follow-up administration. Patients need clear information about what happens next, while healthcare teams must protect personal and clinical data. Astral Promotion can support basic service notifications, OTP verification, IVR routing and system integrations. The healthcare organisation remains responsible for clinical accuracy, privacy, access control, consent and deciding which information is appropriate for each channel.
The right channel depends on the message, customer preference, permissions, timing and the business system that owns the information. Not every workflow needs every channel.
Start with the customer’s next question or action, then choose the simplest channel that can answer it reliably.
Confirm an appointment using accurate information from the appointment system.
Send approved reminders and practical instructions without exposing private clinical details.
Notify when an update is ready and direct the patient to a secure portal or authorised team.
These examples show how messaging and connected workflows may support day-to-day operations. Select only the use cases that fit your process.
Send a clear date/time reminder with a safe way to confirm or contact the clinic. Keep clinical details out of the message unless the channel and process have been specifically approved.
Notify a patient that a report or service update is available, then direct them to an authenticated portal rather than including the report or sensitive result in the message.
Communicate opening-hour changes, collection-slot availability, doctor schedule changes or service interruptions using approved contact lists.
Use OTP SMS to support a one-time login or action-verification step in a secure patient portal. Apply expiry and retry limits.
Use IVR to route appointment, billing, report-status and general-information calls to the appropriate authorised team.
Results depend on accurate source data, useful message design, appropriate permissions, channel fit and follow-through by the responsible team. Technology supports the process; it does not replace it.
Make appointment details and service changes easier for patients to find.
Reduce repetitive confirmation calls when reminders are correctly configured.
Route callers to the appropriate department more consistently.
Keep message templates focused on operational information rather than clinical records.
Connect approved events to notification workflows with traceable ownership.
Support a more predictable patient-service experience while protecting sensitive data.
Each service heading opens its dedicated page with more information. Compare the use case and technical requirements before choosing a package.
Appointment, schedule and operational notifications generated from approved system events.
Send approved clinic-wide service notices to appropriate contact groups.
One-time verification for patient or staff portal access, with secure expiry and retry controls.
Connect appointment or service systems to notifications without copying records manually.
Route calls for appointments, general information and department selection.
Support approved customer-service conversations and templates where privacy and platform rules allow.
Provide longer administrative information through secure, appropriately managed email workflows.
Consider voice announcements for selected operational alerts where the recipient group and message justify it.
Make appointment, location, department and contact information easier to access.
Support carefully scoped integrations with appointment or support systems.
Review current product details, supported volumes and purchase information before placing an order.
A practical starting plan helps avoid buying services that do not match the actual workflow.
Have clinical, privacy, IT and operations owners approve the communication scope.
Separate general operational alerts from patient-specific or clinical information.
Choose the authorised system that triggers appointment, OTP and service events.
Test identity matching, access control, templates, opt-out rules and escalation paths before launch.
Review these points before selecting a service or requesting a setup discussion.
Basic operational information such as appointment date/time, clinic-hour changes or a notice that an update is available may be suitable after organisational approval. Do not send diagnosis, report details or sensitive clinical information through ordinary SMS.
A notification can tell a patient that a report is available and direct them to an authenticated, access-controlled portal. The report itself should remain within the organisation’s approved secure system.
Yes, if the appointment platform exposes a supported event or API and the workflow is configured and tested. Verify patient matching, time zones, cancellations, rescheduling and duplicate suppression.
An IVR can route callers to departments or provide general recorded information. Keep emergency instructions clear and never present an IVR as a substitute for emergency medical services.
No. The healthcare organisation remains responsible for applicable law, privacy, security, consent, access controls, retention and clinical accuracy. Review the full process before using any communication channel.
Estimate appointment and notification volumes, identify the scheduling system, define message templates and approval owners, and decide what data may safely travel through each channel. Then compare the relevant service and Store plan.