La fonction de suggestion automatique permet d'affiner rapidement votre recherche en suggérant des correspondances possibles au fur et à mesure de la frappe.
I guess the first question would be to get some info on why would the stages change backwards? This is not possible with automation, so as you said, it would be only per person.
In terms of the report, would you want to see Bob made 3 lifecycle stage changes last week and Jenny did 6, or would you want to know the details of what was the original stage and then what changed?
The way I see it is to create a custom property to indicate that records every time when a backward change happens. Depending on the reporting requirement, the custom property can be just a "yes/no" field, where when that happens, it's set to "yes" and then you can report on how many contacts have changed to "yes" in the last week and have them broken down by contact owner.
The better I understand the need for the backward change, the more ideas I can come up with. 🙂
I guess the first question would be to get some info on why would the stages change backwards? This is not possible with automation, so as you said, it would be only per person.
In terms of the report, would you want to see Bob made 3 lifecycle stage changes last week and Jenny did 6, or would you want to know the details of what was the original stage and then what changed?
The way I see it is to create a custom property to indicate that records every time when a backward change happens. Depending on the reporting requirement, the custom property can be just a "yes/no" field, where when that happens, it's set to "yes" and then you can report on how many contacts have changed to "yes" in the last week and have them broken down by contact owner.
The better I understand the need for the backward change, the more ideas I can come up with. 🙂