Good morning all,
I'm curious if anyone here would be willing to share some examples of information they've added to a Custom Constituent Header in Tessitura.
I'm currently in the process of thinking through some changes to our headers, and I've already written code to display an icon when a constituent has a gift they've made in the last week, as well as a modification to the baked-in Urgent CSI code so that it will display the icon if the constituent has an open CSI that isn't urgent.
Since I'm looking at this, I'm just really interested to hear other examples so that we can tackle a comprehensive overhaul if it warrants.
Thank you,
Brian
For all users:
We have a Development Staff Liaison attribute that shows up in the header, if it exists.
The use of the word “wheelchair” in a ticket order puts a wheelchair icon in the header.
We put the account number in a Sits With field based on an active association with an end date after “today.” If there are more than one associations of this type, the word “multiple” is returned instead of one account.
A small Spanish flag displays to the left of the patron ID if there is a language attribute of Spanish.
A “construction warning” image shows up to the left of the constituency string if the patron has an open CSI warning of a certain type (usually for gratuitous chargeback activity or other nonpayment issues).
We have a **Read CSI** notification if an account has an open CSI of the Account Issue category, Account Issue-Read CSI activity type. These are used mostly to identify potential duplicate accounts, and occasionally to indicate bad addresses/phones/e-mails. The idea is that a ticket office rep could then ask the patron calling in to confirm or update account information.
For Development only (and senior management), we have a tally of donations to a particular campaign separated out.
Lucie
Unknown said: For all users: We have a Development Staff Liaison attribute that shows up in the header, if it exists.
Lucie,
So this displays out the name of a Development staff employee who is specifically connected to a patron via attributes; very cool. Right now only our Development and Education team members are in Tess, but I think it'd even be a nice thing to have so that Education members know who to refer constituents to for Development needs.
Thank you for sharing!