Make your AI support metrics your own

Make your AI support metrics your own

Estelle Berton, blog author, smiling at camera wearing an orange top with dark shoulder-length hair.

Estelle Berton

|

|

0 Mins

"What's a good engagement rate?" is probably the question I hear most from Lorikeet subscribers. I get it. When you're implementing AI support, you want to know you're on the right track. 

Here's how I answer that question – the best metrics for your business might be the opposite of what works for someone else.

Why benchmarks lead you astray

I recently spoke with a customer who was stressed about their "high" AI engagement rates compared to industry benchmarks. But when we dug deeper, we realized their AI agent was doing exactly what they needed – helping customers discover features, complete complex workflows, and ultimately spend more on the platform.

For them, high engagement was a sign of success. For another business, it might signal product failures.

This isn't about being contrarian. It's about recognizing that AI fundamentally changes what "good" support looks like.

The old rules don't apply anymore

Traditional support metrics were built around human constraints:

  • One-touch resolution mattered because every interaction cost money

  • First response time mattered because customers were waiting in queues

  • Tickets per agent mattered because you needed to staff appropriately

With AI, these constraints go away. Your AI agent can handle multiple interactions without a linear increase in costs. It responds instantly. It scales almost infinitely.

So why are we still measuring success the same way?

Finding your north star metrics

Here's the framework I use with subscribers:

First, clarify your support strategy. Are you using AI to reduce costs and deflect tickets? That's completely valid. Or are you building an AI concierge that proactively helps customers succeed? Also valid. Just be clear about which strategy you're pursuing.

Then, choose metrics that align

  • Cost reduction focus: Track deflection rates, ticket reduction, cost per resolution

  • Revenue/retention focus: Track customer lifetime value, transaction rates, feature adoption

Finally, measure what happens after the interaction. Do customers who engage with your AI agent churn less? Buy more? Get to their "aha moment" faster? That's what really matters.

A real example

One of our telehealth subscribers tracks two different engagement metrics:

  • Medical support engagement (positive) – shows patients are using medical services

  • Customer support engagement (negative) – indicates product friction

Same company, same AI system, completely different success metrics. Because context matters.

Moving forward

I know it's tempting to look for that magic benchmark that tells you you're doing it right. But the businesses seeing real success with AI support are the ones who've done the harder work of defining what success means for them specifically.

Your metrics aren't wrong. They're just not yours yet.

Next time someone shares their AI support benchmarks, don't ask "How do I compare?" Ask instead: "What are they optimizing for, and is that what I want too?"

Book a call

See what Lorikeet is capable of

Share this article

Related posts

Ready to deploy human-quality CX?

© 2026 Lorikeet. All rights reserved.

ABN: 53 669 390 149

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

Ready to deploy human-quality CX?

© 2026 Lorikeet. All rights reserved.

ABN: 53 669 390 149

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

Ready to deploy human-quality CX?

© 2026 Lorikeet. All rights reserved.

ABN: 53 669 390 149

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

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.