Full List of Parsing Terms
February 11, 2020
Terms for Action Type: Create
| Name | This term expects the full name (First and Last) to be found between one set of Bookends. The system will put the first word in the First Name field and the remaining text in the Last Name field. |
| First Name | This term expects only the first name to be found between one set of Bookends. All text between the Bookends will be saved in the First Name field. |
| Last Name | This term expects only the last name to be found between one set of Bookends. All text between the Bookends will be saved in the Last Name field. |
| Company | This term expects only the company name to be found between one set of Bookends. All text between the Bookends will be saved in the Company field. |
| Title | This is the Contact’s Title. |
| Phone | This is the main contact phone number. The system only accepts 10 digit phones for the US and Canada. The system will strip any leading 1 and special characters ( ) – . |
| Home Phone | This is the secondary contact phone number. The system only accepts 10 digit phones for the US and Canada. The system will strip any leading 1 and special characters ( ) – . |
| This term saves the text between the Bookends in the Email field. No effort is made to verify a well formed email. | |
| Comma Separated Address | This term is expecting a full comma separated address to be between one set of Bookends. The system will separate the street address from the city, state and zip and place them in the proper contact fields. Example: 123 My Street, Phoenix Valley, AZ 85284 |
| Address | This term expects only the street address to be between one set of Bookends. All text will be saved in the Address field. |
| City | This term expects only the city to be between one set of Bookends. All text will be saved in the City field. |
| State | This term expects the two letter abbreviation for the State/Province to be between one set of Bookends. All text will be saved in the State field. |
| Full State | This term expects the full State/Province name to be between one set of Bookends. The Full State Name will be saved. All other text values will be saved as found between the Bookends. |
| Zip | This term is looking for the Postal Code/ Zip between one set of Bookends. All text found will be placed in the Zip field. |
| Notes | This term expects Bookends to find a specific area of text to capture as notes. The text will be put in a History Note. If you want to capture the text from a specific starting Bookend to the end of the body of the email, then your End Bookend should be “{END}”. See Garbage Bookends in the Appendix. |
| SMS OK | This term finds a value indicating your rights to text the contact. By default, we set the value to True. Acceptable values include [Y, N, Yes, No, yes, no, True, False, 1, 0]. All other values will be ignored and the setting will default to True. |
| PIN | This term is captured as a separate History Note to make it easy to find. Bookends are required. |
| Big Blob Type 1 | This term will work with following example blob and fetch data by breaking text with space. [0] – Name, [2] Phone, [4] Address, [5] City, State, Zip, [6] Email Bradley Smith678-723-8700 1234 Any Street Mytown, MN 95124 BS@Consulting.com |
| Header Name | This term will find the full name of the contact by looking in the “From” field of the email header. The name will be broken by the first space and stored in the First and Last Name fields. While the Bookends are required, they are not used. See Email Header and Garbage Bookend in the Appendix below. |
| Header Email | This term will find the email for the new contact in header of the email by using the “From Header”. While the Bookends are required, they are not used. See Email Header and Garbage Bookend in the Appendix below |
| Full Body Notes | This term will capture just the body of the email as a History Note. While the Bookends are required, they are not used. See Garbage Bookend in the Appendix below. |
| Custom Field | This term allows you to collect info into Contact Custom Fields. Using the Start Bookend as the Label of the Custom Field and collecting the text value found up to but not including the End Bookend. |
Terms for Action Type: Update
Action Type Update is designed to allow you to receive an email to your auto-generated parser email address and then update the Action Plan and/or Sales Cycle for a specific Contact. ClientTether must have context to know which Contact to update. The terms below tell the ClientTether what information is going to be used to “verify” the Contact record to update. Some of the terms also tell the system where to find the information: Header, Subject or Body.
| Ver Phone Body | This term tells the system that it will be using a phone number to identify which contact to update and that the Bookends for the phone will be found in the body of the email. |
| Ver Email Header To | This term tells the system that it will be using an email to identify which contact to update and that the email will be found in the email header “To:”. In this case the system expects to receive the email by being assigned as a BCC recipient. |
| Ver Client ID | This term tells the system that it will be using a Client ID to identify which contact to update and that the Bookends for the Client ID will be found in the body of the email. |
| Ver External Client ID | This term tells the system that it will be using an External Client ID to identify which contact to update and that the Bookends for the External Client ID will be found in the body of the email. |
| Ver Phone Subject | This term tells the system that it will be using a phone number to identify which contact to update and that the phone will be found in the subject of the email. |
| Ver Email Body | This term tells the system that it will be using an email address to identify which contact to update and that the email address will be found between Bookends in the body of the email. |
| Ver Full Name | This term tells the system that it will be using a Contact’s Full Name to identify which contact to update and that the Full Name will be found between Bookends in the body of the email. |
| Ver First Name | This term tells the system that it will be using a Contact’s First Name as part of the identity for the contact to update and that the First Name will be found between Bookends in the body of the email. Because it is unlikely that the first name alone will identify a unique contact, please include the Last Name term also. |
| Ver Last Name | This term tells the system that it will be using a Contact’s Last Name as part of the identity for the contact to update and that the Last Name will be found between Bookends in the body of the email. Because it is unlikely that the last name alone will identify a unique contact, please include the First Name term also. |
Appendix
Garbage Bookends
Garbage Bookends are place holders that mean little to nothing. For example: If the system is going to capture the full body of the email as a History Note, it already knows what to capture. But the Bookends are still required. So put something in the fields that make sense like: {Start} and {END}.
When Using the term Notes: it often occurs that there is an easy mark for the Start Bookend but nothing to mark for the End Bookend, because you want to capture everything from the starting point to the end of the email. In this case put “{END}” as the End Bookend. This tells the system to capture to the end of the email.
Email Header
You do not normally see the email header. It is information that is used to pass the email through the internet and eventually get to an inbox.