Sarah M. and her team were working to set Agua Dulce Storage up, which included setting up a number for the facility. A brand-new number was purchased in the QMS interface as this is standard practice. An 805 area code was purchased because the no numbers with the facility's area code (661) were available*. The client does not want an 805 number (doesn't make sense geographically), and it was discovered that we could just transfer the number they were already using with Cloud to their QMS account, so we did that. The number that was transferred is a 661 number. Twilio says this number should be working based on what they see on their end, but test texts from the transferred number are not being received nor are they being logged in Twilio at all.
*While the QMS interface said no 661 numbers were available for purchase, this was tested in Twilio itself and 661 numbers were available for purchase. This doesn't really have an impact on this bug, but this is just a note to development about behavior of the SMS interface that was experienced when purchasing a number.
If we need to change the number associated with the facility in Twilio, somehow we need to be able to change it in QMS.