When our front line staff self-identify files that need to be merged, they create a CSI for our admin team to schedule the merge. The front line staff do not have access to the Constituent Merge screen. With 15.1, we've noted that it is no longer possible to merge multiple files into one keep file at a time. We're now looking at how we'll manage that - do we ask the front line staff to create a CSI for each merge so that our admin team can mark one CSI closed and then complete the next CSI after the merge procedure runs? Or, do we ask our admin team to manually keep track? This can be troublesome because we only have our merge proc running three times a week.
So, we have a couple of questions here:
1. How often do you have your merge constituent proc running?
2. How do those on 15.1.x handle multiple merges into one keep file?
3. Do other orgs allow their front line staff to schedule merges themselves?
Any insight into your own process would be great!
Hey Michele,
I believe all the vast majority of our users have access to the merge window. We have the stored procedure run nightly to look for new duplicates and to merge our scheduled duplicates. We have our set very broadly so it brings in a lot of accounts that are not duplicates (I wish there was a way to remove that possible duplicate marker so that Tessitura doesn't find the same "dupes" every day). As for V15.1 and the new merge process, I just setup a reminder in Outlook to do those merges. I suppose I could also set up a task in Tessitura and have a reminder populate every time I have one when I log in the next day, until I schedule the merge.
I'd be happy to talk more with you.
- Chris
Thanks Chris. Do you find that you've had 'issues' with users incorrectly merging files? I worry that they may not be as attentive to the process as our dedicated admin staff.
I haven't noticed that happening at my current employer. I, personally, have made that mistake before. I find it's easier to make that mistake when manually entering account numbers versus using the merge window as that gives you what Tessitura thinks is the duplicate. It's a much easier way to verify that they are actual duplicates in need of a merge. Unfortunately, if you give access to merges, then staff can enter a manual number or use the possible dupes. However...if you instill true fear into staff about merges and that they "not able to be undone", then you should be okay. I always now double check merges I manually enter to ensure I am merging the correct duplicate accounts.