Explore Problems

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.

A merchant received threatening account-closure emails from Stripe despite doing nothing wrong, and phone support confirmed the account was fine while the automated threat emails continued. This reflects a broader pattern where payment processors risk-flagging creates existential uncertainty for compliant businesses, undermining trust in the platform.

A borrower's loan modification, intended to make their mortgage more affordable, instead raised their interest rate and nearly doubled their monthly payment with no clear explanation of how the new terms were calculated. This points to a transparency gap in how loss-mitigation and modification terms are disclosed to borrowers.

A HELOC applicant experienced nine weeks of stalled processing, contradictory status updates, and an accepted counteroffer that wasn't honored, while the bank failed to provide the adverse-action notice required under Regulation B/ECOA. This points to a recurring transparency and process-integrity gap in how lenders communicate HELOC application status and decisions.

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 student using a design tool for academic work finds essential premium assets locked behind a paywall, and cannot access free trials because they lack a credit card. This creates a barrier for price-sensitive or unbanked users who need quality design assets but cannot access the platform's premium tier.

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.

Businesses running paid ad campaigns spend significant manual effort on keyword research, negative-keyword management, and day-to-day optimization. There is demand for automation that handles routine monitoring across both Google and Meta ads platforms, though early tools already exist in this space.

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 Carvana customer's financed vehicle began leaking fluid the day after delivery and spent 9 of the following 12 months in an authorized repair loop for major component failures, culminating in a complete transmission failure immediately after a repair visit. The customer is now left without transportation and outstanding loan debt on a vehicle they consider undeliverable in usable condition.

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.

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.

A long-time AT&T customer had autopay silently disabled after a bank account change, resulting in unexpected return and reactivation fees despite never opting out, and could not find any record of the notification the company claims was sent. This illustrates a structural gap in telecom billing transparency, where account changes and their justifications are not reliably documented or disclosed to customers.

A customer describes multiple missed and rescheduled pickup and delivery commitments during a cross-state move, resulting in wasted paid time off and family disruption. Generic automated notifications replaced reliable coordination, leaving the customer unable to trust or plan around delivery windows.

A business user cannot restrict which locations or devices can access their team chat tool, creating a liability risk when employees install the app on personal phones outside the building. This exposes companies to compliance and data-security concerns they cannot self-remediate within the app.

Intercom users experience roughly 4-hour support response times and find the reporting interface's filter system difficult to navigate without vendor assistance. This creates friction for teams trying to self-serve on both support requests and analytics.

A customer describes being contractually locked into paying for 19 agent seats while only needing 4, after monthly billing was marketed as flexible when it actually just divides a fixed 24-month commitment into monthly charges. Committed seat counts cannot be reduced when business needs shrink, creating ongoing overpayment with no contractual recourse.