> 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/ai/ai-center/how-to-test-answers-in-the-playground.md).

# How to test answers in the playground

This guide shows you how to test how the AI answers a guest question in the playground, without sending anything to a guest.

{% hint style="info" %}
**Before you start**

* A role with permission to use the playground.
  {% endhint %}

## Open the playground

{% stepper %}
{% step %}

### Go to the playground

Go to **AI Center** → **Playground**.
{% endstep %}

{% step %}

### Start a conversation

Click **New conversation**, and choose the **Conversation scope**: the whole organization, a complex, a multi-unit, a listing or a reservation. To test another scope later, start a new conversation.
{% endstep %}
{% endstepper %}

## Ask a guest question

{% stepper %}
{% step %}

### Write as the guest

Type a message the way a real guest would, for example *"when can we get in??"*, and send it.
{% endstep %}

{% step %}

### Check the reply

Read the AI reply. Check the knowledge it used, the fact-check result and the label **Would send** or **Would not send**.

If the reply used the wrong entry or no entry, fix the knowledge, then click **Re-run Auto-Pilot from here**.
{% endstep %}
{% endstepper %}

{% hint style="success" %}
Ask the same thing in three different ways before you rely on an answer. Your Q\&A may say *"What time is check-in?"*, but guests write *"when can we arrive"*.
{% endhint %}

## Troubleshooting

<details>

<summary>What do I do when the AI gives a wrong answer for one property?</summary>

* Start a conversation with that listing, or a reservation there, as the scope, and ask the same question.
* Check which knowledge the reply used. If it is the wrong entry, its scope is probably too wide. Narrow it with **Edit scope** in **Browse**.
* If no entry was used, the answer is missing. Add a Q\&A for that listing, and re-run.
* Also check the listing details, such as amenities and custom fields, in **Properties**. The AI uses those too.

</details>

## Related

* [AI center](https://docs.guestway.io/ai/ai-center.md): what each reply in the playground shows.
* [How to add knowledge to the AI](https://docs.guestway.io/ai/ai-center/how-to-add-knowledge-to-the-ai.md)
* [How to set up Auto-Pilot](https://docs.guestway.io/ai/ai-center/how-to-set-up-auto-pilot.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/ai/ai-center/how-to-test-answers-in-the-playground.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.
