NeetoDesk BlogMilestone M38 – Sub-categories, domain filters, better navigation & stronger spam controls

Milestone M38 – Sub-categories, domain filters, better navigation & stronger spam controls

Akash Srivastava

June 18, 2025

Let’s go through what we got done in milestone M38 (Jun 02 – Jun 15) for NeetoDesk.

New features and enhancements 🚀

Consistent file upload UI

The bulk customer upload flow now uses the same file upload UI seen across other Neeto products for a smoother experience.

Trimmed rich text content using NeetoEditor

Ticket descriptions and other rich text fields are now automatically trimmed using NeetoEditor helpers to avoid unintended formatting issues.

Improved navigation between tickets and customers

Clicking a customer in the tickets list now takes you directly to their profile. Similarly, you can now view all open tickets from a customer’s detail page.

Bulk actions in customer-specific ticket views

Bulk actions available on the general ticket list are now also available when viewing tickets for a specific customer.

Allowlist and blocklist for email domains

Admins can now configure domain allowlists and blocklists to restrict/allow domains from which email addresses are allowed to create tickets or comments.

New sub-category fields for tickets

Two new dependent fields—sub-category 1 and sub-category 2—can now be set during ticket creation, update, or closure.

Stronger spam protection logic

Improved filtering logic now blocks known spam patterns in email addresses more effectively.

Set ticket category in automation rules

Ticket categories can now be updated as part of the actions in automation rules.

Bug fixes ⚒️

Custom categories in automation conditions

Fixed a bug where custom categories were missing from the condition options in automation rules.

Mailbox name changes in Outlook integration

Resolved an issue where primary mailbox data wasn’t fetched correctly due to renamed mailboxes in Microsoft accounts.

Special characters in forwarded emails

Fixed a parsing error that occurred when special characters in forwarded email bodies interfered with original sender detection.

Ready to elevate your customer support?

Let's get started now.