Kin

In the US, insurance carriers are legally required to communicate with policyholders in writing for almost every significant claims decision, including payment, denial, and coverage explanation. Each state has its own regulatory requirements governing what those letters must contain and how they must be worded. For Kin, this meant managing hundreds of distinct letter templates across multiple states, product lines, and claim types.

The margin for error is zero, as an inaccurate or non-compliant letter carries direct financial and legal exposure. At the scale Kin operates, up to 40,000 or more letters per year, as the company grows, manual drafting was never really a viable path. Every letter had to be accurate, fast to produce, and easy to review before being sent.

Kin's engineering team set out to build an internal claims letter platform that would give adjusters a structured, controlled environment to draft, review, and send correspondence that had full legal and regulatory compliance. The challenge was not just solving the compliance problem, but also building the platform efficiently without diverting engineering resources toward building and maintaining a document-editing layer from the ground up.

Kin evaluated multiple editors before selecting CKEditor. The decision came down to two factors: feature completeness and engineering efficiency.

On the features side, CKEditor arrived with everything Kin required: text formatting, table support, copy-paste handling, and critically, Merge Fields and collaboration.

Merge Fields became the operational core of the letter platform. Template authors build base letter templates inside the platform using CKEditor. They insert dynamic placeholders for policyholder-specific data such as the insured's name, mailing address, claim number, or date of loss. When an adjuster opens a template to begin editing a claim-specific letter for the policyholder, Kin's claims API is called to populate those Merge Fields used in the document automatically. The adjuster receives a populated, structurally correct letter ready for review, not a blank page.

This architecture supports two distinct user roles within the platform. Admins create and manage the base templates. Adjusters use those templates to produce individual letters, with the ability to edit those templates or to add additional Merge Fields inline if specific claim circumstances require it. Once a letter is complete, it moves into an approval workflow utilizing CKEditor's collaboration features, Comments and Revision History. Using these capabilities, claims managers can review, annotate, and view and compare version history before they approve a letter.

On top of the discussion and review process, collaboration features also improve the compliance workflow with a clear audit trail at every stage: who authored the letter, what was changed, who approved it, and when. For a regulated industry where documentation integrity matters as much as the content itself, this is also a vital concern.

On the engineering side, CKEditor's native Angular integration allowed the team to implement the editor closely and quickly into their stack. Rather than building and maintaining a WYSIWYG editing component, Kin's engineers concentrated their effort on API design and a template management system that makes the platform function as a compliance tool, not just a word processor.

At the user-level, the internal platform is now in active rollout across Kin's claims department. Early user feedback has focused on the familiarity of the editing experience. Adjusters have noted that the interface and collaboration is consistent with tools they are familiar with, such as Google Docs, reducing the adoption friction. The most consistently praised feature is Merge Fields: adjusters report that automatic data population is the single biggest time-saver in their workflow.

At the platform-level, Kin was able to ship a compliance-ready claims management system in approximately half the time it would have required without CKEditor. By embedding a proven editor component rather than building one in house, Kin's engineering team could commit their capacity to the other parts of the platform like the claims integration or template management layer on a timeline that matched the business need.