›

Support Quality

Freshdesk vs Lorikeet: AI Support for Complex Workflows (2026)

Freshdesk vs Lorikeet: AI Support for Complex Workflows (2026)

Freshdesk vs Lorikeet in 2026: published pricing, per-session vs per-resolution cost, compliance, data residency, and which fits complex support workflows.

Lorikeet Logo

Lorikeet News Desk

·

Updated

Freshdesk and Lorikeet are built for different jobs. Freshdesk is a helpdesk suite with an AI agent attached to it, and Lorikeet is a resolution layer that runs on top of a helpdesk you already own. The question that decides between them is whether your hardest tickets need an answer or an action, and how much proof your compliance team wants before either one goes live.

  • Freshworks publishes Freshdesk pricing openly: $19, $55 and $89 per agent per month billed annually for Growth, Pro and Enterprise, plus Freddy AI Copilot at $29 per agent per month and Freddy AI Agent sessions at $49 per 100 after an included 500 (Freshworks, checked November 2026).

  • Lorikeet has no per-seat charge. Lorikeet publishes its pricing: the Start plan is $2,100 a month and Scale is $5,100 a month (both billed annually), with resolved chat, email and SMS conversations at $0.99 (Start) or $0.90 (Scale) and voice at $1.50 or $1.20. Unresolved tickets and handoffs to a person are not charged. Signature is custom, with a $75K platform fee. Full details are on the pricing page. The plan fee and the per-resolution rate are additive.

  • Freshworks bills a session whether or not it resolved anything; Lorikeet bills only resolved tickets and never escalations. Neither price means anything until both are converted to cost per resolved ticket.

  • Freshworks publicly documents SOC 2 Type II, ISO 27001 and ISO 27701 and offers regional hosting across the US, EU, India, Australia and the UAE. Lorikeet holds SOC 2 Type II, ISO 27001, HIPAA and GDPR, runs on Google Cloud, and lists custom data residency on Signature only.

  • Lorikeet publishes this guide and is one of the platforms compared. We checked competitor details on their own websites in November 2026; if something has changed, tell us and we will update the page.

  • Lorikeet's published pricing names Zendesk, Slack, Intercom, HubSpot, Front, Help Scout, Salesforce, Genesys Cloud and the Lorikeet SDK as the ticket-platform integrations on Start and Scale. Freshdesk is not on that list or on the public integrations list. Flexible Ticketing works with any system that sends webhooks, so a Freshdesk team should confirm how the connection would work and at which plan level, in writing, before signing.

Last updated: November 2026

Most Freshdesk comparisons collapse two separate purchases into one. The first is the helpdesk: ticketing, queues, SLAs, a knowledge base, reporting, the place your agents live all day. The second is the AI layer that closes tickets without a human touching them. Freshworks sells both inside one subscription, which is part of why the suite is easy to buy, and which makes it tempting to assume that if the helpdesk fits, the AI fits too. Those are two tests, and the second gets harder the more your tickets involve money, identity, eligibility or a regulator.

Freshdesk and Lorikeet at a Glance

Freshdesk is Freshworks' customer support suite, launched in 2010 and now part of a publicly listed company. Freshdesk covers email and portal ticketing, and Freshdesk Omni adds chat, messaging and telephony, plus a knowledge base, automations, SLA management and reporting, and it is one of the most widely deployed helpdesks in the SMB and mid-market. Its reputation is earned on price transparency, speed of setup and breadth for the money. Where the ticket mix is mostly password resets, order status and how-to questions, that is hard to beat on value.

Freddy AI comes in two shapes that are easy to confuse. Freddy AI Copilot is agent assist: it drafts replies and summarises threads for a human, at $29 per agent per month. Freddy AI Agent is the customer-facing autonomous bot, priced per session rather than per seat. Freshworks defines a session as a unique interaction between an end user and the AI agent, with an email session running as a 72-hour window from the customer's first message.

