> For the complete documentation index, see [llms.txt](https://docs.guestway.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guestway.io/reviews-and-analytics/review-center/about-the-review-center.md).

# About the review center

This page explains why the review center shows more than the score of a review, and how the extra information helps your team.

## One place for every review

Guests review your properties on several channels, and on Airbnb you also review the guests. Without one place, each channel needs its own login and its own routine, and reviews without a reply are easy to miss. The review center brings the reviews of every channel together, for both sides of a stay, so that your team can sort them, share the work and reply from one list.

## The trend says more than the score

One bad rating can be bad luck. A trend is a pattern. That is why each category rating comes with a percentage that compares it with your earlier reviews. A 4-star review with a declining cleanliness trend tells you more than a single low rating, and it shows where performance slips before your overall rating drops.

## Reviews linked to your team

A review is about a stay, and a stay is the work of people. The cleaning and communication blocks connect a review to the cleaner and the team members of that booking, next to their earlier ratings. This helps you see whether a problem comes from one person or from the way you work. Use it for coaching and targeted feedback, not for blame.

The same question applies to your properties. When you look at the reviews of one multi-unit listing or one complex, you see whether an issue affects the whole property or only one unit.

## Why AI reads the reviews

Reading every review and every conversation in full takes time that a growing portfolio does not have. The AI summarises the review in positive and negative points, reads the conversation with the guest, and drafts a reply from the review and its sentiment. The drafts keep your tone consistent across many reviews, so that your team can spend its attention on the reviews that need a personal answer.

## Related

* [Review center](https://docs.guestway.io/reviews-and-analytics/review-center.md)
* [How to reply to a review with AI](https://docs.guestway.io/reviews-and-analytics/review-center/how-to-reply-to-a-review-with-ai.md)
* [How to write a host review](https://docs.guestway.io/reviews-and-analytics/review-center/how-to-write-a-host-review.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.guestway.io/reviews-and-analytics/review-center/about-the-review-center.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.
