<div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif">We notify once LSR is received to have them contact us immediately if it was not intended, if it was intended they don't have to do anything.</div><div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif">We terminate the service linked to the number (usually just the number) and bill per termination clause in agreement.</div><div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif">We also let them know that we will continue to bill until we receive a cancellation order from them and provide them with instructions on how to do so and that cancelled services are subject to the termination clause of their agreement </div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Dec 29, 2022 at 3:48 PM Carlos Alvarez via VoiceOps <<a href="mailto:voiceops@voiceops.org">voiceops@voiceops.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div dir="ltr">
I would immediately contact the customer and first of all, ask if they are aware and want to authorize it. We’ve only ever had one “theft” port-out, but that was one too many. Secondly I would let them know what their contractual obligations are and ask for their intentions with the overall service, and proceed from there. Inform them of what their last invoice will be and get their approval/agreement along with agreeing that it’s due within 30 days.</div><div dir="ltr"><br></div><div dir="ltr">We’ve had new port-in clients who don’t listen when I tell them to notify the old carrier, and #4 happens. In one case they paid thousands for a couple years. That’s just scumbaggery.</div><div dir="ltr"><br></div><div dir="ltr">On the other hand, we’ve had a customer come back to us because they said we helped them move out in a very helpful way, and didn’t try to fight or be assholes. The new carrier turned out to be cheap but shitty, so they came back. That would not have happened if they had left with bad feelings.</div><div dir="ltr"><br></div><div dir="ltr">Last year we lost a customer because they were bought out by a huge conglomerate, with their own telecom staff of at least six people. The telecom director told me that we had been the easiest to move away from and the most outwardly helpful that she’s ever seen in her career. No dollar benefits here, but I feel good about doing good business.</div><div dir="ltr"><br></div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Dec 29, 2022 at 1:21:09 PM, Mike Hammett via VoiceOps <<a href="mailto:voiceops@voiceops.org" target="_blank">voiceops@voiceops.org</a>> wrote:<br></div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" type="cite">
<div><div></div><div><div style="font-family:arial,helvetica,sans-serif;font-size:10pt;color:rgb(0,0,0)"><span style="font-size:10pt">I have two conflicting opinions in my head (origin unknown) of what to do with the subscriber's service when they port away. In the absence of requirements, what are people generally doing?</span><div style="font-size:10pt"><br></div><div style="font-size:10pt">1) They've ported a given number away, so clearly they don't want our service. Terminate the service and enact any termination provisions in their agreement.</div><div style="font-size:10pt">2) Contact the customer (after the port is complete) and confirm their intention to cancel. <span style="font-size:13.3333px">Terminate the service and enact any termination provisions in their agreement.</span></div><div><span style="font-size:13.3333px">3) </span><span style="font-size:13.3333px">Contact the customer (once the LSR is received) and confirm their intention to cancel. </span><span style="font-size:13.3333px">Terminate the service and enact any termination provisions in their agreement.</span></div><div><span style="font-size:13.3333px">4) </span><span style="font-size:13.3333px">Do nothing different until the customer contacts you to cancel.</span></div><div><span style="font-size:13.3333px">5) Something else.</span></div><div><span style="font-size:13.3333px"><br></span></div><div><span style="font-size:13.3333px"><br></span></div><div><span style="font-size:13.3333px">Number 3 seems like the one most likely to have a regulatory issue, given that you're contacting the customer during the port process, but I think as long as you don't do any retention attempts, you're alright.<br></span><br><div style="font-size:10pt"><span name="x"></span><br><br>-----<br>Mike Hammett<br>Intelligent Computing Solutions<br><a href="http://www.ics-il.com" target="_blank">http://www.ics-il.com</a><br><br><br><br>Midwest Internet Exchange<br><a href="http://www.midwest-ix.com" target="_blank">http://www.midwest-ix.com</a><br><br><span name="x"></span><br></div><br></div></div></div></div>
<div>
<div>
_______________________________________________<br>VoiceOps mailing list<br><a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a><br><a href="https://puck.nether.net/mailman/listinfo/voiceops" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><br>
</div>
</div>
</blockquote>
</div></div>
_______________________________________________<br>
VoiceOps mailing list<br>
<a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/voiceops" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><br>
</blockquote></div>