TryBooking Virtual Assistant: a VA who builds the event so the committee doesn't have to

Nobody searching “trybooking virtual assistant” is a professional events manager. It’s the school office manager building the Year 6 graduation event at 4:50pm, the P&C secretary who said yes to running the trivia night, the netball club volunteer who now owns the presentation dinner because they owned it last year. TryBooking itself is the easy part. The fifty small jobs wrapped around every event, the builds, the refund emails, the dietary spreadsheet, the treasurer asking where the reconciliation is, that’s the part that eats your evenings.

The daily rhythm a VA runs in your TryBooking

The work runs on the event cycle, not the clock, so here is what it looks like across one.

Build week first. A new event goes up: sessions and dates set, ticket types and pricing groups configured (adult, child, family, member rate), the early bird cut-off scheduled so it actually ends when the flyer says it ends, promo codes created for staff or sponsors, and capacity caps set per session so the hall does not oversell. If it’s a seated event, the VA builds the seating plan, tables of ten for the trivia night, rows for the concert, a reserved block for sponsors, before a single ticket sells, because retrofitting a seating map onto an event with 200 bookings is nobody’s idea of a good afternoon.

The booking form gets the same attention. TryBooking’s custom form questions are where schools and clubs quietly win or lose: dietary requirements, permission questions, emergency contact, pickup authority, T-shirt size. Your VA sets the questions up per ticket type so the buyer answers them once, properly, and marks the ones that must be answered as compulsory. Then, closer to the event, they pull a custom report of the answers and turn it into something usable: a dietary count for the caterer, a permissions list for the front office, a size run for whoever ordered the shirts.

During the sales window the rhythm is daily and small. Buyer emails answered (“I booked twice”, “can I move to the Thursday session”, “my ticket never arrived”), refunds processed against your written policy, bookings moved between sessions, tickets resent. The VA watches sales against capacity and flags the sessions that need a push, so your social posts go out while there is still time to matter, not two days before a half-empty night. Once a week the committee gets a one-paragraph sales summary instead of having to log in themselves.

Event week is logistics. A reminder email goes to every buyer through TryBooking’s messaging with the things people actually ring about: parking, entry time, what to bring, which gate. The gate list is exported, the scanning app is set up so door volunteers can check tickets on their phones, and a printed backup list is ready because a phone always dies at the door at 6:55pm.

Then the part that usually never happens: the wrap-up. The VA pulls the event revenue report and the transaction exports, reconciles ticket sales against what is sitting in the TryBooking account, logs the refunds issued, and hands the treasurer a clean summary before the funds transfer. When next term rolls around, the event gets cloned rather than rebuilt, with last year’s lessons already baked in.

Schools, clubs and small promoters use it differently

The same platform, three different jobs. For a school, the volume is the killer: a calendar of paid and free events all year, discos, concerts, working bees, parent-teacher slots, each needing its own form questions and its own permission wording, and the office staff doing it between everything else. The VA becomes the person who owns the event calendar end to end.

For a sports club or community group, it is seasonal and treasurer-shaped. Two or three big fundraisers a year, seating plans, raffle add-ons sold as ticket types, and a volunteer treasurer who needs the money side handed over reconciled, not raw. For a small promoter running gigs or workshops, it is speed: events built and live within a day of the date being confirmed, promo codes for the street team, and buyer emails answered fast enough that people do not ask for refunds out of frustration.

TryBooking suits all three because it is Melbourne-built, priced for community scale at 50 cents a ticket plus 2.5 per cent, and free for free events. A VA suits all three because none of those people were hired to run ticketing.

The honest bit

Some things TryBooking will not do, whoever is driving it. It is a ticketing platform, not a marketing one: it will not fill your event. There is no built-in ad tool, no automation sequences, no CRM nurturing past buyers into future ones. The VA can export past attendee data and work it, but the promotion itself happens outside TryBooking, on your socials, your newsletter, your school app.

The email tools are functional, not beautiful. Buyer messages get the job done but they are not a designed email campaign, and if you want branded comms you will be sending those from elsewhere with the TryBooking export as your list. Seating plans still take proper setting up. TryBooking generates the tables and rows from your counts, but the fiddly part is everything after that: reserved blocks, hidden seats, the pricing schema that ties prices to sections, and saving the venue as a template so next year is faster. Getting that first build right is exactly why it is a job worth delegating. And the money sits in your TryBooking account until someone transfers it out, which the platform will not do on its own and your VA deliberately cannot do either.

One more thing worth saying plainly: the custom report only shows what buyers actually answered. If a permission question was optional and a parent skipped it, no report fixes that. Getting the form right at build time is the whole game, which is why the VA sets compulsory questions before launch, not after.

What stays with you

The judgement calls stay yours. Ticket pricing and whether the booking fees are passed on to buyers or absorbed, that’s a committee or owner decision, and the VA will not change fee settings without instruction. The refund policy itself is yours to set; the VA executes it and escalates anything outside it before a dollar moves. Bank account details and fund transfers out of TryBooking stay with the account owner or treasurer, full stop, and that is a structural boundary, not a promise: the VA’s own login covers event management and reporting, not your banking.

For schools specifically, anything touching child safety or a sensitive parent situation, a custody note on a booking, a complaint with heat in it, goes to your staff under a written escalation rule. The VA runs the admin around your community; they do not make calls about it.

What it costs and where to start

TryBooking work sits on DotVA’s admin tier at $12-17 AUD an hour excl GST. Most placements run 10-15 hours a week, roughly $500-1,100 a month, though event admin is naturally lumpy: heavier in build and event weeks, lighter between, and the same VA usually carries the enquiries inbox and other admin through the quiet stretches so the hours stay honest.

Placement takes 7-10 business days. Your VA spends the first 5-7 days supervised inside your TryBooking account, starting with an event build you approve before it goes live, before doing anything solo. There is a $500 refundable deposit credited to your first month, a 30-day recalibrate-or-replace guarantee, and no lock-in beyond 14 days notice. DotVA has made 87+ Australian placements since 2024, most of them into exactly this kind of role: capable owner or committee, drowning in repeatable admin.

If you are a school or education business, the education page covers the wider admin picture beyond ticketing. The VA cost guide has the full pricing breakdown if you want to sanity-check the numbers first. Otherwise book a discovery call with Jenn, and bring the date of your next event; the build is a good first test.