Feature Requests
Share ideas, discuss and vote on requests from other users in community

Tickets - An Overhaul or at least some fresh ideas.

Matthew R shared this idea 8 years ago

We use WHMCS as our main dashboard for issue tracking for both our web hosting and network support business. As such, our needs may exceed the design of the platform and intended use cases. I am basing my ideas on other products we have tested and reviewed, mainly Zen Desk, HelpDesk Pilot, Kayako, and a few others.

Below are the items I would like to propose based on past support issues and ongoing feedback we get from clients about the way we work.

Assign tickets to staff. We do often flag issues so we know who is working on a ticket. But, we think it would be smarter to have an admin take ownership of a ticket, then pass it off or release it back when no longer able to assist. Kayako does something similar where a ticket but be claimed before you can start working on it. I imagine an OPEN - Unassigned Status would be appropriate.

Default view, tickets assigned to an admin. Show me what I need to be working on then what is OPEN and UNASSIGNED.

Better SLA management. Let me define several service metrics that can help drive tickets to completion. Open for more than 4 hours with no response should be flagged, highlighted, or POP off the screen, etc.

Better grouping of Contacts to Clients. Let me create smart rules like. anything @domain.com gets assigned to client XYZ. Since we support networks, anyone from the company could be calling or emailing in with an issue.

Better form control. We have started using FormStack to process our ticket requests and then route via email. the WHMCS ticket form submissions are just not smart enough to help us route issues to various departments. I can shed more light on this if needed, but basically we wanted our subject lines to be as smart as possible. Helping our clients craft better tickets though automation helps us do a better job.

Let me create custom views of tickets. Ajax or HTML5 ticket layout? Along with this is drag and drop active tickets to status sections. Move a few tickets to mine to assign to me, then drag one to delayed or scheduled.

Huge pet peeve of mine. User 2 at Company XYZ send in a ticket, but User 2 is not the profile contact. In the main ticket view we only see that User 1 at Company XYZ opened a ticket. I would like to see the actual user who sent the ticket in its own column. Company in its own column. Let me sort by any table header.

Let a client add a cc or bcc when opening a new ticket. Often, the client issue affects several people and they want to open a ticket and include all the parties. Allow admins to open a ticket and select multiple contacts as well, instead of a single contact and then the cc field.

Help us crate smarter rules for clients who are incapable of figuring out how tickets work. Since we use the FormStack form to submit new issues, we have to allow piping of email in to the system. Certain clients will FW or RE a ticket and then it opens another ticket, which then as to be merged, etc.

Ticket Timers, We purchased an addon for this, its AWESOME. Include something by default to help us with issues that we need to delay and come back to. Could be because we have to work with a 3rd party or the client is scheduling for later etc. Help us keep the active tickets down so we can focus on what needs a resolution.

Tie tickets, to do, and the PM system together. I would love to be able to add a to do to someone else on my team, and have them see that and know action is required.

Show me on the active ticket screen how many replies, notes, etc there are. Let me know if there are unread notes and replies by bolding the entry or something similar. We constantly have a problem of adding a private ticket note, then the person it was intended for has no idea they are supposed to look at it.

Thats all for now. If other members can add or comment on this that would be great. Anything we can do to make our WHMCS smarter for us so we can do a better job for or clients. Thanks again and thanks for working so hard year after year on improving the product like you have.

Comments (4)


Excellent suggestions.

I added a separate feature request for the number of replies, take a look:



There are some good ideas on this. However i am not going vote on it as the features range too widely, edit your post to group together one set of features that work together to include then create other posts with the other groups of features so that we can vote more accurately.


Hi Mathew, these are all great ideas and we'd love to see them broken down into more actionable work in the feature request site. We appreciate the amount of work that went into thinking through these requests. Please search through the feature request site to see if any of these ideas presented here have already been presented - if not, feel free to create a request for each main idea.

We have made a number of improvements to our ticket system in our 6.3 release, which you can find the details here: http://docs.whmcs.com/Version_6.3_Release_Notes


Hi Matthew - we appreciate the time you took in laying out the features you want to see in the ticket system. The WHMCS team can act on your suggestions in a much more effective manner if they are broken up into individual feature requests. Be sure to check out the existing requests on the feature request site to see if you can vote on any existing ideas. We have also made many improvements to the ticket system in the 6.3 release - details can be found here: http://docs.whmcs.com/Version_6.3_Release_Notes.