> 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/features/call-reason/how-do-i-add-a-new-call-reason.md).

# How do I add a new Call Reason?

You can now create call reasons using Gen AI.

1. To create a new call reason, click “Create New” after activating the Call Reason toggle on the Feature Set Configuration page.
2. Type or select your industry from the dropdown menu.
3. Type or select your calling use case from the dropdown menu.
4. Enter Additional Context in the text box to get better results from AI (optional).
5. Click "Generate".
6. Select your preferred call reason from the AI recommendations.
7. Review the call reason in the Final Call Reason text box.
8. Click "Create".
9. The call reason must have a minimum of 10 characters and a maximum of 100 characters.
10. A mockup of the call reason will be shown in the preview pane.
11. The same call reason can be applied to any number of feature sets. Check the Call Reason page to see all the feature sets using that call reason.

<figure><img src="https://1505116975-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyWoE7a7EzgrlGFIoECsj%2Fuploads%2F3IDNXPGzmpe3XJJDlrKZ%2FCreate%20and%20enable%20a%20call%20reason%20for%20Verified%20Calling%20(1).gif?alt=media&amp;token=d4154805-d73a-450f-a6a3-7a61075a0713" 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/features/call-reason/how-do-i-add-a-new-call-reason.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.