Explore Problems

A Comcast/Xfinity customer on an active payment arrangement had their payment duplicated without consent, was charged an above-cap return-payment fee, and had service disconnected; after a partial credit, the system then generated a new incorrect past-due balance that five support agents could not resolve. This illustrates how billing-system automation errors can spiral into service disruption with no clear path to correction.

A small hospitality business had legitimate guest payments blocked by Stripe's risk system, was refused an override in writing, and then had its account closed days later for the risk signals created by those very blocks. This illustrates a systemic payment-processor problem where automated risk tooling can trap merchants with no appeal path.

A buyer who relied on a retailer's advertised 150-point inspection took delivery of a vehicle with an active safety-system fault, a dangerously worn tire, a failing battery, and undisclosed body damage — all items the inspection had marked as passed. The gap between advertised inspection rigor and actual vehicle condition exposes buyers to real safety risk and unplanned repair costs.

An AT&T customer made a small number of short international calls and was retroactively billed $642 without warning; the carrier refused to apply a lower-cost plan retroactively or resolve the dispute, threatening service cancellation if unpaid. This illustrates a structural lack of upfront cost transparency in telecom international billing.

A homeowner with a $270,000 policy received a fraction of the payout needed after storm damage, because the insurance adjuster performed a cursory inspection, missed extensive water damage and mold later confirmed by a remediation company, and refused to revise the settlement. This points to a structural gap in how insurers assess and validate damage claims.

Buyers of vehicles through online-only car retailers report receiving cars with damage not disclosed in listing photos, discovering the discrepancy only after taking delivery. Short return windows measured in days or a few hundred miles mean the issue is often financially binding before the buyer can act.

A paying Plus-tier subscriber to a notes/whiteboard app finds the product sluggish and buggy across mobile and desktop, and discovers that retrieving document versions older than 90 days requires an Enterprise upgrade. The experience reflects a broader pattern where core continuity features are paywalled behind higher tiers, pushing frustrated paying users toward churn.

A buyer took delivery of a vehicle with an active safety fault that fully disables anti-lock brakes and stability control, a defect not disclosed despite the retailer's advertised pre-sale inspection. The retailer offers warranty repair for mechanical issues but refuses to refund an associated non-refundable shipping fee, leaving the buyer to individually fight for restitution over undisclosed safety defects.

A small business banking with Wells Fargo for years had credit card processing terminated mid-day, including rejection of already-authorized payments, due to an internal audit claiming missing documentation the business had already submitted and confirmed received. This highlights the fragility of relying on a single bank for merchant processing with no failover when internal errors trigger abrupt service termination.

A long-time insurance customer updated their bank account after a compromise, but the insurers billing system kept charging the old closed account, then penalized the customer with a forced full-policy payment despite prompt notification. This reflects a systemic gap in how insurers confirm and propagate payment-method changes, compounded by unresponsive support.

A homeowner describes an insurer that partially processed a windstorm damage claim but failed to complete a requested professional inspection or provide a timely response, leaving a hazardous structural issue unresolved. This reflects a broader pattern of slow, incomplete, and poorly communicated claims handling in the insurance industry.

A telecom customer with an active international roaming protection plan was billed $5,844 in unexpected pay-per-use data charges, a total bill 24x their normal amount. The billing system failed to apply the protection plan despite it being confirmed active by the carrier for years, leaving the customer to fight for a reversal.

A new Shopify merchant describes being asked for additional payments beyond the initial setup fee, running out of money before launching, and then being unable to find a way to cancel — support continued billing despite email cancellation requests. This reflects a broader pattern of unclear upsells and difficult subscription cancellation in SaaS billing.

A service business using QuickBooks Online for invoicing lacks a payment portal integration, forcing manual or disconnected payment collection workflows. This reflects a broader gap for small businesses that need customer-facing payment portals tied directly into their existing accounting software.

Borrowers under tight mortgage closing timelines report loan officers instructing them to alter documented financial behavior (such as rental payment sourcing) in ways that undermine underwriting integrity. This deceptive pressure compounds acute stress for borrowers already navigating high-stakes, time-sensitive transactions.

AI coding agents can write integration code for services like Stripe but have no reliable way to confirm the fix produces the correct end state — tests can pass while the underlying data is still wrong, such as a customer receiving the wrong number of seats after a fix. Developers are left discovering failures in production rather than during development. The core gap is the lack of an environment where an agent's fix can be reproduced and proven correct before shipping.

People who request an insurance quote but do not purchase report being called repeatedly, sometimes 6 to 12 times a day from rotating numbers, even after asking to be removed from the call list. Reps reportedly hang up mid-request rather than honoring opt-outs, reflecting weak enforcement of do-not-call preferences in insurance lead-generation practices.

A March update to Notion increased spacing and visual bloat across the interface, degrading the appearance of long-maintained workspaces that users had carefully organized. Widespread complaints have gone unaddressed, pushing some long-time users to consider migrating to alternative tools.

A customer returned telecom equipment that the carrier confirmed receiving, yet an internal warehouse routing error caused the billing system to charge the customer for unreturned equipment anyway. Support could not reverse the erroneous $600 charge despite documented proof of return, exposing a structural gap between logistics tracking and billing systems.

A legitimate iPhone owner found their device flagged as lost or stolen in a shared industry registry, blocking repairs and warranty service, yet neither the registry operator nor the carrier would take responsibility for correcting the error. This reveals a structural gap: cross-industry device registries lack an accessible dispute or correction process, leaving legitimate owners stuck between parties who each disclaim authority to fix it.