Immediate Change to TeamRaiser Participant Center Email

@Hayley Adams:

@Kent Gilliam
We like that they are trying to make some changes to the platform but we see one initial issue.

We did some testing and it seems as if the site will let individuals sign up as a fundraiser for zero dollars but the email functionality does not work until after a donation is made. The unfortunate part is that when you try to send an email out it appears to go just fine. You even get a pop-up stating it was successfully sent but the problem is it only gets sent to a spam detection area inside Luminate Online. Will some content be added inside the participant center page stating that you must either donate or fundraise $5 before the email functionality will work? Is there a plan to let individuals know their emails were not actually sent out successfully?

Hi @Hayley Adams … They are working on additional stuff for this and I'm hoping we can come up with some better direction on helping orgs notify participants if they are validated and they can actually send email. I'll pass along your comments to the product team.

@Cathy Rosander:

@Kent Gilliam

"Critical changes to your TeamRaiser were implemented on 4/7/2023 that results in new TeamRaiser participants, or participants who don't have a validated record in Luminate Online's Constituent360, unable to send emails from their TeamRaiser Participant Center until a validating minimum threshold is met:

A participant (is it correct here to add “with a validated record”?) must meet one of these criteria to use Participant Center email:

• Participant has transacted $5 or more to the organization at any point
• Participant has received confirmed donations of $5 or more from other donors (please confirm/clarity point in time here for this criteria, is it "as of 4/6 5pm when the change was made?) i.e. If a Participant has been a fundraiser for years in prior events, but just has not self donated or has not yet received a donation)
• Participant record is 365 days or older"
  
• Thanks,
• Cathy

Yes, the change actually went out a little earlier than I was first told so it went out around 5pm on 4/6.

If a participant has been in your database from a prior event then they will not be impacted. The primary goal of impact here is on brand new registrations that are new to your database that are not generating any kind of transaction, whether that be a registration fee, a self donation, or they solicited a donation. But none of your previous event participants should be impacted by this unless they use a new name/email combo that makes Luminate Online/TeamRaiser see them as a totally new constituent.

Hope that helps @Cathy Rosander.

@Meghan Christiansen:

@Kent Gilliam

I tested this on one of our TeamRaisers this morning. I tested a new constituent with $0 raised and also a constituent that has been in our system for over 365 days (also $0 raised). It did work as Blackbaud explained in that the new constituent was not able to send emails and the constituent in our system for over 365 days was to send emails.

My big concern is that as a new constituent with $0 raised, there is no warning about the email tool and you can go through the entire email send process with no issues or warning. There was nothing in the email tool to stop me from attempting to send an email and no warning when I sent the email. It wasn't until I went into my sent folder and opened the actual sent email that I saw this:

Most participants will not click through this much so they will not know their email(s) didn't send. There needs to be a warning for them before they try or in attempting to send the email, or just block them from sending it completely and an explanation of why.

The message added to the sent email also doesn't really make sense to a participant. I reached out to Support and you can change this message in the Message Catalog Editor if you search under “this message was intended”. We will definitely update this message on our end.

@Meghan Christiansen

Thanks for testing and sharing your confirmation how things are working. And yes… we've heard for help in overcoming the experience of non-validated participants not knowing their emails were not being delivered. I'm sharing all of this feedback and hopefully we'll improve on this soon.

One thing to note in an effort to reduce this negative experience is that you should be putting language wherever you can about this requirement. Obviously the registration thank you page and autoresponder is able to be immediately updated. Also I would recommend that you are utilizing the “Sample Solicitation to Forward” email in the autoresponders. In there you can add some language for those totally new to your database by registering for your event. You can even make this conditional content based on record creation date and first transaction value of $0.

I'm working with our team to try to see how we can improve this in the short-term and hope I can generate a walkthrough video with some of that info soon.

Thanks again for your feedback!

@Tanna Lewis:

@Kent Gilliam

RE: your note “You can even make this conditional content based on record creation date and first transaction value of $0” - don't suppose you have s-tag advice for that for the TR pages? I've got the message below added, but that would be nice to cut down who has to look at this. I can research it, but if you know the correct s-tags that would make it easier. Thanks!

@Tanna Lewis …

So there's not a way to make this conditional in an immediate manner right now that we can think of. The only way to make this conditional right now is to create the query to group all those not “validated." So far it seems building a query based on record creation date and whether there is any lifetime gift amount will get group the right constituents.

Then once you get that Group, you can use the S45 conditional like this:
[[?xTRUEx::x[[S45:{INSERT YOUR GROUP ID}]]x:: {insert the content to be displayed} ::]]

Simply add your Group ID and then the content you want to display. If the participant is logged in and is in the Group they will see whatever content you created.

We have several discussions going right now to try to determine better ways to deliver conditional content around this change so I'm hoping to have more updates soon.

@Tanna Lewis:

@Kent Gilliam

Thanks! Do you know if I can query constituents who have raised at least $X across all TRs?

@Tanna Lewis ….

So the best way to do this and keep it running in the future without having to update anything is to create a TeamRaiser Task. You can create a new TR task and have it search any TR event and any Participation Type and then you can choose a “Dollars raised greater than or equal to…” amount. You can select this to run daily. Then in Groups… there is a sub-level called Tasks under Groups and the results of this task will be put there. You can then build conditionals off that Group.

The best part about using this is that as long as you choose “any” and select all participant configurations you won't need to update the Task in the future.

Hope that helps.

@Jeremy Reynolds:

@Tanna Lewis
@Kent Gilliam

How about some S-Tag black magic?

<elevator music while I test this on my live site…>

Edit…gimme a sec, will update that with something more useful…

Heck yeah @Jeremy Reynolds! I was hoping some of our big brains would jump in here! Curious to see what folks like you and @Bruce Baughman might come up with in this area.

@Matt Barr:

@Kent Gilliam

Hi folks - here's what our dev team at Yeeboo Digital have come up for a potential solution in the interim that we're in the final stages of testing.

You are welcome to drop this in and try it yourself, we will complete our own testing this afternoon and will be delivering this to all our clients who use TR once we have testing complete ?

Happy testing and hope this can be of some use to some folks out there.

-----------

This script can be placed in the HTML section of the “home page” of the config of the TR (ie. PC home page) within the participant center.

The script will hide the email tab in the PC as well as the email links in the what to do next section until the participant has raised $5 or above and will display a lightbox to display some content front and center (editable copy is highlighted in yellow) to the participant to ensure they are aware of this if they have not raised above that $5 threshold.

The lightbox will no longer appear once the threshold has been met and the email tab in the PC will appear for the participant once the threshold has been met.

------------

[[?xTRUEx::x[[E48:[[S334:fr_id]]-x[[S1:cons_id]]x:if-dollars-gt:4]]x::
<script>
jQuery(document).ready(function(){
jQuery('ul.nav.nav-pills.top-nav li:nth-child(2)').show();
jQuery('.panel.contacts-panel').show();
jQuery('.panel.what-next-panel ul.what-next-list li:nth-child(2)').show();
jQuery('.panel.what-next-panel ul.what-next-list li:nth-child(3)').show();
});
</script>
::
<script src="//maxcdn.bootstrapcdn.com/bootstrap/3.3.7/js/bootstrap.min.js" type="text/javascript"></script>
<div id="emailMessage" class="modal fade" role="dialog">
<div class="modal-dialog">
<div class="modal-content">
<form id="ybd-popup">
<div class="modal-header">
<button type="button" class="close" data-dismiss="modal">
<span>×</span>
<span class="sr-only">Close</span>
</button>
<h4 class="modal-title">Insert Title Here</h4>
</div>
<div class="modal-body">
<p>Insert some copy here about the $5 minimum donation before email access is unlocked.</p>
</div>
<div class="modal-footer">
<div class="clearfix">
<div class="pull-left">
<button type="button" class="btn btn-primary-inverted" data-dismiss="modal"><span>Close</span></button>
</div>
</div>
</div>
</form>
</div>
</div>
</div>
<script>
jQuery(document).ready(function(){
jQuery('ul.nav.nav-pills.top-nav li:nth-child(2)').hide();
jQuery('.panel.contacts-panel').hide();
jQuery('.panel.what-next-panel ul.what-next-list li:nth-child(2)').hide();
jQuery('.panel.what-next-panel ul.what-next-list li:nth-child(3)').hide();
jQuery('#emailMessage').modal('show');
});
</script>
]]

Thanks @Matt Barr for sharing this awesome process! I knew the community would generate some really good options for this change.

@Matt Barr:

@Jeremy Reynolds

Thanks Jeremy. That was our next piece to try and work out, go community!

I'll post the non-modal version as well for folks to test in the next hour as well as that was our v1 and include the addition creation date check in the script.

@Matt Barr and @Jeremy Reynolds thank you so much for jumping in and sharing as you always freely do. Drinks on me at the next conference! lol