How to Push Emergency Announcements to Employees in ServiceNow

[Kohei Tominaga1]

I'm looking for a way to push emergency announcements to employees in ServiceNow, specifically during a disaster or other critical event. The goal is to reduce the number of inquiries to HR during these times.

For example, we want to provide employees with information on:

• Workforce changes: Shift changes, work from home policies, or closures.
• Mental health support: Resources for dealing with stress and trauma.
• Benefits and pay: Information on leave, pay, and other benefits related to the event.

We've considered Knowledge articles, but while they're useful for employees to search, we need a way to proactively push this information to them. We're aware of the Campaign and News Center features, but I'm not sure if these are designed for direct content creation in a production environment.

Ignoring internal governance processes for now, what are some features in ServiceNow that allow us to immediately push emergency announcements to employees?

I'm open to any suggestions, even if they require some customization or scripting.

Note: I'm not asking about specific implementation details, but rather the best overall approach for achieving this goal.

Thank you for your help!

[Sid_Takali]

Hi @Kohei Tominaga1 https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0727669 

[Pooja_Patil]

@Kohei Tominaga1 , can you elaborate on "I'm not sure if these are designed for direct content creation in a production environment"?

Content Publishing provides many different content types that suit your needs such as banner, announcement, rich content, news etc.
Refer this - https://www.servicenow.com/community/employee-center-articles/content-experiences-and-publishing/ta-...

Content author can create content and publish it to desired audience and pages in any environment, in fact content should be designed in the environment you want to publish it to.

Please mark this as Helpful / Accept the Solution if this helps.

[Pooja_Patil]

Please mark this as Helpful / Accept the Solution if this helps.

[Kohei Tominaga1]

Hi, @Pooja_Patil 
Thank you for your reply.
Our CoE defines that configurations should be done in Dev instance and migrate them to Prod after testing and only Tickets and Knowledge articles can be created directly in Prod instance.
In my scenario, announcement have to be created directly in Prod so that it could be announced soon.

I have not yet learned about Content Publishing, is there any reason the content could be created in Prod?
It would help me to talk with our CoE.

[Pooja_Patil]

There are 3 key pieces for publishing a content - what we want to publish (content), where we want to publish it (portal - page & widget), and who should see it (audience).

The reason we advise to design the content in the environment you want to publish is page, widget and audience setup could be different between environments. If the setup matches exactly you could export content and schedules from one environment and import it to another.

We provide an option to visualize the content in portal before publishing it. When you design a content, you will see Preview in portal button on the publish plan when you select desired page, and widget.