Basics

• This Process step can send a text to exactly one mobile phone number. The mobile phone number must be designated on a Contact record. For example, you can text a Contact to confirm they've filled out a form or registered for an event. That text will be sent to the mobile number on their Contact Record, not the mobile number provided as a form response (if different).
• If a Specific User is set on the Process, that User will be indicated as the sender. If not, the message will be sent from the Process Owner. But in either case, the Message is actually sent from the Outbound SMS Number which is configured as Default = Yes on the Outbound SMS Numbers record.
• If an image is attached to your text message template, it will be included with the text message.

Configuration

1. Create your text message Template.
   • You'll need to designate a From Contact on your Template, but the text message will be sent from either: 1) the Specific User identified on the Process; or 2) the Process Owner.
   • The Process will send your text message, even if Template Active is set to False.
2. Administration > Processes
3. Select your Process or configure a new one
4. On the Steps tab, select "+" to add a new Process Step
5. Complete the relevant fields
   • Step Name: Name of the step you're creating
   • Step Type: 6. Send a Text
   • Escalation Only: This step is skipped and invoked only by another step that has exceeded the task deadline. 
   • Order: The order of this step in the Process.
   • Process: The process that will use this step.
   • Specific User: If populated, the User who will be credited with sending the text message. 
   • Text Template: The record from the Templates page that will become the content of the text in the "Send a Text" step. Valid merge fields must be present on the "All Records" view of the page to which this Process is associated.
   • To a Specific Contact: If the text should always be sent to the same Contact, add them here.
   • Text to Contact Field: If the Contact is to be looked up dynamically, use the Related Table Field Name Lookup convention to find the Contact_ID record. Generally the value in this field will end in "Contact_ID." The table and field lookup convention used by Advanced Search is relevant here. If this field is utilized, you must ensure that the Contact record this field is mapped to always has a valid mobile phone.
6. Save

Merge Fields

If you plan to use merge fields in the text message, keep in mind that only some merge fields are allowed. Note: Any Data Fields you include in your template must be within brackets and must have the same format as the Data Field (including any underscores).

• Data Merge Fields: The field list for the Table Name associated with the Process are available as Data Fields. You can identify these as the column headers on the All Records view of the page set in the Table Name of the Process. These are also the Data Fields you see in the New Message tool for pages configured to use this tool.
  • For Processes, Data Merge Fields take precedent over Contact Merge Fields (below).
  • You can add merge fields by editing the page record.
• Contact Merge Fields: The recipient of the text message is the Contact for any Contact Fields. These correspond to the Contact Fields in the New Message Tool.