Sensitive/Crisis Management Configuration

Sensitive configurations are your automated early‑warning system. They are designed primarily to detect potential crises and sensitive topics, not necessarily to respond automatically.

Use Sensitive configurations for issues such as:

• Allegations of corruption or misconduct
• Legal issues and lawsuits
• Data breaches or security incidents
• Service outages, scandals, or other high‑risk events

Creating a Sensitive configuration

When setting up a Sensitive configuration, you will typically define:

1. Title – A descriptive name (for example, "PR Crisis", "Legal Issue", "Service Outage").
2. Keywords – Sensitive words or phrases to monitor (for example, "corruption", "lawsuit", "data breach", "scandal").
3. Severity Level – A level such as Low, Medium, or High, used to prioritize alerts.
4. Action – What should happen when a match is detected. This often includes:
   • Flagging – The post is immediately flagged for human review.
   • Alerts – Specific team members or mailing lists are notified via the platform and/or email.

warning

Sensitive configurations should be designed in close coordination with your communications, legal, and leadership teams. They directly affect how quickly your organization becomes aware of potential crises.

Typically, sensitive posts are escalated to humans rather than answered automatically. They will appear in the Manual Response Queue for review.