We are a group of users of Blackbaud products and are not affiliated with Blackbaud. We'd love to have you join our community to help and be helped in getting the most from your Blackbaud software.
Register now to join us to get independant advice on your system, connect with 3rd party consultants to help you maximize your database and have a real alternative to the official Blackbaud website.
We currently use appeals to track our invite list and pull them over as a group into the event. We're getting ready to stop doing that and just record the event on each person's record. Where is everyone currently tracking the bouncebacks from email invites and returns from hard copy invites on the event tab?
Email invites - we delete that email address from their record, and don;t
mark it on the event module anywhere.
Hard copy - we mark them as "No valid address" on Bio 1 and don't mark
anyhting on the Event module.
The trouble with what you are describing is that it doesn't just apply to
the event - it applies to the person for every point of contact so marking
it within the event module is a) double data entry or b) putting it in a
place where your other mailings may still use the bad addresses.
__________________ Peter Gulka
Chief Bus Driver
Blackbaud User Society www.blackbus.org
We do exactly the same as Peter just mentioned with the exception of rather than deleting the email completely we change the phone type from E-mail to Bounced so that we know not to try and add it again.
@Lee - we used to do that too until people started getting more than one
bounced email address. We found that the number of times we accidentally
reused a bounced address was so small it didn;t justify the extra clutter.
Same thing applied to wrong numbers for phoning. We would change them to
"Wrong Number" but gave up and just deleted them.
__________________ Peter Gulka
Chief Bus Driver
Blackbaud User Society www.blackbus.org
Our policy is that if the event invitation list is over 200 people, we don't globally add them to the event until they register. We DO note an ACTION item that they were invited. Less than 200 invitees, it's easier to manage in the event.
I have an attribute catagory called "No Mail Reason" and it includes a pull-down description of "No Email - per opt out request" and "No Email - bad email address". That way it's technically on the record, and should we talk to a constituent, we can mention the email address we 'had' on file.
We do the same for return mail - "No Mail Reason" attribute. The No Valid Address button has too many places where you can include/exclude them from things like query/reports/etc., to not cause problems somewhere else.
SARyan
Linear Mode
