Skip to main content
Aug 7, 2015 11:07 PM UTC

TS BEST Practices - Case Status

Hey everyone,

 

I've been thinking about how people might use Case Status in Salesforce in different ways and that it would be nice to understand what the practical uses are for each status and develop some best practices for us as TSEs to follow. Below is what I have come up with so far. I'd love to get your feedback regarding it!

 

New:

  • Cases exist in this status for the short time between the creation of the case and the time cs_ptc sends the “Thank you for submitting your question to us” email
  • Cases remain in this status when it has been created by the TSE using the New TS Case or Clone action in Salesforce
  • A TSE would have no practical reason to set a case to this status
  • As a best practice, TSEs should not be owning any case in “New” status for an extended period of time

 

Assigned:

  • Cases are not given this status in any automated use case
  • Only practical use of this status might be when someone QB’ing a queue assigns a case to a particular TSE who will own it
  • Cases should not be in “Assigned” status for an extended period of time, if at all

 

Working:

  • Cases should be in this status when a TSE is actively working on a case having all the information needed to continue to work on the case
  • As a best practice, cases should be in this state when requesting a patch for a closed SPR or if the TSE has an open case assistance thread to tech leaders or R&D, even if they are waiting for that assistance.

 

Working – Information Requested:

  • Cases should be in this status when a TSE is actively working (even in a limited fashion) on a case but has requested some sort of information from the customer and is waiting for this information to more fully investigate the issue
  • Typically this status is first set following a first contact when a TSE has requested several pieces of information to clarify the issue (e.g. logs, screenshots, answers to questions) and when such information is requested throughout the case
  • This status can be used even when requesting the smallest piece of information, for example, asking the customer what time would be best to conduct a WebEx
  • If a customer hasn’t provided the information needed for the TSE to continue working over a period of time, requiring the TSE to follow up (to avoid stagnancy) then the TSE can move the case to On Hold – Waiting on Customer

 

On Hold:

  • This status, without a sub-status, does not provide much clarity as to why a case is not presently being worked.
  • This status is not frequently used.
  • One way it might be used is when a customer has already validated a solution but the TSE is working to improve an article attached to the case and perform case cleanup before closure

 

On Hold – Waiting on Customer:

  • This status means work cannot continue on the case until information requested by the TSE has been provided by the customer
  • In this status it may not be practical to send an email each week to a customer to prevent stagnancy but instead use a combination of emails and customer-viewable case comments
  • In rare cases (e.g. intermittent issues where logging has been requested), it may be practical for a case to go from this status to On Hold – Awaiting Customer Validation even if a solution has not been provided, in order to lengthen the stagnancy period

 

On Hold – Waiting on Third Party:

  • An extremely rare status signifying that we are waiting on an external resource to move forward
  • Example?

 

On Hold – Waiting on Partner:

  • An extremely rare status signifying that we are waiting on an official PTC Software Partner to move forward
  • This status might be used, for example, when waiting for Adobe to respond to a Live Cycle issue which is causing the Creo View Adapter for Microsoft Office to fail

 

On Hold – Awaiting Customer Validation:

  • The only status with a 30-day stagnancy period
  • A high-confidence solution has been provided to the customer and the TSE is waiting for validation that the issue is resolved
  • A patch has been provided to the customer for them to deploy and validate

 

Information Received:

  • This status is set whenever an email (not sent by the case owner), a comment, or an attachment has been attached to the case
  • Cases in this status often indicate that information has been provided and work needs to be done by the TSE
  • In some instances, this status has been triggered but no work necessarily needs to take place yet (e.g. a customer replying that they will attempt some procedure over the weekend)
  • In these cases, the TSE should take care to set the status back to an appropriate status
  • As a best practice, TSEs should try to minimize cases in this status by processing new information provided by the customer in working towards case resolution

 

SPR Filed:

  • Nothing triggers this status
  • I’m not exactly sure what this is even supposed to convey since action should be on either R&D or on the TSE.
  • The only possible use for this status might be if an SPR is in Needs Info state and work is needed to be done by the TSE.
  • Because it remains in SPR Filed, it’s up to the individual to make sure they are doing what is necessary to get this additional information for R&D to continue.

 

SPR Filed – Waiting on R&D:

  • This is the most common sub-status for SPR Filed and typically means just what it says, that we are waiting on R&D to provide an answer or a fix to a particular SPR.
  • These SPRs are worth taking a look at to see what kind of communications are in the SPR Notes in order to understand R&D’s progress.
  • It’s also worth observing the Expected Release Stream, Ship Priority, and build values in the Tasks List.
  • All this information may helpful in communicating to the customer when a fix might be expected.
  • If the fix is slated for a release down the road, it might warrant marking its related KCS article as Public if it wasn’t already, so that customers can readily find information about the issue

 

SPR Filed – Evaluating Resolution:

  • This status is triggered when a verification task on the SPR has been completed.
  • It will place a comment in the case.
  • If the comment says something like “Related SPR XXXXXXX was verified in Release X-24_M030_22” that’s great because a fix was made in a build of 10.2 M030!
    • If the customer wants to verify this resolution, then the case can remain in this state until they actually have it installed and ready to verify, then it should move to On Hold – Awaiting Customer Validation.
    • Sometimes, the customer isn’t interested in verifying the fix and will simply ask to close the case.
  • If it says something like “Related SPR XXXXXXX was verified in Release null” things get a little more complicated, as this means a task was closed and verified without a fix.
    • Looking at the SPR, you might find that they decided not to implement a fix for a certain release (e.g. no more builds scheduled) but there are other releases/tasks still open.
    • In this case, set the sub-status back to SPR Filed – Waiting on R&D (and let the customer know if they shouldn’t be expecting a fix for their release).
    • You may find that the all the tasks are closed, thus closing the SPR as works to specification or no plans to implement.
    • At that point, the case is back to the TSE to communicate back to the customer (with the TSAM if necessary) and needs to come out of SPR Filed status.

 

Because of it being rare that I will need to have any customer interaction until the patch is delivered I have used "SPR Filed - Awaiting on R&D" status once the patch has been filed and the customer has been given the ECD. I'll then usually keep an eye on the patch generation thread and update the customer/R&D with anything they need.

 

This document was generated from the following discussion: Case Status Best Uses/Best Practices