“Only 6 spots left” is one of the most useful lines you can put on a registration page. It gets fence-sitters to commit, and it stops people from planning a family trip around a workshop that’s about to sell out. The question is how to get that number in front of the public when your sales run through Altru.
The short answer: Altru tracks capacity well on the back end, but showing a live “tickets remaining” count on the public web form isn’t something you should assume it does out of the box. Below is how to confirm what your setup can show, a few workarounds that hold up, and what to think about before you publish a number at all.
Start by confirming what your web forms show today
Capacity in Altru lives on the program or event side: you set how many tickets a time slot or event can sell, and Altru stops selling when it hits that limit. Whether any of that count is visible to the buyer depends on the type of web form and how it’s configured, and the behavior isn’t always obvious from the setup screens.
Before you build a workaround, test it properly:
- Set up a test event or program in your sandbox with a small capacity, say 10.
- Sell most of it through the back office or through the form itself.
- Load the public form as a guest in a private browser window and see exactly what appears: a count, a “sold out” state, or nothing until checkout fails.
- If you’re still unsure, ask Blackbaud support directly whether your form type can display remaining capacity and whether there’s a setting you’re missing. Get the answer for your specific form type, since advance sales, event registration, and membership forms don’t all behave the same way.
Many teams discover the form only reacts at the end, when a buyer tries to add more tickets than remain. That protects you from overselling, but it does nothing to create urgency or help someone pick a different time.
Workarounds that work inside Altru
Watch capacity with a query, then update the page copy
Build a query that returns each upcoming event or time slot with its capacity and tickets sold, and calculate remaining from those two numbers. Run it daily (or more often for popular programs). When something drops below your threshold, edit the web form’s description or the page it’s embedded on to say “Limited availability” or “Fewer than 10 spots left.”
This is manual, and it will drift between updates. That’s why vague language (“limited,” “almost full”) is safer here than an exact number.
Split high-demand sessions into their own forms or events
If one class always sells out, give it its own listing. A dedicated page is easier to update by hand, and you can swap it to a “sold out, join the waitlist” message the moment capacity hits zero instead of letting buyers find out at checkout.
Use staff-facing reports for the phone and front desk
Even if the public can’t see the count, your staff should. Make sure the people answering calls have a saved query or report that shows remaining capacity by date and time. A lot of “how many are left?” pressure goes away when someone can answer it in ten seconds.
Should you show an exact number?
Not always. A few things to weigh:
- Exact counts can backfire on big inventory. “412 tickets remaining” for a general admission day sends no useful signal. Counts work best on small-capacity items: workshops, camps, behind-the-scenes tours, member previews.
- Use a threshold. Show nothing until availability is genuinely low, then show the count or a “few left” flag. That keeps the message meaningful.
- Stale numbers erode trust. If the page says 8 left and the buyer gets an error at checkout, you’ve lost more goodwill than you gained. Only publish an exact count if it updates in real time.
- Holds and comps count. If you hold back seats for members, groups, or VIPs, decide whether the public number reflects what’s actually for sale or the total remaining. Buyers only care about the first.
Showing live availability on your website
If you want availability that updates on its own instead of by hand, the count has to come from Altru at the moment the visitor looks. Social Good’s Calendar Builder creates embeddable timed-ticketing calendars for your website that show real-time availability pulled from Altru, so visitors can see which dates and times are open before they start a purchase. Altru still manages the capacity; the calendar just makes it visible.
Quick answers
Will Altru let me oversell if the page doesn’t show remaining tickets?
Capacity limits are enforced when the sale is processed, so the form should block a purchase that exceeds what’s left. Test this in your sandbox for each form type you use rather than assuming.
What threshold should trigger a “low availability” message?
There’s no standard. A common approach is a percentage for larger events (for example, under a fifth remaining) and a fixed number for small programs. Pick something your team can check consistently.
