A single line of gray text under a form field can save a dozen support emails. “Enter the name as it should appear on the membership card.” “We’ll send your tickets to this address.” “Use the billing ZIP for your card.” These small notes are standard on most checkout pages, and their absence is one of the first things people notice when they look closely at an Altru web form.
This article covers what you can realistically do inside Altru, the workarounds administrators use when the built-in options fall short, and what good helper text says in the first place.
Start by checking what your form options allow
Altru’s web forms let you set up the fields a form collects, the labels on those fields, and some descriptive text on the form itself. What they don’t clearly offer, at least not as a general per-field setting, is a separate help line that sits under an individual field. Options can vary depending on the form type (donation, membership, ticketing) and on changes Blackbaud has made over time. So before you build a workaround, confirm what your forms can do:
- Open a test copy of the form in your sandbox or a non-production form and look at every text option attached to a field or a section, not just the label.
- Preview the form on a phone as well as a desktop. Text that looks attached to a field on a wide screen sometimes drifts away from it on a narrow one.
- If you can’t find a per-field description setting, ask Blackbaud support directly whether one exists for your form type. It’s a quick question, and the answer is better than a guess.
Workarounds that hold up
Put the hint in the label
The simplest fix is also the most durable. A label like Email (your tickets are sent here) or Name on membership card does the job of helper text without any extra setup. Keep the main label word first so it still scans, and put the hint in parentheses or after a dash. It survives form updates because it’s just the label.
The tradeoff is length. Labels that run past a few words get cramped on mobile, so save this for the two or three fields that cause the most confusion.
Use section or introductory text
If the form allows text above a group of fields, use it to explain that group: “The cardholder’s name and address are used for your membership record. If this is a gift, you’ll enter the recipient on the next step.” It isn’t directly under the field, but it reaches people before they start typing, which is often what matters.
Add text with your website’s code, carefully
When a form is embedded on a page you control, some teams use a small amount of JavaScript or CSS on that page to insert a note under a specific field. It works, but treat it as fragile:
- It depends on the form’s underlying markup, which you don’t control. If Blackbaud changes field names or structure, your note can disappear or land under the wrong field without warning.
- It won’t appear anywhere the form is shown outside your page.
- If you add text this way, connect it to the field with
aria-describedbyso screen readers announce it. A visual note alone doesn’t help everyone.
If you go this route, keep a short list of which forms and fields have injected text, and recheck them after Altru updates.
Fix confusion after submission, too
Some of what helper text prevents can be caught later. An acknowledgment or confirmation email that repeats the key details (“Your membership card will read: Jane Smith”) gives people a chance to reply with a correction before it turns into a reprint or a refund.
What helper text should actually say
Whatever method you use, the content matters more than the placement. Good helper text answers the question a person is about to ask:
- Why you need it. “We use your phone number only if there’s a problem with your visit.” People are more willing to fill in fields when they know the reason.
- Where it ends up. “This name prints on the card.” “Tickets go to this email.” This is where most data-quality problems start, especially with gift memberships and households.
- Format, if it matters. Only mention format if the form will reject the wrong one. Don’t explain things the form accepts anyway.
- What happens next. On a gift or tribute field, a line like “We’ll send the recipient a notice” sets expectations.
Keep each note to one short sentence. If a field needs a paragraph, the field itself is probably the problem, and it may be worth splitting or renaming it.
Pick the fields that cost you the most
You don’t need helper text everywhere. Look at the corrections your staff make most often: misspelled card names, tickets sent to an old email, gift memberships recorded under the buyer instead of the recipient, duplicate constituents created because someone used a different email. Each of those points to a field. Start there, and leave the obvious fields (first name, last name) alone.
When the form itself is the limit
If you find that labels and intro text aren’t enough and you’re maintaining a pile of code to patch the forms, it may be time to look at a different checkout layer. Social Good’s Checkouts is a branded, mobile-friendly checkout that replaces Altru webforms for tickets, memberships, and donations, with the data written back to Altru. For teams that want more control over how a purchase or gift form reads, that’s one option worth comparing against what your current forms can do.
Quick answers
Can I add a tooltip or info icon next to an Altru form field?
Not as a standard setting that we can point to. Check your form type’s options in a sandbox and confirm with Blackbaud support. Otherwise, a clear label usually works better than a hidden tooltip, especially on phones.
Will custom code on my page break when Altru updates?
It can. Any script that targets the form’s internal markup depends on that markup staying the same. Retest after updates and keep the list of changes short.
