FCRM > Trigger > Change on Status
It would make our lives much easier if we add the trigger "Status Changed" into Fluent CRM.
This will allow to, actually, squeeze the potencial of the "not that new" [Transactional] State, and do a proper segmentation + compliance with GDPR.
Eg.: User unsubscribes (issue: that will cause, as many know, unsubscription of all list, even they are clients, expecting transactional emails) > FCRM Automation > Change Status to Transactional.
Or, forms, that are just for managing; or cases in which we want to add info from employees from different companies.
Which, btw, brings another request: being able to add the role, when a company is assigned...
for now if you have 2 lists and someone unsubscribes so he unsubscribes from both lists?!!
Ramsis Kasis Yes. Form all of them.
Unless they do something quite unexpected: manage their preferences.
If they use Direct Unsubscribe from their email box or direclty from the Unsubscribe button (whatever is your config here on if you want one-clic unsubscribe or ask for feedback), the user will be unsubscribed from all the lists.
So... yep. It has always been a feature request to be able to have a more granular control over this, so as to just unsubscribe from the list from which the user received the email.
Not the case, sadly
Jorge de los Reyes it is very bad for paid members that they should be in the list to get updates
does any one find a solution for that?
Ramsis Kasis Yes, I know!
Two workarounds (not very decent imho):
-
Do not use #unsuscribe# on emails, but manage preferences instead.
-
Apparently, since "transactional" and the option "Start automation even if not in subscribed status" can be used for this. The thing here is that, suscribers are not changed to transactional when unsubscribed, but to... unsuscribed. And if you do list clean ups (as anyone, legally and for performance must do...), you could end deleting those contacts (clients) from your lists. Or they could stop receiving other info or bulletins they are suscribed to.
So... go directly for: no unsubscribe header but manage preferences is what I've seen the most. Maybe users here have other workarounds.
Just searched for this very thing to see if I was overlooking something. Seems like triggering an automation on a status change would be a no-brainier. If for nothing more than to execute administrative and maintenance automatons on the back end.
Hopefully Shahjahan Jewel Masiur Rahman Siddiki and the rest of the team are considering this for 3.0
Mike R The thing is, it’s already available on the dev docs and you can achieve this with automations. But, not having this natively… is indeed a really missed option.
Just like the unsubscribe button aplicable only to an affected list and not to the whole profile. I really miss that too!
Jorge de los Reyes oh I had not looked at the dev docs. I'll check that out. Thanks for the heads up.