An artistic depiction of Asclepius with a headset and laptop in a modern reception area

A solution for medical centres

JediDesk for clinics

From the first message to a visit that stays in mind.

Try for freeExplore the scenarios

Questions · appointments · reminders

Service questions, appointments and visit reminders form a single patient journey. JediDesk helps your clinic build it in chat: AI explains practical information, a configured bot guides the patient towards an appointment, and a reminder brings the agreed time back to their attention. Reception joins when a person and their decision are needed.

A classical symbol of medicine in modern communication. An artistic AI interpretation of Asclepius.

For medical centres, clinics and private practicesUpdated

Reception's day-to-day work

Patient care begins with organising the visit

People need to understand how to make an appointment, where to go and what happens next. For the clinic, this is a sequence of specific actions that must not get lost among calls and messages.

Reception handles several enquiries

A patient is at the desk, a new call is on the phone, and chat has an appointment question. Each needs a next step.

Appointment status should be clear

A preferred time, awaiting agreement and a confirmed visit are different states. Patients need to know which stage they are at.

Visit details are easy to lose

After booking, questions arise about the date, address or rescheduling. A reminder helps people return to the agreed details.

Some questions need a specialist

Practical answers can be prepared in advance. Individual medical questions require a doctor's involvement.

Before automation

Where the journey to an appointment breaks down

Routine questions take up reception's time

Branch addresses, opening hours and appointment terms recur in enquiries. Your team explains the information manually each time.

The person does not understand their appointment status

Time preferences have been sent, but it is unclear whether the appointment is agreed. This leads to additional calls and questions.

An agreed visit gets forgotten

Time passes between booking and the appointment. Without a reminder, patients have to find the date and details themselves in old conversations.

A request to change the time gets lost

Rescheduling gets mixed with new questions. Reception needs to identify the existing appointment and agree the next action.

Automation use cases

Five conversations that support an upcoming visit

The scenarios combine AI answers with configured appointment and reminder logic. Actions in the clinic's system and handover rules for reception are agreed around your process.

01

Explain services and appointment terms

Someone asks about a service, price or the address of the relevant branch.

AI finds the answer in prepared clinic materials: service descriptions, the current price list and practical rules. If information is missing, it passes the question to reception.

Answers based on clinic materials

The patient receives clear terms and can move on to making an appointment.

02

Make an appointment through a chatbot

The patient wants to arrange an appointment through a convenient conversation.

The configured bot guides the patient through the required appointment steps: service, branch, time preferences and necessary contact details. Confirmation is sent after the visit is agreed under the clinic's rules; until then, the appointment status is explicit. If confirmation is unavailable, reception joins.

Connecting the appointment process

The person follows the appointment journey and sees whether it is confirmed.

03

Remind the patient about an agreed visit

The appointment is confirmed, but the visit is still some time away.

The reminder is sent according to a configured rule and contains the practical appointment details needed. The channel, send time and source of current status are defined during implementation.

Integrations for the reminder scenario

The patient can more easily return to their appointment date, time and address.

04

Pass on a rescheduling request

The patient replies that they cannot attend at the agreed time.

The bot clarifies the required details of the existing visit and the new preferences. It passes the request to reception with the enquiry history. Until the change is confirmed, it does not state that the appointment has been rescheduled.

Handing the conversation to an operator

Your team sees the change request and can agree an available option.

05

Involve the right specialist

The question goes beyond practical answers or requires an individual assessment.

The assistant explains the next step and passes the enquiry on under the clinic's rules. Reception helps arrange contact with a specialist; diagnosis and treatment decisions remain with the doctor.

AI and your team in one process

The patient understands who to contact about a question needing a person.

How the solution works

Enquiry → appointment → confirmation → reminder

One organised journey to the appointment. Each stage makes clear where data comes from and when reception's involvement is needed.

  1. 01

    The patient gets in touch

    They ask a practical question or start arranging an appointment in chat or the clinic's connected bot.

  2. 02

    The bot guides them towards an appointment

    It clarifies the required service and visit details, walking through configured steps with the patient.

  3. 03

    The appointment is confirmed

    After agreement under the clinic's rules, the patient receives confirmed details. Reception picks up unresolved questions.

  4. 04

    A reminder arrives

    The configured message brings the visit back to the patient's attention. A request to change the time goes to the responsible person.

