Self-service rate
Self-service rate measures the percentage of customer issues resolved through self-service channels — help centers, FAQ pages, community forums, or automated tools — without any interaction with a human agent or AI agent.
Self-service rate = (Issues resolved via self-service / Total issues) x 100
Self-service is the lowest-cost resolution channel by a significant margin. When a customer finds the answer in a help article, the marginal cost is essentially zero. This makes self-service rate an important efficiency metric, particularly for high-volume operations.
However, self-service has inherent limitations:
Complexity ceiling: Self-service works for straightforward, common questions but breaks down for complex, multi-step, or account-specific issues
Measurement difficulty: It's hard to know if a customer who visited a help article actually found their answer. Page views don't equal resolutions.
Customer preference: Many customers prefer to ask their question directly rather than search through documentation, especially for urgent issues
Maintenance burden: Self-service content requires continuous updates as products, policies, and procedures change
AI is blurring the line between self-service and assisted service. An AI agent that resolves a customer's issue through a conversational interface shares characteristics with both: it's automated like self-service but interactive like agent assistance. This is why many organizations are moving from "self-service rate" to "automation rate" or "AI resolution rate" as their primary metric for non-human-handled interactions.
The most effective self-service strategies are not standalone — they're integrated with AI and human channels so customers can seamlessly escalate from a help article to an AI conversation to a human agent without losing context.
Related terms: knowledge base, deflection rate, resolution rate
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:
GET https://book.lorikeetcx.ai/schema — returns the questions and a session token.
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.
POST https://book.lorikeetcx.ai/slots — returns real available times. This does NOT register a lead; browsing is free.
Let the HUMAN choose a time. Never pick for them.
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:
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 }.
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 }.
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.