Execute Emergency Response

Step 3: Real Emergency Routing (CRITICAL only)

5. For CRITICAL severity: Initiate outbound call or SMS via Azure Communication Services to local emergency number.
6. Provide emergency dispatcher with: user's registered name (if available), nature of concern, consent status.
7. NEVER transmit Tier 1 conversation content to emergency services — only the nature and severity of the concern.

Step 4: Legal Protocol

8. Notify chief-legal-officer within 5 minutes for duty-to-warn evaluation.
9. CLO determines mandatory reporting obligations (Tarasoff duty, child abuse mandatory reporting, elder abuse).

Step 5: Session Management

10. Lock affected session — only human clinical reviewer can clear.
11. Quarantine all pending Tier 3 outputs.
12. Partner receives warm, brief message:

• EN: "Your partner is taking a moment. We're making sure everyone's okay."
• ES: "Tu pareja se está tomando un momento. Estamos asegurándonos de que todo esté bien."
• HE: "בן/בת הזוג שלך לוקח/ת רגע. אנחנו מוודאים שהכל בסדר."
• Tone: caring and brief — not clinical. See israeli-hebrew-tone-guide for HE.

Step 6: Post-Crisis Follow-Up

13. Schedule automated check-ins: 24h, 72h, 7-day follow-ups via push notification + in-app message.
14. Each check-in asks: "How are you doing? Would you like to connect with a professional?"
15. If user does not respond to 7-day check-in, escalate to human clinical reviewer.

Step 7: Audit Trail

16. Log every action to Azure Blob Storage (append-only, immutable):
    • Timestamp, severity, user_id (hashed), locale, resources delivered, emergency service contacted (Y/N), CLO notified (Y/N), session lock status, follow-up schedule.