Lorikeet is an AI customer support platform for complex and regulated businesses, and it is deliberately not a helpdesk. It connects to the ticketing system you already run and takes over the tickets you decide it should own, across phone and voice, SMS, chat, email and WhatsApp. Every plan includes a forward-deployed support package, so Lorikeet engineers help build the workflows with you rather than handing over a builder and a training video. Lorikeet is built for regulated industries, with customers across fintech, healthtech and insurance. Published customers include Taptap Send in remittance and Carmoola in FCA-regulated car finance.

The honest summary is that these two barely overlap on an org chart. Freshdesk becomes your system of record; Lorikeet sits on top of one and takes work off the queue. The decision is real only at the AI layer, where a team already paying Freshworks judges whether Freddy AI Agent covers the tickets carrying the most risk. If you are still choosing the helpdesk, our Zendesk vs Freshdesk comparison covers that question.

Freshdesk is split into two columns below on purpose, because the suite and the AI agent are separate purchases with separate answers. Treat every figure as directional and confirm it against each vendor's pricing page.




Freshdesk suite

Freddy AI Agent

Lorikeet

Pricing model

Per agent per month

Per session, sold in packs

Annual plan plus per-resolution pricing, no per-seat charge

Published entry price

$19/agent/mo Growth, $55 Pro, $89 Enterprise, billed annually

500 sessions included, then $49 per 100

$2,100/mo Start, $5,100/mo Scale, paid annually

What triggers a charge

Every seat, used or not

Every session, resolved or not

Resolved tickets only; escalations free

Ticketing system of record

Yes, this is the product

Runs inside Freshdesk

No, runs on top of yours

Multi-step backend actions

Automations and connector app tasks

Configured actions from the app layer

Branching workflows that read and write across systems mid-ticket

Pre-launch guardrail testing

Not applicable

Not published

Simulations with pass and fail reports

Audit-trail depth

Ticket history and activity log

Not published

Each response traced to the knowledge, policy and guardrail behind it

Published certifications

SOC 2 Type II, ISO 27001, ISO 27701 via Freshworks trust centre

Inherits the Freshworks set

SOC 2 Type II, ISO 27001, HIPAA, GDPR

Data residency options

US, EU, India, Australia, UAE, chosen at signup

Follows the account region

Standard USA data residency; custom data residency on Signature

Best for

SMB and mid-market teams wanting one suite

High-volume, knowledge-based ticket mixes

Complex, regulated, backend-touching work

What to Look For When You Compare a Suite AI With a Resolution Layer

Five criteria decide this evaluation, and each works better as a test than an attribute. Run them in this order: the earlier ones eliminate options faster.

1. Cost against what you already spend. Split last quarter's volume into tickets a knowledge-base answer can close and tickets requiring an action in another system, then price both vendors against each half. A per-session price and a per-resolution price are not comparable until you divide the session price by your real session-to-resolution rate. Ask each vendor to model twelve months at your actual volume, showing every add-on and overage line.

2. Accuracy and hallucination control. Ask what happens when the model does not know, and expect a mechanism as the answer. Ask whether refusal behaviour is configurable per topic, and whether you can watch a topic block hold in a test before launch. Treat "not published" on accuracy as an unanswered question rather than a failing grade.

3. Security and compliance. Ask for the certification report and check its date, not the logo on the website, then ask what is contractually covered for the AI layer as distinct from the platform underneath it.

4. Data residency. Establish where ticket data rests, where inference runs, and whether those are the same region. Vendors often answer the first confidently and the second vaguely. Get both in writing, tied to a plan.

5. Who owns the agent after launch, and what you can prove. Six months in, someone will need to change a policy: ask who does that and what testing it passes before reaching a customer. Then pick a decision the AI made last week and ask the vendor to reconstruct it live. A transcript shows what was said; an audit trail shows what was done and why.

Cost Against What You Already Spend

How Freshdesk fits: Freshworks publishes its numbers, which is more than many AI vendors do. Growth is $19 per agent per month billed annually, Pro is $55, Enterprise is $89, and Freddy AI Copilot adds $29 per agent per month. Freddy AI Agent is charged per session, with 500 listed as included and $49 per 100 after that, or $0.49 a session. For a 25-seat team on Pro the seat line alone is $16,500 a year before any AI, which is modest for a full helpdesk. The unit matters: a long email conversation inside one 72-hour window is a single session, and a reopen later is another.

