Stonly

Name: Stonly
Brand: Stonly
Rating: 4.7 (238 reviews)

Drive fast, accurate resolutions with the modern knowledge platform for customer service.

Est 2018|Valuation $15.4M|Raised $25.4M|50 Ref Customers

LinkedIn 5K|Web traffic 175K|FTEs 62|HQ Paris, Île-de-France, FR

MarketsCS Knowledge Management System (KMS)Self-Service FAQ / Knowledge Base

Published Oct 15, 2026

01Common complaints

Company sizes or stages where this product is overkill or insufficient
- Very early-stage organizations with minimal support volume
  - If support ticket volume is minimal and a lightweight static FAQ suffices, the operational overhead of interactive guides may not be justified.
- Very large enterprise DAP programs
  - Organizations that require multi-application governance, extensive automation, and formal digital adoption program infrastructure may prefer enterprise-focused DAPs.
Industries or use cases where competitors are more suitable
- Analytics-first product teams
  - Vendors focused on product analytics are typically a better fit if the core requirement is behavioral analytics rather than guided knowledge.
- Training/LMS-centric requirements
  - If the requirement is formal learning, SCORM packaging, and certifications, a dedicated LMS or certain DAP/LMS hybrids may be more appropriate.
Technical requirements that this product cannot meet
- Not explicitly documented publicly. Buyers with strict data residency, on-prem, or specialized compliance requirements should validate feasibility.
Budget constraints that make alternatives more appropriate
- Organizations that require a low-cost onboarding widget or simple tooltips/checklists may find some SMB onboarding tools cheaper and more transparent.
Specific workflows or integrations where the product falls short
- Organizations that require broad middleware/iPaaS coverage or very specific automation connectors should validate availability of connectors and middleware support.
Red flags in the buying process
- If pricing and overage/upgrade policy cannot be clearly explained in writing
- If AI features are offered without clear guardrails, evaluation methodology, and failure-mode planning
Current limitations acknowledged by the vendor
- Vendor public pages emphasize capabilities; limitations are not strongly highlighted.
- Review-driven limitations include:
  - Customization constraints
  - Feature gating / add-ons for certain overlay-like capabilities
Features on the roadmap (not yet available) - note estimated dates if available
- No reliable, dated roadmap sources were included in the accessible materials.
Scale limitations (at what volume/size does it break down?)
- Not explicitly documented.
- If pricing is view-based, scale may not present technical failure but can materially change cost structure; confirm limits and overage policies.
Security or compliance gaps
- Public documentation is partial; SOC 2 Type II is indicated in the Trust Center but details are not fully documented publicly.
- ISO certifications and data residency specifics are not clearly documented in accessible sources.
Technical debt or architectural limitations mentioned in reviews
- Not prominent in available excerpts.
API limitations or integration constraints
- Stonly provides a public API (Swagger UI).
- Some reviewers cite a desire for broader middleware/integration coverage and report occasional integration friction.

