WHMCS Jesse

Robert, I apologize for any inconvenience you've had so far, we're presently reviewing over this ticket and will have a response out to you today. It's been proven hard to determine the cause, so it's needing deeper investigation by our senior staff. Thanks for your patience.

Jin, I apologize for your frustrations with Fast-Track Support, however, please note that the $5 fee is only an introductory fee for the first 30 days. The fee for "Fast-Tracking" your support request will potentially be higher after 30 days as noted in our blog here. Additionally, we've been expanding our support team and have 24/7/365 on-site coverage to allow for this kind of option to be available. In fact, most support requests are getting responded and resolved quicker than it ever has in the past. The Fast-Track Support is merely offering an emergency option for people who want to expedite their support requests, and only available during specific timeframes M-F where we have the most staff available online. If you ever have an issue with the level or quickness of service you have received, feel free to reach out to myself via the forums here or by asking for a manager via the ticket. We are more than happy to address service-level issues. Thanks!

It does appear both tickets are pending a response from you at the moment. Our support team operates 24/7/365, however, weekends are lightly staffed and it was overloaded going into the weekend so responses took longer than usual. I apologize for the inconvenience!

Alexander, I apologize for the large amount of delay, however, there appears to have been an issue with the queue and the ticket was not visible - I have just assigned it over to our integrations queue and they will be updating you shortly. We usually have very quick turnaround on getting integrations completed, so again I apologize for this inconvenience.

Can you please PM me the ticket number?

I apologize for the inconvenience, it appears Sean responded to your ticket and sent you the appropriate file to resolve the issue. Please report your environment information in the ticket if possible so we can continue to track the origin of this issue. Thanks! Can you please submit a ticket here with the error you're getting so a technical analyst can provide you with a fix/workaround? Thanks!

Neklawy: I've responded to your ticket and applied the workaround - sorry for the delays!

Callum-JH: I've reproduced this and filed an internal bug report with case #4032. Sorry for the delays!