|
|
|
|
|
by efitz
35 days ago
|
|
I love this. The best documentation is that which is presented at the exact place and time that it is needed, and users self support really well if you do that. I once worked for $COMPANY and we had a network scanning application. Always generated a lot of tickets from angry people wanting to scream about bots. So we put a web page page on each worker that would inherit some details from whatever job was running, and say “I’m a $TYPE_OF_SCANNER FROM $COMPANY doing $THING_THAT_BENEFITS_YOU. This behavior is covered by our terms of service page at $LINK. If you believe that we should not be doing this, please contact $SUPPORT and provide this code: $SCAN_JOB_IDENTIFIER” Call volume and unhappy customers went way down. |
|
ex: Googlebot/2.1 (+http://www.google.com/bot.html)