- Company sizes or stages where this product is overkill or insufficient - Very early-stage organizations with minimal support volume - If support ticket volume is minimal and a lightweight static FAQ suffices, the operational overhead of interactive guides may not be justified. - Very large enterprise DAP programs - Organizations that require multi-application governance, extensive automation, and formal digital adoption program infrastructure may prefer enterprise-focused DAPs. - Industries or use cases where competitors are more suitable - Analytics-first product teams - Vendors focused on product analytics are typically a better fit if the core requirement is behavioral analytics rather than guided knowledge. - Training/LMS-centric requirements - If the requirement is formal learning, SCORM packaging, and certifications, a dedicated LMS or certain DAP/LMS hybrids may be more appropriate. - Technical requirements that this product cannot meet - Not explicitly documented publicly. Buyers with strict data residency, on-prem, or specialized compliance requirements should validate feasibility. - Budget constraints that make alternatives more appropriate - Organizations that require a low-cost onboarding widget or simple tooltips/checklists may find some SMB onboarding tools cheaper and more transparent. - Specific workflows or integrations where the product falls short - Organizations that require broad middleware/iPaaS coverage or very specific automation connectors should validate availability of connectors and middleware support. - Red flags in the buying process - If pricing and overage/upgrade policy cannot be clearly explained in writing - If AI features are offered without clear guardrails, evaluation methodology, and failure-mode planning - Current limitations acknowledged by the vendor - Vendor public pages emphasize capabilities; limitations are not strongly highlighted. - Review-driven limitations include: - Customization constraints - Feature gating / add-ons for certain overlay-like capabilities - Features on the roadmap (not yet available) - note estimated dates if available - No reliable, dated roadmap sources were included in the accessible materials. - Scale limitations (at what volume/size does it break down?) - Not explicitly documented. - If pricing is view-based, scale may not present technical failure but can materially change cost structure; confirm limits and overage policies. - Security or compliance gaps - Public documentation is partial; SOC 2 Type II is indicated in the Trust Center but details are not fully documented publicly. - ISO certifications and data residency specifics are not clearly documented in accessible sources. - Technical debt or architectural limitations mentioned in reviews - Not prominent in available excerpts. - API limitations or integration constraints - Stonly provides a public API (Swagger UI). - Some reviewers cite a desire for broader middleware/integration coverage and report occasional integration friction.

Deal disqualifiers: what makes a poor fit

Requirement for deep, analytics-first product instrumentation and controlled A/B onboarding experiments
Need for an enterprise DAP across many third-party applications with strict governance
Lack of internal ownership to maintain and continuously improve knowledge flows

Why some customers left for competitors (churn reasons)

Direct "we left for X" statements were not prominent in the accessible materials.
Likely churn drivers (inferred from complaints) include:
- Need for deeper product analytics (favoring analytics-first vendors)
- Multi-application enterprise DAP requirements (favoring enterprise DAP vendors)
- Desire for a more all-in-one onboarding suite that includes surveys, checklists, and NPS functionality

02Why they buy

Competitive advantages validated by customer feedback (not just vendor claims)
- Reviewer feedback frequently highlights timely vendor support and the relative ease of creating and updating step-by-step guides.
Unique features and capabilities competitors lack
- Stonly’s differentiation is primarily the presentation and organization of knowledge as interactive decision trees and workflows, combined with integrations into support agent environments (Front, Zendesk, Salesforce, etc.).
Differentiation from competitors based on reviews
- Reviews emphasize ease-of-use for non-technical content creators and relatively fast iteration.
Value propositions with evidence from case studies
- Vendor case studies report reductions in tickets and time-to-resolution; some press coverage reported measurable reductions for named customers. These claims require validation of methodology.
Areas where competitors clearly have advantages (be balanced)
- WalkMe/Whatfix: deeper enterprise DAP breadth and governance
- Pendo: deeper product analytics and user insights
- Appcues/Userpilot/UserGuiding: broader onboarding suite features and typically clearer SMB pricing

- Competitive advantages validated by customer feedback (not just vendor claims) - Reviewer feedback frequently highlights timely vendor support and the relative ease of creating and updating step-by-step guides. - Unique features and capabilities competitors lack - Stonly’s differentiation is primarily the presentation and organization of knowledge as interactive decision trees and workflows, combined with integrations into support agent environments (Front, Zendesk, Salesforce, etc.). - Differentiation from competitors based on reviews - Reviews emphasize ease-of-use for non-technical content creators and relatively fast iteration. - Value propositions with evidence from case studies - Vendor case studies report reductions in tickets and time-to-resolution; some press coverage reported measurable reductions for named customers. These claims require validation of methodology. - Areas where competitors clearly have advantages (be balanced) - WalkMe/Whatfix: deeper enterprise DAP breadth and governance - Pendo: deeper product analytics and user insights - Appcues/Userpilot/UserGuiding: broader onboarding suite features and typically clearer SMB pricing

03Field reports

