Hello!
I'm looking for input from organizations who have implemented guest checkout in TNEW. Preferably, I'm looking for organizations with a similar structure to ours (season-based performing arts or annual performing arts festival), but I'll take anything. Mostly I'm wondering how bad is the issue with duplicates? Does the increase in revenue offset the additional staff capacity required to maintain duplicate records? How have you addressed the issue of duplicate records created by guest checkout?
Thanks in advance!
Michael
We print the new record summary every Monday for the previous week. Our staff then works on merges in their down time from those new record summary reports. We also train our staff to look for duplicate accounts when they're cleaning up web orders before printing the web. It does take time, but it's worth it.
Thanks Amber Gale! The New Record Summary is definitely something we would need to deploy. I'm sure it fluctuates, but could you ballpark the average number of duplicates in that report every week? I'm glad to hear that the value outweighs the additional labor.
On the new record summary, not all of the accounts are duplicates, however, we do average about 180 a week, or 20 pages (front and back). With an on sale this number can be up to 32-40 pages. It's a slow clean up process, but it gives my staff something to work on during the down time.
Of course, that makes sense. I've seen some other orgs talk about GC being used about 1/3 of the time. Applying that logic (and assuming every GC user had a record already), you've got about 60 duplicates a week. I think that's definitely manageable, and we're fortunate to have a lot of downtime in the offseason, based on the nature of our organization. This has been very helpful. Thank you again!