SUBJECT:
“Thank You for Inquiring about [UNIT_TYPE_#]”
// About should be capitalized. We end up replacing the whole subject line to identify it as “Cub Scouts Pack 123”, because many people that are new don’t understand what “Pack 123” is without context.
BODY:
"Dear [LEAD_FIRST_LAST],
// We can deal, but in our area, “Dear” is too formal.
Thank you for inquiring about [UNIT_TYPE_#]. The question/comment you submitted is: “[LEAD_QUESTION/COMMENT]”. I will try to supply the requested information below. Please let me know if you have any further concerns, so we can assist in welcoming you to [UNIT_TYPE_#].
// Sounds robotic, doesn’t allow you to actually put in any useful info. The whole thing gets replaced with standard info.
Sincerely,
[USER_FIRST_MIDDLE_LAST]
// Who uses their full middle name in a signature block?
Where:
[UNIT_TYPE_#] = e.g., Pack/Troop/Crew/Ship 123. This is reasonable, except that our pack does not use the first digit of the official number, i.e., we have been Pack 167 for almost 40 years, but we’re in the system officially as 3167 because somewhere along the line, our council decided to add a number at the beginning of certain units for some administrative reason, even though the units don’t actually use the first digit in practice.
[LEAD_FIRST_LAST] = whatever the user put in the BeAScout.org “Request More Information” form or the Invitation Manager user puts in the “New Lead” form. This seems useful.
[LEAD_QUESTION/COMMENT] = whatever the user put in the “Questions or Comments:” field on the BeAScout.org “Request More Information” form or “no comment”. Which is useless if they don’t put a specific comment or if the lead was collected from a sign in sheet.
[USER_FIRST_MIDDLE_LAST] = the Invitation Manager user’s full legal name, which is awkward because it includes my middle name and the legal version of my first instead of Dave.
