Compens.ai - Private Compensation Claim Workspace

Consumer Rights Records Preparation

Organize product, service, billing, warranty, and fraud records before you choose any next step. Compens.ai helps you prepare a private packet with source cues and local-rule reminders.

Records

Evidence Packets

organized for review

Source-led

Route Checks

official-source cues

Local rules

Jurisdiction Review

varies by location

FREE

Preparation Guides

user-controlled next steps

Start With a Clean Record of What Happened

Consumer problems are easier to review when the facts are separated from assumptions. Start with the purchase date, seller name, product or service description, order number, account notes, payment method, and a short timeline of what changed after purchase.

For fraud, scam, or impersonation concerns, preserve the original messages, sender addresses, phone numbers, payment records, screenshots, tracking links, and account alerts. Keep copies in a private folder before replying, deleting messages, or contacting a platform.

Imposter and Fraud Signal Checklist

Record the details that help distinguish an official source from an impersonation attempt:

• Unexpected tax or agency call: save the number, voicemail, and any callback instruction.
• Threat involving arrest, jury duty, or urgent payment: record the exact words and payment method requested.
• Health, identity, or benefit request: note what identifier was requested and where the request came from.
• Banking or account warning: verify through an independently found official channel before acting.
• Identity-warning message: preserve screenshots and avoid clicking message links until checked.

Source cue: official agencies usually publish contact and reporting routes. Confirm through those sources, not through links supplied in the message.

Email, Text, and Platform Message Records

Save the full message, sender details, headers when available, links, attachments, and screenshots showing date and time. A copied message without metadata is weaker than the original record.

If money or account access changed hands, add payment confirmations, bank alerts, account-login notices, delivery records, and any platform messages. The packet should show what you saw, what you did, and what changed afterward.

Identity and Account Exposure Records

For account takeover, card misuse, or identity exposure, collect notices from providers, account statements, card alerts, credit-file notices, password-reset emails, and support tickets.

Keep a timeline of discovery dates, account changes, and responses from each provider. Mark sensitive identifiers for redaction before sharing any packet with another person.

Online Shopping and Delivery Records

For non-delivery, wrong-item, quality, warranty, or seller-response issues, preserve the listing, order page, receipts, tracking events, delivery photos, packaging photos, and messages with the seller or platform.

If a platform or payment provider offers a dispute route, note the route name, deadline shown by the provider, and required records. Do not assume one deadline applies everywhere.

AI-Generated or Synthetic Contact Signals

When a message, voice, profile, or video interaction seems synthetic, preserve the observable signals:

• Video or voice call: note the account, time, platform, and any recording or transcript available to you.
• Relative or coworker impersonation: record the request, payment path, and independent verification attempt.
• Long-running relationship or investment pitch: preserve the timeline and all payment or account requests.
• Profile with inconsistent history: save profile links, screenshots, usernames, and dates viewed.
• Unusual link or attachment: save the message and check the sender through a separate source.

For relationship or trust-based scams, the timeline matters. Record first contact, changes in story, requests for secrecy, payment requests, account names, and any platform reports already made.

Some official routes collect reports to identify patterns and enforcement priorities. Your packet should separate personal records from public report routes so you decide what, if anything, to send.

Use a preparation-first posture: verify independently, preserve records, redact sensitive data, and choose next steps only after you understand the source, route, and local-rule context.

Common Consumer Rights Record Types

🛒

Product Defects and Safety Issues

• Photos or videos showing the product condition
• Warning labels, manuals, and packaging
• Purchase proof and warranty terms
• Repair, support, or recall communications

📺

Misleading Advertising and Deceptive Marketing

• Screenshots of ads and offer pages with dates
• Environmental or health-related claims shown to you
• Reviews, endorsements, or labels that affected your choice
• Hidden fee or subscription terms shown during checkout

Source cue: consumer protection agencies publish rules on unfair or deceptive practices

📄

Warranty Denials and Service Problems

• Warranty document and service-plan terms
• Denial message or support-ticket history
• Repair attempts and inspection notes
• Photos, receipts, and product serial information

Local-rule cue: defective vehicle and warranty rules vary by jurisdiction and product type

Source Cues to Check Before Acting

🛡️ Public Consumer Protection Sources:

Unfair or Deceptive Practice Rules

Consumer protection sources explain how misleading offers, hidden terms, fake endorsements, and deceptive billing may be reviewed.

• Misleading advertising or offer pages
• Hidden fees or pricing context
• Endorsements, reviews, or influencer disclosures
• Subscription, renewal, and cancellation disclosures

Preparation note: record the official route name and required fields before deciding whether to report.

Warranty and Service-Plan Sources

Warranty sources explain disclosure, repair, replacement, and provider-response requirements for consumer products.

• Warranty type, coverage period, and exclusions
• Required repair or support process
• Records needed to show repeated product or service failure

Product Safety and Recall Sources

Product-safety sources publish recall, hazard, and reporting information.

• Check product model, serial number, and recall status
• Record the product condition before repair or disposal
• Keep provider notices and safety communications

🚗 Defective Vehicle Local Rules:

Records Often Needed:

Problem record: what failed and how it affected use, value, or safety
Repair record: dates, orders, repeated symptoms, and days out of service
Notice record: written notices and provider/manufacturer responses
Timing record: purchase, repair, warranty, and response dates

Possible Route Topics (Varies by Location):

• Purchase record: price, financing, mileage, and current condition
• Replacement or repair records: what was offered and when
• Fee and process rules: source-specific and location-specific
• Local remedy rules: confirm with official or reviewed sources

Local-Rule Examples:

