Appointments, bookings, and reminders

A reminder sent by hand can slip on a busy day; a cancellation may only arrive at the appointment time; pre-visit details (prep notes, directions, documents) can end up with different people. Each of these comes down to communication before the appointment. Sometimes a no-show is just a cancellation that didn't get through: had canceling been easy, the slot could have gone to someone who was waiting.

• Clinics: appointment confirmations and canceled slots
• Hotels: guest communication before arrival
• Field service and maintenance: scheduled maintenance reminders

• Where appointments or bookings are kept, and if there's software, whether its reminder settings are in use
• Who confirms, through which channel, and how far ahead of the appointment
• Where cancellations and changes arrive, and who is told when a slot opens up
• Whether there's a waiting list, and how it's kept
• What the written proposal could use as criteria: the share of appointments that got a reminder, the share with a confirmation or cancellation reply, no-shows without notice, and whether freed-up slots were filled again

Sometimes the answer is a reminder setting nobody has switched on in the software that holds your appointments, so the sequence Krafera follows starts there and goes only as far as needed.

1. 1 Your software's own reminder, confirmation, and cancellation settings, including which message goes out when
2. 2 A reminder flow running on the software's integration or exports, or on a simple appointment record if there's no software: confirmation and cancellation replies are collected, and the right person hears when a slot opens up
3. 3 A waiting list and a pre-visit information form, fed by regular exports if the software can't be connected

• Wording and timing for reminder and confirmation messages
• A list that collects confirmation and cancellation replies
• A waiting list and an alert for freed-up slots
• A pre-visit information form
• A weekly summary of missed appointments

• Decisions to book, reschedule, or cancel stay with your team; the flow only carries the news.
• If you already use appointment or booking software, Krafera builds reminders around it and suggests replacing it only if discovery turns up a reason to. If appointments live in a paper book or in messages, discovery also shows what kind of record is needed.
• If the software offers no integration or export, the flow that can be built narrows; if more is needed, Krafera sets out the options in the written proposal.
• Reminders stay informational, and you approve their wording; if promotional content is wanted, consent for commercial messages and registration with İYS, the national system Turkey uses to manage those permissions, are handled separately before setup.
• At clinics, Krafera treats even appointment records as sensitive data: reminders don't mention the reason for the visit, and it sets up the flow in the clinic's own system, after the clinic's own legal review where needed.
• Reminders use nothing beyond a name, contact details, a date, and a time, and before setup Krafera agrees with you on how long that data is kept, with Turkey's data protection law (KVKK) in mind.