CRM Software for Economic Development Organizations
+1 (805) 967-1280 | email: sales@outreachsystems.com

What are the substitution variables I can use in emails generated from Neoserra?

Neoserra supports substitution variables in its email templates. Below are some of the substition variables that can be used in emails generated from the Neoserra email interface. The variables must be entered exactly as shown below, including the opening and closing brackets. The variables are case sensitive, and please use the underscore character as shown, not the dash.

Thus, if you insert a bogus substitution variable that is not recognized by Neoserra then it will simply read this as text and present it exactly as entered in the template. Thus, if you intended to use the [CONTACT_NAME_FML] variable but you type it as [CONTACT_FULLNAME] then you will literally see "[CONTACT_FULLNAME]" in the email message. Similarly, if you use a valid substitution variable out of context, this will also cause the variable to be unresolved. For example, if you include a Training Event variable within a Client email template, Neoserra will not be able to resolve it.

Lastly, keep in mind, that if you use a variable for data that has not been entered in the database, then there will be a "blank space" where the data should have beend. In other words, if you select the substitution variable: [CONTACT_FAX] but the contact record in Neoserra does not include a fax number, then the email recipient will see a blank space in the email.

Variable Name What information is inserted
[CENTER_ADDRESS_MULTILINE] Center mailing address (multiline)
[CENTER_ADDRESS_ONELINE] Center mailing address (single line)
[CENTER_EMAIL] Because this variable is often used as the sending email address in the email templates, there is a special bit of logic associated with the [CENTER_EMAIL] substitution variable. Neoserra will first look to see if an eCenter POC Email address has been entered on the center record. If an address has been entered in this field, and the [CENTER_EMAIL] substitution variable is used, then this email address will be used. In the absence of a valid email address in the eCenter POC Email address field, then Neoserra will look for an email address at the top of the center record. If both of these email address fields are blank, then Neoserra will insert the default contact's email address in the [CENTER_EMAIL] substitution variable.
[CENTER_NAME] Center name
[CENTER_PHONE] Center phone number
[CENTER_POCFIRST] The "eCenter Contact First Name" will be used unless this field is blank in which case the center's default contact's first name will be inserted
[CENTER_POCLAST] The "eCenter Contact Last Name" will be used unless this field is blank in which case the center's default contact's last name will be inserted
[CENTER_POC_FML] The eCenter First MI, Last Name will be used unless this field is blank in which case the center's default contact's name will be inserted
[CENTER_POC_LFM] The eCenter Last, First MI Name will be used unless this field is blank in which case the center's default contact's name will be inserted
[CENTER_URL] Center Web site URL
[CENTER_FB_URL] Center Facebook URL
[CENTER_LI_URL] Center LinkedIn URL
[CENTER_O_URL] Center Other Social Media URL
[CENTER_TW_URL] Center Twitter URL
[CONTACT_SALUTATION] Contact salutation
[CONTACT_FIRST] Contact first name
[CONTACT_LAST] Contact last name
[CONTACT_NAME_FML] Contact name (First MI. Last)
[CONTACT_NAME_LFM] Contact name (Last, First MI.)
[CONTACT_EMAIL] Contact's e-mail address(es)
[UNSUBSCRIBE_LINK] A special Opt-out substitution variable, as described in this FAQ
[CONTACT_PASSWORD] Contact's eCenter password
[CONTACT_MOBILEPH] Contact cell phone number
[CONTACT_WORKPHONE] Contact work phone number
[CONTACT_HOMEPHONE] Contact home phone number
[CONTACT_FAX] Contact fax number
[CONTACT_ADDRESS] Contact street address
[CONTACT_ADDRESS_MULTILINE] Contact mailing address (multiline)
[CONTACT_ADDRESS_ONELINE] Contact mailing address (single line)
[CONTACT_CITY] Contact city
[CONTACT_STATE] Contact state
[CONTACT_ZIPCODE] Contact Zip code
[CONTACT_HOUSE_REPRESENTATIVE] Contact's United States House of Representatives information
[CONTACT_STATE_REPRESENTATIVE] Contact's State Representative information
[CONTACT_STATE_SENATOR] Contact's State Senator information
[COMPANY_HOUSE_REPRESENTATIVE] Client's United States House of Representatives information
[COMPANY_STATE_REPRESENTATIVE] Client's State Representative information
[COMPANY_STATE_SENATOR] Client's State Senator information
[PT_EMPS] Client's Part-time Employees
[FT_EMPS] Client's Full-time Employees
[EMPS_EXPORT] Client's Export-related Employees
[GROSS_SALES] Client's Gross Annual /Revenue Amount
[GROSS_SALES_DATE] Client's Gross Annual Revenues Date
[GROSS_SALES_EXPORT] Client's Gross Exported-Related Revenue Amount
[GROSS_PROFITS] Clients Profits/Losses Amount
[GROSS_PROFITS_DATE] Client's Profits/Losses Date
[COUNSELOR_EMAIL] Counselor e-mail address
Similar to the [CENTER_EMAIL] substitution variable, there is a special bit of logic associated with the [COUNSELOR_EMAIL] substitution variable. If the [COUNSELOR_EMAIL] substitution variable is used within an email template and there is no counselor assigned to the client, then Neoserra will use the user's associated counselor record (if available). In other words, if Neoserra user "Jane" is initiating an email to a client using an email template that invokes the [COUNSELOR_EMAIL] substitution variable, but the client does not have a counselor assigned, then the counselor record associated with Jane's user account will be used. If this field is also blank then the message will fail when the variable is used in the FROM field of the message.
[COUNSELOR_FIRST] Counselor first name
[COUNSELOR_LAST] Counselor last name
[COUNSELOR_NAME_FML] Counselor name (First MI. Last)
[COUNSELOR_NAME_LFM] Counselor name (Last, First MI)
[COUNSELOR_PHONE] Counselor phone number
[DATETIME_NOW] Current date/time
[DATE_NOW] Current date
[ECENTER_URL] eCenter link
[SIGNUP_ECENTER_URL_AUTOLOGIN] An auto-login URL for the eCenter online registration page of the contact
who has not yet completed the entire registration form.
[CONFERENCE_ECENTER_URL_AUTOLOGIN] An auto-login URL for the eCenter page of the event for the contact
This substitution variable is only functional on the conference event email templates.
[HOME_ECENTER_URL_AUTOLOGIN] An auto-login URL for the eCenter home page of the contact
This substitution variable is only functional on the contact email templates.
[CONFERENCE_INSTRUCTIONS] Public Instructions from the Training Event record.
[CONFERENCE_REGISTRANT_INSTRUCTIONS] Attendee Instructions field on the Training Event record. This field can also embed substitution variables that are expanded within the email message template. Since the "Attendee Instruction" field is never displayed on eCenter Direct, and this field is really only accessible to the users via the event registration confirmation email, you can embed a substition variable like this:

