Use bot Timezone for attributes (to better filter in People Tab)
W
Will V
People filter, "signed up" is not functioning properly. This one is creating a serious issue when comes to doing follow-ups.
If to use the example as per screenshot, Today is Oct 3 and we need to return results for Oct 1, YET it is also pulling in the Oct 2 results!
We're following up with people who signed up 2 days ago, not 1 day ago. So with this returned data we cant follow up with those Oct 2 users because they’re not ready to be followed up, because they received bot messages just a little while ago
WHAT’S MORE, when we pull up Oct 2 data, those top 3 contacts seen in the screenshot (Oct 1 filter) are not even on it!
So with this filter we basically cant follow up with those 3 contacts today because they’ve not signed up 2 days ago AND when we filter the “2 days ago” contacts on the next day, they're not on that list either. All it means is that those 3 people will MISS a follow up.
That's many people to be missed over the month.
You may say that platform is set to UTC timezone, even though we have set it to EST timezone in the account, but this is not fixing an issue in any way.
Can you guys pls pls pls fix such serious errors?
Edgar Araujo
Updated the title for a better clarity on the matter - the issue here is that we save system attributes such as {{signed up}} within UTC timezone, which causes issues for users outside of this timezone. This may display users from different dates when you try to filter on People Tab.
Edgar Araujo
Updated the title for a better clarity on the matter - the issue here is that we save system attributes such as {{signed up}} within UTC timezone, which causes issues for users outside of this timezone. This may display users from different dates when you try to filter on People Tab.
W
Will V
Edgar Araujo: thanks for the update! and yes, serious issue, messes up the follow up process and stats tracking completely. I bet, for most users here cos how many operate in UTC time zone?
we've all our accounts & systems across the board set in EST, including Chatfuel account settings. so it really does not help that even with these account-based settings a platform still returns it in UTC instead of converting into account-selected time zone.
as far as I know, pretty much every such tool adjusts time zones according to the account settings. it is just that - simply adding the conversion from UTC to the one that's set on the account