Eight portals. One operations platform. Every claim about it stated with the mechanism underneath.
Waypoint runs insurance operations end to end — claims, underwriting, billing, producers, personnel and the people you insure. This site says what is shipped, names what is in build, and shows how each of it works.
Request a DemoBuilt, not planned
What is actually there
What it solves
Auto-assignment runs at creation across every intake door and respects state licensing.
The queue holds every unassigned claim, but in practice it stays near-empty: assignment runs the moment a claim is created — from any of the four FNOL routes, bulk upload or agentic capture — and only licensed adjusters in the loss state are candidates. Supervisors reassign from the same queue when workload demands it, and the change is recorded on the file.
Authority ceilings route the payment request to Payment Approvals, on the file.
Each role carries a payment ceiling. Inside it, the adjuster pays. Above it, the request becomes a queued approval item carrying the claim, the exposure and the reason — visible to every approver rather than sitting in one person’s inbox while they are on leave.
Acknowledgment, contact and decision dates computed from loss and report dates, shown book-wide.
Claim Compliance computes the statutory dates per jurisdiction rather than asking the adjuster to know them. Compliance Deadlines then shows every clock across the operation on one page, so an aging acknowledgment is triaged as a queue item instead of found during a market conduct review.
Total reserve is maintained by the database, so no screen or integration can disagree with it.
The total is computed by the database from the ledger rows, not assembled by application code. A screen, an API caller and a batch job therefore see the same figure, and reserve bands flag an out-of-range change for review while still letting the adjuster exercise judgment.
Outcomes, with the reason attached
The waits inside a claim — unassigned files, pending approvals, unnoticed deadlines — are removed structurally rather than chased by a supervisor.
Money leaves a claim in small, defensible-looking increments. You cannot manage that from a monthly report; you manage it where the reserve is set.
Fewer handoffs, less rework and no monthly reconstruction of what was done and what should be billed for it.
Severity, complexity, reserve adequacy and litigation likelihood, modeled on your own history rather than an industry average.
The isolation, encryption, retention and recovery answers a carrier asks for are already written down — including where the position is weaker than we would like.
Trust
The questions a security review asks
Dual-wall isolation
Application scoping plus forced PostgreSQL row-level security on tenant tables, for every connection.
Encryption with search
Application-layer encryption of personal information; a keyed blind index keeps it searchable without decryption.
One transition door
Every status change validates, records who and why, and writes an audit row. There is no second path.
Verified restores
Encrypted backups with a restore script, a weekly verification and dead-man alarms if either stops happening.
A gated pipeline
The full suite runs before any release, and a red suite will not start the service.
Your exit, in writing
What leaves with you, in what format, and when our copy stops existing.
Questions
Twice, independently. The application resolves the caller’s organization from their session and scopes every query to it; a request cannot name a different organization because the value is never accepted from the client. Underneath, PostgreSQL row-level security is enabled and forced on tenant tables, with policies on both organization and tenant, applied by the database engine for every connection including administrative ones.
No. Portals are separate applications behind separate entitlements, and access is entitlement first, role second, both defaulting to no. A user with a powerful role in an organization that has not bought the module reaches nothing. The ordering is enforced on the server on every request — a hidden menu item is a courtesy, not the control.
It is encrypted at the application layer, not merely on the disk volume. Names, emails and phone numbers stay searchable through a keyed blind index without being readable; tax identifiers and dates of birth are encrypted and masked from non-administrative roles; integration credentials are never returned to any screen once saved; free-text notes are encrypted.
Through a release pipeline that runs all the full automated test suite and refuses to restart the service if the suite is red. Schema changes are ordered and reversible — every migration recorded. Backups are encrypted, restores are verified rather than assumed, and dead-man alarms fire if a scheduled backup or restore check stops happening.
The Billing Portal screens are in the current build phase, though the rating and billing engines beneath them are complete and tested. Per-portal role catalogs are specified and build ahead of those screens. The Customer Portal policy view is designed but needs a policyholder identity model, and policyholder card payment is out of scope pending a compliance decision. That list lives on the site, not only in the manual.
See it against your operating model
Bring your own numbers. We will show the mechanism, not a montage.
Request a Demo