If price wasn't an issue, which would you choose? Take into consideration that there is a loginshare for WHMCS and Kayako.

I will still be using WHMCS for billing and such, just trying to decide which is best for support.

the whmcs support center looks very basic and unattractive .. I'd go with Kayako

In fact we're considering whmcs + kayako for our new web site and I'm wondering if it's actually possible to completely get rid off the links to the builtin helpdesk/knowledge base inside whmcs.

We just want whmcs to handle the billing and NOTHING else .. and be able for customers to have one login to use both kayako and whmcs (just the invoicing part of whmcs)

the whmcs support center looks very basic and unattractive .. I'd go with Kayako

In fact we're considering whmcs + kayako for our new web site and I'm wondering if it's actually possible to completely get rid off the links to the builtin helpdesk/knowledge base inside whmcs.

Just edit homepage.tpl in the theme for the homepage links and header.tpl for the KB link at the top.

Thanks for the info...

Just fyi, your site seems borked .. if you follow any of the order now links you get:

Site error: the file /home/license/public_html/my/order.php requires the ionCube PHP Loader ioncube_loader_lin_4.4.so to be installed by the site administrator.

If you want a live chat and ticket system then Kayako support suite is the way to go.

As for papi are you sure you have ioncube loader? I believe that is error is because of lack of ioncube.

I prefer Kayako support suite compared to WHMCS support center for the features.

As for papi are you sure you have ioncube loader? I believe that is error is because of lack of ioncube.

I think papi talk about Lpal-Jay's site from his sig

I personally prefer WHMCS to Kayako although im currently using Kayako eSupport. WHMCS is much easier to install and configure than Kayako and Matt is much more responsive to his customers than Kayako. WHMCS is very easy to skin and make look like Kayako or anything else you like. If my host had reg_globals on then i would be using WHMCS.

Kayako is easy to install and configure as well. One more for Kayako!

i definitely recommend WHMCS if your not needing a lot of advanced features.

I personally from a customer standpoint cant stand companies that use separate scripts for support and billing.

I personally prefer WHMCS to Kayako although im currently using Kayako eSupport. WHMCS is much easier to install and configure than Kayako and Matt is much more responsive to his customers than Kayako. WHMCS is very easy to skin and make look like Kayako or anything else you like. If my host had reg_globals on then i would be using WHMCS.

Why not turn it on via .htaccess (many hosts support doing so)?

Kayako is allot more flexible and the support center can be through an app which is very handy. WHMCS's support centre for low amounts of tickets at a time. I'd say i'd only use the WHMCS support centre on a short term basis.

Thanks for the info...

Just fyi, your site seems borked .. if you follow any of the order now links you get:

Site error: the file /home/license/public_html/my/order.php requires the ionCube PHP Loader ioncube_loader_lin_4.4.so to be installed by the site administrator.
Yeah, we were having some problems installing the ioncube properly yesterday but now it should be fine.

I give my vote for WHMCS. I have used Kayako in the past and WHMCS is a more complete package for us in terms of handling billing/support. You can also customize pretty much everything with the script which is also nice.

If my host had reg_globals on then i would be using WHMCS.

Wow... Are you kidding? As a PHP developer, I would stay very far away form any script that requires register_globals to be ON. That is VERY bad design, not to mention potentially very insecure! The PHP team has even acknowledged this and has set the default switch of register_globals to OFF since PHP 4.2.0! Stay away!

If price wasn't an issue, which would you choose? Take into consideration that there is a loginshare for WHMCS and Kayako.

I will still be using WHMCS for billing and such, just trying to decide which is best for support.

I own both.

I use WHMCS for support. SupportSuite is pretty slick, don't get me wrong, but it makes life so much simpler when you have your billing and tickets in one place.

Wow... Are you kidding? As a PHP developer, I would stay very far away form any script that requires register_globals to be ON. That is VERY bad design, not to mention potentially very insecure! The PHP team has even acknowledged this and has set the default switch of register_globals to OFF since PHP 4.2.0! Stay away!

Your <<are incorrect>> to state such a thing as register_globals are not insecure themselves, they just have more frequently been used incorrectly. PHP has NOT ever stated that register_globals themselves are insecure and if you properly sanitize/verify these variables, then you have nothing to worry about. This topic has came up many many times already.

Believe though, i used to feel the same way as you until i did a bit of research and read the official stance on them by php.net.

While coding with register_globals on in mind is not insecure itself, i will agree that its lazy coding and there isnt a good reason for doing it.

Your <<are incorrect>> to state such a thing as register_globals are not insecure themselves, they just have more frequently been used incorrectly. PHP has NOT ever stated that register_globals themselves are insecure and if you properly sanitize/verify these variables, then you have nothing to worry about.

You obviously misread my post... I said: "I would stay very far away form any script that requires register_globals to be ON. That is VERY bad design, not to mention potentially very insecure". Notice the bold word? POTENTIALLY very insecure - not inherently or automatically insecure. You really ought to read posts more carefully before criticizing them.

You obviously misread my post... I said: "I would stay very far away form any script that requires register_globals to be ON. That is VERY bad design, not to mention potentially very insecure". Notice the bold word? POTENTIALLY very insecure - not inherently or automatically insecure. You really ought to read posts more carefully before criticizing them.
Just using a .htaccess to turn on register globals for the directory would be fine, would it not?

Since this has gone (way) off topic, and the OP has requested it closed, so be it. If you still have something to discuss, please start a new topic.