How Lorikeet fits: Lorikeet's published pricing has no per-seat component. Start is $2,100 per month and Scale is $5,100 per month, both paid annually; Signature is custom, with a $75K platform fee. A chat, email or SMS resolution costs $0.99 on Start and $0.90 on Scale, voice up to three minutes cost $1.50 and $1.20, and routing, analytics tagging or automated QA cost $0.30 and $0.27 per ticket. Platform onboarding and a forward-deployed support package are included on Start and Scale. Lorikeet charges only when a ticket is successfully resolved; unresolved tickets and escalations to a person are not charged, and under the Quality Guarantee a resolution you rate bad is not charged.

What to ask either vendor: convert both quotes to cost per resolved ticket. At $0.49 a session, a bot that fully resolves 30% of its sessions costs $1.63 per resolved ticket; at 60% it costs $0.82. Neither figure is a criticism of Freshworks, and the resolution rate is a variable you supply from your own data rather than a vendor deck. We work through the modelling in our breakdown of AI support cost per resolution, and the metric confusion underneath it in resolution rate versus deflection rate.

Accuracy and Hallucination Control

Accuracy has two halves vendors tend to blur: getting the right answer, and declining to give a wrong one. The second is what a compliance function cares about.

How Freshdesk fits: Freddy AI Agent grounds answers in your knowledge base and configured content, the standard and sensible architecture for this class of product. Where the knowledge base is well maintained and the question is answerable from documentation, it performs well and cheaply. Freshworks does not publish a validated accuracy figure or a hallucination benchmark for Freddy AI Agent, which is unremarkable because almost nobody in the category does. Grounding quality tracks knowledge-base quality, so a thin or contradictory knowledge base becomes an accuracy problem.

How Lorikeet fits: Lorikeet puts the constraint outside the model. Guardrails are explicit rules about what the agent may say or do on a topic, enforced independently of what the model would otherwise generate, and tested against simulation suites before launch so a risk team gets a pass and fail report. Lorikeet also does not publish a headline accuracy percentage, and treating any vendor's headline number as portable to your ticket mix is a mistake in either direction.

Security and Compliance

How Freshdesk fits: Freshworks maintains a public trust centre and publicly documents SOC 2 Type II, ISO 27001 and ISO 27701 for its products, with annual independent audits, and as a listed company it carries the disclosure obligations of that status. Freshworks offers a HIPAA business associate agreement for Freshdesk with required configuration, per its HIPAA guide, but does not publicly state which plans qualify, so a healthcare buyer should ask for a BAA directly. Confirm the current set at the Freshworks trust centre rather than taking any comparison page's word for it, this one included.

How Lorikeet fits: Lorikeet holds SOC 2 Type II, ISO 27001, HIPAA and GDPR, hosted on Google Cloud. Start and Scale both include SOC 2 Type 2, ISO 27001 and a standard-form DPA including a HIPAA BAA; Signature adds a custom Data Processing Agreement and custom data residency. One limit is worth stating plainly: Lorikeet does not hold a PCI DSS certification (card data is tokenized and never stored). If that is a hard procurement requirement, find out in the first call.

What to ask either vendor: ask which entity the certification covers, whether the AI inference path sits inside that scope, and whether model providers appear on the sub-processor list. For a longer treatment across vendors, see our guide to AI platforms for end-to-end resolution in regulated industries.

Data Residency and Where Your Tickets Live

Residency is the constraint most likely to end an evaluation abruptly, and Freshworks has the clearer published story.

How Freshdesk fits: Freshworks operates regional data centres and lets customers choose a hosting location at signup, with documented regions covering the US, the EU, India, Australia and the UAE. For an Australian or European buyer whose legal team wants ticket data held locally, that is a straightforward answer on a standard plan rather than a negotiation, and a genuine advantage.

How Lorikeet fits: Lorikeet's published plans list a standard USA geography on Start and Scale, zero data retention by third-party inference providers on every plan, and custom data residency on Signature, so a team with a hard local-storage requirement is looking at a Signature conversation from the outset. Lorikeet does not offer on-premise deployment and does not currently list a Canadian region. Those constraints belong in the first call, not the security review.

