> 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/what-are-the-guidelines-for-call-reason.md).

# What are the guidelines for Call Reason?

* The call reason has to have a minimum of 10 characters and maximum of 100 characters.
* The following special characters are not supported in Call Reason   **! @ # $ % ^ & \* ( ) \_ + /**&#x20;
* The following special characters are not allowed  **. , -** at the start or end of the Call Reason text. These characters can however be used within a Call Reason text body.
* Spaces are not allowed at the start or end of the Call Reason text.
* The call reason mentioned must be crisp, meaningful, and easy to understand from the end user's call perspective.&#x20;
* The text should be free from grammar or spelling errors.


---

# 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/what-are-the-guidelines-for-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.
