Sapiens
Core insurance software for policy, billing, and claims processing
Polygrade integrates with Sapiens, a policy, risk, or CRM platform. Sapiens is core insurance software covering policy administration, billing, and claims, used across both property and casualty and life and annuity lines. Polygrade authorizes claims against the context it holds and writes decisions back.
Sapiens is core insurance software covering policy administration, billing, and claims, used across both property and casualty and life and annuity lines. Polygrade reads the context Sapiens already holds and authorizes the claim against it, writing the decision, and everything that led to it, back as the record of what happened.
What Polygrade does with Sapiens
Polygrade captures claim data 24/7 through web form, chat, SMS, and voice, and validates it against the coverage Sapiens holds, policy administration records and claim files, before authorizing repair versus replace, or approving inside your configured thresholds.
The context that reaches Sapiens isn’t a call transcript, it’s a structured SMS conversation. Polygrade triages the homeowner over text, with 80 to 83 percent responding, and that exchange is what populates the fields Sapiens needs to authorize the claim correctly the first time.
From there, Polygrade sources parts across suppliers, tracks the order, and validates the resulting invoice against the authorization record before payment releases, with every decision written back to Sapiens alongside the confidence level it was made at.
How the Sapiens connection works
Sapiens exposes an API for policy and claims data, which is what Polygrade reads and writes against.
Where Sapiens doesn’t expose a field Polygrade needs, a Forward Deployed Engineer builds the mapping during deployment rather than asking Sapiens to change. Authorization, parts, and payment can go live against Sapiens independently of each other.
What stays in Sapiens
Policy administration and billing configuration stay inside Sapiens.
What changes is how much of the authorization decision a person has to make by hand. Polygrade applies your business rules against the context in Sapiens and routes only the exceptions to a reviewer.
Data handling and security
The connection to Sapiens runs on a company-specific Polygrade instance, one carrier’s policy and claim data are never accessible to another. Polygrade is SOC 2 compliant, with both Type I and Type II audits complete.
Every authorization decision carries a confidence level and the inputs it drew from Sapiens, and is logged. Decisions above your configured value or confidence thresholds route to a person before anything executes.
Deploying the integration
A dedicated Forward Deployed Engineer works with your team to build and maintain the Sapiens connection, mapping the specific fields and authorization rules your program already runs on.
Frequently asked questions about Polygrade and Sapiens
Does Polygrade replace Sapiens?
No. Sapiens remains the system of record for the underlying policy and case data; Polygrade executes the authorization decision and the work that follows it.
How does Polygrade connect to Sapiens?
Sapiens exposes an API for policy and claims data, which is what Polygrade reads and writes against. Where no interface exists, a Forward Deployed Engineer builds the connector during deployment.
Are authorization decisions against Sapiens auditable?
Yes. Every decision carries a confidence level and the specific inputs from Sapiens it was based on, and is logged for review.
