> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.klarity.coach/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# The client's between-session check-in

A check-in is a short message that Klarity sends your client between two sessions to ask how they're doing. They reply in one click from a dedicated page, and their reply comes back in their record, ready to prepare your next session.

# Understanding the check-in

As an AI-detected engagement's **due date** approaches, Klarity can automatically send the client a light message: "how's it going?". The client replies from a **public page** (no account to create), and their reply enriches the client's memory. It's a simple way to keep the connection between two sessions, with no effort on your part.

The check-in works hand in hand with the client's **Trajectory**: it triggers from the engagements followed in that tab, and that's where the reply appears.

Three conditions must be met for a check-in to go out automatically: the feature **enabled** in your settings, the client's **consent granted**, and an **engagement with a due date** that is approaching. The reply link sent to the client stays valid for **14 days**.

| A check-in is only sent for an engagement that has a **due date** — that's what triggers the send. Without a detected due date, no message is sent.

# Enabling check-ins

The feature is **disabled by default**. You enable it globally from your settings:

1. Go to **Settings › Sessions & memory**.
2. Turn on **Between-session check-ins**. Klarity will then send the client a short message near the due date of a dated engagement (reply without an account), and their reply will enrich the memory.

| You can customize the wording case by case from the **Trajectory** tab: under an engagement to follow that has a due date, click **Customize check-in**. Left empty, the engagement itself is used as the question.

# What the client sees

The link opens a simple page, protected against bots (reCAPTCHA), with no account creation. On it the client finds:

- a personalized greeting (**Hi {first name}**) recalling that you'd like to know how they're doing;
- the **engagement concerned**, quoted as it was detected during the session;
- a **Your reply** field and a **Send my reply** button.

Only their first name and that engagement are visible on the page — their reply is shared only with you.

| Once the reply is sent, the client sees a thank-you message. If the link has expired or is no longer valid, a page simply invites them to discuss it at the next session.

# Finding the reply on your side

The reply comes back in the **Trajectory** tab of the client record, directly under the engagement concerned:

- Until the client has replied, the engagement shows **Check-in sent, awaiting reply**.
- As soon as they reply, their **Client's reply** shows under the engagement, and you're notified.
- If the AI detects that the engagement was honored or not, it offers an **AI suggestion** that you apply in one click with **Apply** — you stay the decision-maker.

| 💡 **Tip:** enable check-ins for your most independent clients: a light nudge midway is often enough to keep the momentum, and their reply prepares the next session for you.

# Related articles
- Following a client's trajectory
- Configure your sessions & memory