[VoiceOps] Vonage Port Department

[Carlos Alvarez]

I'm thinking it's not malicious, but probably just stupid.  Then again,
Telesphere was rather sleazy-feeling, and Vonage doesn't seem to have
changed them.  The pending order issue has hit us a few times.  They seem
to have been internal orders between Telesphere and Vonage.  When we
pressed with a statement from the customer saying they had not placed any
orders, the ports completed a short time later.

Most of our Telesphere ports were handled by Intelliquent, some by thinQ.
Of the two, thinQ was far better at handling them when something went wrong.


On Thu, Jun 28, 2018 at 8:31 AM Mike Hammett <voiceops at ics-il.net> wrote:

> We did verify the CSR information. All but one phone number was correct.
> There other phone number had the correct address, but a zip code of
> something like 1 2 3 4 5. Seems like something intentionally set up to
> cause ports to fail.
>
> The problems that we've been having lately have ranged from there's a
> pending order, which there was not. We got that one a few times. Now this
> is the second time they tell us that they have everything cleared and that
> it should be good to go.
>
>
>
> -----
> Mike Hammett
> Intelligent Computing Solutions
> http://www.ics-il.com
>
>
>
> Midwest Internet Exchange
> http://www.midwest-ix.com
>
>
>
> ----- Original Message -----
> From: Carlos Alvarez <caalvarez at gmail.com>
> To: voiceops at ics-il.net
> Sent: Thu, 28 Jun 2018 10:23:06 -0500 (CDT)
> Subject: Re: [VoiceOps] Vonage Port Department
>
> I don't know that I can help much, but we certainly have had a LOT of
> issues with Vonage.  They seem to be mostly on numbers that were previously
> with Telesphere, who they bought out.  Many of them failed because
> Telesphere had their own address on them.  So you might ask your provider
> "is the billing address this?"  In a few cases, that worked, they said yes,
> and completed the ports.
>
> This is the Telesphere address:  9237 East Vía de Ventura, Scottsdale, AZ
> 85258
>
> Another partial success has been telling the customer to call Vonage and
> get a CSR.  Partial because their idea of a CSR is a spreadsheet that may
> or may not be correct, but when it is, voilà.  And even when it's not, it
> shows our porting provider that we tried, and the customer clearly does
> have a proper relationship with Vonage.
>
> Good luck.
>
>
> On Thu, Jun 28, 2018 at 8:17 AM Mike Hammett <voiceops at ics-il.net> wrote:
>
> > Could I get a contact in Vonage's port department? Level 3 is the
> > underlying CLEC, but obviously, there's some relationship there being
> > managed. We've been getting the run-around for a month trying to
> complete a
> > port out. We've been working with our mutual customer and regular Vonage
> > customer support, but that's often contradictory and thus far
> unsuccessful.
> >
> > The customer service rep said that the porting department only works via
> > email and wouldn't give us anyone's email.
> >
> > Our last instruction was, "Angela from Vonage said to resubmit the port
> > request again due to the numbers being in migration and that cleared
> > today." which is the same thing they told us about 10 days ago, but
> > apparently, that didn't work.
> >
> >
> >
> > -----
> > Mike Hammett
> > Intelligent Computing Solutions
> > http://www.ics-il.com
> >
> >
> >
> > Midwest Internet Exchange
> > http://www.midwest-ix.com
> >
> > _______________________________________________
> > VoiceOps mailing list
> > VoiceOps at voiceops.org
> > https://puck.nether.net/mailman/listinfo/voiceops
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20180628/85759a45/attachment.html>