Sender/Recipient Profiles

Hello Carl,

Great questions about Nova, let me help to address them.

Yes, Sender Profiles allow you to send an email from anyone else in the club, and or from email addresses not connected to the account in general. Recipient profiles are the opposite of Sender Profiles, its who the target is to receive an email. Both Sender and Recipient profiles are used in Nova in various ways.

To give a current example that customers can interact with today, Membership Success uses both. When Forms are completed for a prospect, the system uses both to complete sending an email to the user interacting with the form. The Sender Profile controlling who it is coming from, and the recipient profile choosing who it will be delivered to. Examples:

When a prospect fills out the interest form the following happens:

• An email is sent to the prospect from the club, thanking them for their application. This users the sender profile to be “from the membership chair”, so that it appears that the club’s membership success person has taken the action.
• In email is sent to the administrators of the club, letting them know that a new application has been completed. This path used a recipient profile to control who the notification goes to.

Under Nova in future updates through our Forms system for example, you would be able to create a form that sends an email to someone via a recipient profile, and you can use a sender profile to configure whom that notice comes from.

To talk about a straight forward use case, if a club or district needed their emails to come from the President / Governor, they would be able to create this sender profile and allow specific users to send from it. Giving the ability to send messages on behalf of users has been a strong request and something we’ve built into the system.

In cases where profiles are used, if no profile is presented, whatever profile is set to the default will be used instead. This goes for both sender and recipient profiles.

I hope this helps!

 

Thanks for the explanation, Zach. This is definitely going to take demonstration video(s) and tutorial pages to walk people through the sequence. One of the security challenges will be that the person who a message appears to be sent from needs to know that this is happening, as they are responsible for the content of that message. Even if someone else actually set it up.

A good practice might be that whenever an auto-generated messages is attached to a Sender Profile, that person is notified with a message that says "You need to know that CR will be sending this message on your behalf ..."

I like the idea of the recipient profile, as I've needed to set up mailing aliases with my ISP for a number of roles in the club. So it will be important to know how to set it up so that CR can process the aliasing rather than the ISP. And it may indeed require a change on my ISP's end to let this happen.

 

Appreciate the input. We don’t expect regular members to use either of these options very frequently if at all. It is intended for administrative use, and account setup. Sender and Recipient profiles in general are something we consider a bit of a “power user” feature, and best used for general accounts like “Membership Committee”, “Rotary Club of X”, etc. Documentation to work with them will definitely be provided.



Let me know if you have any other questions.

 

** we're testing the success functionality, but have a problem. The field in the template is not picking up the default membership chair's name/email etc - even though set up as default. Also noted that the help article shows different images for the setup than the actual fields in the dialogue boxes. The messages are just using Membership Chair -- and no name.. Pleas advise.