Re: Cancellation schedule question

"OOHRAH!@USMC.net" <OOORAH!@USMC.net> wrote in message
news:brag5e$13sgn$1@ID-208801.news.uni-berlin.de...
> Contract ends on Dec 22.
> I've acquired another phone on another service (Sony T610 on TMobile). I
> want to begin the process of transferring my formerly SPCS number to the
new
> phone, and will happily "pay" until the SPCS contract ends. Will I get
> zapped with premature cancellation charges for starting the transfer
before
> the contract expires - even though I pay till that expiration date?
>
> My alternative is to resurrect an old SPCS phone for the interim, but
that's
> a pain. We're a business account so do not incur fees for equipment
changes.
>
> Thanks!

I don't know whether being paid through your contract date is the same as
continuing service through the contract date ... In order to avoid that
problem, I'd recommend going with your alternative plan.

Bob

Contract ends on Dec 22.
I've acquired another phone on another service (Sony T610 on TMobile). I
want to begin the process of transferring my formerly SPCS number to the new
phone, and will happily "pay" until the SPCS contract ends. Will I get
zapped with premature cancellation charges for starting the transfer before
the contract expires - even though I pay till that expiration date?

My alternative is to resurrect an old SPCS phone for the interim, but that's
a pain. We're a business account so do not incur fees for equipment changes.

Thanks!

In article <brag5e$13sgn$1@ID-208801.news.uni-berlin.de>,
"OOHRAH!@USMC.net" <OOORAH!@USMC.net> wrote:

> Contract ends on Dec 22.
> I've acquired another phone on another service (Sony T610 on TMobile). I
> want to begin the process of transferring my formerly SPCS number to the new
> phone, and will happily "pay" until the SPCS contract ends. Will I get
> zapped with premature cancellation charges for starting the transfer before
> the contract expires

yes.

Does your contract really end exactly at the end of a billing period, or
is it there because Sprint improperly slid it forward?



>- even though I pay till that expiration date?
>
> My alternative is to resurrect an old SPCS phone for the interim, but that's
> a pain. We're a business account so do not incur fees for equipment changes.
>
> Thanks!

"Stewart" <soconnor23@yahoo.com> wrote in message
news:soconnor23-ED7193.14393311122003@news02.west.earthlink.net...
> In article <brag5e$13sgn$1@ID-208801.news.uni-berlin.de>,
> "OOHRAH!@USMC.net" <OOORAH!@USMC.net> wrote:
>
> > Contract ends on Dec 22.
> > I've acquired another phone on another service (Sony T610 on TMobile). I
> > want to begin the process of transferring my formerly SPCS number to the
new
> > phone, and will happily "pay" until the SPCS contract ends. Will I get
> > zapped with premature cancellation charges for starting the transfer
before
> > the contract expires
>
> yes.
>
> Does your contract really end exactly at the end of a billing period, or
> is it there because Sprint improperly slid it forward?

Oh, get off this **** Phillipe ... Why do you interject this delusion when
it has nothing to do with the initial inquiry? You are one sick puppy, you
know that of course ...

Bob

In article <brag5e$13sgn$1@ID-208801.news.uni-berlin.de>, OOORAH!
@USMC.net says...
> Contract ends on Dec 22.
> I've acquired another phone on another service (Sony T610 on TMobile). I
> want to begin the process of transferring my formerly SPCS number to the =
new
> phone, and will happily "pay" until the SPCS contract ends. Will I get
> zapped with premature cancellation charges for starting the transfer befo=
re
> the contract expires - even though I pay till that expiration date?
>=20
> My alternative is to resurrect an old SPCS phone for the interim, but tha=
t's
> a pain. We're a business account so do not incur fees for equipment chang=
es.
>=20
> Thanks!
>=20
>=20
>=20
If you plan on moving your number over to T-Mo, do ***NOT*** cancel with=20
us. The moment you use that magic word in a conversation with us, that=20
number no longer belongs to you.

I'm being overly dramatic, but for a reason. The moment we do, in fact,=20
start to cancel service, except as the result of T-Mobile (in your case)=20
contacting us to transfer the number over to them, then the number=20
belongs to us.

The provider you're moving *from* should not be contacted to start the=20
process. That should be started with the provider you're moving *to*.

Now, about when you cancel... that's a toughie. We have very specific=20
FCC requirements, even if we're having a bumpy time of meeting them=20
right now. So, when a port request comes in, we have no choice on=20
meeting it as soon as we possibly can. If you make the request with the=20
T-Mobile, maybe you can see if they're willing to delay it until the=20
22nd, and let you use a temporary number in the meantime. Because as=20
soon as your request comes into us, then we have to process it. If it's=20
early, we'll credit back whatever portion of the monthly charge you=20
haven't used *and* charge you any applicable termination fees.

