# Subsights AI > Publicly sourced profile assembled by Optimly, in the Optimly Index. Last refreshed 2026-10-04. - **Brand record:** https://optimly.ai/brand/subsights-ai - **Dataset:** https://optimly.ai/brand/subsights-ai.json - **Markdown:** https://optimly.ai/brand/subsights-ai/llms.txt - **Official website:** https://subsights.com - **Slug:** subsights-ai - **Categories:** ai-machine-learning, customer-support-cx-software ## Overview - **Tagline:** A strategic AI partner engineered to execute business goals with precision, going beyond basic bots to qualify leads deeply by intent and budget, provide real, nuanced answers, and actively drive outcomes like upsells and targeted discounts. Source: Brand's website (https://subsights.com) · 2026-10-04 - **Description:** Subsights is an AI teammate that streamlines customer support, lead qualification, and revenue growth through advanced chatbot technology. It aims to transform traditional support from a cost center to a revenue engine. Source: Brand's website (https://subsights.com) · 2026-10-04 ## Offerings - **Core capabilities:** - AI-powered chatbot and assistant for customer service - lead qualification - and revenue optimization - capable of handling unlimited conversations - providing expert responses - and driving conversions. Source: Brand's website (https://subsights.com) · 2026-10-04 - **Pricing:** Freemium/Subscription (offers a 'Start Free' option and mentions price_id in signup link) Source: Brand's website (https://subsights.com) · 2026-10-04 ## Audience - **Target industry:** Businesses across various industries, including lead generation, tourism & hospitality, and specialized services, seeking to automate customer interactions and optimize sales funnels. Source: Brand's website (https://subsights.com) · 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.