Release 5.3.37
What changed
This release covers tickets, Scenario Builder, broadcast routing, and overall stability. Some updates are visible in day-to-day ticket handling; the rest make the builder and broadcasts more predictable.
- In tickets, the conversation moves to an in-progress state when someone is assigned or the client sends a message; the bot no longer keeps sending into a closed ticket.
- For custom channel, duplicate ticket rooms are less likely when a matching conversation already exists.
- Contact details in the client card align more reliably in the operator experience.
- After you remove a button from a scenario keyboard, linked transitions are rebuilt more reliably.
- During scenario save and publish, the system behaves more clearly when something goes wrong.
- Values in some Scenario Builder action settings are stored more accurately.
- Broadcasts move to the next step more reliably when routing uses a named entry point.
- Stability under load has been improved.
How it changed
Previously, a ticket could stay “new” even after real work started, the bot could still try to post into a closed ticket, and custom channel flows could create extra duplicate rooms. Removing a keyboard button could leave incorrect transitions, publish failures felt rougher, and some broadcast routes through named entry points were unpredictable.
Now, ticket statuses and bot behaviour match how work actually progresses, room lookup for custom channel is more precise, and contact data stays better aligned with the client record. The builder updates transitions more accurately after button edits, finishes saves more reliably or surfaces clearer errors, handles action settings more precisely, and routes broadcasts through the intended step with more confidence.
Why it matters: operators see ticket state that reflects reality, and teams spend less time fixing scenario issues and manual rechecks.