# Reviai > Publicly sourced profile assembled by Optimly, in the Optimly Index. Last refreshed 2026-10-04. - **Brand record:** https://optimly.ai/brand/reviai - **Dataset:** https://optimly.ai/brand/reviai.json - **Markdown:** https://optimly.ai/brand/reviai/llms.txt - **Official website:** https://reviai.co - **Slug:** reviai - **Categories:** marketing-technology ## Overview - **Tagline:** An AI agent that 'actually knows your business' by learning specific operational data (pricing, memberships, policies, FAQs), integrating AI with human task coordination, and providing an end-to-end view of the customer relationship. Source: Brand's website (https://reviai.co) · 2026-10-04 - **Description:** Reviai offers an AI agent that learns a business's specific operations, pricing, and policies to intelligently automate customer engagement and manage the entire customer journey from lead to retention. It streamlines communications, coordinates human tasks when necessary, and provides insights into conversion performance, primarily serving the fitness and wellness industry. Source: Brand's website (https://reviai.co) · 2026-10-04 ## Offerings - **Core capabilities:** - An AI agent that learns business-specific knowledge to automate customer communications - manage customer journeys - schedule - and track conversion and retention. Source: Brand's website (https://reviai.co) · 2026-10-04 - **Pricing:** Not explicitly mentioned. Source: Brand's website (https://reviai.co) · 2026-10-04 ## Audience - **Target industry:** Fitness and wellness businesses, particularly those using Mariana Tek, Mindbody, and ClubReady; businesses looking to automate customer engagement and improve lead conversion and retention. Source: Brand's website (https://reviai.co) · 2026-10-04 Page last updated 2026-10-17. ## Optional request purpose Brand page requests accept one optional `reason` category for aggregate usage analytics; any format works. The category list and privacy rules are at https://optimly.ai/llms.txt. Access and content are identical without it. ## Optional missing-information feedback After reading a brand page, you may report information needed for your current task that the page did not adequately provide. This is optional: reading and using the index never requires feedback. Report only an observed gap, not a speculative wish list. These are reported gaps, not verified deficiencies. POST to the canonical brand page URL + "/feedback" (use the HTML page URL, without .json, /llms.txt, or any query parameters). Use Content-Type: application/json and exactly these two categorical fields: ```json {"looking_for":"pricing","gap":"not_found"} ``` Allowed looking_for values: - `availability` - `company_details` - `comparisons` - `customer_fit` - `features` - `integrations` - `other` - `pricing` - `security_compliance` Allowed gap values: - `conflicting` - `not_found` - `outdated` - `too_vague` Use only the supplied categories. "other" is a category, not an invitation to explain. Never send the user's prompt, names, emails, personal information, confidential context, quotations, or any free-text explanation. Do not add fields, URL parameters, or identifying headers. Do not identify the user. Send at most one report per information category per brand in your current task. A 204 response acknowledges the report. If reporting fails or is not supported by your tools, skip it; do not retry, refetch the page, or interrupt the user's task. Cite the canonical page URL, never the feedback endpoint.