Only Google captcha is available within the product. Everywhere else on my site Cloudflare Turnstile is used for captcha, when will this option be available within Fluent Support?
Is it possible to trigger an email to the customer once a ticket has been assigned an agent.
Currently in order to do email piping you need the pro version AND it goes through fluent's servers
Is there a way to do piping directly from a POP (or GMAIL) account - I thinking from a security perspective there are instances where you do not want it going through a 3rd party system
We use FluentSupport in a lot of solutions. It’s great — but the AI part being OpenAI-only didn’t fit our needs. We started building a one-off integration… then realized this isn’t just a FluentSupport issue — it’s a WordPress-wide pattern: a lack of real choice.
So we did what any ex-TranslatePress dev would do: built a new plugin to solve it once and for all, across any plugin or theme.
Meet RedirectPress — a simple-to-use WordPress plugin
Set which provider you want to redirect from and where you want to redirect to.
It’s fast (lightning fast), adds virtually zero overhead, and works out of the box with any plugin or theme — no intervention from third-party developers.
Use the provider you prefer — Anthropic, Groq, Google Gemini, xAI, OpenRouter, ShareAI, or any custom endpoint.
Not just AI: point translation to DeepL, re-route SMS/notifications to your gateway of choice, and keep your existing stack intact.
if you want to use other AI providers in your wordpress website, join the waitlist, in the next weeks we will be included in wp.org repo and will work with fluentSupport as well.
Hello, really love the integration between the support and cart, the only issue is that we are not able to change the slug of the page, any way to fix this?
This is so annoying. I love FluentCommunity, really excited about FluentCart, rely on Forms and CRM...
But email piping continues to be a disaster.
New request today, email subject "The Wedding business box - content issue"
Reopens and updates a ticket closed 4 months ago, subject "The Wedding business box - July’s training"
Fortunately, the agent who closed the ticket 4 months ago is in today to get the notification.
- Subjects should be matched fully
- Need ability to lock closed tickets
- why not put ticket number into reply emails so that it can be used for matching
Last night, an new ticket email with no subject updated a closed ticket with the subject "search"
Tried logging with support - they cannot recreate it 🤷
So I use MainWP as my management tool and I was finding I was going back and forth multiple times between fluent and mainwp - so I wrote a plugin for mainwp which pulls in the support tickets (title & link) into mainwp and using a custom field I have it linking to the sites in mainwp
This still needs some work as I have a bunch of coding style things to clean up - also I am a single person agency so I am a single agent - I do not have filtering by agent on this first release.
I'm also seeing if Fluent (or MainWP) want to take this on as official plugin vs me as a 3rd party.
Shahjahan Jewel Rasel Siddiqe - I have a short demo video I can send you.
Is there an update for Fluent Toolkit. I have version 1.0.0. It does not have all the Fluent products listed. Could someone share the link for the most current download please?
Today, the WP Plugin team closed our plugin temporarily and asked us to fix a few things. Our team submitted all the requested changes within two hours of the email.
Reason:
We missed including the GitHub URL in the README, normally they don't close the plugin for this reason, but somehow our plugin got closed temporarily. We don't know exactly when they will review and make the plugin available again. This may take a few days, depending on their queue.
You can still directly download the latest version for this url:
https://downloads.wordpress.org/plugin/fluent-support.zip
We are really sorry for this inconvenience. We are hoping the plugin will be available on wp.org soon.
fluent suport is not anymore available on the repository, why ?
