The TextUs integration for Salesforce provides default records that contain metadata. Salesforce administrators can use these records to create objects that map to a custom application on the Salesforce platform that uses custom metadata types and metadata records, instead of hard-coded data objects or settings.
This guide provides you with definitions of the default records and metadata included in your TextUs integration in Salesforce, as well as a basic overview of how the records can be implemented for a customized integration. However, none of the records in this guide are required to change or update your integration. For more information on how to create and manage custom metadata types, see the Salesforce knowledge base.
Important Note: TextUs does not currently provide technical support for any additional custom metadata types beyond the default groups listed in this guide. For additional questions or support requests related to using and creating custom metadata types, contact your Salesforce administrator.
Mapping custom metadata in your TextUs integration
To access the default custom metadata types included in your TextUs integration in Salesforce, complete the following steps:
On the Setup page, enter Custom Metadata Types in the Quick Find search box.
On the All Custom Metadata Types page, the four custom metadata types listed in the table below are included in your TextUs integration:
Custom Metadata Type Record | Description |
TextUs Contact Mapping Index Field | Stores information for phone numbers that can be mapped to a TextUs contact. |
TextUs Contact Junction Mapping Settings | Stores information for a case or opportunity that can be mapped to a TextUs contact. |
TextUs Contact Lookup Mapping Settings | Defines how case fields in Salesforce can be mapped to contact fields in TextUs. |
TextUs Contact Object Mapping Setting | Stores information for a contact or lead that can be mapped to a TextUs contact. |
TextUs Contact Mapping Index Field
The TextUs Contact Mapping Index Field records allow you to map records between a contact’s phone number in Salesforce and your TextUs integration. By default, the TextUs integration record provides the following field mappings:
Assistant Phone: The contact’s assistant.
Home Phone: The contact’s home phone number.
Mobile Phone: The contact’s mobile phone number.
Other Phone: An additional phone number for the contact.
Phone: The contact’s primary phone number.
You can deactivate an existing mapping by clicking Manage Records, then clicking the Active checkbox listed under the field details.
TextUs Contact Junction Mapping Settings
TextUs Contact Junction Mapping Settings use a many-to-many relationship that allows you to link a record from one object to multiple records of another object (and vice versa).
You can configure the mappings by providing the Junction Object API names and the names of the fields that define the many-to-many relationship. By default, the TextUs integration record provides the following fields which enable you to send outbound texts from Case and Opportunity records:
Case: A customer issue or problem.
Opportunity: A sale or pending deal.
You can deactivate an existing mapping by clicking Manage Records, then clicking the Active checkbox listed under the field details.
If you need to send a text from any other standard or custom object, create a new mapping record where Label must contain the mapped object API name.
TextUs Contact Lookup Mapping Settings
The TextUs Contact Lookup Mapping Settings allow you to establish a lookup relationship between specific fields in Salesforce and contact fields in your TextUs integration.
Your TextUs integration does not provide any default TextUs Contact Lookup Mapping Settings, but if your process requires them, contact your Salesforce or Org Administrator.
If you need to send a text from any other standard or custom object, create a new mapping record where Label must contain the mapped object API name.
TextUs Contact Object Mapping Settings
The TextUs Contact Object Mapping Settings allow you to map fields and relationships from one object to another in your Salesforce and TextUs integration. By default, the TextUs integration record provides the following fields:
Lead: Represents a prospect or a lead.
Contact: A person associated with an account.
You can deactivate an existing mapping by clicking Manage Records, then clicking the Active checkbox listed under the field details.
If you need to connect any other standard or custom object to the TextUs Contact records, create a new mapping record where Label must contain the mapped object API name.
Note: To add another object, contact your Salesforce Admin to manage your TextUs Contact Object Mapping.
Your TextUs integration provides two custom formula fields for lead and contact objects:
Contact formula:
IF(!ISBLANK(MobilePhone),MobilePhone,IF(!ISBLANK(Phone),Phone,IF(!ISBLANK(HomePhone),HomePhone,IF(!ISBLANK(OtherPhone),OtherPhone,IF(!ISBLANK(AssistantPhone),AssistantPhone,'')))))Lead formula:
IF(!ISBLANK(MobilePhone),MobilePhone,IF(!ISBLANK(Phone),Phone,''))
Both form fields are called using the phone field tubl__TextUs_Phone__c. When invoked, the formula fields will validate all standard phone fields on both the contact and lead objects, then enter the value as a phone number in your TextUs integration.
Note: If your organization stores cell phone numbers in a custom field and the order of priority for the fields is different from the order provided formula fields above, contact your Salesforce Administrator for further assistance.