Did something change on the management of bounces and complaints from Amazon SES?

As you may know the "unsubscribe" link from the header on Yahoo! is sent to Amazon SES as complain (not as unsubscribe).

A lead clicked the unsubscribe header link on two emails from my automation, and obviously Amazon SES three days ago said it was a complaint.

I thought it was managed as usual, as "complaint", BUT I was shocked today because that person received my today's email and marked it AGAIN as "complaint", but still as "subscribed" on my FCRM.

Previously v3, for more than 5 years, this worked well.

That's the reason for my question: Did something change on the management of bounces and complaints from Amazon SES? Do I have to do something to solve it?

Thanks!

Really small strange things across the board, lost email sequences email content, coupons work for some, not for others. I can't use my own coupons.
Admin jumps when working with emails, same things for notes in FluentCRM...

Hard to pinpoint, but definitely related to the day it installed. It is really nice as an idea, yet basically same thing as using the wp admin menu since we only have Fluent plugins.

Maybe not stable enough yet?

FluentCRM already lets us send marketing campaigns and transactional emails, which is very powerful.

But there is one missing piece that could become extremely valuable: the ability to receive and manage replies to those transactional emails inside FluentCRM itself.

In Fluent Support, email piping already makes sense because support conversations can live inside the tool. I think FluentCRM could benefit from a similar concept for CRM-related emails. (Like many CRMs...).

For example:

• A lead replies to a transactional email after booking a consultation.
• A client replies to an onboarding email.
• A customer answers a follow-up email with extra context.
• A prospect replies to a sales or relationship email.
• Someone responds to an automated email and that reply should become part of the contact timeline.

Right now, FluentCRM can send the email, but the reply usually leaves the CRM and ends up in the normal inbox. That means the conversation, context and relationship history are split.

With FCRM 3.0, we have track of SMS. But we are missing the basics: email tracks.

In the AI era, this could be a game changer.

If replies could be stored inside the contact profile, FluentCRM could eventually support things like:

• AI summaries of the latest replies.
• Automatic classification of intent: sales, support, objection, interest, complaint, referral, etc.
• Suggested next actions.
• Triggering automations based on the content of a reply.
• Better CRM history for each contact.
• Cleaner handoff between marketing, sales and support.

I do not think this needs to replace Fluent Support. Support tickets should probably stay in Fluent Support.

But CRM conversations are different. Sometimes a reply to a transactional or relationship email is not a support ticket. It is sales context, customer intelligence, onboarding feedback or relationship history.

Having that inside FluentCRM would make the contact timeline much more useful and would open the door to very powerful AI-assisted workflows.

Curious if this is something the team has considered: email piping or inbound reply handling for FluentCRM transactional emails.

--
cc: Shahjahan Jewel Faizus Saleheen 

Post-upgrade, my Choose Template option has now been relegated to this three-dot dropdown, as depicted below. It actually moved twice that I noticed in the past week. It is now in the dropdown to the right. See pic of dropdown.

Could we pull this out of that area and make it more accessible?

While setting up a campaign and move through the four steps to send, I notice that the "Saved" indicator on the bottom right almost fully covers the functional button to move onto the next step. I "x out" of that indicator and move on, but it adds friction to the task. I recommend moving the functional buttons (now black) to a different place. Also, why have some of the buttons at the top and others at the bottom? Are there button location issues between mobile and desktop that they're trying to resolve?

10 days since 3.0 shipped, and you've kept the feedback coming. 3.1 is built around that feedback.

WordPress 7.0 AI support

WordPress 7 introduces a real AI infrastructure, and FluentCRM is ready for it on day one. We believe your CRM, your automations, and your AI workflows should live inside your own WordPress environment, not scattered across half a dozen disconnected tools. 3.1 plugs FluentCRM directly into that future.

AI refinements

• AI contact summaries now respect locale and language (big deal for non-English teams).
• Auto AI model handling is more reliable, with better fallback behavior.
• Gemini 3.5 Flash added to the supported model list.

Footer editing improvements

Three meaningful additions in one place after your 3.0 feedback:

• SmartCode insert menu inside the footer editor.
• Visual and Text editing modes.
• Font family selector, no CSS workaround needed.

Gutenberg, faster and steadier

• Improved asset loading and caching.
• Better automatic block recovery. This was a real source of friction after 3.0, and 3.1 handles it properly now.
• Conditional blocks no longer suppress iframe or media-only content.

Under the hood

• More reliable scheduled email processing, especially noticeable on large broadcasts.
• Searchable custom field, tag, and list dropdowns inside Advanced Filters. If you've been scrolling long lists, this one is for you.
• Plus a stack of smaller fixes across automation triggers, A/B subject validation, campaign tables, action dropdowns, and RTL rendering.

Full release notes: https://fluentcrm.com/blog/fluentcrm-3-1-0/

Keep the feedback coming. The team is cooking 👀

Does anyone know why when I create a newsletter email with Guthenberg editor in FluentCRM, then gmail client doesn't zooms the font properly? Anyone facing the same problem? How to solve?

Since Claude tells me it can’t use FCRM Templates, how does the design process work? Do I have to design everything in Claude or what is the best process?

Hey-- I think this flow could be made way simpler. I've suggested it before, and it was pretty well applauded as a quick win by the team. It hasn't made the rollout, so with alI that spectacular work on v3, maybe it's a good time for one more quick win.

Add a booking button to the user profile, just as in notes :)

Anyone know what happened to the RESTAPI? I found two different references to it in the docs, but not in the GUI?