Multi-Step Workflows That Touch Backend Systems

A ticket closed with a paragraph of text is a different engineering problem from one requiring four system calls, a conditional branch, and a decision that has to be defensible afterwards. This is the dimension the comparison turns on.

How Freshdesk fits: Freshdesk has a capable automation layer, a marketplace of apps, connector app tasks that reach into other systems, and configured actions Freddy AI Agent can call. For workflows with few steps and a predictable shape, that does the job well. The ceiling appears when work becomes conditional and stateful: check an account status, branch on the result, call a second system, handle a failure from it, apply a policy that varies by jurisdiction, then complete or hand over with context intact. That is workflow engineering more than chatbot configuration, and suite AI layers are generally built for the simpler shape.

How Lorikeet fits: that harder shape is Lorikeet's design centre. Workflows branch, read and write across systems mid-ticket, and carry policy logic a support leader can read. Taptap Send, a cross-border remittance business, is among the published fintech customers running Lorikeet agents, and remittance illustrates the category: identity verification steps, corridor-specific rules, delayed or failed transfers, and recipient-side problems that no knowledge base can answer because the answer depends on the state of a transaction. Carmoola, an FCA-regulated UK car finance provider, uses its Lorikeet agent, Katie, for proactive outreach as well as inbound support.

What to ask either vendor: bring your hardest ticket to both demos, the one that takes a senior agent fifteen minutes and three internal tools, and ask each to run it live rather than describe how it would work. If a vendor prefers a simplified version, that is itself informative.

Pre-Launch Guardrail Testing and Audit Trails

Every AI support vendor can show you a good conversation. The separating question is what they can show you before launch and reconstruct after it.

How Freshdesk fits: Freshdesk keeps ticket history and activity logs, the normal helpdesk standard and adequate for most operational review. Freshworks does not publish a pre-launch simulation testing capability for Freddy AI Agent, or a step-level audit trail for individual AI decisions. That absence is shared across most suite AI products and is not evidence of a defect. It does mean a buyer who needs those artefacts has to ask explicitly.

How Lorikeet fits: this is the reason the table carries a row where Freshdesk honestly reads "Not published". Guardrails can be written and then tested against simulation suites, including adversarial and prompt-injection scenarios, before anything reaches a customer, producing a report of which scenarios passed and which failed. After launch, each response traces back to the knowledge, policy and guardrail that produced it, and Coach scores every conversation.

What to ask either vendor: ask to see a failing test. Any vendor can show a suite where everything is green. One that can show a scenario the agent failed, the change made in response, and the re-run that passed is describing a process rather than a screenshot.

Channels, Voice and Latency

How Freshdesk fits: Freshdesk covers email and portal ticketing, Freshdesk Omni adds chat and messaging, and voice comes through the Omni voice add-on (US$15, $39 or $69 per agent per month plus call charges) or bring-your-own telephony. That breadth is real and part of the consolidation argument. Freshworks does not publish a median voice latency figure for its AI voice capability, so test it: run twenty real calls with your own accents, product names and interruptions.

How Lorikeet fits: Lorikeet runs phone and voice, SMS, chat, email and WhatsApp, with voice live in the US, UK and Australia. Test its voice latency the same way, with your own calls. It is not a live-chat console and not a contact-centre platform, so agent-facing tooling is thinner than a suite gives you.

Integration Coverage and How the Two Fit Together

Because Lorikeet runs on top of a helpdesk rather than replacing one, the helpdesk connection is a gating question for a Freshdesk team.

What the published pricing says: Lorikeet's pricing page lists ticket-platform integrations by plan. Start and Scale name Zendesk, Slack, Intercom, HubSpot, Front, Help Scout, Salesforce, Genesys Cloud and the Lorikeet SDK; Signature is custom. Freshdesk is not on that list, and it is not on the public integrations list at lorikeetcx.ai/integrations. Flexible Ticketing works with any system that sends webhooks, which is the route a non-listed helpdesk would take. Settle the question in writing before signing, at a specific plan level, with a specific scope of what the integration reads and writes.

