# Example: Slack thread to team convention

> A Slack thread becomes company context when the durable convention is saved, scoped, and linked back to the source.

## Source to memory

Source artifact: Slack support thread.

Source excerpt: Every escalated handoff needs an owner, a timeframe, and the next action. If one is missing, the agent asks before continuing.

Ambience memory:

- Type: convention
- Title: Escalated support handoffs need owner, timeframe, and next action
- Body: Support escalations name the owner, expected timeframe, and next action before an agent drafts or sends the handoff.
- Scope: team
- Tags: slack, support

Controls:

- Source: thread link is kept for reviewers with Slack access.
- Redaction: customer details stripped from the memory body.
- Scope: support team until adopted company-wide.

Future reuse:

- A future support agent follows the handoff convention without reading the thread.
- A manager can audit why the agent asked for missing ownership details.

## Why Ambience

- Threads are easy to lose.
- Conventions are high-leverage memory.
- Ambience stores the reusable rule, not the entire conversation.

## Related

- [Slack connection](https://ambience.sh/connections/slack)
- [Company context from Slack](https://ambience.sh/company-context/from-slack)