Review platform signals (quantity + averages)

Gartner Peer Insights
- Stonly is shown with a high overall rating and a modest review volume.
G2
- Stonly appears with a high average rating and a moderate review sample with a strong share of top-tier ratings in that sample.
- Note: on some products, very high averages with few low-star reviews can reflect selection bias (satisfied customers are more likely to submit reviews, or vendor-driven review collection may affect distribution). This is not proof of poor quality, but it suggests buyers should validate via reference calls.
TrustRadius
- Stonly is shown with a very small review sample and a lower displayed score on that page; with such a small sample, reliability is limited.
Capterra
- Stonly is presented with an above-average score but a smaller sample size.

- Gartner Peer Insights - Stonly is shown with a high overall rating and a modest review volume. - G2 - Stonly appears with a high average rating and a moderate review sample with a strong share of top-tier ratings in that sample. - Note: on some products, very high averages with few low-star reviews can reflect selection bias (satisfied customers are more likely to submit reviews, or vendor-driven review collection may affect distribution). This is not proof of poor quality, but it suggests buyers should validate via reference calls. - TrustRadius - Stonly is shown with a very small review sample and a lower displayed score on that page; with such a small sample, reliability is limited. - Capterra - Stonly is presented with an above-average score but a smaller sample size.

Direct paraphrased reviewer feedback (positive and negative)

Gartner Peer Insights (positive)
- A Gartner reviewer noted that creating step-by-step guides was relatively straightforward, that content could be built and updated quickly, and that vendor support was responsive and helpful.
Gartner Peer Insights (mixed/critical)
- A reviewer reported generally positive experiences but called out that some paid add-on options could be broader and requested support for additional middleware tools.
G2 (positive)
- A G2 reviewer reported that support was responsive and that the product was straightforward to set up and use.
G2 (critical feature gap)
- A reviewer described an extra-cost overlay feature and noted limitations with inline graphic placement and image-hyperlinking options.
TrustRadius (mixed)
- Pros cited the SDK, documentation, and developer experience; cons included a need for more features around tracking and understanding users, and occasional issues connecting with existing components.
Community discussion (Reddit; anecdotal)
- One user discussing AI agents summarized that structuring knowledge logic in Stonly can reduce hallucinations from AI agents. Another community thread expressed price sensitivity and noted that Stonly and some peers can seem expensive for product-tour use cases.

- Gartner Peer Insights (positive) - A Gartner reviewer noted that creating step-by-step guides was relatively straightforward, that content could be built and updated quickly, and that vendor support was responsive and helpful. - Gartner Peer Insights (mixed/critical) - A reviewer reported generally positive experiences but called out that some paid add-on options could be broader and requested support for additional middleware tools. - G2 (positive) - A G2 reviewer reported that support was responsive and that the product was straightforward to set up and use. - G2 (critical feature gap) - A reviewer described an extra-cost overlay feature and noted limitations with inline graphic placement and image-hyperlinking options. - TrustRadius (mixed) - Pros cited the SDK, documentation, and developer experience; cons included a need for more features around tracking and understanding users, and occasional issues connecting with existing components. - Community discussion (Reddit; anecdotal) - One user discussing AI agents summarized that structuring knowledge logic in Stonly can reduce hallucinations from AI agents. Another community thread expressed price sensitivity and noted that Stonly and some peers can seem expensive for product-tour use cases.

Common criticisms and complaints (observed themes)

Customization limits
- Mentioned on G2 and TrustRadius (users requested more customization).
Integration breadth / middleware support
- Mentioned on Gartner Peer Insights (desire for broader paid add-ons and more middleware tools).
Analytics / tracking depth
- TrustRadius review called out the need for more user tracking and segmentation capabilities.
"Add-on" / tier gating
- Several reviewers and review excerpts indicate certain capabilities are available only as paid add-ons.