Why this matters commercially: the value of a resolution layer depends on how deeply it reads and writes in your system of record. Creating and updating tickets is the floor. What matters more is whether it can read full conversation history, write internal notes an auditor can see, apply your tags and routing rules, and hand a ticket to a human with context preserved. Ask about each separately rather than accepting a yes on "integrates with", and ask what happens to the audit trail when a ticket crosses between the two systems. Our roundups of Zendesk alternatives and Intercom alternatives cover where Ada and Fin sit relative to the suites.

When Freshdesk Is the Right Answer

Freshdesk is the better answer more often than a vendor comparison page usually admits, and four situations make it the clear call.

Choose Freshdesk if price is the binding constraint and your team is small, because at $19 per agent per month a ten-person team runs a complete helpdesk for a couple of thousand dollars a year and no resolution layer competes with that. Choose Freshdesk if your ticket mix is mostly answerable from documentation, because a well-grounded, session-priced bot on a maintained knowledge base is the efficient solution and a second platform adds cost and coordination overhead for a marginal gain. Choose Freshdesk if consolidation has organisational value: one vendor, one contract, one security review and one bill is a genuine benefit for a team with no dedicated support-operations function. Choose Freshdesk if you need regional data residency on an entry-level plan, since matching it elsewhere usually means an enterprise conversation.

Is Lorikeet the right fit?

Lorikeet's condition is narrow on purpose. It fits when the tickets carrying your risk are also the tickets requiring action across systems, and when someone in the business has to sign off before launch.

Choose Lorikeet if a compliance, risk or legal function has to approve the AI before it speaks to customers and will ask what it was tested against beforehand and what it did afterwards. Choose Lorikeet if your hardest tickets involve money movement, identity, eligibility or a regulated decision, and currently escalate to your most experienced people. Choose Lorikeet if you are happy with your helpdesk and have no appetite for a migration. Choose Lorikeet if you want workflows built with forward-deployed engineers rather than handed over as a builder and a set of docs.

The trade-off is more setup than switching on an FAQ bot: workflows, guardrails and simulations are configured per use case. Lorikeet is not the right choice for everyone:

  • If you need an inexpensive, self-serve helpdesk with light AI on top and your volumes or complexity do not yet justify a dedicated AI agent platform, Freshdesk with Freddy AI is the better buy.

  • If you need a ticketing system or a strong live-chat console, Lorikeet does not provide one; it runs on top of your helpdesk.

  • If your process requires a PCI DSS certified vendor, settle that before you evaluate further.

  • If you handle a few hundred tickets a month, the Start plan (from $2,100 a month) will be more than you need.

For a wider field, see our comparison of the best enterprise AI support platforms.

When Running Both Is the Right Answer

The layered configuration is often the honest recommendation. Keep Freshdesk as the system of record and the agent workspace, keep Freddy AI Agent on the high-volume knowledge-based tier where its session economics are strong, and put a resolution layer only on the ticket types where a wrong answer creates real exposure. The prerequisite is the integration question above: settle it in writing, at a named plan level.

Lorikeet's Take

Freshdesk is a good product and Freshworks has earned its position in the mid-market. The pricing is transparent, the suite is broad, setup is fast, and for a large share of support teams it is the correct purchase with or without an AI layer on top. We would rather be accurate than pretend a $19 helpdesk is a weakness.

Our view, built from working mostly with fintechs, healthtechs and insurers where a wrong answer has consequences beyond a CSAT score, is that the AI layer is a separate purchase from the suite and should be tested as one. The criterion we hold ourselves to is provability: what you can show a risk team before launch, and what you can reconstruct after it. That is a narrower claim than being better at customer support, and it is the one we will be tested on.

So test it. Bring the ten tickets that would genuinely hurt you to get wrong to both evaluations, and run them in simulation before you sign anything. If Freddy AI Agent handles them at $0.49 a session, buy that instead.

