A museum that already runs on Blackbaud Altru doesn’t really need “ticketing software” in the abstract. It already has one. Altru sells admission at the desk, handles advance sales and group sales, tracks capacity, and ties every ticket to revenue and (when you capture it) a constituent record. The real question is narrower: is your current ticketing setup good enough for how visitors buy now, and if not, do you replace it or build around it?
This page is meant for the people making that call: operations, visitor services, and whoever owns the website.
What museum ticketing actually has to do
Before comparing vendors, list the jobs ticketing does at your museum. For most institutions it’s some mix of these:
- General admission, sometimes untimed, sometimes timed to spread crowds.
- Special exhibitions with their own capacity and often a surcharge on top of admission.
- Member admission, free or discounted, ideally recognized without a separate process.
- Programs and events: lectures, tours, family days, after-hours events.
- Groups and schools, booked in advance with deposits or invoices.
- Entry control: someone has to check that a ticket is valid for this day and time.
- Reporting: attendance by day and time slot, revenue by channel, and who your visitors are.
Altru handles most of that list in its back office; how well entry control and reporting fit depends on your configuration and hardware, so confirm those details in your own sandbox. Where museums usually feel friction isn’t in the back office. It’s the online buying experience and how availability shows up on the website.
Replacing Altru ticketing vs. adding to it
Some museums look at standalone ticketing platforms because their online checkout looks dated or isn’t mobile-friendly. That’s a legitimate complaint. But swapping out the ticketing engine while keeping Altru for membership, fundraising, and CRM creates problems that tend to show up a few months later:
- Two inventories. If online sales live in one system and desk sales in another, capacity for a timed slot has to be synced, or you will oversell.
- Split visitor data. Ticket buyers end up in a separate database, so the people most likely to become members aren’t sitting next to your members in Altru.
- Membership benefits get harder. Recognizing a member at checkout means the outside system has to know who is a current member, which means another integration to maintain.
- Reconciliation. Finance now matches deposits from two sources and two sets of reports.
None of that is impossible to manage, but it’s ongoing work. If Altru’s ticketing logic already fits your programs, it usually makes more sense to keep Altru as the engine and improve what sits in front of it.
Questions to ask any ticketing option
Whether you’re evaluating a replacement or an add-on, these questions separate a good fit from a demo that looks nice:
- Where does inventory live? Ask whether online availability is read from Altru in real time or copied on a schedule. A copy that runs every few minutes can still oversell a popular slot.
- Where do transactions land? Do sales post into Altru as revenue tied to a constituent, or do they arrive later as an import someone has to run?
- How are members handled? Can a member get their admission benefit online without calling the desk?
- What does a visitor see on a phone? Open the purchase flow on your own phone, on cellular data, and buy a ticket. Count the screens.
- Who maintains the website piece? If adding a new exhibition or event means a web developer has to rebuild a page, that’s a cost to factor in.
- What happens at the door? Confirm the tickets sold online can be scanned and validated the same way as desk sales.
If you’re not sure how a specific Altru feature behaves for your setup, for example how capacity is shared between a program’s online and desk sales, test it in your sandbox or ask Blackbaud support before committing to a design that depends on it.
Getting the calendar right
For timed entry and events, the calendar is the product as far as visitors are concerned. A few things matter more than features lists suggest:
- Show sold-out and nearly-full times honestly. Visitors would rather pick 2:30 than discover at checkout that 1:00 is gone.
- Put the calendar where people look. Exhibition pages, the visit page, and event listings should each show the dates and times relevant to that page, not send everyone to one generic ticketing link.
- Keep the desk and the website in step. If the front desk sells the last ten tickets for a slot, the website should reflect that right away.
- Plan for closures. Snow days and private rentals happen. Know how a closure in Altru shows up online.
How Calendar Builder fits
This is the gap Social Good’s Calendar Builder is built for. It creates embeddable timed-ticketing calendars for your website that show real-time availability from Altru, so the dates and times visitors see match the inventory your desk is selling from. Altru stays in charge of programs, capacity, and revenue; the calendar is the public-facing piece you place on exhibition, event, and visit pages.
Quick answers
Do we need to leave Altru to get modern online ticketing?
Not necessarily. Many of the complaints museums have are about the online front end, which can be improved without moving ticketing out of Altru.
Can untimed general admission and timed exhibitions coexist?
Yes, many museums run both. Decide which one is the default on your visit page, and make the exhibition calendar easy to find from the exhibition page itself.
