Hello @kindnessville,
What a fantastic and insightful question to kick things off! It’s truly wonderful to hear you’re excited to try FluentCRM, and I completely understand why you’d want to clarify this crucial detail before diving into building your automation sequences. Your experience with Mailchimp highlights a very real pain point, and it’s smart of you to confirm how FluentCRM handles such a scenario.
I’m happy to confirm that FluentCRM is designed to elegantly manage email address updates without disrupting your carefully crafted automations. Here’s how it works:
While the email address serves as the primary unique identifier and is the least required field when creating a new contact in FluentCRM, it’s not the sole mechanism used internally to track your subscribers.
When a new contact is added to FluentCRM with their email address, our system automatically assigns a unique numeric ID to that contact. This ID acts much like a personal internal reference number for that specific individual in our database, separate from their email address.
So, if a contact is already engaged in an automation sequence and, at some point, their email address is updated, FluentCRM intelligently recognizes them as the same person because it refers to their unique numeric ID.
This means you can build those long-spanning, multi-year automation sequences with complete confidence! Should any of your subscribers update their email address, FluentCRM will continue their journey in the automation exactly where they left off, without any interruption or causing them to restart. Your automations will simply keep working as intended, unaffected by the change.
Please don’t hesitate to ask if you have any more questions as you explore FluentCRM.
Thread Starter
ZLC
(@kindnessville)
Thank you so much for your kind reply! I’m looking forward to building a sustainable automation with you.