No-show recovery

Missed appointments get a prepared message to rebook.

An appointment that is not attended leaves an empty slot and a client who may simply have forgotten. This workflow notices the miss and prepares a short, polite message offering another time, for your team to approve.

A white calendar card with an empty outlined square, a blue speech-bubble card laid over its corner, and a second calendar card with one gold square filled lie on the paper.
A missed appointment, a prepared message, and the slot filled again.

Where this work slips today

A calendar card with an empty outlined square, then a dashed outline of a message bubble where no message has been written, then a second calendar card whose square is only a dashed outline.
A missed appointment, no message, and a slot that stays empty.

A missed appointment is easy to notice and easy to leave. The agenda shows the empty slot, but following up is one more task in a busy day, so it waits or is done by hand, in a different tone each time. Meanwhile the client who missed it is not offered another time.

How this runs

An empty calendar leads to a prepared message, a rust checkpoint, a newly booked calendar and the closed green ledger. Dots under the stages count the five steps.
A missed appointment, a prepared message held at the checkpoint, the slot offered again and the record. The dots under each stage count the steps below.

On Ateles, a missed appointment becomes a task that moves through a workflow we define with you before anything runs. Each step has a named owner, an agent or a person. The steps below are the intended design, not a record of work already running.

The five steps

  1. A missed appointment is noticed. Your agenda shows an appointment that was not attended. It becomes a task in the shared record, together with the appointment details and any reminders already sent.
  2. The agent prepares a message. A short message offering another time, in the tone you approved. Reminders stay on schedule within the limits you set, and the agent can do only what its permissions allow.
  3. The checkpoint. Like any message to a client, the rebooking message waits. A named team member approves, edits or stops it before it goes out.
  4. The message goes out. Once approved, it is sent and the slot can be offered again, including to people who are waiting for one.
  5. The record keeps it. The missed appointment, the message, the decision and any reply stay in the record, so the next reminder starts from what already happened.

Who does what

The agents do the preparing and your team does the deciding. That line is drawn before anything runs, and nothing crosses it without an approval.

  • The agents prepare. The message to rebook, and the reminders around it, written in the tone you approved and sent on the schedule you set.
  • Your team decides. Who gets contacted, how firmly, and what happens when a case is unusual. A reply that needs a person goes to a named person.

Example: a dental clinic

A patient does not attend a booked appointment. The clinic’s agenda shows it, and the missed appointment becomes a task. An agent drafts a short, polite message offering another time, in wording the clinic has approved.

The message waits at the checkpoint. The receptionist reads it and approves it, and then it goes out. If the patient replies with something unusual, the case goes back to a named person at the clinic. Each step stays in the record.

What the record holds, in order:

  1. The missed appointment and the reminders already sent
  2. The message the agent drafted
  3. The receptionist's approval
  4. The patient's reply, if there is one

See what you could delegate.

A free, no-commitment 30-minute conversation. You leave with a clearer picture, whether or not you work with us.

A calendar card with one gold square filled in, beside a small blue notebook with a pencil lying across it.