> For the complete documentation index, see [llms.txt](https://docs.usepylon.com/pylon-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usepylon.com/pylon-docs/integrations/chat/slack/left-company.md).

# Left Company

Receive real-time notifications when champions leave or join your customer Slack channel

## **How quickly do you know that your champion has left your company?**

Pylon can notify your team when a customer leaves a connected Slack channel.

A leave alert includes **Reason: Left company** when Slack reports that the person's Slack account is deactivated. This label is based on Slack account status. Pylon doesn't independently verify employment status.

Turn this on in **Settings > Channel membership alerts** ([open](https://app.usepylon.com/settings/membership-alerts)) with **Channel Join Alerts** and **Channel Leave Alerts**. By default, alerts go to the triage channel for that customer. Pick a **Membership Alerts Channel** to send them somewhere else instead.

<figure><img src="https://mintlify.s3-us-west-1.amazonaws.com/pylon/images/channel-leave.png" alt=""><figcaption></figcaption></figure>

We also track when new members join channels, and notify you the same way.

<figure><img src="https://mintlify.s3-us-west-1.amazonaws.com/pylon/images/channel-join.png" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.usepylon.com/pylon-docs/integrations/chat/slack/left-company.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
