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

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 ?

Hi team,

Would it be possible to introduce custom ticket number variables in Fluent Support that allow for non-sequential, alphanumeric ticket IDs?

Currently, ticket IDs follow a sequential pattern which may be predictable and not ideal in some scenarios. I’d love the option to configure ticket numbers using variables that can:

• Include random letters and numbers
• Avoid predictable sequencing
• Add optional prefixes/suffixes (e.g. by department or support channel etc..)

Example Variables:

Here are a few formats that would be really useful:

1. {TICKET_PREFIX}-{RAND6}

   → SUP-4F9D3A

2. {DATE:Ymd}-{ALPHA3}-{RAND4}

   → 20251101-ZKR-8271

3. {CHANNEL}-{USERID}-{RAND4}

   → EMAIL-234-8X92

4. {DEPT}-{RAND3}{RAND3}

   → TECH-A9F4B2

This would not only enhance privacy and tracking but also add flexibility for support workflows — especially when we want to refer to tickets in email or public documentation.

Also, it would be great if this ticket ID could be:

• Easily viewed and copied from the ticket detail screen.
• Included in emails sent to the customer.

Thanks for considering this — looking forward to hearing your thoughts

Cheers,

Manoj from ONEMCO

The problem:

Currently, when replying to a ticket via email, customers only receive the latest message without any conversation history. This means they have no context from previous exchanges within the same ticket unless they manually scroll through their inbox to find earlier emails.

This creates a fragmented experience and makes it difficult for customers to follow the conversation naturally.

What I expected:

When managing support entirely via email (using email piping), each reply should include the full ticket conversation history — similar to how regular email threads work, or how other helpdesk tools like Help Scout handle it.

This way, customers can see the complete context of the conversation in every email they receive, without needing to access a support portal or search through old messages.

Why this matters:

Many businesses (including mine) want to offer seamless email-based support without forcing customers to use a portal. The current behavior breaks this workflow and makes FluentSupport less viable for email-first support teams.

Current workaround:

I tried using dynamic codes to include ticket content, but it only shows the initial customer message — not the full back-and-forth conversation.

Request:

Please add an option (even as a toggle in settings) to include the full conversation history in outgoing email replies. This would make FluentSupport much more competitive with other helpdesk solutions that already offer this feature by default.

Has anyone else experienced this limitation? Would you find this feature valuable?

If a ticket has a CC either from the start or on a reply the CC should auto populate and stay throughout the ticket