Explore Problems

Cardholders report that credit union dispute processes rely on automated rules, such as assuming physical possession of goods waives a services-not-rendered claim, that ignore documented evidence like signed contracts proving the merchant failed to deliver. Frontline staff lack authority or willingness to review substantive evidence once a case is auto-closed. This leaves consumers with large disputed charges and no meaningful appeal path within the network's dispute framework.

A credit union initially flagged a series of transactions as fraudulent and blocked the card, yet later rejected the customer's formal dispute for the same fraudulent merchant, citing an automated authorization check. Customers are left unable to contest the rejection despite the bank's own earlier fraud alert on the identical merchant. This reveals inconsistency between real-time fraud detection and after-the-fact dispute adjudication.

A builder describes integration and connection maintenance as the hardest part of running a digital product automation system, harder than building the automation logic itself. Points to a broader pain around keeping multiple connected tools in sync reliably.

A Carvana buyer discovered evidence of unreported prior rear-end damage, including poor bodywork and glass debris, that was not disclosed on the listing or Carfax report. The warranty provider only approved partial repair costs, leaving the buyer exposed to potentially larger hidden structural damage costs.

A team reports that discussions held anywhere other than a top-level task become hard to find again in ClickUp, forcing repeated searches. Teams using deeply nested work tools lose time and context when comment threads are scattered across subtasks and views.

Businesses report support tool bills rising faster than their revenue, seen as a recurring pattern in reviews. Per-seat and tiered pricing makes helpdesk costs scale with growth.

Screen-sharing tools historically offer degraded, view-only support on Linux, and guiding a remote user's screen without cursor control creates a frustrating back-and-forth. This gap motivated an open-source, E2EE cross-platform screenshare project, though enterprise adoption faces its own security and compliance review hurdles.

Understanding whether a website is healthy across SEO, accessibility, security, and AI visibility normally requires combining several separate point tools, and most of those still only produce a score and checklist without evidence or a clear, developer-ready fix. This fragmentation slows down remediation and handoff to engineering.

A customer who cancelled a second mobile line had it re-billed for months despite more than ten calls confirming the cancellation and a refund of prior charges, and later received a third-party collections notice for a balance the company had already said was resolved. Cancellation state is not reliably reflected across billing and collections systems.

A Carvana buyer says the warranty administrator verbally confirmed coverage for recurring mechanical issues but then required $700 in out-of-pocket diagnostics, and a warranty-covered repair was performed improperly, leaving an active fluid leak unresolved. The customer had to invoke state consumer-protection law to seek reimbursement.

A solo founder with modest recurring revenue cannot determine which marketing channel or activity produced each paying customer, illustrating a broader attribution gap facing small, resource-constrained businesses.

Buyers who request a vehicle be shipped between a used-car retailer's locations report missed delivery windows, unexplained accident write-offs, and even receiving the wrong car entirely, with no proactive communication from the company. Follow-up issues like delayed license plate fulfillment compound the frustration when support is hard to reach.

Travelers relying on eSIMs for data abroad can have their eSIM stop working partway through a trip, cutting off connectivity in an unfamiliar place, with most providers offering no straightforward guarantee or replacement process.

A customer reports AT&T activated then deactivated their account and is holding their phone line, refusing to complete a number port so they can switch to another carrier. This traps the customer without service while blocking their ability to leave for a competing provider.

A support team lost custom field data after a teammate merged the wrong Zendesk ticket, discovering that merges cannot be undone and that some custom field data does not carry over to the surviving ticket. This creates risk of permanent, silent data loss from a routine support action.

A customer's Home Depot order was rescheduled three times, with four separate customer service calls each incorrectly confirming the item had shipped. Only on a final call was the customer told the product was never shipped due to damage, forcing a cancellation and reorder.

People planning international moves for work, study, retirement, or ancestry-based visas must dig through scattered government websites, outdated blogs, and generic visa guides to determine eligibility. There is no unified source that maps a person's passport and profile to concrete relocation options, making cross-border mobility decisions slow and error-prone.

A longtime Notion user reports that features they valued — simplicity and a lightweight workflow — are being eroded as the product pushes AI capabilities into the core experience, creating disruption for users who did not ask for them. This reflects a broader tension between tool minimalism and vendor-driven AI feature expansion.

As coding agents increasingly write and review code alongside humans, traditional Git hosting platforms were not designed for agent-native workflows like agent-initiated PRs, in-agent code browsing, or agent access management. Developers need code hosting that treats agents as first-class collaborators rather than bolted-on API consumers.

Teams needing daily view-count tracking for hundreds to thousands of their own public Facebook video and reel URLs cannot use the Graph API due to app approval and token restrictions. Workarounds like metadata scraping and headless browsers return stale or inaccurate counts and break down at scale due to bot detection and fragile page structures.