Happy Monday, everyone!
Do any of you use a specific platform or document for those on your staff that request performances to be built/sold?
I a trying to find the best method to avoid all the email back and forth exchanges.
Thanks for any advice!
Janis
Hi Janis,
We have been using Trello for the last 2+ years to track our Ticketing builds across multiple program areas - Films, Lectures, Courses, Studio Art Classes, Member Events, Education Programs, etc. You can set deadlines, tag members for tasks, create checklists, upload docs for people to be able to submit events and proof what you have built. Because it is web-based, your users can access it pretty much anywhere/on anything, and you can control who has access to specific boards/team members/etc. Like most web programs, it has different levels (basic is free, you can get more features above that for different prices), and it also works with many other web programs (Slack, Dropbox, etc). It has helped us as it allows multiple production areas (Programmers, Tessitura Operations, Web and Creative, Database Marketing, House Managers) to be fully in on everything that is in the pipeline for building and going onsale, and allows for direct messaging within the application that cuts down on some of the email traffic.
Hope that gives you one direction to pursue - glad to answer any additional questions in the build workflow process.
Cheers,
Anne
Hi!
I use Jira, a helpdesk platform and have users submit a ticket with the attached form. Minimizes a good bit of the back and forth if they actually fill it out :) Then I have a template checklist that I paste into the support ticket description that I tick off as a build so they can see progress.
If someone new requests a build, I usually try to set up a quick meeting to explain each field on the form. Note, the attached form was created in Word with "developer" tools, so it's a little hard to edit.
Checklist:
() Built dates
() Prices confirmed
() GL Confirmed
() Holds placed
() Confirmation text added
() Tested in Application
() Tested on Web
() Ready for Sales
() Web copy added
() Published
Example Tessitura Product Request Form.docx
I love this form Amanda! Thanks for sharing it. Who feeds the information into the form - is it the marketing department or different programming areas, or a combination of both?
Usually the person that is running the program. We tend to have one point person in each department that gets a little training on the form and is the one who knows what the date/times/logistics will be.