Explore Problems
Showing 4,502 of 9,996 problems · matching your filters
Banks bounce customers between departments over stuck fund transfers
A customer's fund transfer between their debit and credit accounts goes unresolved for over 10 days, with repeated calls simply routed back and forth between departments without a clear answer. Even escalation to executive customer relations and a branch manager's case filing fails to produce resolution or explanation.
Bank Pursuing Illegal Foreclosure During Open CFPB Complaint Process
Homeowners with active CFPB complaints against their bank receive unsolicited contact from loan servicers referencing unknown account numbers, indicating foreclosure activity continues despite pending regulatory oversight. The disconnect between complaint status and servicer actions suggests the bank's internal systems do not halt collection activity when complaints are filed. Borrowers have no way to enforce a pause on foreclosure while disputes are under review.
Mortgage Servicers Reneging on Derogatory Credit Removal Promises at Payoff
Borrowers who receive verbal assurances from loan servicers that derogatory credit notations will be removed upon payoff find those promises ignored after the transaction closes. The lack of any binding, documented commitment mechanism means borrowers have no recourse beyond formal dispute channels, which are slow and often fail. This exposes a gap between servicer promises and actual credit bureau reporting workflows.
Vehicle Service Contract Claims Denied on Technicalities Despite Persistent Underlying Fault
Buyers who finance a vehicle service contract to protect against repair costs find claims denied on narrow technical grounds (e.g., blaming an unrelated part) even when the actual diagnosed fault persists after the disputed repair. Consumers must pay out of pocket and resubmit documentation to contest the denial. This affects lower-income buyers who financed a service contract into their auto loan for repair protection.
Creditors Verify Disputed Debts Without Providing Actual Contractual Evidence
When consumers dispute credit report entries under the FCRA, furnishers respond with generic billing statements rather than signed agreements or liability proof, treating the dispute process as a formality. Credit bureaus accept this as "verified," perpetuating inaccurate reporting on credit files even when the consumer has documented grounds to challenge the debt's validity.
Card issuers misclassify item-not-as-described disputes as delivery issues
A cardholder disputed a grocery delivery order whose contents did not match what was purchased, but the issuer treated the case as a delivery dispute and denied it based on confirmed delivery rather than evaluating whether the correct items were provided. The issuer requested additional documentation that does not exist because the merchant never issued a final resolution, leaving the customer without recourse.
No Reference Documentation for DataFusion Built-in Optimizer Rules
DataFusion ships 27 logical and 21 physical optimizer rules but provides no reference document describing what each one does. Developers who want to understand query optimization behavior must read source code or run EXPLAIN VERBOSE, creating a steep knowledge barrier for contributors and users alike.
Real estate wholesalers cannot find reliable transactional funding
Wholesalers executing double closing deals struggle to find reliable transactional funding companies willing to provide short-term bridge funding for the A-B leg. The lack of a centralized marketplace for transactional lenders creates friction and delays that can kill time-sensitive deals.
Pocket Shutdown Leaves Read-Later Users Without Full-Text Search
Pocket, a widely used read-it-later service, is shutting down, displacing its user base and exposing a gap in the market: most alternative apps only search article titles, not full content. Users who rely on saved articles as a personal knowledge archive frequently need to retrieve specific paragraphs or passages from months-old saves. The combination of migration urgency and inadequate search depth in existing alternatives creates a real, if narrow, window of opportunity.
AI agents cannot run persistently in the background
Users want AI agents that continue executing tasks when they close their phone or laptop, but current architectures require an active session. This blocks use cases like autonomous research, monitoring, and multi-step workflows that take longer than a typical interaction. The 296 upvotes confirm this is a broadly felt capability gap.
No visibility into which Reddit and HN threads steer LLMs toward competitors
Brands relying on Reddit and Hacker News organic mentions are blind to which specific threads ChatGPT and similar assistants surface when users ask for tools, and which threads tilt recommendations toward competitors.
Marketing and customer acquisition is the hardest part after building
Founders find that marketing and customer acquisition is harder than building the product itself. Universal pain point about post-build growth.
Cold Outreach Fails When Targeting People Without Active Intent
B2B outreach campaigns built on broad demographic targeting yield sub-0.5% reply rates. The core problem is reaching people who are not actively seeking a solution, regardless of how well the messaging is crafted.
AI Answer Citations Do Not Translate Into Traceable Visitors
A site was cited tens of thousands of times in AI answers yet traced only 21 visitors. Publishers and marketers cannot measure or attribute value from AI search citations, so they cannot justify content investment.
Self-Service Truck Returns Lack Verifiable Proof-of-Condition Records
A renter using U-Haul's self-service return app received a false damage claim and a late-night collection call after an on-site attendant took the keys without a documented walk-around. Without a verifiable, timestamped record of vehicle condition at return, renters are exposed to disputed charges they can't easily contest.
Developers Lack Confidence Verifying AI-Generated Code Before Shipping
Developers, especially less experienced ones, increasingly rely on AI to write code but lack reliable methods to verify its correctness, security, and long-term stability before shipping, creating a growing trust gap.
AI Coding Agents Drift From Instructions in Long-Running Tasks
Developers using AI coding agents on long-running work report the agents forgetting instructions, blurring the line between implementing and reviewing, and requiring repeated correction of the same feedback. Existing mitigations like adding more rules to prompts or CLAUDE.md files do not enforce compliance since the agent can still silently skip steps.
AI agents given real credentials lack verifiable, revocable identity
As AI agents gain access to tokens, cloud credentials, and deploy permissions, there is no standard way for a service to verify which agent is acting, who launched it, or whether a credential is bound to that specific agent versus being a reusable secret. Static sandboxing remains the primary safeguard in use, while agent-related security incident rates are reportedly rising.
Session replay analysis too manual for ecommerce teams
Ecommerce teams waste hours manually watching session recordings to identify checkout friction. The pattern recognition needed to find actionable conversion blockers across hundreds of sessions exceeds what humans can do efficiently. This creates a gap between available behavioral data and actual UX improvements.
LLM Rate Limits Force Context Re-Explanation When Switching Models
When an LLM hits its rate or context limit, users must manually re-explain their entire session to a new model, breaking workflow continuity. This friction grows as multi-model AI workflows become the norm, and session context portability is largely unsolved.