[VoiceOps] Rejected port due to having other orders active on the account
carlos at televolve.com
Thu Nov 1 16:06:19 EDT 2012
On Thu, Nov 1, 2012 at 1:01 PM, Paul Timmins <paul at timmins.net> wrote:
> If the customer's account is truly in flux, it makes sense to me. If i
> have a pending order to disconnect 3 lines, and then you request to port
> the entire account, do I give you those 3 lines, or not? If the customer
> requests more lines, and you didn't know about them because the order is
> pending, do I leave those new lines on the circuit (they may have ordered
> them, for example, to satisfy a contractual minimum commitment for a few
> months, for example, and did not want you to port them) or do I allow your
> port to go through, and disconnect the T1 they were supposed to ride on? Or
> do I offer the new TNs to you, and it turns out they were supposed to
> remain with us?
This is understandable, and we've never done that sort of thing. Mostly
it's porting X numbers to carrier A, and Y numbers to carrier B. Leave the
circuit alone until formally cancelled (which Integra requires 30 days
notice of, even if you port out all numbers including BTN).
> I think it's fair to reject for pending orders, but only if the winning
> carrier can find out what those orders are. Your LOA probably gives you
> blanket rights to operate on the customer's behalf - I suggest you do that
> a few times to see what the orders are, and if they're BS, file a complaint
> with the public service commission in the state you're operating in. If
> not, it may at least be enlightening.
We nearly always know what the pending orders are, because we initiated
them, as above. The top problem we're trying to solve is being able to
kill the new customer's commitment to Integra in less time. In a few cases
it's just operational stuff where we need to move things from one circuit
to another and such, but the real hard cost problem is delaying the
turn-down of a PRI for 30 days or more.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the VoiceOps