Email & Texting

Email Replacement Codes

Caution

Please note a few points before you begin using these codes

  1. They are case-sensitive. Unless otherwise indicated, they are all lower-case.

  2. They are for specific uses, so pay attention to the main headers below, as those indicate where/how you can use them. For example: You cannot insert {paylink} in a regular email to an individual and have it function correctly. It works only from an Involvement or in an online registration confirmation email.

  3. They should never be made bold or italics or underlined as that will insert HTML characters that will affect the replacement code. Basically, do not add any type of formatting to an email replacement code.

Note

You can copy a specific paylink (right-click, copy) from the individual’s Member Dialog for an Involvement and email a paylink that way.

All Emails

These replacements can be used in any email sent via TouchPoint. There are category headings within this section to make it easier to find the codes.

Personal Information

The following can be inserted into an email to verify someone’s personal information, or can be used in confirmations, such as Donation Confirmation emails.

{title}

The recipient’s title

{name}

First and Last Name of recipient

{first}

First Name of recipient or preferred name if there is one

{last}

Last Name of recipient

{address}

Line 1 of Street Address

{address2}

Line 2 of Street Address

{city}

Primary City

{state}

Primary State

{csz}

City, State Zip as a single replacement

{homephone}

Home Phone

{occupation}

Occupation

{cellphone}

Displays the cellphone number on a persons’ record. Helpful if you are asking people to opt-in for texting.

{receivesms}

Recipient’s current setting for receiving text messages - either Yes or No.

See also

Texting: Opt-In

{peopleid}

Displays the person’s PeopleId Number.

{birthdate}

Displays the person’s full date of birth - month, day, year.

{firstorjoint}

How this works is dependent on the Contribution Type of the individuals. It will use the person’s first name if the person has a Contribution Type of Individual. It will use the two Primary Adults’ first names (John & Mary) if the couple each has a Contribution Type of Joint.

If both spouses are included in the recipient list, they will each get the email addressed to both of them (John & Mary) if they give jointly. You can filter out one spouse by adding the Condition “Is Head of Household” = true, then the husband will receive the email addressed to both of them.

If you add that Condition and you have couples that give individually the email will go only to the HOH and will be addressed only to him/her.

Just think how you want to use this and create your searches accordingly.

{altname}

Alt Name of recipient

See also

Alt Name

Contribution Statement Options

These replacements can be used in an email to individuals and are a good way to make sure you have a recipient’s correct preferences regarding his contribution statements.

{estatement}

If Electronic Statement is not checked on their record, this will display: Printed Statement in Addition to Online Option. If it is checked, this will display: Online Electronic Statement Only.

{statementtype}

Displays Individual, Joint, or None, based on the selection on their record.

Extra Values

You can use the following to display extra values on an individual’s record. You must know the type (code, text, date, int, bit) to display the information in the correct format.

{extracode:field}

Extra value with Code type

{extratext:field}

Extra value with Text type

{extradate:field}

Extra value with Date type

{extraint:field}

Extra value with Integer type

{extrabit:field}

Extra value with a bit type (checkboxes)

{familyextracode:field}

Family extra value with Code type

{familyextratext:field}

Family extra value with Text type

{familyextradate:field}

Family extra value with Date type

{familyextraint:field}

Family extra value with Integer type

{familyextrabit:field}

Family extra value with a bit type (checkboxes)

Each returns the ExtraValue named in the field.

Replacements for Members of a Division

The following {orgmember:...} replacements take a required divid parameter, where you enter a Division ID# where you see divid. The value returned in the email will be the specified value from the first Involvement in the specified division (divid) in which the person is a member.

{orgmember:location,divid}

Involvement Location—from the Location in the Involvement Settings > General tab

{orgmember:pendingloc,divid}

Involvement Pending Location—from the Pending Location in the Involvement Settings > General tab

{orgmember:orgname,divid}

Involvement Name

{orgmember:leader,divid}

Involvement Leader—the name of the first person enrolled in the Involvement having the Member Type matching the Leader Type specified for the Involvement

Example

Using the IsMemberOf condition, run a search in Search Builder for everyone in the Program Vacation Bible School and Division First Grade VBS

Notice the DivisionId # in the condition. It will be the 2nd number inside the parentheses IsMember (125,6305,0) = True. That is the number you use instead of divid in the replacement codes above.

Drop Membership from an Involvement

Drop From Involvement

This is not in the normal form of an email replacement code, but it does function like one and can be used when emailing to an individual, a tag, Search Builder results or an Involvement. When the text below is inserted into any email, the link allows the recipient to drop himself from the Involvement indicated by the ID# in the code. Enter the actual Involvement ID# in place of the 242 you see below. 242 is the sample Involvement ID#. The recipient sees only the text that you see on line 2 below. You can edit it to say whatever you want. The code itself will not display the name of the Involvement, so you will either want to put that in the statement in place of ‘this Involvement’ or put another statement in the email so they understand which Involvement they will be dropped from.

<dropfromorg id="242">
Click here to be removed from this Involvement.
</dropfromorg>

Important

You cannot use another email replacement code inside the dropfromorg code. For example: Do NOT insert {org} in the statement ‘Click here to be removed from this Involvement’. You cannot put any other replacement code in that text.

Involvement Context - Confirmations, Reminders, Normal Email

These below all work when use in a Confirmation, a Reminder, or a regular email sent directly from an Involvement.

{orgname}

Name of Involvement

{orgmembercount}

Number of members in the Involvement

{smallgroups}, {smallgroups:[prefix]}

