Skip to main content

Text Templates

Create and edit text message templates with dynamic fields and Liquid alias codes for consistent customer texts.

In this article:

Create or Edit Text Message Template

Dynamic Fields for Texts

Add Dynamic Fields to a Text Template

Liquid Alias Codes for Texts

Create or Edit Text Templates

  1. Navigate to:

    mceclip0.png

    Setup > Templates > Text Message Templates

  2. Select New Text Message Template or Edit next to an existing one

  3. Edit the Name, Subject, Recipient, & Body of the text by entering the desired text.
    *Note: HTML5 and Javascript will not work in text templates. The preview on the right will show this code correctly because it's being viewed in the browser but will not translate to SMS and text message.

  4. Preview any changes made to your text message template by selecting a visit from the dropdown to the right of the edit form. To refresh a rendered text message, select the Refresh button at the top-right of the rendered text message to show your most recent edits.

  5. Once all desired updates are made, select Update or Create Text Message Template.

Dynamic Fields for Texts

What are Dynamic Fields?

Dynamic fields allow you to display specific job information such as client name or visit time to personalize your text messages with Liquid Aliases.

For example, if you wanted the text template to read "Hello Leslie," for your client Leslie, you would include:
​Hello :object.client.first_name:

Add Dynamic Fields to a Text Template

  1. Navigate to:

    mceclip0.png

    Setup > Templates > Text Message Templates

  2. Select Edit next to an existing Text Template

  3. Paste a Liquid Alias code from this Liquid Aliases list into the body of the text message where you would like the Dynamic Field to be placed.

    mceclip0.png

  4. Preview this text template by selecting the drop down at the top right and choosing a job/visit

  5. When finished, click Update Text Message
    ​    *Note: The list of Liquid Aliases in SingleOps is constantly growing. Use the tables below to find commonly used dynamic fields. You can copy the Liquid Alias right into your SingleOps Email Template.

Liquid Alias Codes for Texts

Client/Contact Name & Email

Liquid Alias

Description

:visit_all_emails:

Contact's and Client's Email

:visit_primary_emails:

Contact's or Client's Email

:visit_all_names:

Contact's and Client's Name

:visit_primary_names:

Contact's or Client's Name

{{ visit.client.first_name }}

Client's First Name (Only)

Current User Data

Liquid Alias

Description

:current_user_name:

Current User's Full Name

:current_user_first_name:

Current User's First Name

:current_user_email:

Current User's Email

:current_user_office:

Current User's Office Phone Number

:current_user_mobile:

Current User's Mobile Phone Number

:current_user_custom_field_displays_title:
​*Name of custom input in this example is "Title"*

User-Level Custom Input

Emails

Liquid Alias

Description

:all_emails:

Email addresses for all contacts and client associated with the object

:primary_emails:

Email addresses for all contacts associated with the object (client email if no contacts)

:client_email:

Email address associated with visit/job/invoice (usually client) or client email address

Invoice Data

Liquid Alias

Description

:invoice_balance:

Remaining Invoice Balance

${{ invoice.balance | money }}

Invoice Balance - full balance

${{invoice.balance | times: 0.25 | money}}

Invoice Balance - partial
Balance present percentage as decimal

:invoice_total:

Invoice Total with Tax included

Links

Liquid Alias

Description

:visit_online_proposal_link:

Customer can view, accept, and make deposit payments for proposal

:visit_proposal_pdf_url:

Customer can view proposal in pdf form

:visit_work_order_pdf_url:

Customer can view work order in pdf form

:visit_online_invoice_link:

Customer can view and pay invoice

:visit_invoice_pdf_url:

Customer can view invoice

:payment_methods_url:

Customer can edit/update their payment methods

Location

Liquid Alias

Description

:job_location_street_address:

Job Location's Street and Number

:job_location_city:

Job Location's City

:job_location_state:

Job Location's State

:job_location_zip:

Job Location's Zip Code

Names

Liquid Alias

Description

:all_names:

Names for all contacts and client associated with the object

:primary_names:

Names for all contacts associated with the object (client email if no contacts)

:client_name:

Client name

Notes

Liquid Alias

Description

:visit_client_notes:

Client notes attached on a visit level

:job_client_notes:

Client notes attached on a job level

:visit_crew_notes:

Crew notes attached on a visit level

:job_crew_notes:

Crew notes attached on a job level

:visit_internal_notes:

Internal notes attached on a visit level

:job_internal_notes:

Internal notes attached on a job level

Phone Numbers

Liquid Alias

Description

:client_mobile:

Clients mobile number

:account_doc_phone:

Phone number associated with account

Reference

Liquid Alias

Description

:job_reference_number:

Job reference number

:visit_reference_number:

Visit reference number

:reference_number:

Reference number

:job_name:

Job name

:visit_name:

Visit name

:account_inc_name:

Account inc name

:visit_job_custom_field_displays_pets:
​*Name of custom input in this example is "Pets"*

Job-Level Custom Input

Sales Rep Data

Liquid Alias

Description

:sales_rep_name:

Assigned Sales Rep's Full Name

:sales_rep_first_name:

Assigned Sales Rep's First Name

:sales_rep_email:

Assigned Sales Rep's Email

:sales_rep_office:

Assigned Sales Rep's Office Phone Number

:sales_rep_mobile:

Assigned Sales Rep's Mobile Phone Number

Task

Liquid Alias

Description

:task_start:

If referencing a specific task object, this will render the task start date and time, if referencing a job with tasks, it will render the first onsite tasks start date and time

:task_start_date:

If referencing a specific task object, this will render the task start date, if referencing a job with tasks, it will render the first onsite tasks start date

:task_start_time:

If referencing a specific task object, this will render the task start time, if referencing a job with tasks, it will render the first onsite tasks start time

Visit Information

Liquid Alias

Description

:visit_start_date:

Short Visit Date- (MM/DD/YYYY)

{{ visit.start | date: "%A, %B %e, %Y" }}

Long Visit Date- Day, Month DD, YYYY

:visit_start_time:

Visit Start Time (12 hour)- 3:00PM

{{ visit.stop | date: '%I:%M %P' }}

Visit End Time (12 hour)- 3:00PM

{{visit.location.address }}, {{ visit.location.city }}

Visit Location- street address, city

Related Articles
Did this answer your question?