Jump to content

Recommended Posts

Posted

Wen you have a package active with a "Cancel at end of term" active and the client login and make an upgrade to outher package without the limitation of the "Cancel at end of term" option, the current "Cancel at end of term" of the original package to the new package is still present.

 

1- Add a package with "Cancel at end of term" option

2- Add a second Package in the same group without the option "Cancel at end of term"

3- Purchase the first package (add in admin because there is a bug purchasing as client), and activate

4- Now login as client and upgrade to the new package that dosent have the "Cancel at end of term" option by default and activate

 

You will see that the package will still terminate in the end of the first package.

 

Solution:

 

Wen upgrade/downgrade if there is any "Cancel at end of term" Scheduled, it has to be removed. And if the new package as also the option "Cancel at end of term", as to be added after the invoice is paid.

Posted

I don't see an issue with the way it currently works. Setting a package to 'single_term' is identical to creating a service and then scheduling it for cancellation at the end of its term. Service data takes precedence over package data from which it was created. Upgrading/downgrading packages doesn't manipulate pre-existing service information, like a cancellation date. Otherwise, I can imagine clients working around a pending service cancellation (for whatever reason) by switching packages, then switching back.

Posted

I don't see an issue with the way it currently works. Setting a package to 'single_term' is identical to creating a service and then scheduling it for cancellation at the end of its term. Service data takes precedence over package data from which it was created. Upgrading/downgrading packages doesn't manipulate pre-existing service information, like a cancellation date. Otherwise, I can imagine clients working around a pending service cancellation (for whatever reason) by switching packages, then switching back.

 

 

How can we offer a trial package to our clients and then if the client upgrades it can continue using the service?

 

I think this is the only way, and we also can "Restrict" the "trial package", in this way cliets can only upgrade and after the upgrade they cannot select again the trial package.

 

Also only after payment confirmation, the client can upgrade/downgrade again even if that removes the cancelation request.

 

Can anyone else tell your touths on this?  :)

 

We use on WHMCS and also used on AWBS this option to offer trials to our clients and it works great :)

Posted

How can we offer a trial package to our clients and then if the client upgrades it can continue using the service?

 

I think this is the only way, and we also can "Restrict" the "trial package", in this way cliets can only upgrade and after the upgrade they cannot select again the trial package.

 

Also only after payment confirmation, the client can upgrade/downgrade again even if that removes the cancelation request.

 

Can anyone else tell your touths on this?   :)

 

We use on WHMCS and also used on AWBS this option to offer trials to our clients and it works great :)

 

Maybe a suggestion to have the option to mark a package as "not able to downgrade" I'd +1 that.

 

Not able to downgrade as in once they upgrade they can only upgrade or stay on the current plan?

Posted

Maybe a suggestion to have the option to mark a package as "not able to downgrade" I'd +1 that.

 

Not able to downgrade as in once they upgrade they can only upgrade or stay on the current plan?

 

that sounds like an excellent feature.

Posted

that sounds like an excellent feature.

To add to my post maybe a way to show a error message like when the client has a invoice to pay like this:

 

post-38-0-75740800-1409332772_thumb.png

 

Days count down..

 

Edit: Sorry not account as I edited in the picture Service ;)

  • 2 weeks later...
Posted

I've added CORE-1418 for this, which is an improvement to disallow clients from changing the term, or package, when the service is scheduled for cancellation.

 

 

In my opinion its better to continue showing the option to upgrade, and if the client upgrades it will remove a scheduled cancellation if the client change the package, because i think we can use the alredy existent option on packages "cancel at the end of the term" to "force" a client to upgrade a package.

 

What I suggest is for clients not be able to upgrade to packages that have the option "cancel at the end of the term" this way here will be no problems :)

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...