Known issues and limitations in Unified Profiles in Flex (Public Beta)

(warning)

Public Beta

Unified Profiles in Flex is currently available as a limited Public 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. Public Beta products are not covered by a Twilio SLA.

(warning)

Not a HIPAA Eligible Service or PCI Compliant

Unified Profiles in Flex 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.

Outbound communications, such as a phone call from an agent to a customer, do not appear on the History tab .
If your Segment data uses a phone number format other than E.164, work with your Twilio account team to define conversion rules from E.164. Phone numbers in Flex use E.164 format, so to perform a successful search, you must convert phone numbers from E.164 to the formats used by your data in Segment. Typically, Segment uses the same phone number format as your CRM or data warehouse.

Rate this page:

12345

Need some help?

We all do sometimes; code is hard. Get help now from our support team, or lean on the wisdom of the crowd by visiting Twilio's Stack Overflow Collective or browsing the Twilio tag on Stack Overflow.