Explore Problems

A military family's driveway was cracked when a PODS driver dropped their container, but the company's internal claims review concluded PODS was not liable for damage it caused. Because the mover both investigates and decides its own liability, customers with clear property damage have no independent avenue for a fair outcome.

A used-car dealership's business bank accounts were placed on hold for suspected money laundering simply because customers routinely made payments through mobile apps, a normal pattern for the business. Separately, a branch employee submitted a credit card application using the owner's personal information without consent while assisting with an unrelated account matter.

A customer reports that the driver picking up their POD left deep gashes and tire marks across their driveway, prompting them to seek compensation and vow never to use the service again. This mirrors a recurring pattern of moving-container damage claims where the path to compensation is unclear from the customer's side.

A customer ordered two containers destined for different states, but PODS delivered them to the wrong locations, forcing the customer to pay extra out of pocket to have them transferred to where they were supposed to go. Customer service was unavailable to help resolve the routing error, leaving the customer to bear the cost of the company's own mistake.

A customer disputed an unauthorized $1,000 hotel booking charge, providing evidence that the merchant only issued an unrecognized voucher number rather than a standard confirmation, yet the bank denied the dispute after a month-long review with no further explanation offered. This left the customer with no recourse for a transaction they consider fraudulent, despite twelve years as a customer.

A customer describes a moving-container provider as highly responsive during sign-up but effectively unreachable via chat support when attempting to cancel, despite high costs already incurred. This asymmetry, easy to buy, hard to cancel, mirrors a broader pattern in subscription and reservation-based services where support responsiveness drops sharply once a customer signals intent to leave.

A GEICO policyholder reports that although the other driver was clearly at fault and the insurer totaled the vehicle within days of the accident, payment has still not been issued. This reflects a disconnect between how quickly insurers assess claims and how slowly they actually disburse funds.

A new wireless customer's device was repeatedly disabled after being incorrectly flagged as stolen, despite proof of legitimate purchase. Support agents gave conflicting explanations across multiple contacts, fraud claims were denied without clear reasoning, and the customer had to visit a retail store multiple times without full resolution.

People who want an AI agent to operate their Android apps (reading the screen, tapping, typing) must send full screen/accessibility-tree data to a cloud LLM provider, exposing emails, phone numbers, and other PII. There is no standard on-device redaction layer between phone screen data and remote agent providers. The poster shipped a partial fix (local PII detection at roughly 87% accuracy) but flags non-English name detection as a known gap.

Users describe slow customer support responses for complex account and dispute issues, occasional delays in account verification or fund holds especially for newer or higher-risk businesses, and intermittent bugs in third-party integrations. Advanced settings and reporting also require more technical knowledge than the core interface suggests.

A user describes Google Drive's file organization and sharing controls as unintuitive, particularly the process for transferring folder or file ownership to another person, and found that Gemini's own in-app guidance for this task was incorrect. This points to a discoverability gap in core file-management actions within a widely used productivity suite.

Website owners face friction from Google Analytics' cookie-based tracking, which requires consent banners under GDPR and does not integrate with AI agent tooling. There is demand for a cookieless, self-hostable, privacy-first analytics alternative that can also be queried by AI tools.

Groups sharing recurring or one-off date plans, a school calendar shared with hundreds of families, a sales kickoff agenda shared with dozens of colleagues, currently juggle that information across documents, spreadsheets, PDFs, and email threads with no dedicated, easy way to plan and share it. This launch post drew unusually high engagement for the resonance of the underlying pain.

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.

People with faded or low-resolution family photos want to improve their clarity but are wary of uploading sentimental, private images to cloud-based restoration services. They need an easy way to enhance old photos entirely on their own device without surrendering the originals.

Organizations without dedicated Salesforce administrators find the platform difficult and time-consuming to set up and customize, while licensing costs scale up quickly as more features and users are added. This puts effective CRM use out of reach for budget-conscious or admin-less teams.

Knowledge workers spend time manually turning meeting and interview recordings into follow-up emails, task lists, and presentations. This product targets that gap with voice-to-output automation, competing in an already crowded AI notetaker market.

New Salesforce customers find initial configuration complicated enough to require a skilled administrator, and costs increase as more modules or integrations are added. This reflects a recurring structural onboarding-and-pricing friction pattern for complex enterprise CRM platforms.

A family was quoted one price for PODS containers and transportation but ultimately paid more, then waited 9 days past the scheduled delivery date while living out of suitcases. After unpacking, they found a cracked dining table despite having purchased Contents Protection and properly secured the load, but their damage claim was denied for 'normal shifting' and 'improper packing' without any specific supporting evidence provided.