Rivl Insurance is an agency management system for independent property and casualty agencies. It classifies the incoming email that runs a small agency, produces quotes and proposals, issues certificates and identification cards, and gives the insured a portal that does not require a phone call.
One flat rate for the whole agency. It exists because the incumbent systems price per seat, charge for modules, and still leave the principal sorting mail at seven in the morning.
The agency sign in as it runs today. Certificates, ID cards, the client portal, renewals, claims and quoting sit behind one login.
Nothing here is exotic. What is unusual is that it is one product at one price, built for an agency of two to twenty people rather than sold down from an enterprise suite.
Every incoming message classified as renewal, claim, certificate, service or noise, attached to the policy and the insured it belongs to, and routed with a confidence score attached.
Quote intake through to a client ready proposal document, with the coverage comparison the insured actually asks about rather than a raw carrier printout.
Certificates of insurance and identification cards issued from the policy record on request, which removes the most common interruption in a small agency day.
Policy documents, identification cards, certificate requests and first notice of loss in a place the insured can reach at ten at night without calling anyone.
A retrieval assistant answering agency questions from the product documentation itself, so a new hire is not dependent on the principal being free.
Self serve subscription at one price for the agency. No per seat pricing, no module upsell and no implementation fee.
The demonstration version of this product is easy. The production version has to handle a carrier that changes its notice format without warning, an insured who replies to a five year old thread, and a principal who will abandon the system the first time it files something in the wrong place.
Every classification carries a score and a threshold below which the message goes to a person rather than a queue. We tuned this against a live mailbox rather than a curated sample, which is where we learned that a consumer receipt landing in an agency inbox is a precision problem and not a bug to be suppressed.
Ask Rivl answers from a maintained corpus of product help documents rather than from model recall. When the corpus does not cover the question the honest answer is that it does not, which is a design decision and not a limitation.
The system reached production behind a full end to end suite covering the paths an agency actually uses, run on every change. A release that breaks quoting does not reach an agency that has clients waiting on a proposal.
A production incident traced to an import shipped without its module produced a permanent process guard rather than a patch. Repository completeness is now asserted before any deployment. The interesting part of an outage is what it changes.
Payment, plan changes and controlled complimentary access are handled in the product. Nobody has to email us to change a plan, which is the difference between a product and a service contract.
The insured portal is a progressive web application with push notification support, so a certificate request or a claim acknowledgement reaches a contractor on a job site rather than sitting in an inbox until evening.
Underneath the insurance vocabulary this is a document and message understanding system with a self serve product wrapped around it. That combination is the most common thing regulated organizations ask us for, and it rarely has anything to do with insurance.
Intake that arrives unstructured and must be routed correctly. Referrals, remittance, correspondence, claims, applications and complaints. With an abstention threshold so the exceptions surface instead of being absorbed.
Policies, procedures, plan documents, contracts and product documentation made answerable in the words your staff actually use, grounded in the source so an answer can be traced back to a page.
The requests that generate most of your inbound contact are usually the same five. Putting those five behind a portal that works on a phone is the cheapest reduction in operating cost available to most organizations.
Producing an accurate document from structured data on demand. Certificates, letters, statements, summaries and forms, generated from the record rather than typed from it.
Turning something your organization currently does as bespoke work into a self serve product with a price, a signup and a support path. Often the highest margin project available inside an existing business.
Runbooks, deployment guards and monitoring built during the project rather than promised after it. What we hand over is a system your team can run without us on the phone.
Fifteen minutes. Tell us what arrives, who reads it and what it costs you, and we will tell you whether this pattern fits or whether the constraint is somewhere else entirely.