- Customization limits - Mentioned on G2 and TrustRadius (users requested more customization). - Integration breadth / middleware support - Mentioned on Gartner Peer Insights (desire for broader paid add-ons and more middleware tools). - Analytics / tracking depth - TrustRadius review called out the need for more user tracking and segmentation capabilities. - "Add-on" / tier gating - Several reviewers and review excerpts indicate certain capabilities are available only as paid add-ons.

Reasons customers chose this product over alternatives

Reduced engineering dependency
- Reviewers highlighted that content and product teams can manage guides without requiring engineering to build custom onboarding flows.
Support workflow fit (decision trees and step-by-step resolution)
- Reviews emphasized the ability to quickly build and update step-by-step guides and the product’s fit within support workflows.
Responsiveness of vendor support
- Responsive vendor support is frequently cited in review excerpts.

- Reduced engineering dependency - Reviewers highlighted that content and product teams can manage guides without requiring engineering to build custom onboarding flows. - Support workflow fit (decision trees and step-by-step resolution) - Reviews emphasized the ability to quickly build and update step-by-step guides and the product’s fit within support workflows. - Responsiveness of vendor support - Responsive vendor support is frequently cited in review excerpts.

Specific outcomes customers achieved (with metrics when available)

Vendor-published case study metrics reported on the Stonly homepage include:
- Reported decreases in support tickets (examples include substantial decreases in some vendor case studies)
- Reductions in resolution time and training time reported in headline figures
- Reported accuracy and self-serve success rate metrics for AI-driven features
These outcomes are vendor-published and methodology is not publicly detailed on the homepage; treat them as directional until validated.
Press reporting cited a customer example in which a vendor saw a measurable decrease in opened tickets for their most frequent issues after using Stonly (press report; not an independent audit).

- Vendor-published case study metrics reported on the Stonly homepage include: - Reported decreases in support tickets (examples include substantial decreases in some vendor case studies) - Reductions in resolution time and training time reported in headline figures - Reported accuracy and self-serve success rate metrics for AI-driven features - These outcomes are vendor-published and methodology is not publicly detailed on the homepage; treat them as directional until validated. - Press reporting cited a customer example in which a vendor saw a measurable decrease in opened tickets for their most frequent issues after using Stonly (press report; not an independent audit).

Deal-breakers and reasons customers didn't purchase

Not clearly present in accessible sources; however, review snippets suggest:
- If a buyer requires robust user analytics and journey measurement, Stonly may be insufficient relative to analytics-first products.
- If a buyer wants extensive visual overlay/on-screen click-through functionality included in base plans, some features may be offered only as add-ons.

Vendor-published case study metrics (examples)

The Stonly homepage highlights customer stories and headline metrics (e.g., reductions in tickets, faster onboarding/training).
Press coverage cites early customer impact such as Dashlane’s reported ticket decrease for frequent issues.

Critical evaluation of case study claims

Methodology gaps:
- Vendor headline statistics rarely disclose baseline periods, seasonality adjustments, attribution methods, or control groups.
- "Ticket deflection" metrics can be inflated if deflection is measured as guide views rather than confirmed resolution.
What to ask Stonly for during diligence:
- Before/after definitions and time window
- Whether outcomes were measured against comparable cohorts
- How "resolved without ticket" is determined
- Whether improvements were sustained over multiple quarters

- Methodology gaps: - Vendor headline statistics rarely disclose baseline periods, seasonality adjustments, attribution methods, or control groups. - "Ticket deflection" metrics can be inflated if deflection is measured as guide views rather than confirmed resolution. - What to ask Stonly for during diligence: - Before/after definitions and time window - Whether outcomes were measured against comparable cohorts - How "resolved without ticket" is determined - Whether improvements were sustained over multiple quarters

Mixed results / struggling projects

Public sources used did not contain detailed failed-implementation narratives.
Common failure modes (inferred):
- Content becomes outdated
- Decision-tree complexity becomes unmanageable
- Poor data hygiene for targeting/personalization
- Over-reliance on AI outputs without knowledge governance

04Best fit