If you are willing to meet your obligation, then I'd say wait until the=20
22nd and them ask T-Mobile to port your number over. And have a copy of=20
your most recent bill from us to make sure T-Mobile has exactly the=20
information they need to get us to accept the port.
--=20
-+-
R=D8=DF
O/Siris
I work for SprintPCS
I *don't* speak for them.

Excellent explanation O/Siris.

I might recommend starting the port near the end of the cycle (maybe 5 days
before the cycle end date) that the contract expires in because canceling
early in the billing cycle doesn't get you any refund of the difference.

Also, with all the porting issues going on (SPCS is actually doing very
well) I might put a message on your VM just before you start advising your
callers you might not get calls or VM for a few days. I've dealt with
nightmares both in and out porting that both phones stop working for the
duration.


"O/Siris" <robjvargas@sprîntpcs.com> wrote in message
news:MPG.1a42a51ad7b6cb539897ab@netnews.comcast.ne t...
In article <brag5e$13sgn$1@ID-208801.news.uni-berlin.de>, OOORAH!
@USMC.net says...
> Contract ends on Dec 22.
> I've acquired another phone on another service (Sony T610 on TMobile). I
> want to begin the process of transferring my formerly SPCS number to the
new
> phone, and will happily "pay" until the SPCS contract ends. Will I get
> zapped with premature cancellation charges for starting the transfer
before
> the contract expires - even though I pay till that expiration date?
>
> My alternative is to resurrect an old SPCS phone for the interim, but
that's
> a pain. We're a business account so do not incur fees for equipment
changes.
>
> Thanks!
>
>
>
If you plan on moving your number over to T-Mo, do ***NOT*** cancel with
us. The moment you use that magic word in a conversation with us, that
number no longer belongs to you.

I'm being overly dramatic, but for a reason. The moment we do, in fact,
start to cancel service, except as the result of T-Mobile (in your case)
contacting us to transfer the number over to them, then the number
belongs to us.

The provider you're moving *from* should not be contacted to start the
process. That should be started with the provider you're moving *to*.

Now, about when you cancel... that's a toughie. We have very specific
FCC requirements, even if we're having a bumpy time of meeting them
right now. So, when a port request comes in, we have no choice on
meeting it as soon as we possibly can. If you make the request with the
T-Mobile, maybe you can see if they're willing to delay it until the
22nd, and let you use a temporary number in the meantime. Because as
soon as your request comes into us, then we have to process it. If it's
early, we'll credit back whatever portion of the monthly charge you
haven't used *and* charge you any applicable termination fees.

If you are willing to meet your obligation, then I'd say wait until the
22nd and them ask T-Mobile to port your number over. And have a copy of
your most recent bill from us to make sure T-Mobile has exactly the
information they need to get us to accept the port.
--
-+-
RØß
O/Siris
I work for SprintPCS
I *don't* speak for them.

"O/Siris" <robjvargas@sprintpcs.com> wrote in message
news:MPG.1a42a51ad7b6cb539897ab@netnews.comcast.ne t...

> Also, with all the porting issues going on (SPCS is actually doing very
> well)

Spoken like a loyal SprintPCS employee. Too bad it's not true.
(Confirmed to me by Executive Services).

You are so full of sh$t
I hope the folks over at att are getting the pic. on you.
funny but I notice you've started the responding to yourself crap.
trying to get the guys on the new ng to believe you actually post
something other than bs ?
won't work dude your not that bright.

David wrote:
> "O/Siris" <robjvargas@sprintpcs.com> wrote in message
> news:MPG.1a42a51ad7b6cb539897ab@netnews.comcast.ne t...
>
>
>>Also, with all the porting issues going on (SPCS is actually doing very
>>well)
>
>
> Spoken like a loyal SprintPCS employee. Too bad it's not true.
> (Confirmed to me by Executive Services).

I posted that, not O/Siris. I am an employee, as I believe he is.

The porting is going well, SPCS has actually ported IN about twice what has
ported OUT. The system is working well over all, unfortunately ATT and to a
lesser extent Cingular are struggling with both. You have see the info
posted here as well as on CNN, etc.

