Generated when a membership order is renewed through the back office or via the Web. An email is sent to the customer as a “thank you” for renewing.
The logic to select membership orders with a Line Status code of ‘A’ in the “MBR” subsystem and that it is 30 days after the start date of the renewed order. The membership end date must be in the future.
This notification overlaps with other notifications where a new order and payment is received. If you use the notification below, change the procedure so two emails are not sent to your customers for the same event:
· Payment Received
The schedule to run this procedure is determined by the Event Interval setup on the Notification Maintenance screen.
Event Stored Procedure Name: usp_NOTIFY_AFTER_MEMBER_RENEWAL
Chronicle Table Name: usp_NOTIFY_AFTER_MEMBERSHIP_CHRONICLE
None
· There is an assumption here that an Active order line implies that it has been paid. But this may not be true for all organizations. An additional filter can be added for a balance of zero.
· The number “30” is set in the stored procedure as the number of days after the renewed order’s begin date. This number can be changed to suit an organizations membership retension campaign.
· You might want to send this “thank you” message soon after the next year’s renewal is paid. Remove the comparison to the begin date and add the receipt date.
Dear ##CUSTOMER.FIRST_NAME##,
Thank you for renewing your membership with [Insert Association Name Here]. Should you have any questions regarding your member benefits please feel free to contact us via email Membership Benefits or by calling 1-800-BENEFITS.