We already have had a huge interest from people throughout the industry looking to share their knowledge, experience and even their mistakes with fellow professionals at #TPC2017 asking when we will accept papers on suggested sessions for 2017.

In truth, there were sessions we just couldn’t fit into the packed schedule back in March at #TCP2016, so they are already “on the books” so to speak.

Whereas with the help of a number of professionals in the industry we can curate stories and case studies into sessions and learning tracks, we know that there are so many other great stories out there to be told and heard.

In line with other education based conferences, we will be launching a call for papers in the coming weeks, to allow you to submit your ideas for sessions you would like to present.

As soon as the application process is open, we’ll let you know. In the meantime think about the things you have done, learned or even got wrong, along, of course, with how you fixed them and lessons you learnt that your fellow professionals would love to hear about.

You don’t need to be a great speaker or even have lots to say, we are more than happy to help group potential speakers together to have a great session.

  1. The session, including Q&A should be either 30, 45 or 60 minutes long.
  2. It can’t be a sales pitch for your services, products or venue, but can highlight elements of these where relevant
  3. Ideally it should have clear learning takeaways for the audience, either in a new approach, technology or revenue opportunity

Feedback from #TPC2016 delegates showed a clear demand for more ‘case study’ sessions in addition to theoretical sessions, so exactly how did you roll out mobile ticketing, what went wrong and how did you fix it? as opposed to the pros and cons of doing it.

If you have any thoughts on proposing a paper and would like an informal chat, please drop us a line to info@ticketingprofessionals.co.uk and we’ll get straight back to you, or simply register your interest below.

[chimpy_form forms=”2″]