> For the complete documentation index, see [llms.txt](https://docs.truecaller.com/truecaller-for-business/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.truecaller.com/truecaller-for-business/managing-feature-sets.md).

# Managing Feature Sets

The Feature Set listing page is your central workspace for managing all day-to-day operations related to your feature sets. You now get a consolidated view where you can quickly access, review, and manage everything in one place, instead of navigating through multiple layers of the organisation structure.

From this page, you can:

* View all your feature sets in a clean, organised table
* See important details like Caller ID type, listed numbers, active features, and last updated information
* Perform key actions such as viewing stats, archiving, deleting, or copying the feature set ID
* Search and filter feature sets to find what you need faster
* Create new feature sets through a simplified, guided workflow

This page gives you a faster, more intuitive way to handle your daily tasks, whether you're listing numbers, updating features, or reviewing analytics, ensuring smoother operations with fewer clicks.


---

# 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.truecaller.com/truecaller-for-business/managing-feature-sets.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.