The first thing to note is that Help Scout has no built-in SLA feature — something we consider to be a necessity in any customer service organization. Instead, Help Scout suggests tracking the aging of conversations using a combination of different features to create an SLA-like experience.
We recommend:
We added tags to track conversations that had nearly reached an SLA threshold or had already crossed one so that we could easily identify them. This required setting up workflows for SLAs and setting the workflows to run in the appropriate order. Unfortunately, this isn’t a perfect solution, because workflows can only run once per conversation.
While Help Scout’s automation system is quite versatile and can be used for many use cases, it quickly becomes difficult to manage for a large organization. Automatic workflows only run once per conversation (not per thread). This is a serious drawback when you consider that conversations can be revived by customers at any time.
We added tags to track conversations that had nearly reached an SLA threshold or had already crossed one so that we could easily identify them. This required setting up workflows for SLAs and setting the workflows to run in the appropriate order. Unfortunately, this isn’t a perfect solution, because workflows can only run once per conversation.
We added tags to track conversations that had nearly reached an SLA threshold or had already crossed one so that we could easily identify them. This required setting up workflows for SLAs and setting the workflows to run in the appropriate order. Unfortunately, this isn’t a perfect solution, because workflows can only run once per conversation.