# Answer an outage question in live chat, with the evidence

> The EU checkout outage from ticket #4821 arrives in the chat bubble. Support investigates the chat and answers while the visitor waits.

Source: https://triagic.com/use-cases/outage-on-live-chat

{/* The visitor's message and the short reply are scene wording, consistent
    with the landing page. The reads, the finding and the reply facts are
    ticket #4821's (support-without-escalation.mdx). */}

## The situation [#the-situation]

14:09 UTC, two minutes after Zendesk ticket #4821 came in. A visitor on the checkout page opens the chat bubble: *"Our EU checkout has been failing since about 14:00 UTC. Is this on your side?"*

The desktop apps of the people on duty ring: *A visitor is waiting*. Maya, tier-1 support, accepts. Messages and files are end-to-end encrypted between the visitor's browser and her app, through a relay that neither Triagic nor Cloudflare can read.

A chat is worse than a ticket for guessing. The visitor is waiting on the other side, and "we're looking into it" is the only safe answer when you can't see the systems.

## What Triagic looked at [#what-triagic-looked-at]

Maya pressed **Investigate this chat**, picked the support playbook and the integrations to use. Read-only, the same reads as the ticket:

- **Postgres**: `SELECT status, count(*) FROM orders WHERE region='eu' GROUP BY status`. 41 failed, 3 paid since 14:00, inside a read-only transaction.
- **Sentry**: new issues since 14:00. 312 new `StripeCardError` events, first seen 14:02 UTC.

## What it found [#what-it-found]

EU card charges started failing at 14:02 UTC, four minutes after the checkout-refactor rollout. US and APAC are clean.

The suggested reply was drafted from those numbers: *"You're right, and it's on us. A change we shipped at 15:58 CEST broke EU card payments. It's rolled back and payments are going through again."* Maya pressed Send at 14:11.

## What changed [#what-changed]

The visitor got a real answer in the chat, two minutes after asking, from support alone. Maya saved the chat as a ticket, so the conversation and the evidence stay with the request instead of in a closed chat window.

Live chat is off until Triagic support turns it on for your organization; admins then set up widgets, allowed sites and the team to ring in the portal. The same outage, as a ticket: [fewer escalations to engineering](/use-cases/support-without-escalation). See [Triagic for support teams](/for/support-teams).
