Please submit all product enhancement ideas below. We welcome your feedback; your ideas will be reviewed by the Product Manager that oversees the development of that part of the product on an ongoing basis and updated with its current status monthly based on our product planning process. Ideas you submit could help us shape features currently in development or grow our repository of requirements for our next big enhancement. Thank you for taking the time to share your thoughts and expertise with us.
If you believe you are experiencing a defect please contact Support.
If a constituent has multiple accounts with the same email address, he may receive the same message from the same email deployment several times - one for each record. Yes, we should dedupe our data, but for those missed in this process, there should be a simple control added to deployments so that the same single message doesn't go to the same email address more than once. The current practice puts our shared IP at risk because it leads to increased spam complaints and unopened messages.
|Area of the Product|
|Org/Company Name||Alzheimer's Association|
The main thing to consider here, is if you have separate constituents with the same email and you need to send them specific information to them. However, if the email going out does not need to give specific information to the individual users who share an email, then the option should be given to suppress sending more than one message to the same email address.
Attachments Open full size