Hubert, the admin assistant
Busy enough already? Just tell Hubert.
Running a ticketing system should not be a second job. Tell Hubert what you need in plain words, like three more dates or an event just like last year’s. It does the setting up, and nothing changes until you tap Confirm.
The problem
Routine changes mean clicking through the same screens, and the risk is always the one you did not notice until a customer did.
What we built
An assistant that does the job and shows you exactly what will change before it does it.
What is actually in it.
Look up and explain
Describes an event the way a manager thinks of it.
- Sums up a season as a run of dates, not rows
- Explains prices as the usual price plus the exceptions
- Says what is selling online now and what is not, with reasons
- Checks both halves: the event, and whether customers can reach it
- Knows which event or day you have open. This means that event
- Answers what special events did we run last year, with sales
Make changes
Each one confirmed on a card before it happens.
- Add more dates to an event, copied from the latest day
- Change a price from now, from a date, or on chosen weekdays
- Set up a new event like an earlier one, as a draft
- Add a ticket type or product copied from an existing one
- Release items or a whole event, after saying what customers can buy
- Mark days sold out across every channel, or back on sale
What it will not do
The limits are the point, not the fine print.
- Nothing changes until you tap Confirm
- Each card shows old and new values, days affected and tickets sold
- Runs under your own login and sees only what you can see
- Tickets already sold keep their price, and past days never change
- New events start as drafts, so nothing goes on sale by accident
- It will not cancel events, remove days, or change fees or capacity
On the record
Every conversation and confirmed change is kept.
- Price changes recorded in the history as changed with the assistant
- Every admin conversation kept permanently
- An automatic review every morning of the previous day
- Mechanical checks on every conversation, such as a tool error
- Each conversation rated, with a one-line summary and the transcript
- Daily and monthly ceilings, with alerts and a manual pause
Ask it in plain words
Add three more dates, same as last Saturday.
Old and new, side by side
The card shows exactly what will change.
Tickets sold are named
So you see what a price change does not touch.
Like Halloween 2025
It reads back what ran and asks what differs.
Your permissions, not more
It sees only what your own login sees.
Written into the history
Changed with the assistant, on the record.
Hubert, the admin assistant questions
Can it change something without us knowing?
No. Nothing changes until you tap Confirm, and each card shows old and new values, the days affected and any tickets already sold.
Does it see more than the staff member does?
No. It runs under your own login and permissions, and sees only what you can see.
What happens to tickets already sold?
They keep their price. Past days are never changed.
Could it put something on sale by accident?
New events start as drafts and new items start unreleased, so nothing goes on sale by accident. After a release it checks customers can actually reach the event and says what is missing.
What will it refuse to do?
It will not cancel events, remove days, or change fees or capacity, and points you to the right screen instead.
See it running for your venue.
Every demo is built around your venue. We base it on your own website, events and prices, so you can see exactly what changes for your guests and your team.
Request a demo
An honest conversation with the people who built it.