Explore Problems

A business describes being locked into a 12-month Angi contract while receiving largely unresponsive leads -- roughly 90% never answer the phone -- and the customers who do respond frequently expect free work. Angi provides no lead-refund system, leaving businesses unable to recoup wasted spend.

A business received 48 leads through Angi, but roughly 90% never answered calls or responded to messages, and Angi continued billing for them regardless. Angi's own failure to correctly configure the business's approved service-area ZIP codes also caused the business to be charged for leads outside their coverage area, and support offered no meaningful investigation or refund -- only a supervisor callback request.

A customer switching carriers experienced over 144 hours of delay porting two phone lines, with the losing carrier blaming the new carrier and vice versa. The customer has no independent way to verify which company is actually holding up the number release. This reflects a structural transparency gap in the cross-carrier porting process that leaves consumers stuck without service and unable to assign responsibility.

Credit card users have difficulty determining which combination of cards best matches their spending habits, since credit card comparison content is largely affiliate-driven and generic. This forces consumers to either manually calculate rewards or rely on biased recommendations, missing out on optimal cash back.

A business adopting Salesforce reports that setup, integration with existing systems, and employee training took significantly longer than anticipated, with some features feeling unnecessarily complex for their needs. This reflects a broader onboarding-friction problem common to complex enterprise CRM rollouts, not just Salesforce-specific quirks.

Users in busy Slack workspaces experience notification overload, difficulty finding older messages in fast-moving channels, and a learning curve for newer AI features, with huddle quality also varying by connection. These friction points are described as manageable but point to a need for stronger organization and more flexible notification controls in high-traffic team communication.

B2B customer conversations increasingly happen in shared Slack and Teams channels organized around accounts, but existing support and success tools remain structured around individual, ticket-based interactions typical of B2C. This mismatch makes it hard to track account health and cross-customer patterns from how B2B customers actually communicate.

A contractor using Angi's lead platform was charged $200 despite completing no jobs, and continued to be billed even after cancelling and receiving a confirmation number. Support routed calls in circles, and the company noted it isn't monitored by the Better Business Bureau, leaving the customer with no clear recourse.

A 12-year insurance customer was quoted a specific monthly discount over the phone for increasing their deductible, but the issued policy reflected a much smaller reduction. When they asked for the call recording to verify what was promised, the representative refused to escalate or provide access to a manager. This reflects a recurring gap where verbal phone quotes aren't reliably honored or auditable against what customers actually agreed to.

A customer who canceled Allstate home and auto policies after finding a cheaper rate elsewhere was sent to a collections agency, despite never missing a payment or being late. The practice appears to apply broadly whenever a customer switches carriers, punishing departure rather than reflecting any actual delinquency.

A Slack user reports that desktop notifications frequently fail to alert them to new messages, causing missed communications. Stepping away for even a day leaves them buried under a backlog with no efficient way to catch up, turning re-engagement into a tedious manual scroll rather than a guided summary.

A user warns that an app claiming to be Google Docs, distributed outside the official Google Play Store, is actually an AI-generated clone designed to steal user data. This points to a growing pattern of AI-generated counterfeit apps impersonating trusted brands to harvest data from unsuspecting users.

Gusto users report not knowing when early/on-demand pay deposits will actually arrive. The lack of clear timing communication creates financial uncertainty for employees relying on early access to their wages.

A customer facing genuine financial hardship attempted to negotiate a settlement on an overdue storage balance but found frontline representatives refused to escalate the case to a loss-mitigation team, and falsely recorded that the customer had declined settlement offers. The customer was forced to appeal directly to corporate leadership to get a hardship arrangement considered before an auction deadline.

Small multiplayer and matchmaking apps that offer low-friction guest or quick signup accounts have no lightweight way to stop bad actors from mass-creating fake accounts to disrupt matchmaking pools. Existing solutions like rate limiting break down when the legitimate user base is small, leaving indie developers without a proportionate anti-abuse strategy.

A policyholder's claim was denied in part because the insurer asserted damage predated the accident, despite agreement from both the local agent and the body shop that it was accident-related. The customer was told the representative's judgment was final and that escalating to a manager would not change the outcome. This reflects a structural gap in auto insurance claims: no accessible, independent path to contest a low-level adjuster's damage-causation determination.

After being hit by another driver, a claimant faced slow liability acceptance from the at-fault insurer, pressure to accept an undersized rental vehicle, a lowballed repair estimate that forced aftermarket parts, and a lack of communication between the insurer and the rental company that left the claimant with an unexpected rental bill. No single party took ownership of coordinating the claim across these vendors.

A new telecom customer was quoted a monthly price over the phone that excluded activation fees and a promised senior discount that was never actually applied, resulting in a first bill $160 higher than expected. Support and in-store staff each blamed the phone-sales channel for the discrepancy rather than resolving it directly. This points to a systemic gap between what phone sales reps quote and what actually appears on the first bill.

Customers with a past identity-theft flag on their account face inconsistent and contradictory verification requirements when signing up for new telecom service, even after passing identity checks. Different representatives and back-end fraud teams give conflicting instructions, forcing repeated verification attempts before the customer is ultimately denied despite meeting stated credit criteria.

Developers using release-automation tools like release-please, releaser-pleaser, release-plz, and git-cliff hit hard limits: single-forge lock-in (GitHub only), no monorepo support, single-language scope, or changelog-only output without tagging or releasing. This fragmentation forces teams onto multiple tools or custom scripts for multi-forge, multi-language, monorepo release workflows.