This will display a list of all sub-groups that the person is assigned to. If you supply the optional :prefix designation, it will only list those groups that start with that prefix.

{smallgroup:[prefix]}, {smallgroup:[prefix],default}

It will display the sub-group name person is assigned to which starts with the prefix. If you use supply the default text, that is what will display if they are not assigned to any sub-group fitting that pattern.

Example

This would be good for something like a sub-group to specify table number. For example you could have people assigned to tables with sub-groups that look like: table:1, table:2 etc. This way your email replacement code would be {smallgroup:[table:],you are not assigned a table}

{addsmallgroup:name}

This adds the recipient to the sub-group in the Involvement inserted in place of name in the replacement code.

Tip

This is useful when emailing registrants over the period during which they are registering for an event. You may want to send them extra information after you have placed them at a table, or have approved their application or any other post registration process you may be doing.

This way, you can track which persons you have been sent the email and only email those new registrants who are not already in the specified group.

{tickets}

Indicates the number of tickets purchased if you have that question in your registration.

See also

Questions Settings Tab

{barcode}

Inserts barcode representing the registrant’s PeopleId #.

See also

Record by Family Attendance

{location}

Room number (Location) that is on the Involvement’s Settings > General tab

{nextmeetingtime}

The next future meeting the recipient is committed to attend.

{nextmeetingtime0}

The next future meeting that exists in an Involvement will display “none” if there is not a future meeting.

{paylink}

Displays this text: Click this link to make a payment on your balance of $150.00

See also

Fee Settings Tab

Important

If you are manually sending an email that includes the {paylink} replacement code, you must use the Individuals or Child with Parents CC’d email options in order for it to generate properly. It will not work with the Parents email option since they are not the ones enrolled in the Involvement.

Note

When you use the Individuals or Child with Parents CC’d options, the email will also be sent to the Register Email, if one exists. An Involvement member will have a Register Email if an email address was entered at the start of a registration and it differs from the email address stored on the registrant’s record.

{amount}

Total amount of the fee

{amtpaid}

Total amount already paid

{amtdue}

Total amount due

{orgextra:field}

Returns the Involvement ExtraValue named field

Confirmation Emails

These only work in a confirmation email.

{details}

Registration details such as checkboxes selected, answers to questions, etc

{donation}

The amount of extra donation, when Ask Donation is used with a regular online registration.

{paid}

Total paid for this registration

See also

Messages Settings Tab

Note

You can also use {details} in Reminder Emails for Volunteer Calendars, but not if the registration options changes. See Organization Context above.

See also

Messages Settings - Reminder Email

New User Email

{username}

Username

{password}

Password

Recurring Gift Notice

We also have a template for the Recurring Gift Notice on your database. This may be customized by navigating to Administration > Setup > Special Content > Email Templates and filtering for the SystemEmailTemplates role. You can edit this if you want, using the following replacement codes.

{giftsummary}

For all recurring gift schedules: fund name and amount.

You may also use many of the email replacement codes mentioned above, such as {first}, {amt}, {date}, {church}, {tranid}, {name}, {email}, {homephone}, and {cellphone}.

Pledge Replacements

These replacements can be put in an email to anyone in your database to indicate the amount of a pledge to a specific fund and the balance left before they meet their pledge. If the person does not have a pledge, the pledge amount will show as 0.00. If they have given toward that fund, but not made a pledge the balance amount will show 0.00. If they have given more than their pledge, the balance amount will be the overage amount preceded by a minus (“-“). Because you may have multiple pledge funds, you indicate the fund ID in the replacement code.

Caution

You can use these 2 pledge replacement codes for only one pledge fund in each email. So, if you want to update your members and you have 2 pledge funds, send out one email for each fund.

{pledgeamt:100}

Where 100 is the fund id. Shows amount of pledge made for that fund.

{pledgebal:100}

Where 100 is the fund id. Shows balance due based on pledge for that fund.

DiffEmailMessage or NoEmailMessage

{contactphone}

Number on the online registration Involvement - Setting > General

CreateAccount

Only a System Administrator can use this email replacement code. It can be sent to people who are in the database, but who do not have user accounts.

{createaccount}

This link will create a user account and send the person an email with their username and link to create their password.

See also

My Data Accounts

Ticketing

These will only work in conjuction with TouchPoint Ticketing.

See also

Ticketing in TouchPoint

Ticketing confirmation email:

{mytickets:1234,Please follow this link to view all your e-tickets.}

Replace 1234 with the Involvement ID of the Ticketing Involvement. You can also replace the wording after the comma, which will render as the link in the email. This link will take the registrant to a My Tickets page.

{canceltickets}

Provides a link for the registrant to cancel their tickets from the confirmation email. This is a one-time link and will cancel ALL of the users’ tickets within the order. (Not for use in reminder email.)

Note

We recommend you use {mytickets} replacement code in the confirmation email rather than using {canceltickets}. The {canceltickets} will only allow the attendee to cancel ALL tickets, where {mytickets} allows them to choose single tickets for release.


{canceltickets:CLICK HERE}

Replace CLICK HERE with any text you choose to customize the Cancel Tickets text. This is a one-time link and will cancel ALL of the users’ tickets within the order. (Not for use in reminder email.)

{eventday}

Provides the day of the week of the event in the confirmation email.

{ordernumber}

Provides the order number which also appears in the Ticket Sales report.

Ticketing text:

{mytickets:1234}

Replace 1234 with the Involvement ID of the Ticketing Involvement



Latest Update

10/25/2023

Added Ticketing replacement codes