Fantastic information folks!
The to start with launch for 2023 is completely ready for you men. In this release, we’ve got some highly requested characteristics along with some standard fixes and extra. We’re happy to start off the 12 months by creating Fluent Support even richer and additional reputable.
In our past update, we extra JS Aid Desk and Assistance Scout for you splendid people today. This time we have bought a equivalent present for our customers that ended up caught with bulky SaaS products.
We at WPManageNinja imagine client aid is the backbone of a nutritious enterprise. We also believe that supplying client help shouldn’t charge you a ton of funds (specifically when making use of SaaS items).
So with no even more ado, let’s get to the capabilities and fixes in Fluent Help 1.6.8!
Characteristics in 1.6.8
We have executed 3 new functions for this edition. The features are described briefly here. You can test out our documentation for far more specifics.
Initially off, let us check out the Freshdesk migrator. The migration functions using Fluent Support’s ticket importer module we carried out in v1.6.6. Because Freshdesk is a SaaS solution the approach is a little bit much more complicated than Wonderful Aid or Assistance Candy (both self-hosted).
To use the migrator you’ll need a Freshdesk account and a connected API critical to access the ticket facts. Stick to the specific documentation for the whole course of action.
Toggle vehicle-near for Bookmarked tickets
Some of our customers asked for to pause automobile-closing for Bookmarked tickets on Fluent Support’s ticketing technique. To make it possible we included the toggle solution that makes it possible for you to avoid bookmarked tickets from vehicle-closing.
This permits the bookmark attribute to be applied as a marker for tickets that really should not be car-closed. It delivers utility when there is a lengthy-managing help dialogue that is using time to get settled. Vehicle-closing these a ticket can trigger a wide variety of confusion for the customer. Now it is in your command.
Buyer notification for on-behalf ticket generation
As of this release, clients will get a notification e mail when a ticket is opened by an agent on their behalf. Several consumers arrive by way of social media or other resources.
Most of these instances are not able to be added to the ticketing method specifically. In these kinds of situations, an agent has to request the buyer to create a ticket on their enterprise assist desk. We fixed this situation by enabling brokers to start tickets on behalf of prospects.
Some of our end users assumed it would be improved to send a notification to the buyer when an agent opens a ticket on their behalf. We have added it and this ought to remedy the connected troubles effortlessly.
Fixes in 1.6.8
In this version, we mounted 8 bugs. Here’s a transient description of the challenges and fixes.
Fluent Sorts personalized area submission
Building ticket submission kinds applying Fluent Sorts permits buyers to personalize ticket varieties. Having said that, employing custom fields for this intent in Fluent Kinds induced the webhook to fall short. Ensuing in the reduction of ticket facts and failure to make the ticket. This issue has been fixed and now the variety submissions should get the job done as meant.
Ticket development problem with Uncanny Automator
Users of Uncanny Automator reported that forwarding tickets by means of the Uncanny Automator webhook failed to ship Company Inbox facts on Fluent Aid. This was an situation on the Uncanny Automator conclusion and has been solved.
Agent front-conclusion bulk choose pop-up icons missing
The bulk ticket assortment in Fluent Support offers a pop-up for bulk actions. In a devoted front-close for the tickets dashboard, hosted outside Fluent Aid, bulk variety introduced the pop-up, but the icons for the steps were missing. In this launch, we have preset this concern. Now the pop-up need to function as expected.
On-near induce fails to include FluentCRM tags
Making use of the On ticket near bring about for including FluentCRM tags to tickets was not performing. We’ve reworked the triggers module to improved perform in such eventualities.
Password reset/New account button not doing work
When end users clicked the reset password or build a new account button, it didn’t get the job done and an mistake confirmed on the console. We traced this difficulty back again to a quick-code-linked difficulty that was used to exhibit the submission type on a particular website page. We fixed this by tweaking how shortcodes are processed and viewed from Fluent Aid.
Email piped tickets fall short to automobile-assign brokers
Electronic mail piped tickets have been failing in the automated agent assignment workflow. The concern was caused for the reason that the e mail piping result in was not included into the WorkFlow triggers. Now it’s been added and the issue is fixed no make any difference which e-mail supplier you use.
Ticket generation error whilst utilizing current user email
Due to how WordPress databases get the job done, it was creating conflict with Ticket Creation. The root lead to was when creating a ticket from an existing person ID on WordPress, the ticket creation module missing the chosen e-mail. This stopped the ticket from remaining produced with an empty e mail industry. This problem is resolved and must operate effectively from now on.
Reply concern on Telegram
Telegram replies was the most sought-after challenge on Fluent Help. We have figured out the routing for ticket replies working with Telegram’s bot automation and it need to functionality thoroughly now.
We at WPManageNinja normally want to place out a compact and efficient item for our customers. Maintaining that as our core motto we’ll carry on to acquire Fluent Aid to make it an even superior and extra effective assistance desk for WordPress.
We’re always listening to our end users to discover techniques to make Fluent Help the appropriate product for you. So make confident you’re a portion of our Facebook group and Twitter to continue to be in the loop.