> For the complete documentation index, see [llms.txt](https://helpdocumentation.gitbook.io/user-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocumentation.gitbook.io/user-documentation/creating-a-google-review-qr-code.md).

# Creating a Google Review QR Code

* **Create a Business Account**
  * Enter the business name, category, phone number, and email.
  * Click **Create**.
* **Add Business Location**
  * From the dashboard, click **Add Your First Location**.
  * Add your **Google Review Link** or search for the business using Google Search.
  * Verify the business details.
  * Enter a location label and click **Add Location**.
* **Download the QR Code**
  * Once the location is added, the **Google Review QR Code** will be generated automatically.
  * Download the QR code or share it with your designer for printing.
* **Generate AI Reviews**
  * Add or generate AI-based review suggestions for customers.
  * These reviews can be refreshed automatically at the configured interval.
* **Share the Review Page**
  * Open the generated review link or scan the QR code.
  * Customers can select a suggested review, copy the text, and paste it on the Google Review page before submitting.

{% embed url="<https://www.youtube.com/watch?v=hgWK6m__ohA>" %}


---

# 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://helpdocumentation.gitbook.io/user-documentation/creating-a-google-review-qr-code.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.