Skip to main content
All CollectionsProduct Updates
Event Hub QTR 2 - Road map
Event Hub QTR 2 - Road map
Updated over 2 years ago

Hello, please find Quarter2/3 EH product road, a little late due to the enormous activity as can be seen below. We are really hitting our CI/CD strides and pushing changes live sometimes 2-3 times per day. Still a long way from super SAAS companies like Stripe that deliver changes to prod up to 15 times per day :P A long way off from the old Quarterly release programs of older style software.

As usual, our changes are detailed across our 2 application processes. Feel free to book me to discuss or suggest more changes here.

Stream (Corporate/Distribution). - *Complimentary system

Venue-Hirer-teams. - *Asset sale system.

Stream

released

  • Brands

    Our system is now multi-brand. (currently up to 10) On top of auto brand, EDMs - our new RSVP will support auto brand when released. Set your brands in the design center. Update your brand per event. Try our new auto-brand EDMs to reduce EDM build needs./

    • loom

  • Auto EDM and EDM at send.....using the above Branded EDMs may still require some personalization. Edit send time is up next for our EDM dev team.

    • loom

  • importer Audit/Toggle. The next update for the importer will be "favourite map" - to quickly map your standard column names to hose in Event hub.

    • loom

  • Multi-day

  • Enhanced assigned to

    • We have added more options and controls to our assigned-to / Ticket owner processes. Any larger teams using Event Hub will find ticket owner allocation an essential feature to distribute activities across teams.

  • More New tags were added for automation, Both of these are set on the Event Settings tab.

    • [[Guest_list}}. - useful to share the guest list via EDM

    • {{alternate location}} - another location tag for either address or sub-address

  • More custom questions (50% done)

    • We currently only allow 1 custom question. This has been increased to 6. The front end has been completed and we need to incorporate it into the New RSVP process mentioned below.

Coming Up

  • It's time for an update of our RSVP pages - we know P. here is the first UI prepared by Hannah. We will seek more feedback before build - ETA October

  • One of the last major features for Stream will be to better connect "requestors". ie other members of your company who have an interest in tickets for events. This started with our role of Ticket-owner and continues to be developed with the idea of the requestor role. We plan to solve this with

    • an event board and/or

    • https://bot.eventhub.com.au/eventStatus *sample idea only

      In Both cases the roles of the ticket owner or requestor become critical. There can be lots of friction here - we plan to auto-create the user on first-time use - by reference to the Domain of the email address provided.

    • Our Bot can easily be converted to a Yammer or Teams App. We hope that an app in this space will provide major automation benefits for users. Teamer app due Jan-Feb '23.

  • Multi-file. Allow addition of multi-file uploads. A good example is where other tickets are needed like parking/camping at the festivals

  • Multi Event part 2.. complete new Single Event UI as per above.

  • Quick table planner. Allow a quick build of tables for allocation.

  • Quick action RSVP comments


    ​

Venue/Hirer (Sales System)

released

  • Sales Page Price per event. You can now set prices per event/per group.

  • MIN MAX. Set Min-max sales numbers and step increments ( for example "Buy 10 Max as increments of 2 seats...only')

  • Reverse Sales: Rather than a flow of Event -> Product. You can now choose a product and then an event. See the sample here.

    link.eventhub.com.au/nel6. choose to buy now to see the event list drawer.
    Items like parking, where the product sold are the contextual focus, are perhaps built best this way.

  • upsell - catering

    • Loom

  • auto barcode creation. A sale cam now fully trigger

    • ownership > barcode create > ticket create > ticket send.

    We are trialling this with our new integration to skiData parking.

  • We currently share tickets by our tags {{tickets_releasd}}. we have created an upgraded ticket sharing process - a branded ticketing page URL. This should solve the issue of 'on share tickets down the line"

Coming Up

  1. FLOW 2 is about to release. We have plugged any gaps we've seen through initial demos and builds. New flows are about to roll. Hannah will coordinate this per Venue. Stay Tuned

  2. Sales by package - In WIP this week, sales or Multi-event packages is the next upgrade to our sales system

  3. seat picker/allocator

    1. A visual seat picker both for use at the checkout and for post-sale RE-allocation.

  4. Super hirer connect

    1. Our long-term plan is to fully connect Venues and Hirers - thereby by sharing Events/assets and flows, removing the need for any manual data here between hirers and teams. Most work has been done and we expect to trial after FLOW 2 has been released


      1. ​

Future Roadmap

No Code Integrations

A major and critical part of any cloud computing system is integration. Often costly and timeconsuming - it can be the major hurdle to any system build. Whilst Event Hub already supports many Webhooks and APIs (documents shareable by Postman.com)


You may have heard of a new paradigm in this area "no-code integrations". Essentially this provides a drag and drop builder enabling administrators (as opposed to developers) the ability to create real-time - event-based -data-sharing objects.

Event Hub expects to deploy our first version around Q2 2023.

Did this answer your question?