Customer churn rate
Customer churn rate measures the percentage of customers who stop doing business with a company over a given period. It is one of the most critical health metrics for subscription and recurring-revenue businesses.
Churn rate = (Customers lost during period / Customers at start of period) x 100
In B2C businesses, churn is often driven by poor customer experience — and customer service interactions are one of the most direct levers. Research consistently shows that customer service is both the leading cause of churn (when it's bad) and one of the strongest retention tools (when it's good). A single unresolved issue can trigger a cancellation; a single exceptional interaction can save one.
The relationship between customer service quality and churn is not linear. There's a threshold effect: adequate service prevents churn but doesn't build loyalty. Exceptional service — resolving issues quickly, proactively addressing problems, making customers feel heard — actively reduces churn below baseline rates.
For CX leaders, the connection to AI is significant. AI agents that genuinely resolve issues (rather than deflecting them) can reduce churn by:
Providing 24/7 availability, eliminating the frustration of waiting for business hours
Resolving issues in the first interaction more consistently than human agents
Identifying at-risk customers through interaction patterns and triggering retention interventions
Maintaining consistent quality across all interactions regardless of volume spikes
The counterpoint: poorly implemented AI can increase churn. Customers forced through unhelpful chatbot loops, unable to reach a human, or given incorrect information will churn faster than if they'd waited in a phone queue. The implementation quality matters as much as the technology choice.
Related terms: customer retention rate, customer lifetime value, customer satisfaction score
Learn more
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.