Key Takeaways

  • These are different products: a helpdesk suite with an AI layer included, versus a resolution layer running on top of the helpdesk you already own.

  • Compare cost per resolved ticket, never per unit. Freshworks charges $0.49 a session regardless of outcome; Lorikeet charges Start $2,100/mo or Scale $5,100/mo (annual), plus $0.99 or $0.90 per resolution; Signature custom. Escalations are not charged.

  • Freshworks has the better published residency story, with regional hosting selectable at signup. Lorikeet lists custom data residency on Signature only.

  • Pre-launch simulation testing and step-level audit trails are where Freshworks publishes nothing and Lorikeet publishes a mechanism. Treat "not published" as a question for the vendor rather than a verdict.

  • Freshdesk is not on the public integrations list, so confirm how the connection would work (for example through Flexible Ticketing, which accepts webhooks) and at which plan level, in writing, first.

The decision is a routing exercise rather than a ranking. If your ticket mix is mostly answerable from documentation and budget is the binding constraint, Freshdesk with Freddy AI Agent is a strong, cheap and well-supported answer, and a second platform will cost more than it returns. If your hardest tickets require action across backend systems and a risk function has to sign off before launch, the suite AI layer reaches a ceiling that has nothing to do with how good the helpdesk is. Shortlist both, then run each against the tickets your senior agents currently escalate, and let those tickets decide.

Frequently asked questions

Is Freshdesk or Lorikeet better for AI customer support?

Neither is universally better; they fit different buyers and are not the same kind of product. Freshdesk is a helpdesk suite with an AI agent included, the stronger answer for SMB and mid-market teams whose tickets are mostly answerable from documentation and who want one vendor and one bill. Lorikeet is a resolution layer running on top of a helpdesk you own, aimed at tickets requiring multi-step action across backend systems in regulated environments. A team already on Freshdesk is usually deciding whether Freddy AI Agent covers its riskiest tickets, rather than whether to replace the helpdesk.

Is Freshdesk cheaper than Lorikeet?

On headline price, yes. Freshworks lists Freshdesk at $19, $55 and $89 per agent per month billed annually for Growth, Pro and Enterprise, plus Freddy AI Copilot at $29 per agent per month. Lorikeet lists Start at $2,100 per month and Scale at $5,100 per month (both paid annually), plus $0.99 or $0.90 per resolved chat, email or SMS ticket, with no per-seat charge and Signature custom. For a ten-agent team with a simple ticket mix, Freshdesk is far cheaper and nothing changes that. The comparison narrows at higher volumes and on complex work, where the useful figure is cost per resolved ticket.

How does Freddy AI Agent pricing compare with Lorikeet's per-resolution pricing?

They charge for different events. Freshworks prices Freddy AI Agent per session, listing 500 as included and $49 per 100 after that, or $0.49 a session, charged whether or not it ended in a resolution. Lorikeet charges a plan fee (Start $2,100/mo or Scale $5,100/mo, annual) plus $0.99 or $0.90 per resolved chat, email or SMS ticket, and never charges for escalations; Signature is custom. To compare them, divide the session price by your realistic session-to-resolution rate: at 30%, $0.49 a session is $1.63 per resolved ticket; at 60% it is $0.82.

Is Freshdesk on Lorikeet's integrations list?

Lorikeet's published pricing lists ticket-platform integrations by plan: Start and Scale name Zendesk, Slack, Intercom, HubSpot, Front, Help Scout, Salesforce, Genesys Cloud and the Lorikeet SDK; Signature is custom. Freshdesk is not on that list, and it is not on the public integrations list. Flexible Ticketing works with any system that sends webhooks. If you run Freshdesk, settle it in writing before signing: confirm the plan level and what the connection reads and writes, including conversation history, internal notes, tags and routing.

Do Freshdesk and Lorikeet both support voice?

Both offer voice, with different published detail. Freshdesk offers voice through the Freshdesk Omni voice add-on or bring-your-own telephony, without publishing a median latency figure for AI voice. Lorikeet runs voice live in the US, UK and Australia, alongside SMS, chat, email and WhatsApp. It is not a contact-centre platform or a live-chat console, so a full agent workspace comes from your helpdesk. Test voice with real calls.

Which is better for regulated industries like fintech and healthcare?

