Lorikeet

Name: Lorikeet
Brand: Lorikeet

AI Native

Trusted by Fintechs, Healthtechs & other complex businesses to deliver a universal concierge for their customers

Est 2023|Valuation $100M|Raised $49M|44 Ref Customers

LinkedIn 12K|Web traffic 16K|FTEs 104|HQ New York, New York, US

MarketsCS AI Agent AI Customer Support Agents

Published Oct 15, 2026

01Common complaints

- Company sizes or stages where the product is overkill - Small support teams with low-sensitivity, low-complexity tickets where the added configuration and compliance overhead would not justify the cost. - Use cases or industries where alternatives may be superior - If the primary objective is live agent assist, real-time coaching, and post-call analytics rather than autonomous resolution, contact-center-focused vendors may offer a closer fit. - Technical or procurement requirements that may disqualify the vendor - If procurement requires fully public SOC 2 artifact publication, subprocessor lists, or public penetration test reports, and the vendor shares these materials only under NDA, the vendor may not meet strict transparency requirements. - Budget constraints - The Start plan requires annual payment and a minimum monthly commitment; this may be a barrier for pilots that require month-to-month billing or very low volumes. - Integration or workflow constraints - Stacks that require numerous niche, out-of-the-box connectors (e.g., specific core banking or EMR systems) should validate connector availability before committing. - Limitations acknowledged by the vendor - The vendor notes the product may not be cost-effective for small teams with low-sensitivity support needs. - Roadmap and feature availability - No explicit, dated public roadmap items were identified in accessible sources during this research. - Scale limitations - No public stress-test or scale benchmark data was found. Buyers should request performance and SLA documentation during procurement. - Security and compliance gaps - Certification claims exist, but audit artifacts and detailed scope information are shared under NDA; there is no publicly posted full subprocessor list, retention/deletion control details, or public penetration test summaries available in this research. - API and integration limitations - The vendor provides SDKs/APIs; an npm package indicates a configurable API endpoint. Public documentation did not disclose rate limits, sandboxing details, or other integration constraints; buyers should validate these during technical evaluation.

Deal disqualifiers: poor fit

Very low ticket volumes where overhead outweighs benefit
Predominantly informational FAQ use cases that can be solved by cheaper deflection tools
Organizations unwilling or unable to connect internal systems or run integration work

Why some customers left (churn reasons)

No firm, independently verified churn narratives were found in public sources during this run.

02Why they buy

- Observed differentiators (based on public materials and external signals) - Public, per-resolution pricing with published tiers is relatively uncommon in the enterprise AI agent market and is an observable differentiator in vendor materials. - The vendor emphasizes an auditability and compliance posture in public documents, including SOC 2/ISO 27001 and willingness to sign BAAs, which is an area to validate during procurement. - Validation limitations - Independent customer feedback and third-party reviews are limited in volume; the unique points above are primarily visible from vendor-published materials and should be validated in pilot deployments and reference checks. - Areas where competitors retain advantage - Competitors with longer operating histories in contact-center operations or broader enterprise deployments may offer more extensive referenceable deployments, broader analytics capability, or more mature procurement and integration practices.

Why customers chose the product, based on vendor messaging and available signals

Vendor materials indicate buyers selected the product for automation of multi-step workflows, multi-channel support including voice, and a compliance-focused approach suitable for regulated industries. Independent corroboration of these rationales is limited in public sources.

03Field reports

Direct quotes from major review platforms and community channels

- Gartner Peer Insights: No vendor-specific review page was found in publicly accessible search results in this run; the platform may be gated or not list the product. - G2: The vendor listing had no reviews at the time of this research, limiting the usefulness of G2 for buyer sentiment. - TrustRadius: No review page was found in accessible sources during this run. - Reddit: Discussions involving the vendor are sparse; search results often return unrelated results (e.g., references to the bird species). One Reddit thread included a brief suggestion to try the product in a general discussion but no detailed first-hand deployment review. - Trustpilot: A very negative public review was located that described a poor end-user experience, including repeated/looping responses, difficulty escalating to a human agent, and a problematic onboarding experience for the reviewer.

