The Customer Who Signed Up With a Fake Name (And Why I Didn't Care)

Mid-thought: I had a customer named "Mickey Mouse." Email address: [email protected] Payment method: a prepaid card. Everything about this signup screamed "fake."


I almost cancelled his account. Then I checked his usage. He watched 30+ hours per week. He never opened a ticket. He paid on time. He had been with me for 8 months.


Here's the thing — customers use fake names for many reasons. Privacy. Paranoia. A desire to protect their identity. A fake name does not mean a fake customer. A fake name does not mean a scammer.


In most cases, resellers cancel accounts with fake names because they assume the worst. They lose legitimate customers who are just privacy-conscious.


What actually works is focusing on behaviour, not identity. A customer who pays on time and doesn't cause problems is valuable regardless of their name. A customer who opens 10 tickets per month and pays late is a problem regardless of their name.


One real-world scenario: a reseller in Leeds had a customer named "Test User." He assumed it was a scammer. He almost cancelled. Then he noticed the customer had been active for 2 years. Same name. Same payment method. Same consistent usage.


He realised "Test User" was just a private person who didn't want to share their real name. He left the account active. "Test User" stayed for another 2 years.


The pattern that keeps showing up is that resellers waste time policing identities when they should be policing behaviour. Your IPTV Reseller Panel logs show behaviour. Behaviour matters. Names do not.


Mickey Mouse paid on time for 2 years. He never complained. He referred 3 friends (using real names). I never learned his real identity. I didn't need to.


Focus on behaviour. Ignore fake names. Keep good customers regardless of what they call themselves.


A loose sentence: A paying customer is a paying customer, even if their name is a cartoon character. Collect the payment. Move on.


 

Leave a Reply

Your email address will not be published. Required fields are marked *