• Replies 20 replies
  • Subscribers 362 subscribers
  • Views 132 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. 

  • $organization in reply to Andrew Recinos
    1024x768 Clean false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4

    Dilemma: The Box Office has a line of walk-up patrons (with a 20 minute wait for those at the end) to buy a $17 ticket. A member asks the harried ticket rep  to update their address. How many steps will this take before it becomes a disservice to those waiting in line? Does the ticket rep just skip it, if it is too involved?

     

    We need to be careful what we make mandatory or a required field, not all organizations need the audit trail, or would happily relinquish it in the name of efficiency. In the current Tessitura, I would gladly substitute a required telephone number field for a mailing address, and it would speed up some kinds of transactions (and yes, creates a problem with dups…but shouldn’t that be our decision what to require for our institution).

    Thanks!

     

    From: Tessitura Next Generation Forum [mailto:forums-nextgeneration@tessituranetwork.com] On Behalf Of Andrew Recinos
    Sent: Monday, March 15, 2010 7:22 PM
    To: rbernard@smm.org
    Subject: Re: [Tessitura Next Generation Forum] Changes

     

    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

    From: Dale Aucoin <bounce-daleaucoin4707@tessituranetwork.com>
    Sent: 3/15/2010 5:31:38 PM

    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




    You were sent this message automatically by www.tessituranetwork.com because you subscribed to the Tessitura Next Generation forum email notifications. You may reply to this message or visit the site to reply to the post above. If replying via email, please consider deleting the previous message text before sending to help with readability on the site. Thank you!

Reply
  • $organization in reply to Andrew Recinos
    1024x768 Clean false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4

    Dilemma: The Box Office has a line of walk-up patrons (with a 20 minute wait for those at the end) to buy a $17 ticket. A member asks the harried ticket rep  to update their address. How many steps will this take before it becomes a disservice to those waiting in line? Does the ticket rep just skip it, if it is too involved?

     

    We need to be careful what we make mandatory or a required field, not all organizations need the audit trail, or would happily relinquish it in the name of efficiency. In the current Tessitura, I would gladly substitute a required telephone number field for a mailing address, and it would speed up some kinds of transactions (and yes, creates a problem with dups…but shouldn’t that be our decision what to require for our institution).

    Thanks!

     

    From: Tessitura Next Generation Forum [mailto:forums-nextgeneration@tessituranetwork.com] On Behalf Of Andrew Recinos
    Sent: Monday, March 15, 2010 7:22 PM
    To: rbernard@smm.org
    Subject: Re: [Tessitura Next Generation Forum] Changes

     

    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

    From: Dale Aucoin <bounce-daleaucoin4707@tessituranetwork.com>
    Sent: 3/15/2010 5:31:38 PM

    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




    You were sent this message automatically by www.tessituranetwork.com because you subscribed to the Tessitura Next Generation forum email notifications. You may reply to this message or visit the site to reply to the post above. If replying via email, please consider deleting the previous message text before sending to help with readability on the site. Thank you!

Children
  • $organization in reply to Ray Bernard
    Nice catch, Ray!

    Perhaps "required" could be defined by something like user group?  Eg address reason is required if you log in as membership or development, but not if you log in as a box office user.  Or, perhaps there is some field which fills in with a default value for each group, as sources do now; any change made at the box office would default to "box office change."  The cashier doesn't spend time entering the data, but at least the back-end user will have some idea where/why the change happened.

    On another note, as for the "source" or "reason" for the change, I'd love to have NCOA as a reason - it would be nice to easily tell an automated NCOA change from a personal phone call.  Might help to untangle the occasional confusing record, too - if the patron calls and says "why on earth did my address get changed?" we could look and say, "Oh, looks like the post office did it" - and then we'd know that if the patron wants their address the other way, we should mark the record not to be run thru NCOA.

    Beth

    * * * * *

    The Dead Sea Scrolls: Words That Changed the World exhibition is at the museum through October 24, 2010. Witness authentic 2,000-year-old manuscripts, including the earliest biblical writings. Spiritually significant. Scientifically stunning. Visit www.smm.org/scrolls.

    Elizabeth A Varro
    Membership Manager
    Science Museum of Minnesota
    (651) 265-9829


    ----- "Ray Bernard" <bounce-raymondbernard7790@tessituranetwork.com> wrote:
    | From: "Ray Bernard" <bounce-raymondbernard7790@tessituranetwork.com>
    | To: bvarro@smm.org
    | Sent: Tuesday, March 16, 2010 9:31:53 AM GMT -06:00 US/Canada Central
    | Subject: RE: [Tessitura Next Generation Forum] Changes
    |
    | 1024x768 Clean false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4
    |

    Dilemma: The Box Office has a line of walk-up patrons (with a 20 minute wait for those at the end) to buy a $17 ticket. A member asks the harried ticket rep  to update their address. How many steps will this take before it becomes a disservice to those waiting in line? Does the ticket rep just skip it, if it is too involved?

     

    We need to be careful what we make mandatory or a required field, not all organizations need the audit trail, or would happily relinquish it in the name of efficiency. In the current Tessitura, I would gladly substitute a required telephone number field for a mailing address, and it would speed up some kinds of transactions (and yes, creates a problem with dups…but shouldn’t that be our decision what to require for our institution).

    Thanks!

     

    |

    From: Tessitura Next Generation Forum [mailto:forums-nextgeneration@tessituranetwork.com] On Behalf Of Andrew Recinos
    | Sent: Monday, March 15, 2010 7:22 PM
    | To: rbernard@smm.org
    | Subject: Re: [Tessitura Next Generation Forum] Changes

     

    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

    |

    From: Dale Aucoin <bounce-daleaucoin4707@tessituranetwork.com>
    | Sent: 3/15/2010 5:31:38 PM

    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


    |
    |
    | You were sent this message automatically by www.tessituranetwork.com because you subscribed to the Tessitura Next Generation forum email notifications. You may reply to this message or visit the site to reply to the post above. If replying via email, please consider deleting the previous message text before sending to help with readability on the site. Thank you!


    |
    |
    | You were sent this message automatically by www.tessituranetwork.com because you subscribed to the Tessitura Next Generation forum email notifications. You may reply to this message or visit the site to reply to the post above. If replying via email, please consider deleting the previous message text before sending to help with readability on the site. Thank you!