Kindly

Name: Kindly
Brand: Kindly.ai
Rating: 4.8 (34 reviews)

Creating the world's most loved AI agents

Est 2016|Valuation $30M|66 Ref Customers

LinkedIn 6K|Web traffic 5K|FTEs 100|HQ Oslo, NO

MarketsCS AI Agent

Published Oct 9, 2026

01Common complaints

- Company sizes or stages where this product is overkill or insufficient - Very small teams with low interaction volume may find a sales-led enterprise platform and ongoing governance overhead disproportionate to their needs. - Extremely large global enterprises that require full CCaaS capabilities (advanced telephony, WFM, enterprise reporting) may prefer vendors focused on contact center suites unless the organization is specifically adopting Kindly as an AI layer on top of an existing stack. - Industries or use cases where competitors are clearly superior - Voice-heavy contact centers where Genesys or NICE provide deeper telephony and workforce optimization features. - Organizations seeking a single-vendor, end-to-end helpdesk suite (ticketing + KB + marketplace) may find Zendesk or Intercom more aligned with that requirement. - Technical requirements that this product cannot meet - If SCIM, advanced audit logging, and specific compliance certifications are mandatory gating criteria and these cannot be demonstrated, buyers should consider vendors with more transparent compliance artifacts. - Budget constraints that make alternatives more appropriate - Organizations that require low-cost, transparent self-serve pricing might prefer smaller SMB-focused chat/support tools with published plans and month-to-month terms. - Specific workflows or integrations where the product falls short - Complex back-office workflows (refund approvals, chargebacks, regulated complaint handling) may require robust human-in-the-loop permission layers; buyers should validate how Kindly supports action gating and approvals. - Red flags in the buying process (e.g., requires annual commitment, no free trial) - Sales-led procurement paths commonly imply annual commitments and less transparent unit economics; validate contract terms, overage policies, and volume re-forecasting clauses during procurement. - Current limitations acknowledged by the vendor - Vendor marketing emphasizes guardrails and grounded answers but does not provide a detailed public list of known limitations. - Language support is documented but may require vendor engagement for certain languages or depth of support. - Features on the roadmap (not yet available) - note estimated dates if available - No public roadmap with target dates was found in accessible sources. - Scale limitations (at what volume/size does it break down?) - No explicit public throughput limits were identified. Incident reports suggest performance and AI matching issues can affect fallback rates under some conditions. - Security or compliance gaps - Public security certifications are not documented; the trust center exists but some documents may be gated and require direct vendor engagement. - Technical debt or architectural limitations mentioned in reviews - Review themes include a learning curve and perceived complexity for some implementers, which may indicate product or documentation maturity gaps. - API limitations or integration constraints - Public documentation does not fully disclose API breadth, rate limits, or all supported integration patterns; buyers should request API documentation and integration details during evaluation.

Deal disqualifiers: what makes a poor fit

Requirement for publicly documented SOC 2 Type II / ISO 27001 prior to engagement and the vendor cannot provide those documents upon request
Limited internal capacity to maintain conversational flows, QA, and content freshness
Need for transparent, self-serve month-to-month pricing with public rates (sales-led annual contracts may not meet this need)

Reasons some customers left for competitors (churn reasons)

Publicly available Kindly-specific churn information is limited. General market patterns show organizations sometimes reduce AI automation when it increases churn or harms CSAT because automated routing or closures do not resolve customer issues. Pricing model issues are also a known cause of switching in the broader market.

02Why they buy

- Competitive advantages validated by customer feedback (not just vendor claims) - Some review-platform themes align with vendor messaging (ease of use and customer support) in available reviews, indicating partial independent corroboration of implementation support and usability for certain customers. - Unique features and capabilities competitors lack - The vendor's most differentiated public claims are a Europe-focused data posture, multilingual support, and services intended to enable internal CS teams to manage conversational flows. - Differentiation from competitors based on reviews - Independent review volume is smaller compared to major incumbents; differentiation is primarily evident in vendor positioning and selected customer case studies rather than a large body of third-party commentary. - Value propositions with evidence from case studies - Vendor case studies show high containment and cost-per-contact reductions for specific customers; these are vendor-reported and not independently verified. - Areas where competitors clearly have advantages (be balanced) - Intercom and Zendesk provide broader end-to-end suites and larger ecosystems. Larger incumbents typically have more visible compliance documentation and larger pools of peer reviews.

03Field reports

Direct quotes from Gartner Peer Insights, Reddit, TrustRadius, G2, HackerNews

- Gartner Peer Insights - Attempts to locate Kindly-specific reviews on Gartner Peer Insights did not return readily accessible product review pages via open crawling; Gartner often restricts automated access and requires category/product matching. - G2 (Kindly product reviews) - G2 listings indicate favorable ratings for ease of use and customer support in some reviews, while aggregated themes also include criticisms such as a steep learning curve, complex usability, and chatbot issues. - Capterra - Capterra lists Kindly with product positioning and pricing/alternative comparisons; detailed verbatim negative quotes were not accessible in the retrieved snippets and should be reviewed directly on the platform for full context. - Reddit (community perspective — many discussions address AI support generally rather than Kindly specifically) - Community threads include examples where AI-first support reduced ticket volumes but led to increased churn or unresolved customer issues, highlighting the difference between deflection metrics and true resolution. - Discussions recommend careful use of assist vs. replace models and human review gates for high-risk actions (refunds, complaints). - Hacker News - Mostly hiring posts referencing Kindly as a chatbot/SaaS platform; limited end-user product critique surfaced in accessible HN results.

