> For the complete documentation index, see [llms.txt](https://help.gleantap.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.gleantap.com/audience/using-segments.md).
# Using Segments
How to use your pre-built segments within Gleantap
Once you have finished creating your segments, what comes next? There are a variety of different ways to use your segments once they are created, which we will explore below.
### Campaigns
The most obvious use case for segments is when setting up Email and SMS campaigns.
On step 3 of an Email campaign you will see all of your segments available for you to choose from. You can select multiple from this screen, as well as exclude other segments you want to avoid.
On step 2 of an SMS campaign you will see all of your segments available for you to choose from. You can select multiple from this screen, as well as exclude other segments you want to avoid.
For Ongoing campaigns, make sure the segments you are selecting have been set up as Dynamic segments to make sure they work properly.
### Flows
Flows, like campaigns, are triggered by Dynamic Segments. When setting up your Flow, you will see your segments listed and can choose from the list to activate the Flow.
You can also use Segments on the third step of a Flow to 'unenroll' from a Flow as well.
### Automations
Sales Automations are another area where you can use Segments to help run your account. When creating a new automation, one of the options for the Trigger is 'added to a segment,' which means that anyone in a segment or later added to a Dynamic Segment will trigger the automation.
### Inbox
The last way to use Segments in your account is through the inbox. Each segment you make is automatically added as a Group you can text through the inbox.
You can also filter by segment to see responses from a certain group of users. In the Inbox, click on this button to open your filters.
Then you can select from Choose Segment to see responses from only the people in the segment.
---
# 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://help.gleantap.com/audience/using-segments.md?ask=&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.