https://www.example.com/course/?ref=[CONTACT_EMAIL]

Which would be expanded to:

https://www.example.com/course/?ref=jandoe@companyx.com

This feature provides added flexibility with event registrations (assuming the email address in Neoserra corresponds to the email address in the event registration tool.)

[AGREEMENT_URL] Link to eCenter agreement page
[REQUEST_PRODUCT] eCenter requester products/services
[REQUEST_PSCS] eCenter requester PSC codes
[REQUEST_NAICS] eCenter requester NAICS codes
[REQUEST_SICS] eCenter requester SIC codes
[REQUEST_STATUS] eCenter requester business stage
[REQUEST_BUSTYPE] eCenter requester business type
[REQUEST_GENDER] eCenter requester's gender
[REQUEST_ETHNIC] eCenter requester's ethnic/race background
[REQUEST_EXPORT_COUNTRIES] eCenter requester export counties in ISO code format
[REQUEST_PRODUCT] eCenter requester products/services
[REQUEST_PSCS] eCenter requester PSC codes
[REQUEST_NAICS] eCenter requester NAICS codes
[REQUEST_SICS] eCenter requester SIC codes
[REQUEST_STATUS] eCenter requester business stage
[REQUEST_BUSTYPE] eCenter requester business type
[REQUEST_GENDER] eCenter requester's gender
[REQUEST_ETHNIC] eCenter requester's ethnic/race background
[REQUEST_EXPORT_COUNTRIES] eCenter requester export counties in ISO code format


Want more? Browse our extensive list of Neoserra FAQs.