Which clients should you invite to book again?

Invite a returning client only when there is a current, specific reason and no known reason to hold back. The longest absence is not automatically the strongest candidate. Start by removing unsuitable contacts, then review completed services and any timing the client actually agreed. The result should be a small list of decisions, not a mass mailing. This guide explains a manual selection method or a rule set to evaluate in an assistant, not an automatic KLIOSO targeting feature.

Decide what the selection is allowed to mean

A candidate means “worth a personal review,” not “needs this service” or “will book.” Those claims require information that visit dates alone cannot provide. Write down the purpose before choosing a threshold: perhaps you want to honour requests for a later check-in, or review regular maintenance clients who have not yet arranged their next visit. Keep those purposes separate because they rest on different evidence.

Choose a narrow service group for the first review. Mixing a one-off event service with a recurring routine creates misleading comparisons. Use only relevant booking history and explicit client preferences; spending, personal circumstances and guessed dissatisfaction are not shortcuts to relevance. A clear scope also makes the list easier to explain: every included person should have a reason you can state without inventing motives or reading unrelated private notes.

Apply exclusions before calculating elapsed time

First check whether the client has declined this kind of contact, asked you to wait or already received an invitation that remains unanswered. These conditions should stop another invitation even if the calendar says many weeks have passed. A refusal is not a lower priority score that can be outweighed by a long absence. Record the actual boundary and follow it instead of letting the same person reappear every time you refresh the list.

Next look for a future booking for the relevant service. That usually removes the need to invite the client again. A different upcoming service needs a closer look, not an automatic extra message. Also exclude a one-off appointment when there is no recorded reason to repeat it. When the contact identity is uncertain or two records may belong to one person, resolve that issue before selection; do not send two invitations to discover whether they are duplicates.

Reconstruct a reliable starting point from history

Identify the last completed visit for the service you are considering. A recent cancellation, future reservation or unanswered request is not a completed treatment and must not reset the starting date. Check status and service together. If several services happened in one visit, use the relevant one rather than assuming that everything in the client's history follows the same return rhythm.

Look for a stated next step before estimating an interval. “Please ask me again in November” is stronger evidence for review timing than a generic service cycle. Where no agreement exists, past completed visits may suggest a pattern, but a small or irregular history does not establish one. Mark the uncertainty rather than manufacturing an average that looks precise. The point is to know what supports the review date, including when there is not enough information to choose one.

Use the interval as a review window, not a deadline

If a service has a reasonable repeat rhythm in your own practice, use it to decide when to inspect the record. It is not proof that the client is overdue or that a new appointment is necessary. Adapt the window to what the client has told you, and avoid presenting a scheduling rule as health or treatment advice. A maintenance interval is an aid to organisation, not a diagnosis of what the person needs.

Consider three records with the same time since their last completed visit. One client asked for contact around now and has no new booking: review for a possible invitation. Another already booked next week: remove the duplicate task. A third said they would get in touch themselves: wait. The dates match, but the decisions differ. This is why a simple “days since last visit” filter is a starting view rather than a complete selection rule.

Give each reviewed record one clear outcome

Use three practical outcomes: consider an invitation now, review later for a stated reason, or do not contact. Keep “insufficient information” as an unresolved review item rather than silently putting it into the first group. For every outcome, retain a short reason tied to the relevant record: an agreed month, a future appointment or a request to wait. These are working descriptions, not claims that an app provides those exact statuses.

If the decision is to consider an invitation, check current availability and the latest conversation before drafting anything. Selection has not sent a message, reserved a slot or confirmed a service. If the client has already acted elsewhere, update the outcome. For a later review, record what must change or which agreed date matters; avoid an arbitrary daily reminder that keeps bringing back the same unresolved case without new evidence.

Test the rules against exceptions and keep the list small

Before relying on the method, walk through a few contrasting records: a completed visit followed by cancellation, an existing future booking, an explicit request to wait, and a one-off service. Check that each reaches the intended outcome and that the explanation matches the source. If a rule includes someone who should be excluded, fix that rule rather than hiding the individual while leaving the cause in place.

Review only as many candidates as you can handle thoughtfully. A long list is not evidence of a better system, and a short or empty list can be correct. Refresh a decision when its facts change, especially after a new booking or client reply. Reliable selection starts with boundaries, uses truthful history and ends with a human choice. KLIOSO client records and the calendar can support those checks; no rule can replace the client's freedom to decide whether another visit suits them.