• Replies 20 replies
  • Subscribers 362 subscribers
  • Views 145 views
  • Users 0 members are here
Related

Changes

Andrew Recinos
$organization

Hi all,           

Today we are asking about tracking constituent information changes in your business.  If a constituent’s information is changed in any way in the system, what do you need to know about the change?  What are some stories from your business (current and future) where you need to know about additions, removals or changes to constituent information? 

Thanks!

Andrew

Parents
  • $organization
    We often come across information that has been updated on an account and that information is incorrect or there is research added and it is incorrect.  Sometimes it is an audited area of Tessitura and we can track it back to a user.  Of course sometimes we can find out who made the change but since they no longer work for the company we cannot find out why they changed/added the information.
     
    For a while, when we had a full-time researcher, we would keep track of what research was done, where the information came from and who did the research in the Research-Research area.  That has kind of slipped away.
     
    For some areas of Tessitura it would be great to have a mandatory "source" and "reason" when updating information -For example when changing an address.  I think it would be cool to have a utility that only lets you add/change an address if you say where you got the new address and/or why you're changing the address.  Right now we track source/reason for address changes in Contacts Customer Service but people sometimes forget to add the contact note.

    Dale
  • $organization in reply to Dale Aucoin

    Hi Dale and others,

    Can you give me a few examples of Source and Reason? Would the source not be the same thing as the user (or in the case of changes made via the web, the constituent themself?)

    Also, would you expect Reason to be free text or something you choose from a list?

    Thanks!

    Andrew

  • $organization in reply to Andrew Recinos

    I could be wrong but maybe he is referring to source as being basically "Contact Method" like in the current CSI structure and even if not I'm thinking that is a good thing to keep track of anyways.
    I like having the options available in CSI's to record this information including the free text option but like both Dale and I mentioned unless it's mandatory it doesn't really work.
    So with that idea in mind and solely in regards to fields we've established may need some sort of additional required audit information be it dropdowns and/or text it would be nice if when updating those fields either a CSI (assuming they will exist in the next gen) gets generated to fill out or that required additional information gets sent to an audit trail of some sort for reference. 

Reply
  • $organization in reply to Andrew Recinos

    I could be wrong but maybe he is referring to source as being basically "Contact Method" like in the current CSI structure and even if not I'm thinking that is a good thing to keep track of anyways.
    I like having the options available in CSI's to record this information including the free text option but like both Dale and I mentioned unless it's mandatory it doesn't really work.
    So with that idea in mind and solely in regards to fields we've established may need some sort of additional required audit information be it dropdowns and/or text it would be nice if when updating those fields either a CSI (assuming they will exist in the next gen) gets generated to fill out or that required additional information gets sent to an audit trail of some sort for reference. 

Children
No Data