Patient enquiryClinic rulesConfirmed appointmentReminder scenario

Capability map

What supports the patient's journey to the clinic

Answers, appointments and reminders have their own sources. The map shows which data the clinic prepares and where its team joins the conversation.

A patient enquiry in chat or a connected bot

A marble Asclepius wearing a headset — an artistic depiction of a clinic communication assistant
JediDeskCommunication between the patient and reception

  • Services and terms

    Explains prepared descriptions, appointment rules and price-list terms.

    Source: Clinic materials

  • Addresses and branches

    Helps find practical information before a visit.

    Source: Current clinic contacts

  • Appointments through the bot

    Guides through configured steps and required questions.

    Source: The clinic's appointment process

  • Visit confirmation

    Reports agreed details after actual confirmation.

    Source: Confirmed appointment status

  • Reminders

    Brings attention back to the visit according to a defined sending rule.

    Source: Appointment details + configuration

  • Reception's involvement

    Passes on unusual questions and requests to change the time.

    Source: Handover rules for a person

The patient understands the next step, and your team sees enquiries that need its involvement.

A map of clinic scenarios. The artwork is a metaphor for service, not a depiction of a doctor or medical advice.

Channels and integrations

Connect the conversation to your clinic's process

Choose patient communication channels and prepare information sources. The appointment and reminder scenario is agreed separately, according to your system, available actions and team responsibilities.

Website chat

Appointment questions alongside service pages and clinic contacts.

About the channel

Telegram

A conversation through a connected bot with configured patient steps.

About the channel

WhatsApp

Practical enquiries through your team's connected channel.

About the channel

Clinic materials

Service descriptions, the current price list, addresses and practical rules. The responsible team checks and updates the wording.

How to connect

Appointment and reminder system

Available actions depend on the specific system. Checking times, confirmations, changes and sending messages require an agreed scenario and testing.

How to connect
Asclepius with a phone, appointment book and blue bell — an artistic metaphor for a visit reminder
Bringing attention back to an agreed appointment. An artistic AI interpretation of Asclepius.

Example conversations

The patient sees the next step within the conversation

Illustrative clinic conversations. These show the logic, not Aurora correspondence or real patient conversations; details and wording are configured around your process.

  1. 01Confirmed appointment
  2. 02A reminder with details
  3. 03Contact with reception

From intent to a confirmed appointment

The clinic's configured chatbot
  1. Patient

    I'd like to make an appointment for a consultation on Friday.

  2. Clinic bot

    Which specialist would you like to see, and at which branch? Let's clarify the appointment details.

  3. Patient

    A general practitioner at the central branch. The afternoon would be better.

  4. Clinic bot

    Your preferences have been received. Once the visit is agreed, we will send the confirmed date and time. The appointment is currently awaiting confirmation.

  5. Clinic bot

    Your appointment is confirmed. Visit details and a reminder will be sent according to the clinic's rules.

The last message is sent only after the visit is actually confirmed, not immediately after collecting preferences.

The patient distinguishes between awaiting agreement and a confirmed appointment.

A reminder and a request to change the time

Connected reminder channel
  1. Clinic bot

    A reminder about your agreed visit. If your plans have changed, please let reception know — we will help arrange the next step.

  2. Patient

    Unfortunately, I won't be able to attend. Can I reschedule?

  3. JediDesk AI

    Please provide the date of your existing appointment and a more convenient day. I'll pass your request to reception.

  4. Patient

    I'd like to move Friday's appointment to next week.

  5. JediDesk AI

    I'm passing on your preferences. Reception will check the appointment and agree a new time. Rescheduling has not yet been confirmed.

To identify the appointment, your team uses the agreed verification method without disclosing another person's details.

Changed plans become an enquiry for the responsible person rather than an unnoticed reply.

Results and benefits

A more organised patient journey and reception workflow

Assess results within your process: are appointment steps completed, is the status clear, do reminders arrive, and does your team see change requests in time?

Fewer repeated practical answers

Prepared materials help AI explain appointment rules, addresses and service terms without your team searching again each time.

A consistent appointment process in chat

The patient answers the required questions and sees what is already agreed and what still needs the clinic's decision.

Visit details are close at hand again

The reminder brings back appointment information and provides a clear contact route if plans have changed.

Context for reception