"David" <dlandsdowne@wsys.net> wrote in message
news:dlandsdowne-CE557B.06365512122003@news02.west.earthlink.net...
> "O/Siris" <robjvargas@sprintpcs.com> wrote in message
> news:MPG.1a42a51ad7b6cb539897ab@netnews.comcast.ne t...
>
> > Also, with all the porting issues going on (SPCS is actually doing very
> > well)
>
> Spoken like a loyal SprintPCS employee. Too bad it's not true.
> (Confirmed to me by Executive Services).

David wrote:

> "O/Siris" <robjvargas@sprintpcs.com> wrote in message
> news:MPG.1a42a51ad7b6cb539897ab@netnews.comcast.ne t...
>
>
>>Also, with all the porting issues going on (SPCS is actually doing very
>>well)
>
>
> Spoken like a loyal SprintPCS employee. Too bad it's not true.
> (Confirmed to me by Executive Services).


What Phillipe, you mean that your talk with Executive Services is not
true?

Must be, because even the FCC lists Sprint as nowhere near the headache
of some other carriers. Your beloved new carrier, AT&T Wireless, has
racked up a whopping 322 complaints and counting as of December 10.
Even Verizon Wireless had more porting complaints, with 122. Sprint
rang in at 94.

If you'd like to review the data yourself:

http://www.wirelessweek.com/article/...ype=stockwatch


But then, you seem quite unhappy with your new carrier anyway, Phillipe.
You've already charged them with fraud, calling people who disagree
with you "AT&T apologists" and are pulling all the same crap in the
attws newsgroup that you have in here. Which proves only one thing:
you're a troll, and most of your little rants are totally baseless. You
sir, have proven that you're a loser, through and through, without any
of us having to help you along.

--
E-mail fudged to thwart spammers.
Transpose the c's and a's in my e-mail address to reply.

"David" <dlandsdowne@wsys.net> wrote in message
news:dlandsdowne-CE557B.06365512122003@news02.west.earthlink.net...
> "O/Siris" <robjvargas@sprintpcs.com> wrote in message
> news:MPG.1a42a51ad7b6cb539897ab@netnews.comcast.ne t...
>
> > Also, with all the porting issues going on (SPCS is actually doing very
> > well)
>
> Spoken like a loyal SprintPCS employee. Too bad it's not true.
> (Confirmed to me by Executive Services).

Yeah, right. I'm sure they always share information with people that don't
have an account with them. Your lies get more outrageous, and your total
lack of credibility is laughable. I guess I will now refer to you as 'The
Village Idiot'- it seems to fit well.

In article <dlandsdowne-CE557B.06365512122003
@news02.west.earthlink.net>, Daviddlandsdowne@wsys.net=20
says...
> "O/Siris" <robjvargas@sprintpcs.com> wrote in message
> news:MPG.1a42a51ad7b6cb539897ab@netnews.comcast.ne t...
>=20
> > Also, with all the porting issues going on (SPCS is actually doing very
> > well)=20
>=20
> Spoken like a loyal SprintPCS employee. Too bad it's not true.
> (Confirmed to me by Executive Services).
>=20

Are you EVER going to honestly quote me, Philly?

I didn't say that.

--=20
-+-
R=D8=DF
O/Siris
I work for SprintPCS
I *don't* speak for them.

In article <dlandsdowne-CE4494.04310613122003
@news02.west.earthlink.net>, Daviddlandsdowne@wsys.net=20
says...
> Yes you did. It's right there ferom yesterday's post. When you get=20
> caught exagerating or lying you refuse to apologize. Like December for=20
> SMS.
>=20

So you're just going to completely ignore Fellow Traveler's=20
own admission that *he*, not I, posted that, and you're=20
going to maliciously lie all over again?

You know, for someone so sensitive about using the Lord's=20
name in vain, you sure have no problem violating His rules.

--=20
-+-
R=D8=DF
O/Siris
I work for SprintPCS
I *don't* speak for them.

In article <MPG.1a4518d94a357ed7989929@netnews.comcast.net> ,
O/Siris <robjvargas@sprîntpcs.côm> wrote:

> In article <dlandsdowne-CE4494.04310613122003
> @news02.west.earthlink.net>, Daviddlandsdowne@wsys.net
> says...
> > Yes you did. It's right there ferom yesterday's post. When you get
> > caught exagerating or lying you refuse to apologize. Like December for
> > SMS.
> >
>
> So you're just going to completely ignore Fellow Traveler's
> own admission that *he*, not I, posted that, and you're
> going to maliciously lie all over again?
>
> You know, for someone so sensitive about using the Lord's
> name in vain, you sure have no problem violating His rules.


Man you've just otally lost it sirus.

David wrote:

> Man you've just otally lost it sirus.


Pot / Kettle dip ****.