> 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/user-feedback/how-do-i-setup-a-questions-feedback-campaign.md).

# How do I setup a Questions feedback campaign?

1. Click on the "+" sign and select "Questions" from the Add New menu displayed.
2. Type the question that you want your customers to answer as a part of the campaign. The question can be of 100 characters maximum.
3. There can be three types of feedback questions - Multi choice short, Multi choice long, Free Text. Select the feedback type from the drop down menu after typing the question.
   * For Multi choice short questions, there can be a minimum of 2 options and a maximum of 3 options.&#x20;
   * For Multi choice long questions, there can be a minimum of 2 options and a maximum of 4 options.
4. Each option can be 15 characters maximum.
5. Click on “Save” to save your Question as a feedback card.&#x20;

<figure><img src="https://1505116975-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyWoE7a7EzgrlGFIoECsj%2Fuploads%2FZygsjBy3PalYfw7k6z1d%2FUser-feedback_Question.gif?alt=media&amp;token=dedd9878-ef46-4bcb-a090-374596172cb0" alt=""><figcaption></figcaption></figure>

6. To add more Feedback Cards, click on the “+” sign below an existing feedback card.&#x20;
7. The order in which the feedback cards are being displayed, is the same order that your customer will see the Call Ratings/Questions after answering/missing/rejecting your call.&#x20;
8. If you wish to reorder your feedback cards, simply drag a feedback card above or below another existing feedback card.


---

# 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/user-feedback/how-do-i-setup-a-questions-feedback-campaign.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.
