> 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/how-can-i-create-a-new-feature-set-from-the-listing-page.md).

# How can I create a new feature set from the listing page?

You can create a new feature set directly from the listing page by selecting **"Create New Feature Set."**\
The creation flow is now a simplified two-step process:

1. **Select or auto-populate your organisation structure**\
   (Based on RBAC, the system may auto-fill your department/operation.)
   1. **If needed a new department/operations/process can also be created**
2. **Give the feature set a unique name**

After confirming, your feature set is created, and you can proceed to configure features and numbers.

{% hint style="info" %}
Note : The maximum char limit for a Feature Set name is 40 characters.
{% endhint %}

<figure><img src="/files/sduFaXwf8G3dirTltRZD" 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 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://docs.truecaller.com/truecaller-for-business/managing-feature-sets/how-can-i-create-a-new-feature-set-from-the-listing-page.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.