Zisson Socialboards 2026 – No. 4
12/11/2026
This release focuses on read-only fields, configurable ticket view behavior, a new ticket assignee webhook event, Trustpilot integration changes, and miscellaneous improvements and bug fixes.
Improvements:
Support for read-only fields
Configure ticket view behavior after closing a ticket
Ticket assignee change webhook event
Trustpilot integration update
Miscellaneous improvements and bug fixes
Support for read-only fields
What’s new
When creating a field in the Field library, Admins can now choose to make it read only. Users will still see the field’s content but will not be able to edit it.
How it works
Admins specify this option when defining a new field in the Field library.
The contents of the field can still be changed using rules or APIs, but the content is not editable by users.
If the field is marked as read-only, it will disable required flags.
How to use
In the Settings, in the Field library when creating or editing a field, click to tick the option Read-only.
Configure ticket view behavior after closing a ticket
What’s new
Admins can now configure what happens in the ticket view when an agent closes a ticket. They can choose whether the closed ticket is removed and whether the next available ticket opens automatically.
How it works
Both settings are disabled by default. A closed ticket therefore remains visible until the agent selects another ticket.
When Remove closed ticket from ticket view is enabled, the ticket is removed from the user’s view after they close it.
Admins can also enable Automatically open next ticket to open the next available ticket. If this setting is disabled, no ticket is selected automatically. If no next ticket is available, the appropriate empty state is shown.
How to use
Go to Settings, General, Display settings to configure the two settings. Automatically open next ticket can be enabled only when Remove closed ticket from ticket view is enabled.
Ticket assignee change webhook event
What’s new
A new ticket_assignee_change event is available in the Ticket webhook group. It notifies integrations when a ticket is assigned, reassigned, or unassigned.
How it works
The event includes the previous and new assignee, the user recorded as making the change, ticket information, and the event time. It is sent for changes made in the Inbox, through the Public API, by ticket rules, through automatic chat assignment and bot takeover, and during bulk updates.
How to use
Enable ticket_assignee_change in the Ticket event group in your community’s webhook settings. Configure your integration to process the event payload.
Trustpilot integration update
Following guidance from Trustpilot themselves, the integration for Trustpilot now requires a paid Trustpilot subscription.
Miscellaneous improvements and bug fixes
End-user chat navigation events are now timestamped and highlighted in the chat ticket, making them easier for agents to follow.
Agents will no longer see a message notifying that a webchat was initiated by the Chat API.
When an agent replies to a chat created through the Public API, the ticket remains open instead of being automatically set to pending.
Admins now see a warning when Set anonymization time is selected as the action type.
The FAQ widget settings will now correctly filter the Socialboards chat widget by category, as intended.
Images uploaded for FAQ categories will now display correctly in the FAQ.
If a reply template includes font colours and line breaks, they will now be applied to messages that use that template.
Users can now select reply templates by clicking them from the list, as well as using the arrow keys and pressing Enter.
User can save tags on FAQ articles as expected.
Vendor users can now access shared ticket content through links in email notifications.
The automatically added verifyToken URL parameter can now be disabled for a community. The verification token is still sent in the request header.
Emails reported as bounced by the email service are now marked as bounced in Socialboards.