If I NEED customers who are opting into SMS to format their numbers into +1 (xxx) xxx-xxxx in order to be able to text them - there should be a way to either format the property to force that input, or a template in the ops hub that is designed to do that autoformat once enrolled… This seems like such a huge oversight to me. I shouldn’t need to be (or hire) an advanced coder to use an upgrade like this that’s based on a logical progression. Customer opts in to texting through form, customer provides a number in whatever format they want because the field isn’t delimited, workflow accepts the form as enrollment criteria and attempts to send a text welcome to whatever string of numbers customer entered, workflow fails. I see no work-around for this other than a manual re-enrollment process that requires manual reformatting of the phone and that’s just unrealistic, untimely for the customer, and inefficient for my team.