Shahjahan Jewel is it possible to add a 'create booking' button from the contact page that pre-fills contact fields for the booking?

Hi,

I have been receiving a fatal server error related to FluentCRM since May 23rd.

When the error occurs:

I am currently using FluentCart in Test Mode. The error happens when I make a test purchase using a test user account. This test purchase triggers a FluentCRM automation to send an email, and the fatal error occurs at the exact timing the automated email is dispatched.

Error Mail Details:

Error Type: E_ERROR (or E_COMPILE_ERROR)

Error Message: Cannot declare class FluentEmogComposerAutoloaderInit6ba88f1695515329cfc7e4b26033cc69, because the name is already in use

File: /home/igial/tokyobigaku.com/public_html/whp/wp-content/plugins/fluent-crm/app/Services/Libs/Emogrifier/scoped-vendor/composer/autoload_real.php:5

Could you please investigate this issue? It appears to be a class redeclaration conflict occurring during the automation process.

Environment:

• FluentCRM Version: 3.1.0
• FluentCart Version: 1.3.28 
• WordPress Version: 6.9.4
• PHP Version: 8.3.30

Thank you

RESOLVED: Smartlink was tested in "test email" but they don't work in test emails.

I created a FluentCRM smartlink to an event page that is governed by membership rules access. I am sending the email out through FluentCRM to the registered user. However, when I test the link to a test account, I get directed to the standard MP login page. I even turned off MP "Redirect unauthorized visitors to a specific URL" to see if that was the issue. Smartlink autologin is enabled.

Has anyone found a way to make this work? MP is inside my automation to create lists and tags.

UPDATE (June 2): I've resolved this for my setup by rolling back — full details in the comments below. Leaving the original post for context, since it seems others hit the same thing.

After upgrading to 3.0 / 3.1, sending large campaigns became extremely slow on my setup. A campaign to ~30,000 subscribers was taking days to finish, where before it took well under an hour.

My configuration: FluentSMTP, server-side cron correctly set, ample memory, and no changes whatsoever to the configuration — only the plugin version changed.

I did quite a bit of testing to rule things out (server, memory, SMTP, cron) before posting, and I'd be glad to share what I found. Has anyone else run into this after the 3.x upgrade, and found a path forward?

Right now, when we capture leads through Fluent Forms, the IP address can already be collected as part of the submission data (which is something Fluent Forms has supported for a long time).

In many legitimate operational and compliance-related scenarios where there is a valid legal basis, that IP can be used to determine approximate country or city information for the lead.

What always surprised me is that FluentCRM does not currently process or enrich that data automatically.

In our case, for workflows where it is legally justified and operationally necessary, we built our own automation layer:

• capture IP from Fluent Forms,
• verify it through a trusted service,
• update the contact profile inside FluentCRM automatically.

So technically, yes, this can already be solved with custom workflows. And ours work reliably.

But honestly, it still feels like a patch for something that is extremely basic inside a modern CRM.

Having approximate location data is sometimes operationally necessary for:

• determining whether a service can legally be provided,
• shipping restrictions,
• VAT/tax handling,
• language segmentation,
• timezone-based automations,
• fraud prevention,
• compliance-related workflows.

Most CRMs already handle this natively.

So my question is:
is native IP-based country/city enrichment part of the roadmap for FluentCRM v3 or future releases?

Even better:
having trusted geolocation providers integrated directly into FluentCRM would make this much more powerful and reliable.

Because right now, needing external automations for something so foundational feels a bit strange inside an otherwise very complete ecosystem.

And of course, the more services, jurisdictions, automations and edge cases you handle, the more operational obligations you have (and the more room there is for costly mistakes if these basics are not handled properly inside the CRM itself).

I created an automation that includes starting a 7 email sequence.

Later I apply a tag ("got-sequence") tag, but it applies it as soon as it sends email #1

How can I apply a tag only after the whole email sequence has been sent? I don't see anywhere in sequences to apply tags.

I may change the length of the email sequence, so adding a day delay won't be reliable.

Thanks in advance!

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?