# Link chats to an incident and tell customers when it ends

Source: https://frosvo.com/docs/link-chats-to-incidents
Updated: 2026-11-06

Link the chats of customers hit by a known problem to an incident on your status page, pass on your updates, and tell each of them once when the incident is resolved.

When one fault affects many customers, you end up answering the same question in many chats. Linking those chats to the incident lets you close the loop for all of them in one step: when you resolve the incident, each linked customer who is still waiting gets one message.

## Before you start

You need an incident on one of your [status pages](/docs/status-pages). It must be open (investigating, identified or monitoring) to be linked. Incidents from other workspaces never appear.

## Steps

1. Open a customer's conversation and expand **Linked incident** in the side panel.
2. Choose the open incident, then **Link**. Repeat for every chat affected by the same problem.
3. Carry on helping people as usual. If you post a public update on the incident, linked customers with an open chat get your words as a short message (the newest update only, at most one every ten minutes). Updates on a private status page are never sent.
4. When you resolve the incident on the status page, Frosvo sends each linked, still-open conversation a short reply saying the problem has been resolved and inviting them to reply if they still see an issue.
5. The panel then shows **Resolved, customer told**.

## Find chats that may be affected

On the status page screen, open **Incidents & maintenance** and choose **Related chats** on an ongoing incident. Frosvo lists open chats from the last three days that mention the same words as the incident title and its components. This is only a proposal: tick the chats that really are about the incident and choose **Link**. Nothing is linked or sent until you do. Very generic words such as "slow" or "error" are ignored, so a vague title may find no suggestions.

## What is sent, and what is not

The reply names the incident only if its status page is public. It never includes details of other customers or other chats. Conversations that are already closed are skipped. A link can be removed until the customer has been told, and an incident can be linked to up to 500 conversations.

## Common problems

- **The incident is not in the list.** It is already resolved, is a scheduled maintenance, or belongs to a different workspace.
- **The customer was not told.** Their conversation was closed when the incident was resolved, or the reply could not be sent in that channel. Reply by hand.
- **Monitors resolved it by themselves.** An incident opened and closed by a monitor counts as resolved, so linked customers are told when the monitor sees recovery.

## Related

See [status pages](/docs/status-pages), the [inbox](/docs/inbox), the [progress card](/docs/customer-progress-card), the [needs-attention queue](/docs/needs-attention-queue) and [asking a customer for details](/docs/ask-customer-for-details).

## Common questions

### Are chats linked to an incident automatically?

No. Your team chooses which conversations belong to an incident. Nothing is guessed from the wording of a message.

### Who is told when the incident is resolved?

Only customers whose conversation you linked and that is still open. Each is told once, in their own conversation. Closed conversations get nothing.

### Does the message show the incident title?

Only when the incident is on a public status page. For a private status page the message just says the problem was resolved.

### Can I undo a link?

Yes, until the customer has been told. After that the link stays on record so you can see who was told.
