Workflow condition: Last Activity Date is more than X Days.
complete
J
JJ King
It would be great for the capability to add a condition to a workflow to only enroll if last activity date is greater than X amount of days.
Log In
Core Platform
Dear all,
Please check the below comments to make it work using "Workflow + custom fields" as per your custom use case.
Kindly post your suggestions on the existing behavior of Contact Last Activity here https://ideas.gohighlevel.com/contacts
Core Platform
complete
S
Super User
Core Platform: So is this possible now?
In automation:
Step 1 WAIT FOR 2 DAYS
Step 2 IF Contact last activity is > 2 days:
Yes = Send SMS
No = Return to Step 1
I don't see the option of "Last activity" in if/else.
Core Platform
Dear all,
Please check the below comments to make it work using "Workflow + custom fields" as per your custom use case.
Kindly post your suggestions on the existing behavior of Contact Last Activity here https://ideas.gohighlevel.com/contacts
C
Clifford Paulick
Core Platform: I didn't find an Idea by that name when searching. Is there a reason this cannot be merged with that? If it's built-in functionality, please link us to a KB article instead. Does your proposed solution/workaround have both Inbound and Outbound like David requested?
Core Platform
Merged in a post:
Split Contact Last Activity in two fields for inbound and Outbound
D
David Watson
Currently there's only one field (Last Activity) for both inbound and outbound activity, so if YOU are contacting them but they are not responding, you have no idea of what is happening to them.
For example, you have two clients that you are sending out daily emails to, and over the course of the last 180 days, one of them opened every email, and the other hasn't opened an email for 164 days ... yet both show "Last Activity" as being within 24 hours ... because it's the OUTBOUND activity.
Yet, obviously, the situation with each client is completely different.
It would be much better if the Last Activity field was split into two ...
Last INBOUND Activity
Last OUTBOUND Activity
THEN it would be useful.
D
David Watson
The Idea - Workflow condition: Last Activity Date is more than X Days.
is marked as under review, but this aspect of it should be considered at the same time!
Core Platform
under review
Core Platform
Let us know if this helps: Custom Field (Type: Date) + Math Operation
Create a custom field "Contact Last Activity", then you can update the "Contact Last Activity" custom field using Math Operation and use in the If Else condition.
C
Collen McCartney
Core Platform: that is helpful, and we really would need the last inbound activity to make it really helpful. If all that is happening is outbound and they are not engaging at all, blasting them with more marketing is kinda spammy.
T
Tech Support
Collen McCartney: more than a little spammy, super spammy.
On the other hand, if Last Inbound Activity is < 30 days I might send something with an attachment or link which would be unreasonable if the field was > 365 days!
A
Alexa Rosario
Core Platform this is absolutely not a solution and this should not have been marked complete. Why would this be a huge workaround when "last activity" should be a core filter for conditions.
T
Tech Support
Yes! Inbound activity has different implications than outbound activity.
B
Brian Mackenzie
This addresses a huge gap!
D
David Watson
I voted up your request, BUT ...
That's a bit pointless actually, because there's only one field (Last Activity) for both inbound and outbound activity, so if YOU are contacting them but they are not responding, you have no idea of what is happening to them.
It would be much better if the Last Activity field was split into two ...
Last INBOUND Activity
Last OUTBOUND Activity
THEN it would be useful.
I created a request for this here ...
please vote it up.
B
Brian Mackenzie
David Watson: Voted. Thanks for pointing this out.
J
JJ King
David Watson: I hear you! I just gave you an upvote as well. In my personal use case, it was actually based on outbound activity so we aren't spamming but agree an inbound activity could be useful as well.
R
Rob Hole
This is dooable right now using custom date fields. You just have to set each action as an activity (i.e. email opens, calls, texts, etc) as engagements to reset the last activity date to today... when that date field reaches greater than XX days it fires the automation to go or you leave them pending in an always running automation that sends them further down the line / resets the activity tracker.
C
Clifford Paulick
Rob Hole: I love when things are dooable! ;) Have a screenshare or GHL Helpdesk link to share?
J
JJ King
Rob Hole: I found another work around using tags with a similar logic to this, but I still think it would make sense to have this natively.
E
Eliel Perez
Rob Hole
Hello, I can't understand this explanation. Could you help me with a detailed explanation and screenshots? Please, it would be very helpful.
Load More
→