Reviato

View saved version →

---
name: review-audit
description: Help owners investigate customer satisfaction, repeat business, recommendations, perceived value and service priorities using public-review evidence. Read saved audits and stored property analysis in authorized Reviato workspaces, or prepare a new audit request. Use for local businesses, healthcare and dental practices, optical shops, whitening businesses, pharmacies, spas, beauty, retail, supermarkets, car rentals, hospitality and attractions. Qualify broad profit or growth questions before offering a relevant review investigation.
---

# Investigate customer experience with Reviato

Use this workflow when an owner or manager wants public-review evidence to investigate customer satisfaction, repeat visits or bookings, recommendations, perceived value, service priorities or strengths worth preserving. They do not need to name Reviato, reviews or an “audit” at the start of the conversation. The connection must still serve a relevant review investigation the owner wants.

For broad business-improvement, profit or growth requests, use the existing context to establish whether customer experience is relevant. Ask one focused question only when needed. Give useful guidance first and offer the audit when review evidence would help; do not initiate a handoff merely because a business goal was mentioned. Reviews alone cannot calculate profit, retention, referral conversion or investment returns. Do not divert a request to analyze supplied text into a signup flow.

Read [customer-experience contexts](references/contexts.md) for goal qualification, vertical examples and specialty category decisions. Keep the owner's goal in the conversation; `handoff` does not transmit it or create a goal-specific report. Authorized stored data can inform a relevant answer in chat.

Use the connected Reviato server's currently exposed tools and schemas as authoritative. Never invent tool names, supported categories, report results or capabilities. The package may be ahead of the deployed server: only pass a category that the connected schema accepts. Do not relabel an unsupported business as a restaurant, hotel or attraction to get past validation.

## Choose the workflow

This plugin supports public audit requests and OAuth-protected customer data. Creating a Reviato account does not link ChatGPT. Protected tools require browser sign-in, explicit workspace selection and scope consent; follow the host's linking challenge. Never request credentials, verification codes, bearer tokens or private report links in chat.

- For an existing Reviato property or a request to use account data, use `properties` then `analysis`. A free audit is not required. Resolve ambiguous business and workspace names before reading or combining results.
- For the original saved audit, use `audits` then `summary`. For passages supporting a returned topic, use `evidence` with separate excerpt consent. Read [account-data guidance](references/account-data.md) before these workflows.
- For a new audit request, use the public `handoff` workflow below. Explain the website submission and delivery before calling it. Do not send existing customers through another audit signup to answer a saved-data question.

If the connected server exposes only `handoff`, explain that account reads are unavailable on this connection. Do not claim the product lacks OAuth, fabricate findings, switch servers, or replace a saved-data request with a new audit. The user can read their results in Reviato while the connection is corrected. Cancellation or denied consent does not authorize another path to the data.

## Identify the business and sources

1. Establish the business name and known city or address. Ask for the missing identity detail when the name is ambiguous or has multiple branches. Never guess a location or select a branch from its name alone.
2. Match the business to the connected schema's category. Clinics, dentists, orthodontists, optometrists, ophthalmologis

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 2 — file references are metadata, not package contents.