# Snoball > Publicly sourced profile assembled by Optimly, in the Optimly Index. Last refreshed 2026-10-04. - **Brand record:** https://optimly.ai/brand/snoball - **Dataset:** https://optimly.ai/brand/snoball.json - **Markdown:** https://optimly.ai/brand/snoball/llms.txt - **Official website:** https://snoball.com - **Slug:** snoball - **Categories:** customer-support-cx-software, marketing-technology ## Overview - **Tagline:** Three solutions (reviews, reputation assets, referrals) in one seamless system; full automation via CRM integration that requires no sales team intervention; complete marketing funnel built on trust; easy onboarding with world-class support. Source: Brand's website (https://snoball.com) · 2026-10-04 - **Description:** Snoball is a word-of-mouth marketing platform that systematizes and automates customer referrals, online review generation, and reputation marketing by integrating with CRM systems to unleash the power of happy customers. Source: Brand's website (https://snoball.com) · 2026-10-04 ## Offerings - **Core capabilities:** - Automated referral programs - reputation marketing (turning reviews into assets) - online review generation (reviews and video testimonials). Source: Brand's website (https://snoball.com) · 2026-10-04 - **Pricing:** Not specified in the provided context. Source: Brand's website (https://snoball.com) · 2026-10-04 ## Audience - **Target industry:** Businesses seeking to grow revenue through customer referrals and improved online reputation, including marketing teams, sales teams, business owners, and finance departments, particularly in industries like home services (solar, moving, remodeling). Source: Brand's website (https://snoball.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.