Feature Request: Capability to suppress the "Operating hours have started" Notification

Working towards migrating off zendesk and this is one of the primary reasons. Absurd that this issue has persisted this long.

An older request but something, as rightly said above, is not needed for all cases. A way to supress this message would be ideal for the majority it seems.

Hello again.
I haven't seen any solution available for this problem.
Our situation is as follows:
there are agents with a chat license who have hours to manage the chat and hours to answer tickets, this means that while they manage the tickets (other agents are managing the chat) they continually get this annoying message "Operating hours have started" and they complain because they have no way to avoid it.
I really hope it's included in the roadmap as soon as possible.
Regards.
Mary

Hi Zendesk team, is this on the roadmap? The workaround is not viable for our teams. Thanks

I completely share the sentiment that this message is extremely annoying. It's become a daily nuisance, and it's gotten to the point where I cringe when I see it. It's definitely not the kind of experience I'd like to kick off my day with.

The suggested workaround is quite convoluted and impractical. Creating a separate group or department, configuring operating hours, and employing JavaScript APIs seems like an overly complicated solution for a feature that we didn’t request.

It'd be so much better if the system could address this problem directly, rather than making us jump through hoops.

Such an annoying message.  We know our chat hours have started.  It's our job.  We do it every day.  I don't need to see this day after day.  Allow us to turn this warning off completely.

Thank you 1263082075849 for the reply. Please, would really appreciate the ability for admins to assign a permission to allow certain users to suppress alerts in Agent Workspace!

Hi Dan, 

We don't support the Operating hours started notification suppress capability that's been called out and something we'll evaluate in the context of AW. This problem is not valid from the Messaging and OCC point of view and something specific to chat product. 

Hey Shawna,

Not really an option, as we're not working with JS APIs with the web widget. We only have/need one department, creating more and then getting developer resources to write some custom scripting to the widget isn't a practical solution.