Octwin by Cequens · Playbook
Appointments, viewings, service visits and consultations — taken in the chat the customer is already in, against real availability, without anyone answering a phone.
The problem
What the customer does
Every step is a tap — routed straight to the answer, with no language-model call in the loop.
What you declare
Written once as declarations in your pack. Changing your Thursday hours is a line of configuration, not a development ticket.
The guarantee
The slot the customer taps is checked and claimed at the moment they tap it. Availability is derived from what is actually booked, not from a cached list a second customer might also be looking at.
Afterwards
When the customer next messages, the agent already knows they came in on Thursday. Asking how it went is one turn, in the thread that booked it — not an email nobody opens.
Reminders — read this before you promise one
Meta only lets a business message a customer freely for 24 hours after that customer's last message. Outside it, a pre-approved template is required.
| Reaching the customer | Today |
|---|---|
| Replying while they are in the conversation | Fully supported |
| Anything within 24h of their last message | Fully supported |
| Web widget, any time | Fully supported |
| A WhatsApp reminder the day before, unprompted | Needs an approved template — still landing |
What to say in the room. Booking, changing and cancelling all work today, because the customer starts those conversations. Do not commit to automated day-before WhatsApp reminders yet — confirm the timeline before it reaches a contract.
Where it fits
The engine is domain-blind. What changes between these is the declaration, not the platform.
Next
The demo takes about ninety seconds and ends with a real row in a real diary — which you can then watch us move from the console.
OCTWIN BY CEQUENS · Scheduling & bookings