I am very interested in ClientEXEC but I am using Kayako now. I am thinking of using ClientEXEC ordering and billing functions. But does anyone use it together with Kayako Knowledge Base? How difficult is it to port the support tickets from Kayako to ClientExec?

I haven't personally tried to do that yet with any of my client but i'm sure its possible. Have you seen or tried the new version of Clientexec?

I have seen it but haven't tried it. Wanted to use Clientexec but it seemed to overlap the functions of Kayako, that's why still a bit hesitant on its usage.

I haven't personally tried to do that yet with any of my client but i'm sure its possible. Have you seen or tried the new version of Clientexec?

I have seen it but haven't tried it. Wanted to use Clientexec but it seemed to overlap the functions of Kayako, that's why still a bit hesitant on its usage.

I'm a huge supporter of ClientExec, but personally I don't believe it will ever be as strong and versatile as Kayako in regards to being a full featured Help Desk.

I would rather run two separate systems, one for Billing and one for Support. ClientExec is an amazing Billing System, and Kayako (IMO) is an amazing Support System. There's nothing wrong with using two systems that overlap in a few areas, and it will also limit the damage in the event of an exploit being found in one system. (May not apply if the ClientExec login share module is being used with Kayako...)

Take WHMCS or any other "All in One" solution that has ever been compromised, now the attackers have the billing, the server details, and all of the trouble ticket's which could include further logins to other systems depending on what you are supporting.

Thanks, I guess I will go ahead with Kayako and ClientExec, just need a second opinion :)

I'm a huge supporter of ClientExec, but personally I don't believe it will ever be as strong and versatile as Kayako in regards to being a full featured Help Desk.

I would rather run two separate systems, one for Billing and one for Support. ClientExec is an amazing Billing System, and Kayako (IMO) is an amazing Support System. There's nothing wrong with using two systems that overlap in a few areas, and it will also limit the damage in the event of an exploit being found in one system. (May not apply if the ClientExec login share module is being used with Kayako...)

Take WHMCS or any other "All in One" solution that has ever been compromised, now the attackers have the billing, the server details, and all of the trouble ticket's which could include further logins to other systems depending on what you are supporting.

Take WHMCS or any other "All in One" solution that has ever been compromised, now the attackers have the billing, the server details, and all of the trouble ticket's which could include further logins to other systems depending on what you are supporting.

Now Clientexe is no expectional or any other software on the net. Its all about how the coding is secure and how your servers are secure.

Now Clientexe is no expectional or any other software on the net. Its all about how the coding is secure and how your servers are secure.

I didn't say ClientExec was the exception, as they most certainly have had security issues in the past. All I'm saying is that if everything is integrated into one system, like WHMCS or Ubersmith, there is a higher potential for more data to be compromised through a script vulnerability.

(Yes, if the server is compromised... everything is fair game to being owned).