When a parent purchases a class for a child, we are going to be setting up a record for the parent (if a record does not already exist) and a record for the child, then create the association.
The problem is we need to track the ticketing history in the child's record so if I am purchasing an Art Class for my 5 year old son I need to indicate the constituent id for my son somewhere in the line item so we can update the Ticketing History on the child record.
This information will be useful for the life of my child's record for future upselling and donor cultivation.
Has anyone ever done this? Any feedback will be greatly appreciated.
We enter the child's customer_no in the For section of the Special Request screen to tie each child to a lineitem.
First Stage Children’s Theatre uses a special request on the order to link back to the child - everything after that happens via stored procedure.
MH
matt_hilgers@milwaukeeartspartners.org
IM: matt_hilgers
From: Tessitura Ticketing Forum [mailto:forums-ticketing@tessituranetwork.com] On Behalf Of Robert Taulty Sent: Tuesday, January 05, 2010 1:32 PM To: Matt Hilgers Subject: [Tessitura Ticketing Forum] Selling Children Classes
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Ticketing Forum. You may reply to this message to post to the Ticketing forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
We do the same by using the special request on the order. We also have a history table that we update for the the child record. This stores things Like absences, number of times late, class(performance).
We also assign the child to the order using the For field on Special Requests. Our Ticket History is customized to display the classes that the child has been assigned to including the parent’s name and constituent number in the Location field (and the parent’s Ticket History displays the child’s name in the Location field).
Hi,
We're just starting to use Tessitura for Education, and I'm looking into using the 'For' field on Special Requests for both parent/child ticketing history and also for School bookings (i.e. the ticket order would be processed on the School Master record, and the Teacher would be assigned via the 'For' field). Is there a standard, non-customised procedure in Tessitura that replicates ticket history on both the Parent and the Child record and is also useful for reporting processes? Or is this custom work that we'd need to undertake?
Any advice gratefully received!
Thanks,
Kate
Hi Kate,
We are doing something similar to this. There isn't anything standard to facilitate this. What we did was have a job that runs through out the day and looks at the special requests. Then it populates a custom history table. This history table is used in building the ticket history tab on the custom record. I would be happy to share what we have.
Jon
Hi Jon,
That would be great - thankyou! As I'm still fairly new to Tessitura (and as I'm not the IT specialist for the Royal Exchange), I wonder if you can let me know how you would prefer to share what you have, or whether it's already on TASK?
Thanks again - I'm beginning to see the light at the end of the tunnel!