An SLA clock has three kinds of condition. Start conditions decide when it begins counting; in this practice site every clock starts when the request is created. Pause conditions stop the count while the request sits in a status the team does not control, such as Waiting for customer. Stop conditions end the cycle, usually at Done or, for a first response goal, when an agent starts work.
The clock is therefore running, paused or stopped at any moment, and separately within its goal or breached. A paused clock can already be breached: pausing freezes the count, it does not refund time. A stopped clock keeps the time it had at the stop.
Choose conditions from the promise. "We resolve requests within two working days, not counting time we wait on you" needs Waiting for customer as a pause and Done as a stop. "We respond within two hours" needs a stop at the first agent action. This site keeps one cycle per request; hosted SLAs can restart cycles when a request reopens.
Pick pause and stop conditions from the promise you made.