Open natehn opened 2 years ago
Thanks for raising the issue @natehn !
The context is that I want to start doing a monthly update to our sponsors on Open Collective, we have 35 listed here: https://opencollective.com/mautic
When I go to send an update it attempts to send it to some 350 people - presumably every person who has ever contributed anything, including event tickets.
I think it should be possible to:
It might also be wise to consider the implications of sending an email to people who got a ticket from an event 2 years ago as well - really we should be checking if we still have permission to contact them, not sure if OC does that in the background already though.
Might be that it is not possible to do, but I think it is also not possible for us to push these over to Mautic owing to not having the individual contact address for the organisations who sponsor us.
Who is your user?
This user has put on many events and also has a number of financial contributors.
What are they trying to achieve?
They want to send an Update to only their financial supporters, without also sending it to all past event attendees.
How are they currently doing this?
They are not.
Triage Template (core team only)
This template is for members of the team to triage for prioritisation. For more guidance see https://www.loom.com/share/369ab467fbc64dec848085d38ff57ca0: P1 high frequency, high impact P2 low frequency, high impact P3 high frequency, low impact P4 low frequency, low impact Examples of high impact - a problem affects users during an essential process (expenses and payments > onboarding and registration > contributing) with no workaround. High frequency - >10% of users affected (measured as a proportion of total potential users for this case).