Nice, B is a great fit for Lia. Let’s lock it in and then you can hand this straight to CTO as “appointment narrowing v2”.

---

## 1. New wording – **Style B (friendly but concise)**

### 1️⃣ Customer: *“I can do this weekend” / “this weekend is fine”*

**Lia reply:**

> “No problem, Simon – a weekend visit works well.
> Would **Saturday or Sunday** be better for you, and do you prefer **morning or afternoon**?”

---

### 2️⃣ Customer: *“Next week is fine” / “I can do next week”*

**Lia reply:**

> “That’s fine, Simon – we can look at **next week**.
> Are **weekdays or the weekend** better for you, and do you prefer **morning or afternoon**?”

---

### 3️⃣ Customer answers only day

*(“Saturday”, “Sunday”, “Tuesday works”, “any day in the week”)*

**Weekend day:**

> “Great, Simon – **Saturday** is no problem.
> Would you prefer **morning or afternoon**?”

**Weekday (example Tuesday):**

> “Great, Simon – **Tuesday** works.
> Would you prefer **morning or afternoon**?”

---

### 4️⃣ Customer answers only time-of-day

*(“morning”, “afternoon”, “evening after work”)*

**No day chosen yet → keep it gentle and forward-moving:**

> “Thanks Simon – **morning** suits us fine.
> Would **Saturday or Sunday** be better for you, or is a **weekday morning** easier?”

---

### 5️⃣ Customer picks both day & time-of-day

*(“Saturday morning”, “Sunday afternoon”, “Tuesday morning”)*

Lia jumps straight to specific slots:

> “Perfect, Simon – **Saturday morning** works.
> I’ve got **10:00am or 11:30am** available.
> Which would suit you better?”

(CTO can configure the actual times per site; this is the pattern.)

---

### 6️⃣ Customer gives a **specific time**

*(“11”, “11am”, “half 9”, “about 4”, etc.)*

Lia confirms and books:

> “Thanks Simon – that’s ideal.
> I’ve booked you in for **Saturday 13/12/2025 at 11:00am** at **Lincoln Audi**.
> If anything changes, just drop me a quick message here and I’ll happily move it.”

(Obviously date/time filled from the backend.)

---

### 7️⃣ If time is **outside hours** or unclear

*(“really late”, “after 7pm”, “whenever”)*

> “We’re a little limited at that time, Simon.
> I can do **[earliest_time] or [later_time]** on **[chosen_day]** – which would you prefer?”

---

## 2. Behaviour / logic changes for CTO (you can paste this)

Here’s a short spec you can drop into the CTO chat:

---

**“Appointment narrowing – weekend & next-week logic (Style B)”**

Please update the appointment flow so that:

1. **New intent tags:**

   * `APPT_THIS_WEEKEND`
   * `APPT_NEXT_WEEK`
   * `APPT_DAY_SELECTED` (Saturday, Sunday, Mon–Fri)
   * `APPT_TIME_OF_DAY_SELECTED` (morning / afternoon / evening)
   * `APPT_SPECIFIC_TIME` (e.g. 11, 11am, half 9)

2. **Memory fields stored in dp_conversations:**

   * `preferred_day` (Saturday / Sunday / Monday …)
   * `preferred_week_bucket` (`this_weekend`, `next_week`, etc.)
   * `preferred_time_of_day` (`morning`, `afternoon`, `evening`)
   * `preferred_specific_time` (normalised “HH:MM”)
   * These must persist between messages so Lia can *narrow* instead of repeating.

3. **Conversation rules (in order):**

   * If intent = **APPT_THIS_WEEKEND**
     → reply: *“No problem, Simon – a weekend visit works well…”*
     → ask: **Saturday or Sunday + morning/afternoon**.

   * If intent = **APPT_NEXT_WEEK**
     → reply: *“That’s fine, Simon – we can look at next week…”*
     → ask: weekdays vs weekend + morning/afternoon.

   * If **only time-of-day** known (morning/afternoon) but **no day** yet
     → reply asking: weekend vs weekday, keeping time-of-day fixed (see template above).

   * If **day is known** but **time-of-day not yet**
     → ask just for morning/afternoon.

   * If **day & time-of-day known** but **no specific time**
     → offer **two slots** generated from opening hours
     (e.g. 10:00 and 11:30 for morning, 1:00 and 3:00 for afternoon).

   * If **specific time given** (11 / 11am / “half 9”)
     → normalise to a valid slot within hours
     → book and send the **full confirmation** with date + time + “at Lincoln Audi” line.

4. **Tone rules:**

   * Use **first name only** in all appointment replies (“Simon”, not “Simon Howard”).
   * Use **Style B**: friendly but concise, no emojis by default, 2–4 short paragraphs max.
   * Never re-ask for information the customer already clearly gave (e.g. don’t ask “Saturday or Sunday?” *after* they’ve said “Saturday”).

---

If you copy-paste the **templates in section 1** plus the **spec in section 2** to your CTO chat, that gives them everything needed to tighten this behaviour.

If you’d like, next step we can do is:

* design a **tiny test script** of 5–6 appointment conversations you and your testers can run (weekend, next week, vague time, specific time, reschedule).