Smarter confirmations, credit deductions, and booking reliability fixes

A busy fortnight of fixes and improvements. The biggest change is one you will feel straight away: when confirming a reschedule or cancellation through the chatbot, the confirmation message no longer shows a price. Reschedules and cancellations don't cost anything, and the chatbot now knows that.

Deduct manually granted credits from your dashboard

You can now deduct credits from manually granted allowances directly in your admin panel, not just from package purchases. The credit history view shows the remaining balance on each grant, and a Deduct button appears whenever credits remain. A small note confirms that totals can take up to 30 seconds to update after a change.

A fix that matters: the chatbot cancelled the right booking

We fixed a bug where, if a customer said they did not want to cancel a booking, the chatbot could get confused and eventually cancel the wrong one. The system now correctly recognises refusal as a signal to abandon the task, not continue it. We also fixed a related issue where switching between bookings during a cancellation flow left the task summary out of sync with the actual booking selected.

Availability was too generous near bookings with buffer times

Some services have a buffer period before or after them — preparation or clean-up time. We found that these buffers were being respected when generating available slots, but not when checking conflicts with existing bookings. That meant slots that should have been blocked were showing up as available. This is now fixed.

Reliability: long conversations no longer cause errors

Very long conversations were occasionally causing a payload error when saving the conversation state. The system now keeps only the most recent 50 messages, which is more than enough context for the chatbot while keeping things stable.

Business reschedule notifications sent the wrong message

When a business owner rescheduled a booking on behalf of a customer, the notification they received was the customer-facing version of the message — including the wrong field names. Tenants now receive the correct business-to-business notification.

We're also working on some improvements to billing and the follow-up experience, more on that soon.