Company sizes: specific employee counts and revenue ranges

Best fit (inferred from review personas and typical deployment):
- SMB to mid-market: small to mid-sized organizations
- Support organizations that can maintain content ownership (a knowledge manager or enablement function)
Enterprise fit appears plausible (industry reviewers include enterprise users), but diligence should focus on governance, SSO/SCIM, and security requirements.

Industries and verticals where adoption is strongest (with customer examples)

Public references to customers include a mix of SaaS and tech-enabled services. Vendor and press mentions reference companies such as Telus, Univision, Backmarket, Gorgias, UCLA, Dashlane and others.
Review snippets indicate usage across industries including media, energy/utilities, construction, retail, and software.

Roles and personas: decision makers AND end users

Decision makers
- VP/Head of Support, VP Customer Experience
- Support Ops / CX Ops
- Head of Knowledge Management / Enablement
- Product leaders (if used for onboarding)
End users
- Support agents and team leads
- Customers using self-service help widgets / embedded guides

Pain points and challenges the product addresses

Repetitive "how do I…" tickets and high support volume
Inconsistent agent troubleshooting and quality
Slow onboarding for new agents ("tribal knowledge" problem)
Engineering bottleneck for building in-app guidance

Qualification criteria: what makes a good fit

Organizations with complex support workflows that benefit from branching logic
Organizations that can commit resources to knowledge governance and maintenance
Needs for guidance inside help desk/CRM workflows

Real customer examples with company names when available

Press- and vendor-reported examples include Telus, Univision, Backmarket, Gorgias, Mynd, UCLA.
Early customer mentions in press coverage referenced companies including Dashlane, Devialet, Happn, and Calendly.

05The pitch

What the product does (core value proposition in objective terms)

Stonly is an interactive knowledge and guidance platform designed primarily for customer support and self-service.
Core building blocks repeatedly emphasized across sources:
- Step-by-step interactive guides and branching decision trees
- In-app / in-workflow delivery via widgets, embeds, and help desk integrations
- "AI Answers" / conversational bot and "AI Agent Assist" to surface knowledge and suggest responses
- Analytics and feedback loops to improve knowledge performance over time
Vendor framing: the vendor describes Stonly as a knowledge platform intended to reduce ticket volume and speed resolution.

- Stonly is an interactive knowledge and guidance platform designed primarily for customer support and self-service. - Core building blocks repeatedly emphasized across sources: - Step-by-step interactive guides and branching decision trees - In-app / in-workflow delivery via widgets, embeds, and help desk integrations - "AI Answers" / conversational bot and "AI Agent Assist" to surface knowledge and suggest responses - Analytics and feedback loops to improve knowledge performance over time - Vendor framing: the vendor describes Stonly as a knowledge platform intended to reduce ticket volume and speed resolution.

Target market and market positioning

Primary buyers and users appear to be:
- Customer support / CX operations leaders
- Support enablement / knowledge management teams
- Product teams responsible for onboarding and in-product guidance
Stonly overlaps multiple categories:
- Knowledge Management (KM) for support
- Digital Adoption Platform (DAP)-like in-app guidance (but with more emphasis on knowledge/decision trees than tooltip-driven tours)
Market positioning (inferred from integrations + reviews): support-centric guided knowledge that integrates with ticketing systems such as Zendesk, Salesforce, Freshworks, ServiceNow and messaging tools.

- Primary buyers and users appear to be: - Customer support / CX operations leaders - Support enablement / knowledge management teams - Product teams responsible for onboarding and in-product guidance - Stonly overlaps multiple categories: - Knowledge Management (KM) for support - Digital Adoption Platform (DAP)-like in-app guidance (but with more emphasis on knowledge/decision trees than tooltip-driven tours) - Market positioning (inferred from integrations + reviews): support-centric guided knowledge that integrates with ticketing systems such as Zendesk, Salesforce, Freshworks, ServiceNow and messaging tools.

Get a comprehensive analysis of Stonly including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →