An alert that disappears while attention stays elsewhere has technically fired, but it may not have changed the moment. Persistent acknowledgement is UP Timer’s answer to that gap.
The alert competes with the task already in front of you
A timer often reaches zero at exactly the point a person is most absorbed. The paragraph is nearly finished, the call is still active or the design problem has just become clear. A single chime enters that moment briefly and then leaves.
The user may genuinely intend to respond, but the screen still holds the strongest cue. Seconds later, the notification is gone and the task continues.
Persistent does not mean adding more different notifications
The product principle is simpler: keep the same due prompt active until there is a conscious response. The on-screen message remains visible, and the selected sound or male or female voice continues subject to browser permission and device settings.
It is to stop the selected transition disappearing without a noticed response.
One behaviour supports four different events
The work or break timer reached its selected endpoint.
The next point in the personal water routine arrived.
It is time to consider a safe change of position.
An immediate or scheduled learning window can begin.
Acknowledgement has a precise meaning
Pressing Acknowledge confirms that the alert received a response. It ends the active prompt and allows the timer to continue into the next state.
It does not prove that water was drunk, movement happened, a break was taken, learning occurred or focused work was completed. This boundary is essential for honest personal use and for any future Company product.
Control still matters
A prompt that waits must remain configurable. Users need appropriate timings, clear pause and reset controls, a choice of alert treatment and a way to enable or deny browser permissions deliberately.
Persistent acknowledgement should be noticeable, not punitive. If a timing creates repeated unnecessary interruptions, the right response is to change the routine rather than tolerate alert fatigue.
See the alert behaviour in the complete product flow.
The Persistent Acknowledgement page explains due, active and acknowledged states—and the clear limit of what acknowledgement records.