California: check source rules for vehicles under manufacturer warranty
New York: check source rules for covered new, used, or leased vehicles
Texas: check source rules for serious safety defects and timing

Source cue: start with your jurisdiction or consumer-protection office source before relying on any summary.

Prepare Your Records: Step-by-Step

🛒Prepare a Product Defect Packet

Step 1: Document the Product and Impact

• Photos or videos: show the product, defect, packaging, and condition
• Health or safety records: include only what you choose to share after redaction
• Purchase proof: receipt, order confirmation, card statement, or invoice
• Preserve the product when practical until you understand the route requirements
• Witness or support notes: who saw the issue and what they observed

Step 2: Draft a Provider Notice

Prepare an editable notice draft before sending anything:

[Your Name] [Address] [Date] [Company Name] [Address or support route] Re: Product or Service Record - [Product Name, Model #, Purchase Date] I purchased this product or service on [date] from [seller]. On [date], I observed the following issue: [short factual description]. Records available: 1. Purchase proof: [record] 2. Product or service evidence: [record] 3. Company response so far: [record] I am preparing my records and would like the company to explain the available review, repair, replacement, or response process. Sincerely, [Your Signature]

Step 3: Map Official Source Routes

Before reporting anywhere, record the official route name, source URL, and required fields.

• Some routes collect reports to identify patterns.
• Some routes may trigger safety, recall, or enforcement review.
• Keep a copy of what you send and any confirmation number.

Step 4: Mark Review Questions

Separate facts from questions:

1. Warranty or service-plan review:
- • What was promised in the written terms?
- • What repair, return, or review route was provided?
- • What records show dates, amounts, and company responses?
2. Safety or hazard review:
- • What product condition or warning issue is documented?
- • What official recall or safety source did you check?
- • What sensitive records should be redacted before sharing?
3. Provider-response review:
- • What did the provider know from your messages?
- • What response or non-response can you document?

Preparation note: strong packets usually include purchase proof, dated photos, provider messages, source checks, and a clean timeline.

🚗Prepare a Defective Vehicle Packet

Step 1: Document All Repair Attempts

• Keep every repair order with date, symptoms, diagnosis, and work performed
• Count days out of service from dated records
• Group records by repeated symptom or related system
• Track purchase date, mileage, warranty period, and repair dates

Describe how the issue affects use, value, or safety in plain facts.

Step 2: Prepare Written Notice

Create an editable draft before sending:

[Your Name] [Address] [Date] [Manufacturer or provider route] [Address or official contact route] Re: Vehicle Repair Record - [Year, Make, Model, VIN] I purchased or leased this vehicle on [date]. Since purchase, I have taken the vehicle for repair [X] times for this issue: [short factual description]. Repair dates: [list dates and days in shop] Records available: [repair orders, messages, photos, warranty terms] I am preparing my records and would like the provider to identify the available review or repair process for this issue. Sincerely, [Your Signature]

Preparation note: confirm the correct recipient through the official source or vehicle documents before sending.

Step 3: Track Provider Response

• Record any inspection or repair appointment offered
• Record stated response windows from source documents
• If repaired, keep the final repair order and monitor whether the same issue returns
• If unresolved, preserve the response record and mark the next source route to review

Step 4: Compare Review Routes

Common route categories to compare:

Manufacturer or program review route:
- • Record program name, source link, required forms, and deadlines shown
- • Check whether the route is optional or required in your location
- • Keep copies of submissions, confirmations, and responses
- • Do not treat generic timelines as local-rule proof
Independent review preparation:
- • Prepare a concise timeline and record index
- • Mark sensitive account and identity details for redaction
- • List source questions you want checked
- • Keep next steps under your control until you choose otherwise

Preparation note: a review-ready vehicle packet usually has purchase records, repair orders, dated communications, mileage, and a route/source checklist.

📺Prepare a Misleading Advertising Packet

Advertising Records to Preserve:

Environmental or sustainability claim shown to you
Pricing comparison or sale terms shown during purchase
Origin or manufacturing claim shown in the offer
Health, safety, or performance claim shown to you
Review, endorsement, or influencer disclosure that affected your choice

Step 1: Gather Evidence

• Screenshot ads and offer pages with date and URL visible
• Save packaging, labels, and inserts showing the claim
• Document what you received compared with the advertised claim
• Add source checks, not conclusions, about whether the claim is supported

Step 2: Map Official Report Routes

Record the relevant official or platform route before sending anything.

• Some routes look for repeated patterns across reports.
• Some routes may lead to public enforcement or corrective action.
• Source cue: keep the official source link and confirmation number with your packet.

Step 3: Check Public Group-Action Signals

If many consumers describe the same issue, keep this as a research signal, not a conclusion.

• Search public notices and reviewed sources for the company and issue pattern
• Save source links, dates, and eligibility notes in your packet
• Prepare questions for an independent reviewer before sharing personal records

Source cue: public examples can help identify record types, but they do not predict your outcome.

Preparation note: public report routes and group-action signals serve different purposes. Keep your personal packet separate until you choose a route.

Consumer Rights Source Examples

Source cue: public agency record

Volkswagen Diesel Emissions Matter

Use public enforcement records as examples of what source-backed timelines, product claims, company notices, and consumer communications can look like.

Public record example

Source cue: advertising claim record

Keurig Recyclability Claim Review

Use advertising and packaging examples to identify the exact claim shown, where it appeared, and what record would support a review.

Public source example

Source cue: repair timeline record

Defective Vehicle Repair Timeline

Use repair timeline examples to organize repair orders, dates out of service, provider responses, and source-rule questions before any next step.

Preparation example