> For the complete documentation index, see [llms.txt](https://threadly.gitbook.io/threadly/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://threadly.gitbook.io/threadly/groups/dynamic-conversation-groups/planhat-segments.md).

# Planhat Segments

**Planhat Segments** are Dynamic Conversation Groups where membership is determined by your Planhat CRM data. Instead of manually selecting channels, you define filter rules based on customer health scores, lifecycle stages, renewal dates, or custom Planhat properties — and Threadly keeps the group current automatically.

{% hint style="info" %}
Planhat Segments require the **Planhat integration** to be connected. See [Planhat Integration](/threadly/integrations/planhat.md) for setup instructions.
{% endhint %}

***

## Why Use Planhat Segments?

If your Slack channels map to customer accounts (e.g., a `#customer-acme` channel for each customer), Planhat Segments let you:

* Send renewal reminders only to customers within 60 days of renewal
* Reach out to accounts with health scores below your churn threshold
* Automate lifecycle-based communications (Onboarding → Active → At-Risk)
* Scale customer success outreach without maintaining lists manually

***

## Creating a Planhat Segment

1. Go to the **Groups** tab in Threadly.
2. Click **New Group** and select **Dynamic Group**.
3. Under **Data Source**, choose **Planhat**.
4. Define your **filter rules** (see below).
5. Preview the matching channels.
6. Give the segment a name and click **Save**.

***

## Available Filter Properties

| Property              | Type   | Example Filter                            |
| --------------------- | ------ | ----------------------------------------- |
| **Health Score**      | Number | Health Score less than 40                 |
| **Lifecycle Stage**   | Text   | Lifecycle Stage equals "Onboarding"       |
| **Renewal Date**      | Date   | Renewal Date within 60 days               |
| **ARR**               | Number | ARR greater than 10000                    |
| **Custom Properties** | Varies | Any property you've configured in Planhat |

***

## Example Filter Rules

**Target at-risk accounts:**

> Health Score **less than** `40`

**Target renewal pipeline:**

> Renewal Date **within** `60` days

**Target onboarding accounts:**

> Lifecycle Stage **equals** `Onboarding`

**Combined — at-risk AND enterprise:**

> Health Score **less than** `40` **AND** ARR **greater than** `50000`

***

## How Channel Matching Works

Threadly maps Slack channels to Planhat records using a field you configure during setup (typically the company name or a custom Slack channel field stored in Planhat). When a record matches your filter rules, the corresponding Slack channel is included in the segment.

Segment membership refreshes automatically each time you send a message or trigger a workflow using this group.

***

## See Also

* [Planhat Integration](/threadly/integrations/planhat.md) — connect your Planhat account
* [Dynamic Conversation Groups](/threadly/groups/dynamic-conversation-groups.md) — overview of how dynamic groups work
* [HubSpot Segments](/threadly/groups/dynamic-conversation-groups/hubspot-segments.md) — similar setup for HubSpot users
* [Attio Segments](/threadly/groups/dynamic-conversation-groups/attio-segments.md) — similar setup for Attio users


---

# 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 dynamically by asking a question.

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

```
GET https://threadly.gitbook.io/threadly/groups/dynamic-conversation-groups/planhat-segments.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.