FluentSupport 2.0.5 Release - Minor Update
We just shipped a fresh update with some new features, performance improvements, and bug fixes. Here's what's new:
- Dark Mode for Admin Dashboard: The admin dashboard now supports dark mode for a more comfortable support experience, day or night. It's the very first version, so we'll need some color adjustments in the upcoming updates.
- OpenAI GPT-5.2 Support: FluentSupport now integrates with OpenAI's latest GPT-5.2 and GPT-5.2 Chat models to power your AI-assisted support workflows.
- View Tickets (Read Only) Permission: Need to give someone visibility without edit access? We've added a dedicated read-only permission so you can control exactly who can see and who can act.
⚡ Improvements
- Ticket list loads noticeably faster — no more waiting around
- Large-scale Zendesk migrations are now significantly more optimized
🐛 Bug Fixes
- Draft Reply permission not working correctly — fixed
- Attachment links breaking during ticket merges — fixed
- Unordered list formatting in ticket content — fixed
- Integration settings save button not always visible — fixed
- "Waiting Since" tooltip showing wrong date — fixed
- Saved Replies left menu link — fixed
- Login page styling glitch — fixed
- Date range picker layout on smaller screens — fixed
Update and enjoy! As always, let us know if you run into anything. 🙌
P.S. If FluentSupport has made your support workflow easier, we'd love a quick review on WP repo. It means a lot to the team! 👉 https://wordpress.org/support/plugin/fluent-support/reviews/
YES!
Looks good! The "view tickets" is a step in the right direction, but we still need admins to be able to reply to or close a ticket as another user, so that we don't have to log into a different browser using a different account to reply as "Customer Support" instead of under our own name. Alternatively, please could you allow admins to use a different name when replying to a support ticket (or when closing it)? Small business owners who do everything including answering support tickets don't want to look like they are doing everything, or sometimes people won't ask a support question if they think they are bothering the site owner. Thanks for considering this request!
Dark Modeeee 😍😍😍 Thank you so much Jewel and Ninja-Team! ♥️
Thanks! Do you have any plans on making FluentSupport fully self-hostable? I know I’ve asked before, but I saw the FluentCart video you uploaded a couple of days ago where your colleague highlighted the importance of self-hosting.
Karl Emil Nikka It's a self-hosted plugin and only for the email piping, we needed the parse the incoming email which we use AWS serverless Lambda and we fully open-sourced that here and anyone can actually host that themselves: https://github.com/WPManageNinja/fluent-support-email-parser
Shahjahan Jewel Thanks. Is the parser still maintained? It hasn’t been updated for four years. If it’s still maintained, that’s great for all customers who are willing to pipe their emails through a US based company’s cloud, but please consider offering an IMAP based solution in the future.
Karl Emil Nikka That repo still works as Email Stucture don't get changed often and same is true for Lamda Functions. We will check the IMAP solution but the only problem is IMAP requests are complex and expensive. We will see if we can build something around it. That will reduce our Lamda costs as well.
Shahjahan Jewel Thanks! And for all bypassing readers, you can currently use FluentSupport in a GDPR compliant way by self-hosting the parser in Amazon’s cloud since Amazon AWS is part of the Data Privacy Framework program. I just don’t have any confidence in agreement long-term.
Shahjahan Jewel I still have the same problem. When I close a ticket, it still appears even though it is closed. When I click on the ticket and go back, it appears as closed.
Congrats for the View Tickets (Read Only) Permission feature!
and also noticed viewing tickets list is much faster 👍