Message Tags

image

What is a Personalized Text Message?

A personalized text message-also known as a tagged message-allows you to define a text message that can combine text that you type with tags that function as placeholders for information stored in the member record in the database or in another data source. Textboom will automatically replace each tag with the particular data value for each member. You can use tags in any text message field.

Note: The tags are only optional. There is no requirement whatsoever to use any tag when creating a text message.

How to construct a message with tags?

The text message that you want to send may be a combination of static text, data that is dynamically taken from the database or specialty values that are generated just before the message is sent. When you write a message, you enter the text that you want and insert tags precisely where you want to use personalized information. To separate tags from the text we use this notation: ||fieldname, parameter||. The items found between each “||” will be replaced by data that Textboom fetches the actual information and formatting it properly. The “||” will NOT be part of the message that is sent.

Notes

  • The double “||” sign is made of two “|” (pipe) characters.

  • Remember that the maximum length of the message to be sent is 160 characters. In checking the length, Textboom will also take into account the length of the tags.

  • Fields value may be empty, so when you design the message please be aware that there is nothing to fill the tag. E.g. if your message include: “Dear ||firstname|| ||lastname|| …” and the first name field is empty the message might show as: “Dear Smith ….”

  • We highly recommend that you use tags with the max length parameter defined, so that you guarantee the final message will be fewer than 160 characters. For example, use ||firstname, 7|| instead of ||firstname|| to ensure that only the first 7 characters of the first name will be included.

  • For some fields, you can also select the format for presenting the data. This is especially important for date fields. For example, use ||created, D1|| to display the date as mm-dd-yyyy (10 characters), or ||created, d3|| to display the date as yy-mm-dd (8 characters, with the year shown first).

    Supported Database Field Tags

    When crafting a message, you can use the data that the system stores in its database about members. The system has predefined fields that you can populate, as well as custom fields that you can define for your specific needs.

    The rule is very simple: the name of the field is also the name of the tag. For example, the field

    City can be used as the tag ||city||, or if you define a custom field Tutor, the tag is ||tutor||.

    Now, since fields hold different type of information at different lengths, and text messages are limited in length, the system allows you to control the format (the presentation of the data) and restrict the length of the data.

    List of predefined fields that you can use as tags

    image

    The (A) fields tags will include a max length optional parameter, max. If, for example, you write

    ||fieldname, max||, this will specify that up to first max characters of “fieldname” in the message. ||firstname,7|| will include the first 7 characters of the member’s first name.

    The (D) field tags will include a date/time format parameter:

    • d1 = mm-dd-yy (Default Format)

    • d2 = dd-mm-yy D2

    • d3 = yy-mm-dd D3

    • d4 = mm-dd (Birthday & DOB Fields)

    • d5 = dd-mm (Birthday & DOB Fields)

    • d6 = Mon dd (e.g. Mar 24, Birthday & DOB Fields)

    • t = HH:SS PM/AM

      Examples:

    • ||fieldname,d1|| – display date field in d1 format

    • ||fieldname,T|| – display time with time zone

    • ||created, D1|| will display 11-01-2010. Let’s look at a complete message example:

“Dear ||firstname,8||, we sent u a message on ||created,d1|| and we didn’t hear back

from you. Plz call us at 800-123-4567 and mention store id ||storeid||”

||firstname,8|| = get the “first name” from db limited to first 8 characters.

||created,d1|| = get the “created” date from db and enter it in d1 format.

||storeid|| = get the “storeid” field for this member

Random Code Tag

||Random, FormatLength|| – You can include a random tag to generate a unique code. The format of the random tag can define if this is a Numeric/Alphanumeric/Alpha type as well as combine lowercase and UPPERCASE characters. The length of the tag defines how many characters will be generated. You can generate a code separated by dash “-“ to create a multi- part code.

Format

N or n = Numeric (Digits only)

A = Alphabetic UPPERCASE (Letters Only) a = Alphabetic Lowercase (Letters Only)

M = Alphanumeric – UPPERCASE (Mixed digits and letters)

m = Alphanumeric lowercase (Mixed digits and letters)

