Does auto-scoring replace my QA team?
No, and we would not want it to. Kelanyn does the reading; your QA specialists do the judging. In practice their job shifts from sampling random tickets to reviewing the flagged 5%, handling agent disputes, and keeping the rubric calibrated. Teams tell us that is the work they wanted to be doing all along.
How accurate is the scoring?
During onboarding you run calibration mode: Kelanyn scores conversations your graders have already reviewed, and you see the agreement rate per rubric line before anything goes live. Where the model and your graders disagree, you tune the rubric definitions until they converge. Low-confidence scores are always marked and routed for human review rather than reported as fact.
What happens to our customer data?
Conversation data is encrypted in transit and at rest, stays in your regional data store, and is never used to train models for other customers. You control retention, delete a ticket in your helpdesk and it is purged from Kelanyn within 24 hours. We sign DPAs, support EU data residency, and our SOC 2 Type II audit is underway ahead of launch.
Which helpdesks do you support?
Zendesk, Intercom, and Freshdesk at launch, covering tickets, email, and chat. Voice and additional platforms are on the roadmap; if yours is not listed, email us, integration order is driven by early access requests.
How do agents feel about being scored on everything?
Better than you would expect, because full coverage is fairer than sampling. Under a 2% sample, one bad ticket can tank an agent's month. Scored across all 200 of their conversations, one bad ticket is one bad ticket. Agents see their own scorecards, can dispute any score, and disputes go to a human.