Waypoint Suites / Producer Portal
Distribution that stops calling you for answers
Two audiences in one portal: agencies see their own book, statements and paperwork, and the carrier side sees hierarchy, schedules and performance. Licensing gates what either can place.
Formerly the Agent Portal. The rename followed the audience — producers and principals are who signs in.
Walk an agency’s weekProblem 1 — Inbound questions
The answers are already in the portal
My Book
Their business, their view
A producer sees their own book; a principal sees the agency’s. Scope follows the role, not a filter somebody sets.
My Statements
Commission, self-served
Statements per agency and per producer, available without an email asking for them.
My Paperwork
Appointments and licenses
Current state, expiries and what is outstanding — visible while there is still time to act.
Problem 2 — The appointment wall
Business that cannot be placed without authority
Hierarchy
Structure as platform data
Agency, principal and producer relationships live in the platform, so commission and reporting read one tree.
Schedules
Commission terms
Schedules attached to the relationship rather than to a spreadsheet somebody maintains.
Performance
Production, per agency
Volume and mix by agency and producer, on the same data the statements read.
Termination, not deletion
A relationship ends. The record does not.
An agency is terminated, which stops new placement while leaving the book, the history and the commission record intact and fully reportable. There is no delete path, because a book you cannot reconstruct is a liability the moment somebody asks about it.
Placement stops
No new business can be written the moment termination takes effect.
The book stays
In-force business, history and commission record remain readable.
Reporting works
Terminated relationships still appear in historical production reporting.
Audited
The termination itself is a recorded transition with a reason and an actor.
Role catalog — Producer Portal
Roles are per-portal. An agency principal who also works claims for a carrier holds two roles in two portals rather than one role broad enough to reach both.
The carrier-side pages sit behind carrier roles, not agency ones — an agency principal cannot reach another agency’s hierarchy, and the refusal is enforced server-side on every request.
What it solves
In the portal, scoped to the producer or the agency, without a request being made.
License and appointment state gate placement at the point of quoting.
Agency, principal and producer structure is platform data, with schedules and performance reading the same tree.
Termination stops placement and preserves everything else, still reportable.
Scope follows the role and is enforced on the server; agency roles cannot reach carrier-side pages at all.