Independent public-interest project · Scientific framework under active development · Live public pilot
UXR Case Record
Factor Free Breakfast Promotion Produced a Conditional Add-On-Only Remedy
On May 16, 2025, two contemporaneous Factor emails documented one $20 remedy after a contributor-reported Free Breakfast redemption failure. The first described two $10 add-on discounts and required an add-on item; the second clarified that the same $20 credit would apply only to a later non-discounted order. The contributor reports that the promotion allowed only add-ons and that seeking correction required more than 30 minutes in chat and more than 30 minutes by phone. The emails support the remedy terms and are materially consistent with that account, but do not independently establish the initiating promotion wording or support dialogue. The conditional remedy did not provide the promised breakfast benefit or a complete resolution.
- Case ID
- UXR-2025-0516-000001
- Case status
- Unresolved
- Overall resolution
- Partially Addressed
- Immediate remediation
- Inadequate
- Individual remedy
- Partial
- System reform
- Not Demonstrated
- Verification
- Not Tested
- Monitoring
- Not Started
- Routing
- Partially Routed
- Public revision
- 1
- Publication basis
- Anonymized With Contributor Approval
- Last updated
- August 05, 2026
Responsibility and routing
This section displays only publicly supportable responsibility relationships. Candidate recipients and unverified submission paths remain outside the public assignment list.
Factor 75
Service · Private or Nongovernmental
Factor issued and administered the reactivation promotion and controls the promotion, checkout, customer-support, cancellation, and remedy systems described in UXR-2026-000002. The corporate-parent and internal departmental hierarchy have not yet been verified for routing purposes.
Current routing position: Factor is confirmed as the company that issued the documented May 2025 response. The current reusable public contact route, internal unit with final corrective authority, corporate-parent escalation path, and any appropriate external oversight route remain unverified and are not presented as assigned.
Agency dimensions affected
These terms connect the case-specific record to UXR's controlled agency vocabulary. Open a term to see its public meaning and reform direction.
Informational Agency
Agency Dimension
Informational agency means receiving the information needed to understand and act in a usable form.
For people using the system: Signals whether the person had usable information rather than buried, contradictory, or missing information.
Reform direction: Make essential information visible, consistent, accessible, and available before commitment.
Decision Agency
Agency Dimension
Decision agency means having real, informed options and a practical ability to choose among them.
For people using the system: Shows whether choices were real, informed, and usable rather than forced, deceptive, or punishing.
Reform direction: Remove forced defaults, hidden consequences, deceptive framing, and artificial barriers to refusal or reversal.
Procedural Agency
Agency Dimension
Procedural agency means having a clear, usable path through the steps required to act or seek remedy.
For people using the system: Shows whether the process offered a usable route or trapped the person in loops, contradictions, and undefined requirements.
Reform direction: Align instructions and channels, remove loops, preserve progress, and define the next actionable step.
Corrective Agency
Agency Dimension
Corrective agency means being able to challenge a failure and reach someone or something capable of fixing it.
For people using the system: Shows whether the person could repair a failure without extraordinary persistence, expertise, or cost.
Reform direction: Create clear escalation, correction, restoration, and verification paths with authority to act.
Temporal Agency
Agency Dimension
Temporal agency means retaining practical control over how a system uses, delays, or consumes a person's time.
For people using the system: Shows when a system takes time without notice, control, progress, or proportionate necessity.
Reform direction: Reduce avoidable delay, disclose timing, preserve work, and protect remedy windows.
Cognitive Agency
Agency Dimension
Cognitive agency means being able to understand and act without the system forcing unnecessary mental reconstruction or overload.
For people using the system: Shows when the system transfers interpretation, memory, comparison, or diagnostic work to the person.
Reform direction: Reduce contradictory explanations, repeated narration, hidden dependencies, and unnecessary mental bookkeeping.
Reliance Agency
Agency Dimension
Reliance agency means being able to judge whether a system's promises and explanations are safe to act upon.
For people using the system: Shows whether the person could safely rely on what the system said without independent auditing or defensive verification.
Reform direction: Align promises with delivered behavior, disclose limitations, and make verification possible before commitment.
Case concepts
These governed terms support comparison and discovery without replacing the narrative findings or their evidence limits.
Agency-Extracting Friction
Friction Type
Agency-extracting friction shifts avoidable time, effort, risk, or control from an institution onto the person using it.
For people using the system: Shows when the system makes the person pay in effort or control for an avoidable institutional failure or convenience.
Reform direction: Remove the avoidable transfer, restore practical control, and measure the human burden previously externalized.
Time Loss
Invisible Tax
Time loss records the minutes or hours a system unnecessarily consumes or makes unusable.
For people using the system: Shows the direct life cost of waiting, repetition, rework, lost progress, and recovery.
Reform direction: Reduce avoidable duration, preserve progress, disclose timing, and design for first-contact resolution where appropriate.
Cognitive Burden
Invisible Tax
Cognitive burden is the unnecessary thinking, remembering, comparing, and diagnostic work a system forces onto a person.
For people using the system: Shows the thinking work transferred from the system to the person.
Reform direction: Reduce ambiguity and repetition, preserve context, expose system state, and ask only for information that changes the outcome.
Emotional or Dignity Harm
Harm Type
Emotional or dignity harm records stress, humiliation, invalidation, or degradation caused by how a system treats a person.
For people using the system: Shows that technically completing a task does not erase degrading or destabilizing treatment.
Reform direction: Remove degrading practices, improve communication and escalation, and design correction without humiliation or coercive emotional endurance.
Lost Opportunity
Harm Type
Lost opportunity is a concrete chance, right, benefit, or activity that a system made unavailable or materially harder to obtain.
For people using the system: Shows what the person could no longer do after delay, obstruction, misinformation, or failure.
Reform direction: Protect time-sensitive opportunities, preserve pending work, and create restoration paths when the system causes loss.
Recovery Burden
Invisible Tax
Recovery burden is the extra work a person must perform to detect, prove, and repair a failure the system should have handled.
For people using the system: Shows that even successful correction may leave the person paying for the system's failure.
Reform direction: Automate or simplify detection and recovery, preserve state, assign corrective authority, and prevent restart requirements.
Conditional Individual Workaround
Workaround or Resolution Class
A conditional individual workaround gives one person limited relief but only through added restrictions or continued participation, leaving the system unchanged.
For people using the system: Shows that a remedy may offer some value while still demanding additional participation or reproducing the disputed burden.
Reform direction: Make relief prompt, usable for the promised purpose, independent of unnecessary future purchase or participation, and visible in the account.
Promotional Promise and Redemption Mismatch
Issue Pattern
A promotional promise and redemption mismatch occurs when the advertised benefit and the practical path to receive it do not operate as one coherent offer.
For people using the system: Warns that the advertised value may not be practically obtainable through the linked flow.
Reform direction: Test the complete recipient-to-checkout path, make the promised benefit visible, and ensure every channel uses the same definitions.
Category or Labeling Mismatch
Issue Pattern
A category or labeling mismatch makes it materially unclear which items, benefits, or actions actually qualify.
For people using the system: Shows that apparently similar words or menus may hide materially different eligibility or consequences.
Reform direction: Use consistent labels, expose category relationships, and identify qualifying items before commitment.
Support Guidance Mismatch
Issue Pattern
Support guidance mismatch occurs when the help channel cannot accurately explain or operate the system the person is using.
For people using the system: Warns that contacting support may not reliably restore agency if representatives cannot see or explain the relevant state.
Reform direction: Give representatives campaign and account visibility, exact diagnostics, coherent instructions, and access to corrective authority.
Delayed Compensation
Issue Pattern
Delayed compensation postpones usable relief and may require the person to keep participating or spend more before receiving value.
For people using the system: Shows that nominal compensation may not restore value when the person must wait, remain exposed, or spend more first.
Reform direction: Make compensation immediately available where practical and disclose every material timing condition before acceptance.
Conditional Remedy Requiring Continued Participation
Issue Pattern
A conditional remedy requiring continued participation gives relief only if the person keeps using or paying the system involved in the dispute.
For people using the system: Shows when relief may function only if the person remains exposed to the organization or delays exit.
Reform direction: Make the remedy independent of unnecessary continued participation and preserve access after cancellation or withdrawal.
Repeated Explanation and Proof Labor
Issue Pattern
Repeated explanation and proof labor occurs when a person must keep restating or re-proving information the system already has or should carry forward.
For people using the system: Shows the additional work imposed when every channel or representative treats the issue as new or misframes the person's actions.
Reform direction: Preserve context across channels, expose what the system already knows, and ask only for information that changes the decision.
User-Burden Transfer
Issue Pattern
User-burden transfer makes the affected person detect, diagnose, prove, or coordinate a failure the institution is better positioned to handle.
For people using the system: Shows when the system's apparent efficiency depends on unpaid user labor and personal vigilance.
Reform direction: Move detection, state preservation, diagnostic visibility, and recovery initiation back into the system.
Case contents
- Provisional UXR case
- Case summary
- What the contributor was trying to do
- Date and case-number note
- What happened
- Core system failure
- Demonstrated by supplied artifacts
- Contributor-reported with material artifact support
- Strongest unresolved counter-explanation
- Not established
- How the system affected the contributor's agency
- Friction and invisible costs
- Actual harm
- What this means to another consumer
- What this means for Factor 75
- Paths to remediation, reform, and verification
- Factor 75's response
- Current status
- Why UXR publishes cases like this
Provisional UXR case
This page documents a historical contributor experience using UXR's developing case architecture. It separates artifacts, testimony, uncertainty, individual response, system reform, and verification. It is not a legal judgment, a universal score, or proof of company-wide prevalence.
Case summary
The contributor reports that a Factor Free Breakfast promotion allowed only add-ons and that seeking correction required more than 30 minutes in chat and more than 30 minutes by phone. Two Factor emails sent fifteen minutes apart on May 16, 2025 document one $20 response: two $10 add-on discounts requiring an add-on item, usable only on a later non-discounted order. The response did not restore the promised breakfast benefit or demonstrate correction of the underlying system.
What the contributor was trying to do
Redeem Factor's advertised Free Breakfast promotion and receive the promised breakfast benefit.
Date and case-number note
The case number includes 2025-0516 because May 16, 2025 is the date of the first located Factor email documenting the response. UXR uses that date as an estimated intake anchor. The exact date and time of the initiating promotion failure and first support contact have not been independently established.
What happened
- The contributor reports that a Factor Free Breakfast promotion allowed only add-ons.
- The contributor reports spending more than 30 minutes in chat and more than 30 minutes by phone seeking correction.
- The contributor requested written confirmation that a telephone promise had produced an actual account adjustment.
- At 12:27 PM on May 16, 2025, a Factor representative confirmed two $10 add-on discounts and required an add-on item in the order.
- At 12:42 PM, the same representative clarified that the same $20 credit would apply only to the next non-discounted order.
- The two emails document one conditional $20 response, not two remedies.
- The record does not show delivery of the promised breakfast benefit, proportional redress for the reported support burden, or system reform.
Core system failure
Factor's promotional benefit, breakfast and add-on category structure, support process, and remedy rules did not operate as one coherent system. A contributor-reported Free Breakfast redemption failure produced a documented response restricted to add-ons and delayed until a later non-discounted order. The response required additional participation and did not restore the promised category of benefit or demonstrate systemic correction.
Demonstrated by supplied artifacts
- Two Factor emails were sent fifteen minutes apart on May 16, 2025 by the same representative.
- They describe one $20 response as two $10 add-on discounts.
- An add-on item had to appear in the order.
- The same $20 credit would apply only to a later non-discounted order.
Contributor-reported with material artifact support
The emails do not independently state the initiating complaint or support duration, but the add-on-specific and delayed remedy structure materially fits the contributor's account.
- The emails followed a complaint that a Free Breakfast promotion allowed only add-ons.
- The support process consumed more than 30 minutes in chat and more than 30 minutes by phone.
- The emails were requested to confirm that a telephone promise had produced an actual account adjustment.
Strongest unresolved counter-explanation
Factor may have intended the $20 account value as a practical goodwill response when direct restoration was unavailable. The record does not establish the value of the original breakfast benefit or the representative's authority and constraints. Even under that explanation, the response remained in a different product category, carried delayed-use conditions, and did not demonstrate that the promotion path had been corrected.
Not established
- The exact May 2025 promotional wording or checkout state.
- The complete chat or telephone dialogue.
- The exact monetary value of the promised breakfast benefit.
- Deliberate deception, management knowledge, or deliberate retention intent.
- The number of other customers affected.
- A campaign-wide, company-wide, or industry-wide pattern.
How the system affected the contributor's agency
The taxonomy references are authoritative. These case-specific applications remain separately reviewable.
- Informational agency: The reported Free Breakfast benefit and documented add-on-only response did not provide one coherent account of what value was available.
- Decision agency: The contributor could not evaluate the practical offer or remedy with all material conditions visible.
- Procedural agency: More than one hour of reported support did not produce a direct restoration path.
- Corrective agency: The documented response supplied conditional value but did not restore the promised category or demonstrate system correction.
- Temporal agency: Support consumed more than one reported hour, and the response delayed use until a later non-discounted order.
- Cognitive agency: The contributor had to reconcile categories, verify a telephone promise, and interpret two remedy descriptions.
- Reliance agency: The experience reduced the ability to rely on promotion and support descriptions without independent verification.
Friction and invisible costs
- More than 30 minutes of reported chat support.
- More than 30 minutes of reported telephone support.
- Repeated explanation and proof labor.
- A need to request written confirmation of a telephone promise.
- Two descriptions of one remedy.
- A material restriction clarified only in the second email.
- Compensation confined to the disputed add-on category.
- Delayed eligibility until a later non-discounted order.
- Later evidence recovery and case reconstruction.
Actual harm
Artifact-supported effects include one conditional $20 response limited to add-ons and delayed until a later non-discounted order. Contributor-reported effects include more than one hour of support burden, failure to receive the promised breakfast benefit, repeated explanation and proof labor, cognitive and emotional burden, and reduced confidence in Factor's promotions. The exact monetary value of the original benefit and any larger out-of-pocket loss are not established.
What this means to another consumer
A low-value promotional failure can impose more recovery time than the benefit is worth. An account credit can appear to resolve the contact while changing the product category, delaying use, or requiring continued participation. Consumers may therefore abandon the promised benefit or accept materially different terms simply because contesting them costs too much time.
- A remedy can supply some value without restoring the promised category.
- Material restrictions may appear only after a customer has already spent substantial recovery effort.
- Delayed credits can require continued participation before compensation becomes usable.
- A closed support contact does not establish that the underlying promotion path was corrected.
What this means for Factor 75
These are operational implications, not findings of deliberate misconduct.
- Support labor exceeded the likely face value of the promotional benefit.
- The response category and timing conditions could leave the original failure unresolved while making the contact appear addressed.
- A restriction omitted from the first written confirmation increases clarification work and distrust.
- Account-specific credits can hide recurrence if they do not create a defect record for promotion, product, and support owners.
- A later materially similar case suggests that the May response did not demonstrate durable prevention of recurrence.
Resolution architecture
Paths to remediation, reform, and verification
This case separates five questions that must not collapse into one status. Immediate remediation asks what Factor should have done after receiving credible notice. Individual remedy asks whether the contributor received adequate redress. System reform asks what Factor must change for future users. Verification asks what would prove the change works. Monitoring asks whether the correction remains effective. The documented $20 response addressed part of one layer but did not complete the others.
- Overall
- Partially Addressed
- Immediate remediation
- Inadequate
- Individual remedy
- Partial
- System reform
- Not Demonstrated
- Verification
- Not Tested
- Monitoring
- Not Started
Factor supplied one conditional $20 add-on response, so the record does not describe total organizational silence. That response did not restore the promised breakfast benefit, fully address the reported recovery burden, demonstrate systemic reform, complete an acceptance test, or begin durability monitoring. The May case therefore remains unresolved.
Immediate Remediation
What Factor should have done when notified
This layer describes the incident response Factor should have initiated after the contributor reported that the Free Breakfast promotion produced only add-ons. It addresses diagnosis and correction of the known failure, not merely compensation and not yet durable reform.
Factor should have preserved the promotion and account state, identified the configured breakfast benefit, compared it with the reported add-on-only path, reached someone with corrective authority, and restored the promised benefit or an accepted equivalent before closing the incident through conditional add-on credit.
- Preserve the promotion, account state, support history, and transaction context.
- Identify the exact promotion and qualifying breakfast path.
- Compare the reported failure with the configured benefit.
- Escalate to a function with promotion visibility and corrective authority.
- Provide one coherent written explanation.
- Restore the promised breakfast benefit or an accepted equivalent before defaulting to add-on-only credit.
- Record the incident for system review.
Current status: Factor documented one conditional $20 add-on response, but the available record does not show diagnosis of the promotion failure, restoration of the promised breakfast, corrective escalation, or system review.
Completion or verification standard: Completion requires a preserved incident record, promotion comparison, corrective escalation, coherent explanation, and restored or contributor-accepted equivalent benefit.
Individual Remedy
What Factor still owes the affected contributor
Individual redress should restore the promised breakfast benefit or provide an accepted equivalent that addresses the failed benefit and recovery burden. A completed individual remedy would not by itself prove systemic reform.
Factor provided one $20 response, but it remained restricted to add-ons and delayed until a later non-discounted order. Adequate redress would restore the represented breakfast benefit or provide an equivalent the contributor accepts without requiring additional unwanted participation.
- Provide the promised breakfast benefit or a contributor-accepted equivalent.
- Account for the reported support and recovery burden when determining proportional redress.
- Make corrective value visible and promptly usable.
- Do not require an add-on item unless accepted as equivalent.
- Do not require continued subscription or a later non-discounted order unless those conditions are accepted as equivalent.
Current status: The documented $20 response supplied some account value but did not restore the promised breakfast category, disclose all restrictions at first confirmation, or provide a complete and proportional remedy.
Completion or verification standard: Completion requires the promised benefit, documented equivalent value, or other contributor-accepted redress. Individual completion would not verify systemic reform.
System Reform
What Factor must change
This is the central UXR layer. The May case exists to specify how the promotion, support, and remedy system should change for future users, not merely to seek additional account value for one person.
A Free Breakfast failure should not default to add-on-only compensation under later purchase conditions. Factor's promotion definitions, product eligibility, support visibility, escalation, credit rules, and complaint instrumentation must operate as one coherent system.
- Use consistent definitions for breakfast and add-ons across promotion, eligibility, checkout, support, and remedies.
- Let support identify the exact promotion and benefit attached to an account.
- Create an escalation path to promotion and corrective authority.
- Require remedies to restore the promised category or an accepted equivalent.
- Avoid later full-price participation requirements unless the customer accepts them.
- Disclose all material remedy restrictions in the first confirmation.
- Aggregate comparable failures so recurrence reaches accountable system owners.
Current status: The available record documents an account-specific conditional response but no reform plan, implementation owner, completed change, acceptance test, or monitoring.
Completion or verification standard: Completion requires documented implementation across the affected systems followed by reproducible testing. A one-account credit does not establish reform.
Verification
What would prove the reform worked
UXR should not mark the case systemically resolved because Factor reports a change or adjusts one account. The failed promotion, support, and correction path must be tested.
Verification requires an observable test showing that an actual breakfast benefit is clear and redeemable, support can diagnose the offer, a failed redemption receives prompt correction, and remedy restrictions do not appear only after acceptance.
- The same class of Free Breakfast promotion presents a clear qualifying breakfast item.
- The benefit can be redeemed without category reinterpretation.
- Support can locate and explain the promotion.
- A failed redemption can be corrected in the promised category or through an accepted equivalent.
- All material restrictions appear before acceptance.
- Corrective value does not require later full-price participation unless affirmatively accepted.
Current status: No implemented reform has been demonstrated and no end-to-end acceptance test has been performed.
Completion or verification standard: A dated test record must capture each material system state, support response, corrective outcome, and pass or failure against every criterion.
Monitoring
What should be monitored after implementation
A successful test shows that the path worked once. Monitoring asks whether the correction lasts and whether comparable Free Breakfast, add-on-only remedy, or delayed-credit failures continue.
After implementation and verification, Factor should monitor failed redemptions, add-on-only substitutions, delayed credits, repeated support contacts, and comparable complaints. Credible recurrence should trigger reverification or reopen the reform pathway.
- Track failed Free Breakfast redemptions.
- Track add-on-only substitutions and delayed credits.
- Track repeated support contacts and manual overrides.
- Review complaints and cancellations for recurrence.
- Repeat the acceptance test after material changes.
- Reopen reform review when credible recurrence appears.
Current status: No verified implementation exists, so durability monitoring has not begun.
Completion or verification standard: Monitoring should define a review period, recurrence indicators, material-change triggers, results, and any required reverification.
Factor 75's response
A Factor representative sent two emails fifteen minutes apart. The first confirmed two $10 add-on discounts and required an add-on item in the order. The second clarified that the same $20 credit would apply only to the next non-discounted order. These messages document one conditional response. They do not independently state the initiating complaint, acknowledge a system defect, provide the promised breakfast benefit, or report system reform.
Response date: May 16, 2025
Current status
- Case status: Unresolved
- Overall resolution work: Partially Addressed
- Immediate remediation: Inadequate
- Individual remedy: Partial
- System reform: Not Demonstrated
- Verification: Not Tested
- Monitoring: Not Started
- Evidence confidence: Remedy terms artifact-supported; initiating complaint and support duration contributor-reported with material artifact support.
- Public case record revision: 1
- Resolution model: UXR Resolution Model 0.1
Why UXR publishes cases like this
This case shows why a payment or credit cannot serve as a universal resolution label. The public record distinguishes what the organization documented, what the contributor reported, what individual redress remains incomplete, what system reform would require, and what evidence would prove that reform worked.
Public discussion
Comments are moderated. A comment does not automatically become evidence, corroboration, a correction, or an organization response. Do not place private account information, medical information, or sensitive evidence in comments.