Castro App Founder Reports Limited Impact of Personal Customer Support. The founder had hoped that responding personally to user emails would build loyalty, but found the approach did not improve satisfaction. He believed daily use of the app and thoughtful replies would make customers appreciate the subscription model. When email volume grew, he hired a frequent user to answer messages. He noted that occasional quick fixes impressed customers, but most detailed responses were unsatisfying and sometimes annoyed users. He categorized incoming emails into subscription complaints, bug reports, unclear questions and feature requests. Subscription complaints were rare, with only one customer in two years expressing surprise at the subscription cost, and 99 percent of replies generated negative sentiment regardless of wording. Offering a 30‑day trial did not change attitudes and led to fewer trial conversions. Bug reports were useful when reproducible, but many were duplicates or vague, providing little actionable information. Nuanced questions about app store processes or account issues represented less than 1 percent of emails and were resolved when relevant. Confused customers often returned with repeated inquiries, creating a cycle that increased workload without improving loyalty. Feature requests typically came from a small, unrepresentative group and could lead to extensive roadmap demands if implemented. The founder concluded that personal support was not a differentiator and that focusing on product improvements yields better outcomes than trying to build rapport through email.