Length

  1. Single digit between 2 to 20: This option will create one continuous code Example: ||random, N6|| will create a random, numeric number with 6 digits

  2. Hyphenated code: This option will create a Multipart code; each part – separated by dash – can have different number of characters

    Examples: 4-4 (9 characters long code); N4-4 can generate 6782-9164 3-3-3 (11 characters long code); M3-3-3 can generate H32-3KS-W9R 3-2-4 (11 characters long code); a3-2-4 can generate ndc-gv-wkma

    Code Generation

    To eliminate confusion on the part of people reading the code on a phone, we do NOT use the following numbers and letter in the random:

    Numbers: 0, 1

    Letters: O, I, o, l (lowercase L) Examples:

    • Congrats ||firstname,7|| ||lastname,10|| you joined us on ||created||. Plz go to www.HelpHunger.com and enter code ||random,M3-3-3|| To finalize ur application.

    • Congrats ||firstname,8|| for joining our Mobile VIP Club. Plz call 800-123-4567 and enter code ||random,N6|| To finalize ur application.

      Now (Date) Tag

      ||Now[+/-n H/D/W/M/Y], [Timezone], [Format]|| – You can include a date tag that will generate a date based on date/time now. A date will be automatically generated by the system, based on Now (the current date & time). You can include a +/- delta (hours, days, weeks, months, years) from Now() and decide if the date should consider the recipient time zone (if available) or a specified time zone.

      The format of the Now tag defines the appearance of the date in the message and it takes the same formats like any other Date field that is stored in the database.

      Let’s use an example: You have a campaign that responds to the keyword PROMO and you want the member to receive a special promo with a time limit of 3 days after they received the promo message. Since you don’t know when members will text PROMO, you need a dynamic way to generate the date, here is how: include the tag ||Now+3D, PST, D1||. So, if the member sent PROMO on 09-10-2011, then the system will generate the promo response message with the date 09-13-2011

      Now Tag Parameters

      Now +/- Delta options:

      1. aH = No. of hours to add/subtract from. Example: +6H, -12H

      2. bD = No. of days to add/subtract from. Example: +7D, -5D

      3. cW = No. of weeks to add/subtract from. Example: +1W, -2W

      4. dM = No. of months to add/subtract from. Example: +3M, -3M

      5. eY = No. of years to add/subtract from. Example: +7Y, -1Y

      Time Zone Options:

      1. PST, PDT

      2. MST, MDT

      3. CST, CDT

      4. EST, EDT

      5) GMT+/-1-23 (e.g. GMT+2)

      Presentation Format options:

      1. d1 = mm-dd-yy (Default Format)

      2. D1 = mm-dd-yyyy

      3. d2 = dd-mm-yy

      4. D2 = dd-mm-yyyy

      5. d3 = yy-mm-dd

      6. D3 = yyyy-mm-dd

      7. t = HH:SS PM/AM

      8. T = HH:SS PM/AM (EST/CST…)

      Examples:

    • Congrats ||firstname,7|| ||lastname,10|| you are the winner of our big prize. Plz arrive to our store on 123 main street until ||NOW+1W, CST, D1|| to claim ur prize.

    • Congrats ||firstname,8|| for joining our Mobile VIP Club. Ms. Smith will call you on

      ||now+1W, EST|| to introduce you to the specials of the VIP club. Plz call 800-123-4567 if you need to reschedule.

      Notes:

      1. In the second example, the tag is using the default date format (d1), so it doesn’t need to be included.

      2. The simplest way to use this tag is: ||now|| – This will show today’s date, based on EST time zone, with the format mm-dd-yy

        Text 2 Win Counter Tag

        ||T2WCOUNTER, [X][n]|| – This is a specialty tag for Text 2 Win campaign where many members text a keyword and the system keeps count of how many texted in. Each message that was received is assigned a number based on the order in which it was received (like in a queue) and this number can be used as a tag in the response message.

        The optional parameter X of this tag allows you to select if the system should present the actual counter number or the remainder of diving the counter by X. This way the number the system will generate for this code will always be between 1 and X-1.

        The optional parameter n, can be replaced by any number between 1 and 9 to set how many digit will be used to show the counter value. E.g. ||t2wcounter,3|| will show 001.

        Here’s an example: You have a T2W-X where every 50th member wins. Since 49 out of each 50 are not winning, you want to let them know their number out of 50, so that they feel it was a fair game. So, you can include the T2WCOUNTER tag in your Non-Winner response message,

        ||T2WCOUNTER, X2||. In this example, the tag will return the numbers 01 to 49.

        Other examples:

    • “Sorry, you didn’t win. You were number ||t2wcounter,x|| out of 50.”

    • “Your message arrived in number ||t2wcounter,3|| today and only every 50 wins. You can try your luck again tomorrow after 6PM.”

      Preview Window

      With tags, it is a little more complex to compose a text message without making mistakes. The preview window should assist you to ensure that the outcome represent the indented message.

      Textboom holds a “Preview Member” that has all member fields populated. This “Preview Member” is used to show you what a real message would look like when the tags are replaced with actual data stored in the database.

      “Preview Member” Fields: Cellphone: 19999999999 Carrier: AT&T Wireless Firstname: Jane Lastname: Richards

      Email: jrichards@mail.com DOB: 11-02-1980

      City: Mobile State: Alabama

      Zip: 36617 Country: United States Optinsource: www.website.com Created: 12-15-2009

      So, when the user enters tags, they will be showing the respective values of the “Preview Member” record fields from above:

      Example:

      image

      Here’s a closer Look:

      image

      image