Questions and previous clarifications stay in the conversation. Your team can continue from the point where its involvement is needed.

Customer experience

How businesses use JediDesk

About Aurora

Chatbot appointments and visit reminders

The scenarios are confirmed by the JediDesk team. The illustration is artistic, not a photograph of the clinic or its interface.

Aurora is a medical centre in Dnipro. According to the JediDesk team's description, patients can make appointments through a chatbot and receive appointment reminders. This is an example of two connected scenarios: arranging a visit through conversation and bringing attention back to an agreed appointment.

  • Appointments through a chatbot
  • Appointment reminders

Built around your process

Why JediDesk suits clinic communication

Answers from your materials

The clinic defines service information and practical rules. AI works with a prepared knowledge base and defined answer boundaries.

JediDesk AI capabilities

A person joins with context

Reception receives the enquiry history when details need agreement, an unusual question needs resolving or contact with a specialist must be arranged.

Chat and operator work

A scenario for your appointment process

Appointments, confirmations and reminders are agreed around the clinic's workflow. The scope of an external system connection is determined by its capabilities.

Connecting external systems

Launching the solution

Start with one clear appointment journey

Involve those responsible for reception and the appointment system. They will help define visit statuses, required questions and reminder rules. The launch timeline depends on material and connection readiness.

  1. 1

    Prepare practical answers

    Gather services, the price list, branch contacts and appointment rules. Define which questions go to reception or a doctor.

  2. 2

    Describe appointment steps and states

    Define required fields, the confirmation source and actions available to the bot. Separately agree behaviour when system data is unavailable.

  3. 3

    Configure reminders

    Choose the channel and send time. Define how the scenario accounts for changed or cancelled visits and where the patient's reply goes.

  4. 4

    Test the full journey

    Walk through booking and confirmation, receive a test reminder, and check a rescheduling request and handover to a person before launching for patients.

How to configure JediDesk AI

Before you start

Frequently asked questions

About chatbot appointments, reminders, connections and the clinic team's involvement.

Can patients make an appointment through a chatbot?

Yes, chatbot appointments are one of JediDesk's clinic scenarios. According to the team's description, Aurora clinic uses this process along with appointment reminders. For your clinic, agree the steps, required data and method of confirming the visit. Schedule access and actions in an external system depend on the connection. Until actual confirmation, the bot must explicitly show that the appointment is still awaiting agreement.

How are appointment reminders configured?

A reminder relies on agreed appointment details and a scenario defined by the clinic. During setup, choose the channel, send time, message content and how the patient's reply is received. Also define where the current visit status comes from after a change or cancellation. The interval and channel are not the same for every clinic: they are tested with a sample appointment within your process.

Can we connect our appointment system or medical information system?

Connection feasibility depends on the particular system's technical capabilities and permitted actions. First define which data needs to be read or passed on, such as appointment status or confirmed details. Time searches, visit creation and changes are checked separately. An integrations page does not mean a ready-made connection to any medical information system; the implementation scope is agreed before launch.

Can a patient ask to reschedule an appointment?

The request can be received in the conversation and passed to reception with the necessary details. Your team must identify the existing visit, check preferences and confirm the new arrangements. Until that happens, the message must not suggest that the appointment has already been rescheduled. Automatic changes in an external system need separate agreement and testing, including updates to future reminders.

Does the assistant answer medical questions?

This page concerns communication arrangements: services based on clinic materials, appointment terms, booking and reminders. Individual questions about health, diagnosis or treatment should go to a medical professional under the clinic's rules. These boundaries are set during assistant configuration. Reception helps organise the next step, while a doctor makes clinical decisions.

What data is needed to launch the scenario?

Start with service descriptions, practical rules, required appointment fields and the confirmation source. Reminders need agreed visit details and a configured communication channel. Define the data list for the specific action: arranging an appointment does not require indiscriminate collection of medical histories in chat. Separately agree team access, the method of identifying the appointment and rules for handing the enquiry to a person.

Other industries

Find your next use case

The next step — your clinic

Help the patient get from a question to an appointment

Build a clear process in chat: practical answers, appointments and reminders. Start with a scenario your reception team knows well.

Try for freeSign up

The free trial lasts 14 days. Appointment and reminder configuration is agreed around your clinic.

  • Your appointment rules
  • Clear appointment status
  • A visit reminder
Top