Time slots that book and dates the chatbot gets right

Two reliability fixes this week. The chatbot was offering time slots it couldn't always book, and it was sometimes labelling yesterday's session as upcoming. Both are fixed, with smaller improvements to notifications, follow-ups, and the calendar.

Slots you offer should always book

The clearest fix is one that was causing real disruption. When a client chose a time from the chatbot's list and confirmed it, the booking was sometimes rejected. The problem was a mismatch in how available slots were calculated versus how the booking check worked — both apply a buffer gap between sessions, but only the booking check was applying it to the candidate slot itself. So a slot would look free when offered, then fail when the client tried to confirm it. Now both calculations use the same rule, so any slot the chatbot offers will pass the booking check.

Dates the chatbot gets right

Two date-handling fixes shipped this week.

The chatbot was sometimes labelling a past session as upcoming when a client asked about their schedule. It was trying to work out past versus upcoming from the date alone, and occasionally getting it wrong. Now every booking is classified as past, today, or upcoming before the chatbot writes its answer, so the label is always correct.

Separately, asking to "block out Friday" was being treated as an open-ended repeating block rather than a single day off. The chatbot would ask "how long should that repeat for?" instead of just blocking the next Friday. That's now fixed: a bare day name with no repetition language means one day.

Replies to notifications

When a client replies to a booking notification — to acknowledge it or to ask to reschedule — the reply is now handled by a single, deterministic classifier. Previously this ran across multiple paths, which caused occasional mis-routing: in some cases, a reply was being attached to the wrong booking. Now the classifier reads what the notification actually offered and routes accordingly: acknowledge, reschedule, or pass to the general conversation.

Calendar and a few more

If you use the calendar's month view and you had a busy day with several sessions, the latest session on today's date could silently disappear — no entry, no "+N more" link — because today's cell was styled differently from every other day and threw off the overflow calculation. That's fixed: today now overflows to "+N more" like any other busy day.

Payment reminders sent to clients who had messaged recently were using a charged template message when they didn't need to — the free in-window message was available but wasn't being chosen. That's now corrected, so your credits go further.

The automated follow-up system also received four fixes to how conversations hand off between stages — specifically around consent capture, ownership transitions, and conversation state. If you run follow-up sequences, these changes make the hand-offs more reliable.

We're also working on some improvements to how messages are billed across multiple connected channels, more on that soon.