A visitor buys timed tickets online and shows up forty minutes late. Then they ask for a refund because the weather turned. Your policy covers both situations. The problem is proving they saw it. “It’s on our website” doesn’t hold up well at the admissions window. “You checked a box agreeing to it” holds up better.
That’s why so many museums, zoos, and gardens want an “I agree to the terms and conditions” checkbox on their Altru ticket purchases. Below is what’s realistic in Altru, what you can do without new tools, and the questions to settle before you add anything.
Start with the honest part: what the Altru web form can do
Altru’s online ticket sales run through its web forms. You can edit the text and descriptive content on those forms, so you can always display your terms or link to them. A required checkbox that blocks the purchase until it’s checked is a different thing. You’ll want to confirm whether your version of the ticketing web form supports it before you promise it to anyone.
We don’t want to guess here, because form options change and setups vary. Two quick ways to find out:
- Open the form’s configuration in a test environment (or on a copy of the live form) and look for custom fields, required fields, or consent options in the checkout step.
- Ask Blackbaud support directly: “Can the online ticket sales form require a terms-and-conditions acknowledgment before payment, and is that acceptance stored anywhere on the order or constituent?” The second half of that question matters as much as the first.
If the answer is yes, you’re mostly done. If it’s no, or “only as display text,” keep reading.
Decide what you actually need the terms to do
“Add terms and conditions” can mean three different things, and each one calls for a different fix:
- Disclosure. You want buyers to see the refund, late-arrival, and photography policies before they pay. Clear text on the form near the payment button usually does the job.
- Active agreement. You want a deliberate action from the buyer, such as a checkbox, so nobody can say they missed it. This takes a required field, which is the part Altru may or may not support for you.
- A record. You want to look up a specific order later and show that this buyer agreed on this date. This is the hardest part, because the acceptance has to be saved somewhere you can query, not just clicked once on a web page.
Before you change anything, run the wording past whoever handles your legal or risk questions. Activities with real liability exposure, such as animal encounters, behind-the-scenes tours, kids’ camps, or anything on water, may need a proper waiver instead of a checkout checkbox. That’s a different process.
Workarounds that work without new software
Put the terms where buyers can’t miss them
Add a short, plain-language summary directly above the payment section of the ticket form: “All sales are final. Timed tickets are valid for your selected entry window. See full terms.” Link “full terms” to a stable page on your website. A three-line summary gets read far more often than a link alone.
Repeat them in the confirmation
Whatever confirmation or eTicket email goes out after an online purchase should restate the key terms. That gives you a dated message tied to the order, and it’s the version visitors actually go back and reread.
Cover the front desk too
Web forms are only half your ticket sales. For daily sales at the desk, post the main policies at the point of sale and train staff to mention the no-refund rule and timed-entry rules when they apply. For group sales, put the terms in the quote or contract you send before the group pays.
Keep a version history of your terms
Your terms will change. Keep a dated copy of each version, even just a shared document with dates, so you can tell what a buyer in April agreed to versus a buyer in September. People skip this step most often, and it’s the one that matters when something is disputed.
If you need a real checkbox and a stored record
If disclosure isn’t enough and Altru’s form can’t require agreement, the other option is to sell tickets through a checkout layer that sits in front of Altru and still writes orders back to it. If you go that route, don’t stop at “does it have a terms checkbox?” Also ask:
- Can the checkbox be required, so the order can’t be completed without it?
- Can different events or ticket types show different terms?
- Where does the acceptance end up? Can you see it in Altru, through a query or on the record, or only in the vendor’s system?
- Does it record which version of the terms was accepted?
Where Social Good fits
Social Good’s Checkouts is a branded, mobile-friendly checkout that replaces Altru web forms for tickets, memberships, and donations, with the transaction data written back to Altru. If you’re thinking about moving ticket sales off the standard web form for this or other reasons, ask us how terms acceptance would work for your specific setup. Bring the questions above.
Quick answers
Is linking to our terms page enough?
Probably for disclosure, but not for active agreement. A link that nobody has to click is easy to dispute. A visible summary next to the payment button is a meaningful step up.
Do members buying free tickets need to agree too?
If the terms cover behavior, timed entry, or no-shows rather than refunds, yes. Apply the same terms to every ticket type so staff don’t have to make case-by-case calls.
