Damo

@WHMCS John @WHMCS ChrisD surely by now, with all the feedback and grievances aired, WHMCS will have something to say publicly to their customers.

Hello, There's been plenty of feedback about the recent announcements from WHMCS about the changes to licences and pricing. Apart from two replies (Chris, and John (referencing Chris')) it's just silence from the WHMCS side. Does WHMCS have nothing to say in a reply to all the feedback provided? *Please keep this thread quiet until a response comes from WHMCS staff. There are other threads open to share our experience/comments/disgust.

If you have an owned license of WHMCS you can save 30% This is on their homepage as of right now.

We've paid $99.95 USD for the last 4 annual "Support and Updates" addon. e.g. 2018, 2019, 2020 and this year.

It is unreasonable to discontinue 6/12 month support purchases for Owned licenses immediately (management decision and is final) on this notice. Yet the price increases come about on July 1st 2021. That's a very calculated move. A sure way to have WHMCS owned licenses choose between three options. - Run a legacy version (current licence) - Switch to a monthly fee (Chris' suggestion that this spreads the annual cost out is just laughable. A $99 annual fee doesn't equate to $20 per month for 12 months) -Find an alternative product. WHMCS don't want the smaller clients anymore, that's quite clear. If these changes are in the interests of WHMCS customers then I'd find it more reasonable and equitable for owned licensed holders to be able to purchase one more annual support extension. That way the opportunity to get current software remains whilst adjusting. As an owned license holder the moment I switch to the monthly plan, apart from the steep price hike, I can no longer go back to my owned license (even though technically I can continue to use it) because the data set will no longer be compatible. Owned licenses effectively become moot.

Well that's different to the count I see when viewing the clients page. There's active clients with no active services and they're still counted. WHMCS needs to provide the method used to determine it so that we can prepare and understand this pricing change.

Apparently 'Never' doesn't mean never.

It doesn't show on an owned license. I'd like to see WHMCS provide this so that we can determine what plan we are forced to move to should we stay with WHMCS.

There's lots of this discussion that interests me (on a few levels) but at the end of the day it's a choice to use WHMCS and if you don't like it (legally/ethically/best practices aside) then don't use it. WHMCS is not the same company it was. There is not the same interaction and personal level with the developer (Matt) it's now a corporate entity. Beating your head against a wall or waving your fist isn't going to get attention. Legacy clients will be expected to drop off so it's better to cut them loose through policy. Legacy clients aren't going to bring continued revenue. Sadly that's a reality.

Have you considered SupportPal as an alternative to Kayako? It's actively supporting WHMCS, the integrations are so clean and seamless. We dropped Kayako when they forced their cloud system upon customers. Best move we ever did.

Instead of modifying the template you should create a child template. That way your changes won't get overwritten when an update comes out for Twenty One.

Both options are available. See the documentation here https://docs.whmcs.com/Affiliates At the product level you can set it to One Time if that's what you want to do.

I never said it wasn't looked at, and 'complete and utter rubbish' is a tad emotive. Historically speaking, and there is no way logically you can deny that, the feature request system has not been the place to get changes made. An updated client theme / bootstrap is by no means a recent request. And I'd like to get you started on the feature request/vote system - you've been here long enough, and as the community manager, that's done a lot of good things I'd hope that a more user (paying clients 'community') friendly system would get implemented. I appreciate that very few of the client base will visit the forums and / or the requests site but GIGO still applies.

You're joking yeah? A feature request that requires yet another login and historically the last place that WHMCS looks at. I appreciate the reply but towing the companies line is a tad insulting. Shame on me for offering a users perspective.

It would be great to be able install a hot fix from within WHMCS. The built in updater could be used seamlessly to do this. Manually patching before the next release is cumbersome and inconvenient.