Do you have a dumb question that you're kind of embarrassed to ask in the main thread? Is there something you're just not sure about?
This is your opportunity to ask questions. No question too simple or too silly.
Culture war topics are accepted, and proposals for a better intro post are appreciated.
Jump in the discussion.
No email address required.
Notes -
What's the deal with 3-4 day email customer service response times?
Had a warranty issue and emailed the brand, which replied with an auto responder that I should expect a reply in 3-4 days.
For the sake of this question, let's assume for this question that the autoresponder is telling the truth, and that it's been at this wait period for months now.
Email accumulates and does so asynchronously, so a 3-4 day backlog doesn't disappear if you don't get to it quickly. Hypothetically, if the entire team got together and crunched through the queue, then theoretically they could shave the response time to 0-1 days in perpetuity. Similarly, if the team all took a vacation for a week, then the queue would become 10-11 days in perpetuity.
Unless I'm missing something, it seems like there is no good business reason for an email queue to be 3-4 days steady state. It would either stretch to infinity due to understaffing, cut down to zero if there is excessive staffing, or be managed into a 0-1 day queue with a one time crunch push if staffing is accurate. In what universe could a capably managed team have to deal with a 3-4 day email response time on an ongoing basis?
There's nothing inherently contradictory at all about what you describe, because you are calling it a queue when it is really a pipeline, and process pipeline's length is not directly related to its capacity. For example, you could have a process pipeline that contains certain things that just inherently require time, such as review by multiple people who process daily batches.
More options
Context Copy link
Your question is reasonable. I've always assumed (without evidence) that "steady state" isn't perfectly steady, and overprovisioning to get to zero backlog constantly would be expensive. Both short-term day-to-day noise and seasonal effects (few warranty claims on snowblowers in July) could make volumes unpredictable, and a couple of days slack would let you schedule shifts based on volume.
Although as Oracle pointed out, it could be a contractual obligation. I've certainly had interactions with, say, insurance where I've been quoted 60 days to evaluate a claim, but gotten a response within a week.
More options
Context Copy link
It's the SLA (Service Level Agreement) that the customer service company set up with the brand.
I don't know what company you're emailing, whether it is large or small, but it is likely they outsource some of their support to a multi-client service desk that can handle tier 0 or tier 1 requests. The company is paying for a 3-4 day SLA, and if the service desk goes over that length of time there are penalties. Because the multi-client service desk has a multitude of clients, each with a different cadence for emails, the service desk will prioritize emails according to SLA, ensuring all emails are answered with the least financial penalty to the service desk.
I don't have any experience with 3-4 day SLAs (that seems excessive to me) but I have seen emails sit in a queue all day, getting answered by the night guys at 10 PM, because the SLA was 24 hours and other companies had <2 hour SLAs.
More options
Context Copy link
More options
Context Copy link