Fluent Support 1.9.0 is here 🚀
Our team just released a minor update of FluentSupport. Version 1.9.0 focuses on refining the support experience with better control, helpful context, a free-of-cost SaaS helpdesk migration option, and small but meaningful enhancements across the platform.
Changelog:
- New: Integration with Fluent Community. (Pro)
- New: Informational replies on admin ticket responses.
- New: Help Scout, Freshdesk & Zendesk Ticket Migration Now Available in Free Version.
- Improved: Internal note functionality now works for closed tickets.
- Improved: Responses in closed tickets can now be edited.
- Fixed: Error message shown for the Priority field when the Product is required in the customer portal.
- Fixed: Fatal error triggered by the Share Essentials weekly cron job.
- Fixed: Customer responses are not displaying in agent response stats within agent reports.
- Fixed: Incorrect ticket response count shown in today's stats.
- Fixed: Broken media upload CSS in the page editor caused by the [fluent_support_admin_portal] shortcode.
- Fixed: "Waiting For Reply" filter not working in advanced filtering.
- Fixed: Responsive issues in the Agent Portal.
Our team is also working on a big update (2.0) with a super optimized admin UI upgrade and some exciting new features.
Full changelog: https://fluentsupport.com/fluent-support-1-9-0/
Soon jumping from version 1 to version 3? That must be a big one!
Hans van Gent maybe a big AI update ;)
Hans van Gent Sorry that will be version 2.0
Love the new updates. Thank you. Also love the Community integration. Is integration for the knowledge base with FluentCommunity also in the cards?
Great!!! kindly include the scheduling option in 2.0 and also add the attachment option when creating ticket
It looks like you can type any password for a valid Login when the 2FA is enabled and the code will be send to a user - password validation is completly skipped?
Note: I am using a custom page with a shorcode: [fluent_support_portal] and [fluent_support_login] in the "Message for non logged in users" field.
Please check if this is a bug or just me playing around.
Mat Had support test this out and they couldn't reproduce the behavior. Probably site specific.
Rasel Siddiqe it was fixed with the FlunetAuth plugin 2.0 update
Hi there,
Guys, could you please tell me — is there any other way to integrate incoming email into the system besides email piping? For specific reasons, I'm unable to use Amazon Lambda, and I'd like to know if a direct integration with incoming email is planned?
Or is this limitation actually part of the module's intended design?
If I can't use Amazon Lambda, it feels like I’m missing out on about 80% of this plugin’s potential. It's such a powerful solution held back by a narrow bottleneck.
All incoming correspondence from FluentCRM, FluentBoards, and possibly even FluentBooking flows through FluentSupport — and FluentSupport depends entirely on Amazon Lambda. That means without access to Lambda, half of the power of the entire Fluent ecosystem becomes inaccessible.
Is there any alternative or potential workaround for integrating incoming email with FluentSupport?
Thanks in advance for your reply!
I really love the Fluent ecosystem — but some technical decisions are definitely causing a bit of pain 😊
Best regards,
Eduard
Eduard Maniatovskii Hey Edward, we hear what you're saying here. Going to have a discussion on this in the next feature meeting. Appreciate the input you've provided.