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 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.

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 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.

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.

Developers running multiple AI coding agents per project end up opening many separate terminal windows, often 5-6 per project and 30+ across concurrent projects, making it easy to lose track of context and process state. This terminal sprawl creates friction for anyone orchestrating multiple agent processes and background tasks during AI-assisted development.

Developers extracting structured data from messy unstructured text via a single LLM prompt frequently encounter hallucinated field names, malformed JSON, and failures on edge cases. This undermines the reliability of automated data-extraction pipelines that depend on consistent, schema-conforming output.

A buyer who purchased a used vehicle from an online car marketplace discovered roughly $5,000 in needed repairs — including a broken suspension spring and severely worn brakes — just three days after delivery via an independent inspection. This raises doubt about the thoroughness of the platform's own pre-sale inspection process. The core concern is not needing repairs on an older vehicle, but that safety-relevant defects passed the seller's inspection undetected.

A Carvana customer discovered their electric vehicle's '150 point inspection' certificate was actually for a gas vehicle, and the car had an undisclosed suspension defect that persisted for a year, posing an ongoing safety risk to the buyer and their child. Carvana refused to take the car back, refund, or trade it despite acknowledging on a recorded call that resolution had been possible earlier.

A policyholder was promised a specific coverage plan verbally by an insurance agent, but the insurer had no call recording to verify it and denied the claim based on the written policy instead. This highlights a structural gap: insurers often lack accessible verification of verbal commitments, leaving customers without recourse when coverage details are disputed.

Drivers who file no claims can still have inaccurate accident records placed on shared insurance industry databases such as CLUE and LexisNexis, which raises their rates with every insurer that pulls the report. Correcting these systemic data errors requires navigating opaque dispute processes with the insurer, and discount-qualifying credentials like defensive-driving courses or veteran status are often not honored in the process.

High-volume merchants using Stripe pay elevated processing fees when installment plans split a single customer relationship into many separate transactions, and Stripe built-in dunning and failed-payment recovery tools are only basic. Businesses end up building custom reporting to proactively identify and act on at-risk subscribers, since native tooling does not surface this.

A customer describes AT&T failing to apply three separate promised bundle discounts on a new wireless line, being overcharged as a result, and then having a support call end abruptly when requesting a supervisor with no follow-up. The case highlights a structural failure in telecom promo-application systems and escalation processes that leaves customers without recourse when promised pricing is not honored.

Teams using monday.com's AI Work Platform have no way to set upfront AI credit limits per user, so a single team member who builds boards inefficiently or overuses AI fields can consume the shared credit pool for the whole workspace. Admins are left with no granular control to cap or throttle individual AI usage before costs accumulate.

A long-term storage rental customer reports being overcharged for undelivered services, losing billing-portal access needed to manage the account, and having their container removed with family belongings still inside — despite a confirmed, automatically reconfirmed pickup date. Offshore customer service demanded payment over the phone without providing account information or resolution.

A customer disputing unauthorized charges on a telecom bill found the disputed balance increased rather than decreased after multiple support tickets and hours-long phone calls over several weeks. The dispute-resolution process repeatedly failed to correct the underlying billing error, leaving the customer with a larger past-due balance than the original disputed amount.

A customer disputing charges with a rental company had additional late fees deducted while the dispute was still under formal review, leaving them without funds for basic needs. Follow-up support calls resulted in long hold times and repeated transfers with no resolution, exposing a gap between stated dispute policy and actual billing system behavior.

A customer describes repeated, unexplained delays in a scheduled storage container pickup, receiving only automated email updates and no accountability from phone support that routes to endless robotic menus. The lack of a human escalation path leaves customers unable to resolve time-sensitive logistics issues, driving frustration toward refund demands and legal action.