> 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-can-i-create-a-user-feedback-campaign.md).
# How can I create a User Feedback campaign?
1. After setting up your Verified Business Caller ID, you can enable User Feedback in your feature set.
2. Click on the User Feedback toggle to activate it.
3. If you have an older User Feedback campaign, you can select it or you can create a new one.
4. Start by giving a name to your campaign (max 50 characters).
5. Add a description of the campaign within 255 characters.
6. Select when the campaign should be triggered - when a customer answers your call or when a customer misses your call or rejects your call.
> To access your available list of campaigns, click on the User Feedback under the Features section in the left hand side panel of the console.
7. Post this, you can need to further configure your user feedback by clicking on the “+” sign to add individual questions as feedback cards.
8. Select the type of question you wish to add - Call Ratings or Question.
---
# 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-can-i-create-a-user-feedback-campaign.md?ask=&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.
