In plenty of historic houses, the front parlor holds about a dozen people, and not one more. That room size decides more about your ticketing than any software feature does. Tours run on a fixed schedule, a docent leads each group, and a tour that’s oversold by four people runs late for the rest of the day.
Historic sites that run on Blackbaud Altru are generally not looking to replace it. Memberships, donor history, and admissions revenue already live there, and moving them would be a big project. The real question is whether Altru’s ticketing, plus whatever sits on your website, fits the way a tour-based site actually sells admission. This page covers what to look for, what Altru already covers, and where the gaps usually are.
How historic sites differ from general-admission venues
A zoo or science center can usually let people walk in all day and only worries about capacity on holidays. Most historic sites have tighter constraints:
- Small, fixed group sizes. Capacity depends on the smallest room on the tour route, the staircase, or how many people one docent can manage. It’s rarely negotiable.
- Guided, scheduled tours. A 10:00 and a 10:30 tour are different products with separate capacities, not one general admission ticket with a time printed on it.
- Several tour types. A house tour, a grounds-only pass, a behind-the-scenes or attic tour, and seasonal programs like candlelight or holiday tours, each with its own price and limit.
- Seasonal and weather-driven schedules. Hours change across the year, and outdoor or unheated buildings can close on short notice.
- School and group visits. These are often booked months ahead, need deposits or invoices, and take a whole time slot.
- Members who expect free or discounted entry still need a seat on the tour, so they have to count against capacity too.
Any ticketing setup you choose has to respect these limits first. Everything else comes second.
What Altru already handles
Altru covers most of the back-office side of tour ticketing. Daily sales for walk-up visitors, advance sales for people who book ahead, and group sales for schools and tour operators are all part of the core product. Programs and events can carry capacity limits, memberships connect to constituent records, and revenue flows into the same batches and reports your finance team already uses.
For many sites, the basics are fine. The trouble shows up in how scheduled tours are set up and in what the visitor sees online. Before you buy anything, it’s worth checking how your current setup handles:
- Capacity per tour time, and whether walk-up and online sales draw from the same pool.
- Members reserving a free tour spot, and whether that spot counts against capacity.
- Closing or canceling a single time slot (a weather closure, a private rental) without rebuilding the schedule.
- Combination tickets that cover more than one building or tour.
If you aren’t sure whether Altru handles one of these natively in your configuration, test it in a sandbox or ask Blackbaud support before assuming you need new software. A configuration change is cheaper than a new tool.
Where the gaps usually are
The common pain point is the website. Visitors want to pick a date, see which tour times still have room, and buy in a minute or two on their phone. When the online experience is a generic form, or a calendar on your site that someone updates by hand, a few things go wrong:
- The website shows a tour as available after it has sold out at the desk.
- Visitors call to ask what’s open instead of booking, and front-desk staff become the reservation line.
- Special programs get a separate page and separate process, so staff keep two lists in sync.
- Mobile buyers give up when the form is hard to use on a small screen.
None of those are back-office problems. Altru may hold the right capacity numbers, but the visitor just isn’t seeing them.
Questions to ask any ticketing tool for an Altru site
- Where does availability come from? It should read from Altru in real time, not from a copy that someone refreshes.
- Where do the orders land? Sales should end up in Altru with constituent records and revenue intact. A separate database you reconcile later is a long-term cost.
- Can it show different tour types clearly? House tour, grounds pass, and seasonal programs should be easy to tell apart on one calendar.
- Does it work on a phone? Test it yourself on your own phone, on cellular data, before you sign anything.
- Who keeps it updated? If adding a new tour time means a change in two systems, it will drift out of sync by midsummer.
- What happens at the door? Ask how tickets bought online get checked in. Older buildings often have weak Wi-Fi, so confirm how check-in behaves when the connection drops.
A sensible order for setting this up
Start with the building, not the software. Write down the true capacity for each tour, the tour schedule by season, and your member policy (free entry, guest passes, whether members reserve ahead). Then set those rules up in Altru so they match. Only after that does it make sense to put a better buying experience in front of visitors. A cleaner calendar on top of messy capacity settings just sells the wrong numbers faster.
Run one season with the new setup and look at a few things: how many calls the desk gets asking about availability, how often tours oversell or go out half-empty, and how much of your advance revenue comes from mobile buyers. Those numbers tell you whether the change worked better than any vendor demo will.
Where Calendar Builder fits
For the website gap described above, Social Good’s Calendar Builder puts an embeddable timed-ticketing calendar on your site that shows real-time availability from Altru. Visitors see which tour times still have room, and Altru stays the place where capacity and sales are managed.
Quick answers
Do we need to leave Altru to get better tour ticketing?
Usually not. Most of the problems historic sites run into are about configuration or the online experience, and both can be fixed while keeping Altru.
Should walk-up and online sales share one capacity?
Yes, in almost every case. Separate pools are how a 12-person parlor ends up with 16 people in it.
