Hello and thanks for reading our 21. Qtr3 Roadmap update.

If you missed last month here it is:
​

I'll review our guest (attendee management system) first this time followed by our Venue system.

Here's hoping the high level of vaccinations rates facilitates a quick back to normal for our Industry.

Bi Reporting: Deployed

New BI(business reports) framework is deployed and 3 new reports are in-app.

These are currently being added on a per-user basis only. If you don't see and would like to - simply let our support team know. The new MS power BI framework lets us provide almost any report in any format.

Email transactional audits trails are being added this week.

FBT standard pricing: WIP

Each company will be able to add standardized pricing at the Venue-FAC-Ticket level rather than the pure ticket level. This will allow much faster and easier FBT valuations.

URL - sharing (complimentary registration) : QA / About to deploy

Share a limited ticket URL to sponsors or teammates.

Any guests added to the page will add to the guest (and contacts) as attending. You can choose to direct to the A or B list.

B-list: QA / About to deploy

Send requests from Calendar or shared URL (above) to A or B list.

Promote guests from the A or B list with one click.

Preferencing stage 1: WIP

We've begun building meta data preferences.

Standardizing event types and team names for example. We will then apply the same meta data through the app.

Salesforce or any CRM - webhooks: Deployed

Event, contact, and the guest list created and changed fired to any endpoint.

Seat planner: build and deploy.

Core planner is built - we are now joining modules like our guest list.

You'll see a new Menu Item "layouts" below our facilities.

Here I am testing on 30 x 20 = 600 seat "bay".

Paid for registration: QA

It's a fairly trivial extension for us to allow paid-for tickets inserted into the guest list (rsvp-attending as true). Using our already app components like Payments. orders, url builders, ticket builders, we've added an event-page builder to create a "paid for" events registration process.

Many companies build a registration system first. We did last. If you are using Event Brite or tools like it this enables a more cost-effective version and truly creates a full end-to-end event system and "one source of the truth" database.

Preference automation. Data ready: Individual preferencing: Planned next QTR

We've already begun the standardization of Event metadata as per above (event Type and team names). You'll soon see on some team events like this.

The standardization of team metadata was critical before we began automatic capture of event and team preferences via the RSVP and registration processes.

Stay tuned.

Email validation planned next QTR

Many customers are still sending to dead email addresses - this is unproductive and reduces our IP health. We plan to add auto validation of emails soon - Free for T5 - for some customers this will become mandatory.

Vaccine validation: seeking more input

** the future of mail. Is it time to invite via SMS.??

Alex

Questions/ Survey

We are adding another 4 custom question types and ratings as input. This will enable "auto-survey" as an ongoing process. Stay tuned.

BI reports: deployed

New sales reporting and accounts analysis has been deployed. Email audits are about to be released this week.

Standard Event reports

More standard event reports - including aggregated guests lists.

Found in any single event view.

Full event/Venue Guest List - if acceptable from the distributor - will default to true.
​

Sales items updates
3 major upgrades to sales processing are in WIP.

All in WIP and planned deployable by Mid October for new season sales release for the AU market.

On completion here we will review and plan per sales - URL branding.

Events Page - Sales categories

EH is adding a sales "category" - a level above the current sales URL tag.

This will allow us to provide a permanent page of "events for sale" - by category. You determine/create the categories - and then add an icon and a URL from, the sales system.

This will include newsletter (account) registration and our first step to a full "booking system" - including non-event days.

In our first step to including non-event day sales - users will need to identify - via facilities config - assets bookable on non-event days with appropriate config. eg max hours/ pre-advance block times etc. We will add and store contract exchange and link our flow builder to enable upsell of food and asset needs (projector/tables chairs) etc. We will add a filterable UI to move between event days and non-event days

Presentation

This will be both a URL and embed code for any website you might already have with editable CSS controls.
​

**** If our Attendee/Guest management users would also like a permanent Events page like this - let me know - easy to facilitate. Whilst the Events system started as an invitation system...there is no reason why that can't be flipped to add "expressions of interest " prior to an inviting release - - via a page like above - shared across your organization.

Accounts "domain"

Additional Org domain and account owner added to the accounts system. Useful when collaborating with hirers and / agents on events build (one source of the truth) and for allocation and measurement of sales data.

F&B flows

4/5 components completed for Flow 2. Expedited Beta Nov-Dec

layout /Seat Planner

About to move to Beta.

thanks

Scott and team :)