Confirmed facts only
Keep drafts, guesses, and unconfirmed details out of export-ready material until the user confirms them.
Claim Packs
A claim pack is the private working bundle a user can build before deciding whether to submit a complaint, request review, or compare source-backed routes. This page explains the bundle without collecting facts.
Preparation, not submission
Claim Packs does not generate legal documents, file complaints, contact companies, estimate compensation, or share personal data. It points users to existing preparation surfaces.
Readiness posture
Private by default
A pack starts as user-controlled preparation, not a shared artifact.
Review before use
Sensitive details, missing dates, and route requirements should be checked first.
Explicit next step
External sharing or submission must be a separate opt-in action.
A claim pack is only ready to leave the private workspace when user-confirmed facts, route context, review blockers, and explicit action are clear.
Keep drafts, guesses, and unconfirmed details out of export-ready material until the user confirms them.
Carry the selected complaint route, requirements, and source notes beside the packet instead of implying eligibility.
Flag sensitive details, missing dates, redaction needs, and human-review questions before any external use.
Exporting a pack does not submit, publish, contact, advise, represent, or guarantee compensation.
Each official route now has a read-only claim-pack template preview. The preview shows which sections are source-backed, what still needs checking, and where to inspect the opportunity before opening a private workspace.
6
36/36
0
compens_ai.explore_claims_claim_pack_template.v0
Prepare a private packet for a financial product, service, account, debt, payment, or credit reporting complaint.
Template sections
6/6
Open before use
0
Open before use
No route-level template blockers.
This overview reads existing public route data only. It does not create a case, collect facts, generate documents, contact anyone, or promise eligibility.
View opportunitycompens_ai.explore_claims_claim_pack_template.v0
Prepare a private packet for a scam, deceptive sale, hidden fee, subscription, refund, or bad-business-practice report.
Template sections
6/6
Open before use
0
Open before use
No route-level template blockers.
This overview reads existing public route data only. It does not create a case, collect facts, generate documents, contact anyone, or promise eligibility.
View opportunitycompens_ai.explore_claims_claim_pack_template.v0
Prepare a private DOT refund packet for cancelled or significantly changed flights, unused refundable tickets, ancillary fees, baggage-fee refunds, ticket-agent merchant-of-record questions, or 24-hour booking cancellation records.
Template sections
6/6
Open before use
0
Open before use
No route-level template blockers.
This overview reads existing public route data only. It does not create a case, collect facts, generate documents, contact anyone, or promise eligibility.
View opportunitycompens_ai.explore_claims_claim_pack_template.v0
Prepare a private packet for airline service, delay, cancellation, denied boarding, baggage, or accessibility issues.
Template sections
6/6
Open before use
0
Open before use
No route-level template blockers.
This overview reads existing public route data only. It does not create a case, collect facts, generate documents, contact anyone, or promise eligibility.
View opportunitycompens_ai.explore_claims_claim_pack_template.v0
Track a phase-two route for UK financial complaints that may need final-response or waiting-period review.
Template sections
6/6
Open before use
0
Open before use
No route-level template blockers.
This overview reads existing public route data only. It does not create a case, collect facts, generate documents, contact anyone, or promise eligibility.
View opportunitycompens_ai.explore_claims_claim_pack_template.v0
Track a phase-two EU consumer redress route for cross-border complaints, ADR, and ECC-Net review.
Template sections
6/6
Open before use
0
Open before use
No route-level template blockers.
This overview reads existing public route data only. It does not create a case, collect facts, generate documents, contact anyone, or promise eligibility.
View opportunityThe useful packet is structured enough for review, but still editable and controlled by the user. Each part should stay separate until the user chooses the next action.
A short user-written description of what happened and what outcome they want.
Key dates and events, separated from guesses, opinions, and missing information.
Documents, messages, receipts, photos, or records the user may later choose to attach.
Source-backed complaint or redress routes that might fit after the user checks requirements.
Questions, sensitivity flags, and blockers to resolve before any sharing or submission.
A clear record of what is private, what is incomplete, and what still needs explicit consent.
The marketplace brief requires users to get useful orientation before payment or complex registration. Claim Packs should make that split explicit without activating checkout, partner review, or external sending from the public page.
Always visible
Users can understand the pack shape, evidence gaps, route context, and blocked actions before they share facts.
User controlled
Users decide when to add facts, attach proof, redact sensitive details, and prepare an editable packet.
Explicit opt-in
Paid pack generation, human review, export, partner handoff, or success-fee experiments stay separate from this page.