Hi everyone!
Our souces are, in a word, messy! Ticketing struggles to find them. I'm pushing to standardize with formal naming conventions. I've yet to find one that works across all departments.
We frequently have 12+ promo codes running simultaneously for a single production (across many) and track with fine detail between subs and single tickets.
Has anyone come up with a spectacular format you would be willing to share? Perhaps there's documentation I've missed?
I'm considering a seperate Excel document though it seems counterintuitive!
Many thanks for sharing!
Michelle
We have several means of getting the information for a source code... it's all meant to be crossed referenced, and duplicated information so that our staff can easily access it anywhere they feel comfortable with.