Use case · Insurance
Prove that quote, bind and claim work after every release, and keep the evidence.
Prove that customers can get a quote, buy a policy and submit a claim from the outside, and show regulators the evidence.
Journeys worth assuring
Get a quote web
The quote form is the top of every funnel. When a rating engine or a third-party data enrichment call slows down, conversion falls before anyone sees an error.
Buy a policy web
Payment gateways, document generation and policy issuance are three suppliers in one step. The failure boundary matters for who you call.
Submit a claim web
First notice of loss is a regulated customer outcome. A broken upload widget is a Consumer Duty problem, not just a bug.
Reach claims by phone voice
IVR menus route to different queues by product. A carrier or IVR change can silently strand a whole line of business (cross-channel).
Insurers depend on a small number of journeys that each touch several suppliers: a rating engine, address and vehicle enrichment, a payment gateway, document generation, and often a broker or aggregator feed. Internal telemetry sees each system in isolation. ScoutSentinel exercises the whole journey from the outside, every few minutes, and tells you which step and which supplier the failure begins at.
What a Watch looks like
You describe the capability in plain language: “UK customers can get a home insurance quote and buy it with a test card, every five minutes, from three European locations.” ScoutSentinel discovers the entry points, proposes deterministic steps and assertions (status codes, visible elements, quote value within a range, an issued policy number) and asks you to approve the plan.
What you get when something breaks
One Event, not fifteen alerts. It shows the failure boundary (the step and the request that first failed), what still works (renewals, claims, sign-in), the confidence behind the conclusion and the coverage that produced it. Screenshots, HAR archives and the failing response are attached as evidence, hashed at capture, that you can share with a supplier or a regulator.
Outcome and behaviour, separately
After a release the quote journey may still succeed while the premium shown changes shape or a consent step appears. ScoutSentinel reports the outcome as achieved and the behaviour as changed, so product operations can decide whether the change was intended without waking the on-call engineer.
Why now
- Consumer Duty and FCA operational resilience rules ask for evidence that important business services stay within impact tolerances.
- Aggregator traffic punishes slow quotes immediately; a degraded rating engine is a revenue event, not an incident ticket.
- Claims and complaints handling have regulatory clocks. Timestamped, hashed evidence shortens the argument about when a journey broke.
Assure your first insurance journey
Describe the capability in plain language. ScoutSentinel proposes the plan, you approve it, and the first evidence arrives within minutes.