# Internal Channels & DMs

### Internal Customer Channels

Use Internal Slack Channel Connections to link your team’s internal Slack channels to the corresponding customer account in Pylon. For example, your `#deal-customer` or `#internal-customer` channels.  You can also create a ticket from an internal channel by reacting with ":ticket:" emoji ![:ticket:](https://a.slack-edge.com/production-standard-emoji-assets/14.0/apple-medium/1f3ab.png).

\
This ensures customer context from internal conversations shows up directly in the account view and AI fields.

* Once connected, Pylon will pull up to 90 days of message history, making relevant context searchable and visible in account notebooks, AI fields, and more.

<figure><img src="/files/oQbwEhVHdJ8Di1ZntCjg" alt="" width="375"><figcaption></figcaption></figure>

* You can use these internal channels as targets for notifications via triggers.

<figure><img src="/files/C5LGJy89k0Tfu5SO6kBI" alt="" width="375"><figcaption></figcaption></figure>

### Internal Team Channels

You might have broader internal channels like `#sales` or `#customer-success-team` where you discuss context on customers, including competitive intel, churn risk notes, or other meaningful context.

On the [Training Data](https://app.usepylon.com/settings/ai-controls/training-data) page you can connect an internal channel and Pylon will backfill 90 days of context, as well as watch for new messages. Pylon will attempt to automatically associate context to the relevant account, making it available in all AI features like [Notebooks](/pylon-docs/account-intelligence/notebooks.md).

<figure><img src="/files/o4cxeRbetJvd5rD76akG" alt="" width="316"><figcaption></figcaption></figure>

<figure><img src="/files/3SoUYDSyXCHf6Rqrthbp" alt=""><figcaption></figcaption></figure>

### Slack DMs

You can log context in Pylon associated with the right account from your Slack DMs - for example conversations with champions, buyers, or users.

These messages get fed into Pylon AI and are available across the platform as context, for example in [Notebooks](/pylon-docs/account-intelligence/notebooks.md).

<p align="center"><img src="/files/24urZ3qHEFle1cqCRN0R" alt="" data-size="original"> </p>

Learn more on how to sync direct messages [here](https://support.usepylon.com/articles/1133928219-how-to-track-slack-dms-in-pylon?lang=en).


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.usepylon.com/pylon-docs/account-intelligence/accounts/internal-channels-and-dms.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
