If I could have only one thing, it would be field change activity logging
It blows my mind that there is no way for us to see who, what, and when a contact's/lead's information changes.
Our team is constantly in and out of contacts, making changes to customer fields, and updating contact information. When we find a problem, we have to contact ZDSell support, so they can go lookup the logs and relay what happened, and when, and by whom. This takes days, and sometimes weeks.
Gosh darn it, it would be great if that information was written into the activity area.
-
Hi @...,
Thank you for your feedback - this is a great suggestion! I'll make sure a member of our Product Team reviews your post.
In the meantime, a workaround is to use our API for an external "audit log" for your account. It is possible to use Sell's Firehose API to see changes in near real-time and store those changes in a third-party system.
-
Thanks Katie, because the Firehose API is only available on the Elite Plan, it would increase our annual bill 300% and that's out of the question.
-
Understood! The Firehose API is a workaround and only available on the specific plans so I'll make sure our Product Team sees your feedback request for an audit log in your account.
-
+1! I'm not sure, however, that the loggin of this kind of activity should live in general activity of the contact/deal/person/lead. I believe it should be a separate tab where you can only see system changes that have been made. Changing ownership, territories, contact data, etc.
-
+1
We need a log similar to how there's the Events option on tickets in Support.
-
I think this points at a broader issue that the activity record isn't really a database log, it's a place to demonstrate that a rep is working a lead or account. I prefer a change log to be in the activity history too. Whether or not field changes are visible to every user is a different issue, but if there's no talent or access to use the Firehose API, a departing employee could sabotage the data and no one would know it.
Please sign in to leave a comment.
6 Comments