Ablevoice vs voip.ms

I've used www.voip.ms for years with at max a dozen numbers (DIDs). They've done well the vast majority of the time until now. I recently attempted to port out a number. It’s only reasonable that voip.ms use automation as the primary means of fulfilling ports. Computer automation is FAST and I expect 99.9% of ports succeed via automation. In this case, despite having voip.ms provide me the necessary authorization info via email (matched my account records as well) and emailing it to the receiving carrier, it’s been 9 days, hours of frustration, and a dozen unsuccessful attempts. Account Name **** **** Address *** **** **** City **** State ** ZIP Code ***** No pin Account number and BTN- ********** Voip.ms assures me if only the receiving carrier would share the PON (port order number) identifier with them they'd investigate and resolve whatever the hangup is. I find it fishy voip.ms doesn't already see the PON when each port attempt takes place (it seems they're outsourcing that part of their business to another vendor and collaborate poorly) It's equally suspect as to why the receiving carrier doesn't see the PON identifier either. The receiving carrier may outsource as well. When the automation doesn’t succeed, my experience has been that voip.ms shirks assuming ownership for the problem and an effective secondary means to allowing these to succeed. The receiving carrier has been willing to conference call, chat, email chain etc. Especially because the receiving carrier could be communicating with voip.ms the very moment the request is initiated, voip.ms acknowledge and promptly resolve any hitch in the process. Voip.ms has stonewalled such reasonable efforts. It seems rotten a person should have to go so far as to contact the FCC/NPAC. I used to be an evangelist for their service. Now, I'm just desperate to get my numbers released voip.ms