Include MANY more patron fields as Merge Tags
Looking through the available merge tags, I see very few fields from the patron record represented: First name, last name and patron barcode. When I attended webinars on LX Starter many months ago, I could swear the audience was told that all fields exposed to the print templates interface would likewise be available in LX Starter.
Having read the Idea Exchange post https://ideas.iii.com/forums/951985-lx-starter/suggestions/46813306-take-a-good-hard-look-at-patrons-data-privacy-in, it is clear that many of these patron record fields are being passed through to LX Starter, so please make them available for merging and/or to drive conditional logic (which is a whole 'nother suggestion).
Emma Olmstead-Rumsey commented
This would be very valuable for addressing patrons correctly. I'm sure the customers that use titles would like the ability to include them. We use a UDF in our library for parent/guardian name on children's accounts, and it would be nice to address the notice to the parent/guardian when something was present in that field and the notice is going to the parent's email address, not the child's.
We'd also like the ability to include preferred name in notices instead of legal name (we use a clunky swapped setup in our instance of Polaris to keep the legal name fields mandatory, so the "name" fields that are merge tags are legal names for us, not preferred names).