Godiva Escalation Contacts

Identify escalation contacts for Godiva incidents by severity and domain.

Updated Apr 24, 2026

Search Tags:#on-call #roles #escalation #notification #incident-management #godiva #after-hours

Ready to run

npx skills add https://github.com/myriosMin/godiva --skill godiva-escalation-contacts

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Godiva Escalation Contacts
Source: https://github.com/myriosMin/godiva/tree/main/claude-managed-agents/skills/godiva-escalation-contacts
Command: npx skills add https://github.com/myriosMin/godiva --skill godiva-escalation-contacts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Role-based escalation contacts for Godiva incidents — who to notify by severity tier and domain, with escalation paths and after-hours rules.

Core Features & Use Cases

Role-based escalation logic by severity and domain across Payment, Core / SAP, Infrastructure, MyTengah, Channel / uPortal, Support, EV, and Content.
Clear escalation paths with backups and after-hours rules to ensure timely responses.
Centralized guidance for incident response, approvals, and vendor escalation as required.

Quick Start

Consult the escalation contacts to determine who to notify for a given incident severity and domain.

Frequently Asked Questions about Godiva Escalation Contacts

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I identify the correct escalation contacts for Godiva incidents by severity and domain?▼

To identify escalation contacts for Godiva incidents, match the incident severity tier (Critical, Major, Minor) and domain (Payment, Core, Infrastructure, MyTengah, Channel/uPortal, Support, EV, Content) to the designated role-based notification paths.

What are the after-hours rules for Godiva incident notification and escalation?▼

After-hours rules for Godiva incident notification dictate specific backup contacts and alternate escalation paths to ensure timely responses outside standard hours, maintaining continuous incident management coverage across all severity tiers.

Who should I notify for a Critical incident in the Payment or Core domain?▼

For a Critical incident in the Payment or Core domain, notify the designated role-based escalation contacts, including primary responders and specified backups, to accelerate response and fulfill policy-driven routing requirements.

Does Godiva incident escalation routing policy support backup contacts for Infrastructure and MyTengah domains?▼

Yes, Godiva incident escalation routing supports predefined backup contacts for Infrastructure and MyTengah domains. This ensures continuous notification and documented escalation paths if primary on-call roles are unavailable.

What is the best way to structure role-based approvals and vendor escalation for Godiva incident management?▼

The best way to structure role-based approvals for Godiva incident management is to follow the centralized escalation guidance, which maps severity tiers and domains to specific approval roles and required vendor escalation paths.

When do I need to use after-hours escalation paths instead of standard incident notification routes?▼

You need to use after-hours escalation paths when incidents occur outside standard business hours, triggering specific backup contacts and alternate notification rules to maintain timely response and resolution.