Practicality of having a 24 hour SLA for "task update" goal.

[David Quiram]

My boss would like to have a 24 hour SLA to help the team keep on top of performing a daily update on tickets. He likes the visual of having the SLA timer on the screen when you are looking at a task and seeing how long you have on the timer. 

He would like the feature to function in a way where when the agent performs an update on the task, the timer gets reset and a new 24 hour timer is started. 

This works in the scenario of just performing a reply to the end user within 24 hours and having automatic status transitions. Using statuses like "Agent Updated" and "Employee Updated" for direct examples. 

What makes this a little more complicated is sometimes we have to perform research, testing, and some planning on some requests. In those instances we wouldn't have an update for the user to perform that status change. We might end up using a couple of different statuses to indicate what's going on with the task, but he would still like an update on the task every 24 hours. 

I tried some testing using internal/external comments to flag the SLA to start/stop, but it would require two SLA timers to juggle which one was counting. A single comment trigger couldn't be used to both stop an SLA and start a new instance of the same SLA. 

Right now I have a temporary solution of automated comments if a task wasn't updated in the past 24 hours, but isn't not the mechanical SLA function that he would like to utilize. 

Is there a way to achieve what my boss is wanting with the native SLA functionality?