Balance: Include both higher-rated AND lower-rated feedback with equal weight

Positive (vendor case studies; marketing testimonials)
- Vendor case studies include outcome metrics such as reduced cost per contact and high automation rates for specific query types; these metrics are vendor-published and not independently verified.
Negative (review-platform themes)
- Aggregated themes from review platforms include learning curve/complexity and chatbot quality issues reported by some users.

Common criticisms and complaints (support issues, bugs, missing features)

Review-platform themes: learning curve and complexity in onboarding/building are commonly cited.
Reliability incidents: third-party incident trackers show incidents, including a mid‑2026 incident described as performance degradation in AI matching that caused messaging delivery issues and increased fallback rates. Such incidents indicate potential production failure modes where AI matching degrades and increases fallbacks.

Reasons customers chose this product over alternatives

Vendor testimonials cite relative ease of use, multilingual support, and integration capabilities as reasons for selection.

Specific outcomes customers achieved (vendor-published metrics; not independently verified)

Voi: vendor-reported a large reduction in cost per contact and a very high automation rate for parking queries, with reported growth in monthly conversation volumes.
Norwegian: vendor-reported double‑digit reductions in live chats and in enquiries reaching agents.

Customer pain points and frustrations mentioned in reviews

Aggregated themes indicate pain points around learning curve/complexity and occasional chatbot quality issues.
Community discussions note risks of "hollow closures," failures on context, and customer frustration when escalation paths are not smooth.

Deal-breakers and reasons customers didn't purchase

No widely publicized, Kindly-specific deal-breaker threads were found. Common AI-support deal-breakers in the market include lack of data grounding, insufficient action-permission controls, unreliable escalation, and unpredictable usage-based pricing.

Detailed customer success stories with metrics

- Voi (vendor case study) - Vendor reports a very high automation/containment rate for parking queries, a substantial reduction in reported cost per contact, and a notable increase in monthly conversation volume. - Norwegian (vendor case study) - Vendor reports fewer live chats and a reduction in enquiries reaching agents who handle complex cases. - Elkjøp (vendor case study) - Vendor highlights handling of multiple languages across Nordic outlets and reports multi‑million yearly conversation volumes.

Specific results and quantified business impact

The case-study metrics are specific and plausible (cost per contact, deflection, automation rate), but they are vendor-published and were not independently verified in the accessible public sources.

Implementation details and time to value

Vendor materials indicate simple use-cases can go live quickly while enterprise deployments take longer; public case study materials do not provide granular post-launch governance detail.

Challenges faced during adoption and how they were resolved

Public case studies emphasize implementation support from the vendor but often omit granular detail on retraining cycles, governance, or specific failure modes encountered during adoption.

Note when metrics are vendor-published without independent verification

All case-study metrics referenced above originate from vendor-published materials and lack independent third-party verification in the accessible sources.

Note methodology gaps (e.g., "ROI calculated by vendor, methodology not disclosed")

Vendor case study metrics do not include detailed methodology (definition of sessions/resolutions, whether resolution is customer-confirmed vs. system-inferred, baseline measurement windows, labor cost assumptions). Buyers should request:
- Precise definitions of key metrics (session, resolved, fallback).
- Whether resolution is customer-confirmed or system-inferred.
- Pre/post measurement windows and seasonality controls.

Include mixed results - projects that struggled or failed when available

No public, Kindly-specific failed implementation case studies were located in accessible sources. Broader market evidence indicates that AI-first support initiatives can degrade churn/CSAT if deflection is prioritized over confirmed resolution.

04Best fit

Company sizes

Likely fits mid-market to enterprise organizations with high inbound support volume, typically larger support teams or significant interaction volume, and sufficient operational maturity to manage conversation design and integrations.

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

Travel: Norwegian (vendor case study)
Mobility: Voi (vendor case study)
Retail/e-commerce: Elkjøp (vendor case study) and other e-commerce examples cited in vendor materials

Roles and personas: decision makers AND end users

Decision makers
- VP/Head of Customer Support
- Director of CX / Support Operations
- Digital transformation leaders focused on service operations
- Security/IT stakeholders responsible for integrations and data processing
End users
- Support operations managers building conversational flows
- Knowledge base/content owners
- QA leads monitoring conversations and fallback behavior

Pain points and challenges the product addresses

High volumes of repetitive queries (order status, account queries)
Seasonal or episodic volume spikes without proportional hiring
Multilingual support needs across European markets

Qualification criteria: what makes a suitable fit

Availability of clean customer/order/account data to ground automated responses
Established escalation model and human coverage for edge cases
Operations in Europe or a requirement for a vendor with a Europe-focused data posture

Real customer examples with company names when available

Norwegian
Voi
Elkjøp
Boozt (logo/testimonial on vendor materials)
Posten Bring (testimonial on vendor materials)

05The pitch

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

- Kindly describes itself as an AI support platform intended to automate a portion of frontline customer service interactions across multiple channels (web chat, voice, messaging, in-app), with escalation/handover for requests that require human intervention. - The vendor describes use of guardrails to reduce incorrect responses and emphasizes grounding answers in business/customer data via integrations (CRM, authentication systems, OMS/fulfillment, etc.). - The product is positioned for high-volume customer service operations that seek to scale interaction handling without a proportional increase in headcount, maintain service quality, and establish an internal AI-driven support capability.

Target market and market positioning

The vendor targets AI support leaders responsible for high-volume customer service operations and presents regional positioning based in Oslo with a Europe-focused data residency message.
Industry emphasis in vendor materials includes e-commerce/retail, travel, logistics, finance, and utilities/services.

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

Download full report →