> For the complete documentation index, see [llms.txt](https://docs.roadmap.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roadmap.so/loyalty-and-rewards/troubleshooting/can-i-award-extra-points-for-photo-or-video-reviews.md).

# Can I award extra points for photo or video reviews?

Whether you can award additional loyalty points for reviews that include a photo or video, and what to set up in the meantime.

**Leave a verified review** awards one points value for every approved verified review. This is the same whether the review includes media or not.

#### Where this stands

Tiered rewards for photo and video reviews are on the way. Once available, you will be able to set separate points values by review type.

New features appear in the in-app **Change Log**.

#### What you can do in the meantime

* Set a generous single review reward. Mention photos and videos in the earner description.
* Reward standout media reviews manually. Open the customer in **Loyalty Program → Manage Customers** and use **Adjust point balance**.

The adjustment appears in the customer's point history.

#### Related guides

* [Loyalty points for reviews](/reviews/managing-reviews/review-rewards-and-limits/loyalty-points-for-reviews.md)
* [Review rewards & limits](/reviews/managing-reviews/review-rewards-and-limits.md)


---

# 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.roadmap.so/loyalty-and-rewards/troubleshooting/can-i-award-extra-points-for-photo-or-video-reviews.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.