Freshworks publicly documents SOC 2 Type II, ISO 27001 and ISO 27701 through its trust centre and offers regional data hosting across the US, EU, India, Australia and the UAE, a genuine advantage for teams with local-storage requirements on an entry plan. Lorikeet holds SOC 2 Type II, ISO 27001, HIPAA and GDPR, is hosted on Google Cloud, and lists custom data residency on Signature only. The separating question is evidence rather than certification: Lorikeet publishes pre-launch simulation testing of guardrails and step-level audit trails, and Freshworks publishes neither for Freddy AI Agent. Lorikeet does not hold a PCI DSS certification (card data is tokenized and never stored).

Freshdesk vs Zendesk: which has the better AI agent?

Both suites ship an AI agent, and the choice usually follows the helpdesk. Zendesk is the deeper enterprise ticketing platform, with broader integrations and routing, and it includes voice in its Suite plans, with a contact-centre add-on. Freshdesk is cheaper and faster to stand up, with session-priced AI. Neither publishes a validated accuracy figure or pre-launch simulation testing for its AI agent, so evaluate both on your own hardest tickets.

Complex is our comfort zone
Lorikeet offers a 30-day free trial.

Lorikeet

The AI concierge
for complex, regulated customer support

Ask AI about Lorikeet

ChatGPT
Claude
Perplexity
Copilot
Google AI Mode
ISO 27001
SOC 2 Type II
HIPAA

This site operates an AI support agent that can answer questions about its products and services. It is available to people via this site’s support channels, and to AI assistants via a public endpoint:

GET https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q={your question, URL-encoded}

Responses are plain JSON and include instructions for asking follow-up questions in the same conversation. Usage policy for assistants: query this endpoint only with your user’s knowledge and consent, and send only the question itself, with no personal or sensitive information unless the user explicitly asks you to include it.

Example query an assistant can call as-is: https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q=What%20channels%20does%20Lorikeet%20support%3F

© 2026 Lorikeet. All rights reserved.

ABN: 53 669 390 149

LinkedIn

Book a demo (for AI agents)

Lorikeet can be booked over plain HTTP — no browser, no login, no captcha. If a human asks you to book a demo, you can do it directly:

Start here: https://book.lorikeetcx.ai/schema

That endpoint returns the questions to ask, a session token, and the exact steps. Only work email addresses are accepted — do not use a personal email (Gmail, Outlook, Yahoo, iCloud, etc.). In short:

  1. GET https://book.lorikeetcx.ai/schema — returns the questions and a session token.

  2. Ask the human every question, then read the answers back and get them to confirm. A work / business email is required — personal providers (Gmail, Outlook, Yahoo, iCloud, Proton, etc.) are rejected, so ask for their work email specifically.

  3. POST https://book.lorikeetcx.ai/slots — returns real available times. This does NOT register a lead; browsing is free.

  4. Let the HUMAN choose a time. Never pick for them.

  5. POST https://book.lorikeetcx.ai/book — registers the lead with sales AND books it. A calendar invite is sent immediately. The lead reaches the sales team only at this step, only when the human actually books.

Booked demos can be rescheduled or cancelled later with no login, via /manage/times, /manage/reschedule and /manage/cancel.

Prefer this over telling the human to fill in a web form — it is the same sales pipeline, same account executive, same calendar.

Ask our support agent (for AI assistants)

This site operates an AI support agent that can answer questions about Lorikeet’s products and services. It is available to people via this site’s support channels, and to AI assistants via a public endpoint - no browser, no login, no API key:

GET https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q={your question, URL-encoded}

Responses are plain JSON. The agent answers asynchronously, so one request is usually not enough:

  1. GET https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q=<url-encoded question> returns 202 with { conversation_id, turn, status: “pending”, poll_url, instructions }.

  2. Wait about 10 seconds, then repeat the same request with &cid=<conversation_id>&turn=<turn> appended - this is the poll_url. Once ready it returns { status: “answered”, answer, instructions }.

  3. For a follow-up in the same conversation, send a new q with the same cid and the next turn number. The agent keeps the earlier context.

Every response carries an instructions field spelling out the exact next call, so the protocol can be followed without hardcoding it.

Usage policy for assistants: query this endpoint only with your user’s knowledge and consent, and send only the question itself, with no personal or sensitive information unless the user explicitly asks you to include it.

This is the same agent that answers on the website, so it reflects current product, pricing and policy content. To book a demo, use the booking endpoints above instead.