You open a support case on a Tuesday because the daily sales batch won’t commit. By Thursday you’ve answered the same clarifying question twice, the case has been reassigned, and someone on your team is asking whether it’s worth calling at all. Anyone who has administered Altru for a few years has lived some version of this.
The good news: most slow support experiences come down to a few things you can control, mainly how the problem reaches Blackbaud, who on your team is allowed to send it, and when to stop waiting and escalate. This guide covers all three, plus where to turn when the official channel isn’t the fastest route.
Know which channels your organization actually has
Blackbaud support options vary by contract and support plan, and they change over time, so don’t rely on what a former colleague remembers. Log in to your Blackbaud account and check what’s listed for your organization. In general you’ll find some combination of:
- The knowledgebase. Searchable articles covering known issues, error messages, and how-tos. Search the exact error text first; a surprising number of “bugs” already have a documented workaround.
- Cases. A written ticket you submit and track online. This is the channel that leaves a paper trail, and it’s the one to use for anything that needs investigation.
- Live chat or phone. Useful for quick questions and for urgent outages. Availability and hours depend on your plan.
- Blackbaud Community. Peer forums where other Altru users and sometimes Blackbaud staff answer questions.
If you can’t see a support option you expected, that’s worth a direct question to your Blackbaud account contact rather than an assumption that it doesn’t exist.
Make sure the right people can open cases
A common source of delay has nothing to do with the problem itself: the person reporting it isn’t set up as a support contact for the organization, or their login is tied to an old email address. Then the case gets stuck verifying identity before anyone looks at Altru.
Fix this before you need it. Confirm which staff are listed as authorized contacts, remove people who have left, and make sure at least two people in different roles (say, your Altru admin and your membership or finance lead) can submit and view cases. If you’re not sure how authorization works for your account, ask support to confirm it during a calm moment, not during an outage.
Write a case that can be solved on the first read
The single biggest factor in turnaround is whether the first technician can reproduce the problem without writing back. Include:
- What you expected and what happened instead. One sentence each. “Expected the membership to renew for 12 months; it renewed through the old expiration date” is far better than “renewals are broken.”
- Exact steps to reproduce. Describe the area of Altru (memberships, advance sales, a specific web form, a query) and what you did in order.
- Specific records. Constituent names or lookup IDs, transaction dates, batch numbers, query names. Generic descriptions force a back-and-forth.
- The exact error text and a screenshot. Copy the message word for word; paraphrasing hides the clue.
- When it started and what changed. A new membership program, a price change, a staff permission update, a browser update. Even if it seems unrelated, mention it.
- Who and what is affected. One user or everyone? One computer or all of them? One form or every form? This narrows the cause fast.
- Business impact. “We cannot sell tickets online” and “a report column is mislabeled” deserve different priority, and saying so plainly helps support triage it correctly.
Before you hit submit, try the issue as a second user and in a different browser. If it only happens for one person, it’s likely security roles or a local setup issue, and you’ve just saved a day.
When and how to escalate
Escalation works best when it’s specific and documented. If a case isn’t moving:
- Reply on the case itself rather than opening a new one. Duplicate cases split the history and can restart the queue.
- Restate the impact with a date attached. “Our member event opens online sales on the 14th, and renewals are failing” gives a clear reason to raise priority.
- Ask directly whether the issue has been identified as a defect and, if so, whether there’s a reference you can track and a workaround in the meantime.
- Involve your account or customer success contact if a case has stalled for an unreasonable time or affects revenue. Give them the case number; they can usually see the history.
Stay factual and polite. The technician on your case often has limited control over priority, and a clear, calm summary is easier for them to pass up the chain.
Use your peers
For “how do other organizations handle this?” questions, the Altru community is often faster than a case. Post in Blackbaud Community, search past threads, and look for regional or sector user groups where museums, zoos, and gardens compare notes. Peers can’t fix a defect, but they often know the workaround that keeps you running while one gets fixed.
Keep your own record
Keep a simple shared log: case number, date opened, summary, status, resolution. Over a year it shows patterns, such as the same issue every fall when membership renewals peak, and gives you something concrete to bring to a renewal conversation or a vendor review. It also means the next admin doesn’t start from zero when you’re out.
Quick answers
Should I call or open a case?
Call or chat for a full outage or a quick question. Open a written case for anything that needs investigation, so the details and history are captured.
Can a consultant or partner open cases on our behalf?
It depends on your agreement and how Blackbaud authorizes contacts for your account. Confirm with support before relying on it.
