Insurance operations, stated plainly Trust Request a Demo
Waypoint Claims

Waypoint Suites / Customer Portal

The customer sees their claim. Nothing else.

A claim-scoped view for the customer on the other side of the loss: status, what has been received, what is still needed, and how to send it.

The policy view is designed but not shipped — it needs a policyholder identity model, and policyholder card payment is out of scope pending a card-handling compliance decision. Both are on the roadmap, neither is implied here.

See the customer view
1Page shipped — claim-scoped, deliberately narrow
0Remy assistants — a customer session is not a staff session
0Card payments accepted — out of scope, not coming quietly
1Claim visible per session, and only theirs

The scope

What a customer is shown, and why it stops there

Status

Where the claim stands

Current status in language a person who does not work in insurance can act on.

Documents

What has arrived

What has been received and what is still outstanding, so the answer is not “we will check”.

Upload

How to send the rest

A direct route for the missing document, landing on the file rather than in an inbox.

What is not here, on purpose

A customer session is not a staff session

Remy, the in-product assistant, is absent from this portal by design. So is any view of another claim, any premium screen, and any surface that could disclose a party’s encrypted personal information. The portal is scoped to one claim and to the person on it.

No assistant

Remy is internal. A customer is not staff.

One claim

Session scope is the claim, not the person’s whole history with you.

No premium

Policyholder billing is a different portal with a different payer.

Roadmapped

Policy view: designed. Card payment: out of scope. Stated, not blurred.

How a customer reaches the claim

There is no catalog to publish here, because there is nothing to grant. Scope ends when the claim no longer needs it.

  • Claim-scoped session
  • No standing account
  • No staff role
  • No cross-claim view

Personal information in the claim is encrypted at the application layer, and a keyed blind index keeps names and contact details searchable by your staff without being readable at rest.

What it solves

Count your status calls first

Then look at this page and decide how many of them it removes. That is the only number that matters for a customer portal, and it is measurable within a month.

See the customer view