> Congressional staff already have plenty of tools for separating those form letters from real, constituent-written letters. I can dig up their names, but they're built by high-level contractors.
Intranet Quorum. Last updated in about 1996. It's probably what 95% of staff uses, and it's woefully inadequate. Clearly you talked to zero congressional staffers in the creation of this software. Which is a shame. Because if you had, your software would be effective.
Heck, even if you'd read one of the dozens of reports from the Congressional Management Foundation _FROM 10 YEARS AGO_ http://www.congressfoundation.org/index.php?option=com_conte... you could spot the problem here.
Whether advocacy organizations "send" the emails or whether they're sent by an individual has no bearing on either the legitimacy of the message, or whether or not they will remain unread.
I'd encourage you to hop on a plane, and go visit some congressional staffers and ask them how they'd like to receive your messages. Then build a tool starting from there. Like it or not, they're the customer.
Intranet Quorum. Last updated in about 1996. It's probably what 95% of staff uses, and it's woefully inadequate. Clearly you talked to zero congressional staffers in the creation of this software. Which is a shame. Because if you had, your software would be effective.
Heck, even if you'd read one of the dozens of reports from the Congressional Management Foundation _FROM 10 YEARS AGO_ http://www.congressfoundation.org/index.php?option=com_conte... you could spot the problem here.
Whether advocacy organizations "send" the emails or whether they're sent by an individual has no bearing on either the legitimacy of the message, or whether or not they will remain unread.
I'd encourage you to hop on a plane, and go visit some congressional staffers and ask them how they'd like to receive your messages. Then build a tool starting from there. Like it or not, they're the customer.