Balance of sentiment

Public third-party review coverage is thin. The available independent review datapoints were limited and skewed toward a single negative public review; there were few or no comparable independent positive reviews on major software review platforms found in this run.
Vendor-published testimonials are present on the company site, but these are not independent validation.

Common criticisms and complaints observed

From available third-party public feedback (limited): repetition or looping in conversation, difficulty reaching a human agent, and poor handling of certain onboarding flows.
Category-level complaints relevant to buyer diligence: automated systems that fail to escalate appropriately, disputes over what constitutes a resolved ticket, and implementations that create customer frustration when the automation does not meet expectations.

Reported outcomes

The vendor publishes performance claims on its site; these claims were not independently verified and lack public methodology descriptions.

Deal-breakers observed in public materials

Vendor materials acknowledge that deployment overhead and compliance prerequisites may make the product less suitable for very small teams with low-sensitivity support needs.

Case Studies

#### Vendor-published customer examples - The vendor site includes testimonial quotes and example ticket resolutions across channels; many examples do not include independent verification or detailed methodology for reported KPI improvements. - Vendor press materials list example customers and pilots such as Eucalyptus, Step, and MagicEden; independent confirmation of production deployments was not identified in accessible sources during this run. #### Reported metrics and verification gaps - Vendor-published metrics are presented on public pages but lack disclosed methodologies, baselines, and independent validation. Buyers should request methodology and raw data during procurement evaluation. #### Implementation details and time-to-value - Publicly available details are limited. The product and pricing pages reference testing, simulations, and evaluation processes that suggest an evaluation-driven onboarding approach. #### Challenges during adoption - No independent, detailed case studies describing adoption challenges were found in accessible sources. One negative end-user review suggests that misconfigured escalation controls can degrade experience. #### Methodology notes - The vendor shares some compliance artifacts under NDA, which is common, but it limits public verification of certain security claims.

04Best fit

Company sizes: employee counts and ticket volume guidance

Based on published pricing guidance:
- Start plan: organizations with relatively low monthly ticket volumes (likely small to mid-market support operations)
- Scale: organizations with moderate to higher monthly ticket volumes (likely mid-market to larger teams)
- Enterprise: organizations with very high ticket volumes or complex, highly integrated implementations

Industries and verticals

Official positioning emphasizes fintech and healthtech. The vendor also references insurance and gaming in compliance materials. Press materials list example pilot customers in payments, finance, and healthcare-adjacent spaces.

Decision makers and end users

Decision makers: Heads of Customer Support, VP/Director of CX, Compliance and Risk leaders (in regulated industries), CIO/CTO or platform engineering for integration work.
End users: Support agents (for escalations), team leads, QA and operations teams responsible for SOPs and workflow management.

Pain points addressed

High-volume, repeatable but multi-step support workflows that require system actions (refunds, scheduling, policy changes)
Need to control processes with auditability in regulated workflows
Desire to reduce average time-to-resolution without proportionally increasing headcount

Qualification criteria: what makes a good fit

Repetitive, codifiable workflows that require integration with internal systems
Established SOPs and willingness to operationalize them
Procurement processes that can handle NDA access to compliance artifacts

05The pitch

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

- Lorikeet describes its product as an AI-based customer support agent intended to resolve customer issues end-to-end across phone, SMS, chat, email, and WhatsApp. The vendor materials state the product is intended to support tasks beyond FAQ responses and to handle multi-step workflows. - Product materials indicate capabilities for executing standard operating procedures (SOPs), integrating with customer systems (examples shown include Zendesk, Stripe, and internal APIs), and escalating cases to human agents with context when the automated agent cannot complete a task safely.

Target market and market positioning

- Lorikeet targets fintech and healthtech companies and positions itself for environments with regulatory and compliance requirements. - The product is presented as an alternative to simple FAQ chatbots, focusing on automated execution of workflows. It competes in the AI customer support automation / autonomous CX agent category and is compared by vendors and some sources to Sierra, Decagon, Ada, and contact-center AI platforms such as Cresta. (source: Vendor pricing and product pages)

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

Download full report →