• Replies 7 replies
  • Subscribers 416 subscribers
  • Views 175 views
  • Users 0 members are here
Related

Ticketing for Online event accessed by unique codes

Donald Graham
$organization
Hi all,

We are looking for anyone who can offer help or advice for a request we have got from our programming team.

We are looking to sell for a online event on Tess/TNEW which we can sell as a normal general admission event. We then need to somehow get to customers who has bought a place a unique, special 16 digit code so they can access the event online. What is tricky is that the codes we need to send to customers are provided by the producers of the event. I.e. they can't be something that comes directly from Tess automatically (like a ticket number). The producers provide the codes in advance of the event going on sale.

We also want to get the code to the customer asap after they have made the purchase, although the event itself is at a set time and date. We want to be able to sell right up until the event starts (ideally until 30 min before).

If anyone has found a good way to do this, or something similar, for any events they are ticketing for it would be great to hear a rough outline of how you did it!

Many thanks,

Donald
Parents
  • $organization

    I've been doing what I call "post-order" emails for a few different events recently. The customer purchases through TNEW as usual, and we add a tiny bit of dynamic content to the TNEW confirmation email that basically says "further details are forthcoming". With the TNEW confirmation serving as a purchase receipt, the customer then receives an additional email within 3 minutes containing additional details -- in our case, something like a secret link to a watch page, or a unique calendar event add widget.

    This is implemented by running a SQL Agent Job every 30 seconds that scans for new orders and adds rows to T_TEMPLATE_QUEUE. You would need to build an HTML template for this email. In your case, prior to queueing the email as part of the SQL Agent Job, you would have some SQL code that assigns one of the unique 16-digit codes to the SLI no purchased by the customer -- you would need to load these codes into a local table ahead of time, and devise a table schema so that you can persist the SLI-code assignment. Inside your HTML template, you would pull the codes out of this table based on the SLIs in the order -- likely using the Custom/ DataService endpoints.

    Some other posts I've written recently that relate to this:

Reply
  • $organization

    I've been doing what I call "post-order" emails for a few different events recently. The customer purchases through TNEW as usual, and we add a tiny bit of dynamic content to the TNEW confirmation email that basically says "further details are forthcoming". With the TNEW confirmation serving as a purchase receipt, the customer then receives an additional email within 3 minutes containing additional details -- in our case, something like a secret link to a watch page, or a unique calendar event add widget.

    This is implemented by running a SQL Agent Job every 30 seconds that scans for new orders and adds rows to T_TEMPLATE_QUEUE. You would need to build an HTML template for this email. In your case, prior to queueing the email as part of the SQL Agent Job, you would have some SQL code that assigns one of the unique 16-digit codes to the SLI no purchased by the customer -- you would need to load these codes into a local table ahead of time, and devise a table schema so that you can persist the SLI-code assignment. Inside your HTML template, you would pull the codes out of this table based on the SLIs in the order -- likely using the Custom/ DataService endpoints.

    Some other posts I've written recently that relate to this:

Children
No Data