In all seriousness, this would be a billion dollar idea if people who
need it were willing to pay for it.
The problem of course is that some would rather complain to you that the
Roomba can't get on the internet, and if you don't do something they'll
post on Yelp and Facebook saying that you block Roombas, and then write
a letter to the FCC saying we need regulation to prevent ISP's from
blocking Roombas. So we end up greasing the squeaky wheels and even
designing our network and procedures to make it easier to accommodate
the squeaky wheels.
I wonder if anyone ever called the electric company to ask why their
lightbulbs are blocked and their amps are throttled. I wonder if anyone
ever called tech support for their new TV and got told that the TV
doesn't turn on because of firewall rules at the electric company.
My thoughts from a decade ago when I ran the technical side of a hosted
PBX startup:
1) The end service usually fails because of a local LAN issue.
2) The service gets to troubleshoot the LAN, just to keep services
running.
3) Change your business plan. Instead of $50 - $100 for your current
service, charge $120 - $150 for LAN troubleshooting, and throw
your current service in gratis.
You will end up with the same amount of work, but get a higher return.
--
AF mailing list
[email protected]
http://af.afmug.com/mailman/listinfo/af_af.afmug.com
