{"id":294,"date":"2012-12-19T12:45:25","date_gmt":"2012-12-19T12:45:25","guid":{"rendered":"https:\/\/www.cmwlab.com\/blog\/?p=294"},"modified":"2026-01-06T12:23:26","modified_gmt":"2026-01-06T12:23:26","slug":"support-case-tracker","status":"publish","type":"post","link":"https:\/\/www.cmwlab.com\/blog\/support-case-tracker\/","title":{"rendered":"Support Case Tracker"},"content":{"rendered":"

Learn how Comindware Customer Headquarters uses Comindware Tracker for managing customers\u2019 support requests. We have designed our own custom CRM system which suites our needs and match our processes.<\/p>\r\n\r\n

\r\n\"CMW<\/a><\/p>\r\n\r\n

It allows us to manage support cases, track customers\u2019 and engineers activities, analyze typical issues and create knowledge base content with solutions, connect with QA and development teams to work on complicated problems.<\/p>\r\n\r\n

Each support case tracks all the aspects of the support request providing management with full set of data for problems analysis feeding various Comindware teams with information they need to make company\u2019s processes, polices and products even more customer oriented, efficient and easy to use.<\/p>\r\n\r\n

Support operations are hard to imagine without convenient support case tracker. Nowadays there are tons of such tracking systems out there and sometimes it is hard to select the one that exactly matches your needs.<\/p>\r\n\r\n

\u201c…It helps us track cases, manage their backlog, filter them against priorities and ensure all relevant data are available to each support engineer on his fingertips…\u201d<\/blockquote>\r\n\r\n

We in Comindware decided to try our own Comindware Tracker<\/a> and see if it is capable of doing the job we need. And guess what? We were able to set it up the way we need. It helps us track cases, manage their backlog, filter them against priorities and ensure all relevant data are available to each support engineer on his fingertips.<\/p>\r\n\r\n

Moreover should we need to modify the current case flow, add\/or remove some case statuses, add more fields into the case we are not limited here. We do not even have to put our case tracker offline to make changes, thus our support operations are never interrupted by maintenance outage. But let me show you how things are done here in Comindware Customer HQ<\/a>.<\/p>\r\n\r\n

\n \n\n Get a 30-day trial!\n\n <\/a>\n<\/section>\r\n\r\n

To start a new case one just need to press \u201cNew Support Case<\/em>\u201d button:<\/p>\r\n\r\n\"Open<\/a>\r\n\r\n

and fill in the form that opens up with the information required. Note that mandatory fields are highlighted so engineers are aware what information they need to collect to create a case:<\/p>\r\n\r\n\"Enter<\/a>\r\n\r\n

Once all fields are set, the case can be saved and its life cycle starts.<\/p>\r\n\r\n\"Support<\/a>\r\n\r\n

As you can see, we are tracking all the important data, which helps us allocate proper support resources and ensure customers are getting attention they need at the right time.<\/p>\r\n\r\n

All communication with customers is tracked right within the case in the discussion tab, product environment information is available in the tab next to it:<\/p>\r\n\r\n\"Case<\/a>\r\n\r\n

In the situation when the problem is complicated and requires other teams to jump in support cases can be linked to other items located in QA, Development or Product Management trackers. It helps us see case dependencies and ensure cross-team collaboration<\/a> is under control.<\/p>\r\n\r\n

For example: if a case is linked to a certain software bug in the bug tracker<\/a>, support engineer can easily identify the fix availability and provide the customer with the required information without even looking into the bug because all the necessary information from the bug item is available right within the support case:<\/p>\r\n\r\n\"case\r\n\r\n

History tab is one of my favorite ones. When there is a need to analyze certain case actions, it will help you put together the full story and understand what was going on with the case from the point of its creation until its closure:<\/p>\r\n\r\n\"Case<\/a>\r\n\r\n\"Support<\/a>\r\n\r\n

As seen from this screen shot our support case\u2019s lifecycle starts from the \u201cStart<\/em>\u201d step and gets closed at \u201cEnd<\/em>\u201d step. \u201cOpen\u201d step is located in the center. This is where the most of the job with the case within the Comindware Customer HQ team is done. Other statuses are of \u201cpending\u201d type for us because when a case sits in one of them, we expect a response either from a customer or from some other team.<\/p>\r\n\r\n

To ensure no one is dropping the ball the \u201cNext Contact Date<\/em>\u201d field is used. This helps support engineers identify cases, which are sitting in pending statuses for too long and follow up with customers and other teams.<\/p>\r\n\r\n\"case\r\n\r\n

Finally, we have set up a special backlog calculation system to control case flow and calculate cases\u2019 \u201contime\u201d. This provides us with additional visibility into support processes and provides additional control for case management:<\/p>\r\n\r\n\"case\r\n\r\n

I\u2019d love to stop here but this is not the end. We went even further and started to track case closure details that shows us time taken to resolve the case, case closure reason and KB<\/a> solution article that was used to solve customer\u2019s problem. If something was done that is missing in KB our engineers are describing solution used so that our KB team could use this data to enrich KB content.<\/p>\r\n\r\n

As you see, Comindware Tracker<\/a> allowed us to build a quite complicated CRM system, which is now helping us track all the important data about our customers and issues they experience, ensuring our support team provides high quality services. We do understand that there is always a room for improvement and we are ready to tune our processes when required, and thanks to Comindware Tracker and its ElasticData technology<\/a>, we are no longer limited technically.<\/p>\r\n\r\n

\n \n\n Get a 30-day trial!\n\n <\/a>\n<\/section>\r\n\r\n
\n
\n