Explore Problems
Showing 3,644 of 8,902 problems · matching your filters
Auto Lender Fails to Release Lien After Payoff, Blocking Trade-In
After an auto loan is paid off via refinancing, Ally Financial fails to deliver the lien release to the receiving lender or DMV in a timely manner. The active lien blocks the vehicle from being traded in at a dealership. Consumers have no visibility into the lien release status or timeline.
Banks Withhold Customer Funds After Closing Accounts With No Timeline
After unilaterally closing checking and savings accounts, Wells Fargo withheld $3,800 in funds that arrived via legitimate ACH from the US Treasury. The consumer had no advance notice and received no timeline for when the funds would be released. Account closures that trap incoming deposits leave consumers unable to cover basic expenses.
Device Insurance Verification Requires Sending Code to the Broken Device
When a phone screen fails completely, Xfinity and Assurant insurance require authentication via an OTP sent to the broken device—making it impossible to complete a valid claim. The authentication loop is structurally broken for the exact scenario it should cover. Affects all device insurance programs with SMS-only 2FA.
Meta WhatsApp Business API Approval Delays Block Healthcare AI Deployments
Developers building WhatsApp-based healthcare tools in emerging markets face multi-week Meta review delays that stall launches and customer acquisition. The approval process lacks transparency and offers no expedited path for regulated or time-sensitive use cases.
Google Backup Fails Silently During Phone Factory Reset, Causing Data Loss
A long-time Google user reports losing all data, including years of messages, after following Google own instructions to factory reset their phone and restore from Google backup. Two weeks of support engagement produced no resolution, pushing the user to abandon the Google ecosystem entirely.
Insurers deny clearly documented hail damage claims despite multiple expert confirmations
A long-tenured multi-policy customer reports having hail damage confirmed by four independent roofers, yet the insurer disputes the claim. Illustrates a structural pattern of insurers resisting payout even with strong third-party evidence.
Banks respond to CFPB complaints with boilerplate non-answers
Consumers who file CFPB complaints against major banks receive generic regulatory acknowledgment responses that address none of the specific issues raised. Banks provide no findings, no corrective actions, and no resolution path — treating the complaint process as a procedural checkbox rather than a remediation mechanism. This pattern undermines the effectiveness of the CFPB complaint system as consumer recourse.
Predatory tribal lenders hide true loan costs until after funds disbursed
Tribal lenders exploit sovereign immunity to omit APR, monthly payment, and total repayment cost from pre-disbursement disclosures, revealing the true terms only after the consumer has received funds. Borrowers discover they owe multiples of the principal with no practical means to exit. The structural issue is the regulatory gap that sovereign tribal lenders exploit to bypass Truth in Lending Act disclosure requirements.
Insurance adjusters accuse claimants of dishonesty and are disrespectful during hit-and-run claims
A hit-and-run victim reports the assigned insurance adjuster repeatedly accused the claimant of lying, spoke disrespectfully, and hung up mid-call. Reflects a structural pattern of poor conduct standards in claims adjustment.
Telecom Carriers Charge Roaming Fees Despite User Opt-Out Compliance
Travelers who follow carrier-provided instructions to avoid international charges — including staying in airplane mode — still receive unexpected roaming fees. AT&T customers report being billed for international passes they explicitly declined, with no clear dispute path. The gap between carrier guidance and actual billing behavior creates unresolvable confusion and financial harm.
AI Coding Agents Struggle to Produce Pixel-Perfect Frontend Code From Figma Designs
LLM coding agents excel at logic and backend code but fail at translating Figma designs into precise, responsive frontend implementations because they lack design-aware context about component structure and visual intent. Frontend developers spend significant time correcting AI-generated UI code that misinterprets the design. Tools that bridge design context into agent workflows are emerging to fill this gap.
Manual revenue recognition breaks down as contracts and usage-based billing scale
Finance teams managing revenue recognition in spreadsheets struggle with inconsistent treatment of contract modifications under ASC 606, key-person dependency on a single spreadsheet owner, and the inability to calculate usage-based billing accurately. This is a structural accounting problem affecting any B2B company as contract volume and billing complexity grow.
Legal Teams Manually Check Related Documents for Inconsistencies During Transactions
Legal transaction review requires reading and cross-referencing multiple related documents to identify conflicting terms, missing provisions, and inconsistencies — a time-intensive process that scales poorly with deal complexity. AI document intelligence platforms that automatically extract key terms, flag inconsistencies across documents, and generate issue reports could dramatically reduce review time. This represents a high-value enterprise legal tech opportunity with strong willingness to pay.
Local LLMs Not Yet Reliable Enough to Replace Frontier API Models for Business Use
Developers wanting to reduce dependency on cloud AI providers find local LLM models still fall short of frontier model quality for research, coding, and business tasks. Meanwhile, hardware costs for capable local inference remain prohibitive, leaving teams stuck in a dependency they cannot economically or technically escape — a gap that is closing but not yet solved.
Debit Card Fraud Disputes Denied Despite Submitted Documentation
Bank customers filing debit card fraud disputes and providing all requested supporting documentation are having claims denied without proper investigation. Reg E requires provisional credit and investigation within specified timelines, but banks are closing claims without meeting these standards. Consumers with no checking account access due to disputed charges face compounding harm from the denial.
Intercom Fin AI ignores escalation rules in edge cases
Intercom Fin AI deviates from configured escalation paths and routing logic when handling complex or edge-case support tickets, causing mis-escalations that break support workflows. Teams with sophisticated triage logic cannot rely on Fin for reliable rule adherence. This is a structural reliability gap affecting any AI support agent with complex routing requirements.
Stripe transaction fee structure becomes unmanageable at high transaction volumes
High-volume merchants find Stripe's per-transaction fee model increasingly difficult to forecast and optimize as transaction counts scale, with limited tooling to analyze fee exposure or negotiate rates. Email and chat support channels are too slow when urgent payment infrastructure issues arise. These two friction points compound each other for growth-stage businesses where payment reliability is mission-critical.
Stale Remote Job Postings Waste Applicants' Time
Job seekers repeatedly apply to remote job postings that have already been filled or removed, because job boards don't reliably reflect real-time posting status. The issue is systemic across job platforms rather than isolated to one site, and wastes significant applicant time and effort.
Storage Logistics Provider Offers No Human Escalation for Repeated Pickup Delays
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.
HubSpot Sales Hub Duplicate Records and Rigid Sequence/Compliance Workflows
B2B sales teams using HubSpot Sales Hub face weak native deduplication, causing duplicate prospect records from scheduler bookings and sequence replies that require manual cleanup. Active sequences cannot be edited mid-flow, and there is no bulk workflow to purge contact activity for CCPA/CAN-SPAM opt-out requests, adding RevOps overhead during high-volume outreach periods.