The Update Profile Traits Widget is currently available as a Private Beta product and the information contained in this document is subject to change. This means that some features are not yet implemented and others may be changed before the product is declared as Generally Available. Private Beta products are not covered by a Twilio SLA.
The Update Profile Traits Widget is not a HIPAA Eligible Service or PCI compliant and should not be used in Flex or Segment workflows that are subject to HIPAA or PCI.
Studio uses Widgets to represent various parts of Twilio's functionality that can then be stitched together in your Studio Flow to build out robust applications that require no coding on your part.
New to Twilio Studio? Check out our Getting Started Guide!
With the Update Profile Traits Widget, you can set or update trait values for a customer profile from within a Studio Flow. Take information you learn about a caller during a flow execution and send it to Unified Profiles to update profile trait data. This allows you to enrich profiles to personalize future customer experiences based on their profile traits.
With the Update Profile Traits Widget, you can:
preferred_name
trait from Robert
to Bob
. Then, when a customer calls in again, you can correctly refer to them by their preferred name without having to ask again.zip_code
trait to help you authenticate a caller on future calls.Before you configure and use the Update Profile Traits Widget, you'll need:
The Update Profile Traits Widget requires the following information:
Friendly name | JSON Definition Key | Description | Default |
---|---|---|---|
Connection (Profile data source) | profile_connector_instance | The Segment instance to connect with | None |
Unified Profile ID (Search Parameters) | profile_connect_sid | ID of the profile to write to Here's an example of a value that you might want to use in this field: {{widgets.look_up_profile_1.ProfileData.profileConnectSid}} | None |
Traits | traits | List of key/value pairs of traits to write to the specified profile. If the trait doesn't exist, it will be created and populated with the value you send. | Empty |
These events trigger transitions from this widget to another widget in your Flow. For more information on working with Studio transitions, see Studio's Getting Started guide.
Transition friendly name | Key | Description | When should Studio take this transition? |
---|---|---|---|
Update profile | profileUpdated | Profile was updated with provided traits | If the profile update was successful, this should transition to a widget write succeeded state |
Profile not found | profileNotFound | Profile could not be found | When the profile could not be found with the profile ID provided |
Failed | failed | Profile failed to update | If the profile update was unsuccessful |
This example shows how to use the Update Profile Traits Widget to set the value of the trait callback_number
for a customer.
When the flow receives an incoming call, Studio checks to see if the profile has a value for the trait callback_number
. If not, the flow asks the customer to provide a new one.
Once the caller provides a number, the Update Profile Traits Widget updates the trait callback_number
with the new number as the value. On future calls, you can retrieve this callback number so that customers won't have to enter it again.