I’ll try to clarify this, let me know if it helps or if you need further information, I could update the documentation then.
The SLA is only accounted within the provided business hours (that’s why you need to define a calendar).
So short: The SLA will respect weekend, holidays and times where your company is not in service.
This means if you have a first response time of let’s say 2 hours, your business time ends at 5pm and your customer sends his mail at 4pm, then the ticket will not escalate on this day (as it would have to escalated at 6pm). Instead, it will escalated one hour after your next working day has started.
When using SLA it’s important to know, what Zammad counts as response and what not.
Responses are all article types that are public / the customer can see so:
- Public Notes (not default! Can be adjusted via Console)
- E-Mails sent to the customer
Private messages are no response, even though you’ve been working on the ticket!
Most SLAs are only set to open tickets (which makes sense) but not to pending states.
So if you have a ticket in a pending state all the time (no matter if you’re waiting for a customers feedback or not) the SLA will not kick in, the ticket won’t escalate.
First response Time
First response time can be up to 99 hours (if you use arrow up you can trick zammad, not sure how this affects calculation!). This actually is about the first response you give your customer to the ticket (and is one time).
If you have no upcoming values like update time or solution time, the SLA chain will end at this point.
Update time can get quite troublesome, it describes the time frame between each valid response the agent has time for working on the issue. If you choose this value too small, you’ll have escalating tickets all the time. This value is calculated from the last ticket update with public article and so can be “extended”.
This one is global and can’t be resetted. It should always be bigger than first response, as otherwise you don’t have the slightest chance.
This calculates the resolution time from the ticket creation time. So if the ticket solution is set to 1 hour you have one hour from ticket creation to solve the issue, other wise it will permanently escalated.