> 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/manage-listing/how-do-i-list-phone-numbers-using-manage-listing.md).

# How do I list phone numbers using Manage Listing?

1. From the “Operations” page on your console, navigate to “Manage Listing”, on the top right corner.
2. Select the "List numbers" option from the drop down menu.
3. A right sidebar modal will open with options to select Department, Operations, Process, Subprocess, and Feature Sets for which you wish to list more numbers.
4. Upload your list of numbers as a CSV file. Note that your CSV file should not exceed 2MB.
5. You will see two options for your file - Rewrite and Append.
   1. Rewrite: This action will delist your existing numbers from any of the feature sets that you have access to including priority badged numbers and add the list of new numbers uploaded in the CSV.
   2. Append: This action will list your new numbers from the CSV along with the existing numbers for your selected feature set.
6. Click the "Publish" button to submit.
7. Numbers will be validated, and successfully formatted numbers will be listed.

<figure><img src="https://1505116975-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyWoE7a7EzgrlGFIoECsj%2Fuploads%2FXhunSdjUtAL4h9s4KT4F%2FTruecaller%20for%20Business%20(1).gif?alt=media&amp;token=0ce053c1-275b-44fd-8a1f-0832b91a18bc" 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 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/manage-listing/how-do-i-list-phone-numbers-using-manage-listing.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.