April 2026 updates – Stronger permissions, smarter automation flow, and more reliable widget experience

Let’s go through what we got done in April 2026 in NeetoChat.

New features ✨

Role-based chat visibility improvements

Chat listings now consistently respect role permissions across all views (assigned, unassigned, closed, mentioned, and all). Agents with “own chats” access now only see conversations assigned to them.

Multiple GitHub issues per conversation

You can now link multiple GitHub issues to a single chat conversation, making it easier to coordinate with engineering on complex customer threads.

Timezone-aware business hours and away messages

Business hours can now be configured with a specific timezone, ensuring the widget shows the correct away message based on actual working hours.

Better canned response previews

Canned responses now display the actual reply content instead of just descriptions, making selection faster and more accurate.

Enhancements ✨

More reliable automation pipeline

Webhooks are now consistently triggered at the end of automation rule execution, including edge cases with synchronous rules.

Improved knowledge base integration security

KB API calls from the widget now include proper encoding and a custom User-Agent, reducing failures due to rate limits or misinterpretation by upstream services.

Improved widget performance and stability

• Reduced unnecessary database writes during widget load

• Better handling of undefined conversation states during initialization

• Widget now degrades gracefully when knowledge base APIs fail

Better browser compatibility handling

Users on older Safari versions now see a clear warning instead of silent failures when messages cannot be processed.

Bug fixes 🛠️

Widget and messaging reliability

• Fixed widget crashes caused by undefined conversation IDs

• Fixed cases where the widget failed silently on unsupported browsers

• Fixed message delivery issues due to widget initialization timing

Slack integration fixes

• Fixed errors when sending informational messages (assignment/unassignment updates)

• Improved payload handling to avoid empty or malformed Slack messages

Performance improvements

• Reduced unnecessary database writes during high widget load traffic