performance reminder email success stories

Hello!

Our organisation will be soon implementing automated performance reminder emails through Mail2. We have done extensive research to explore what the content of these emails should be but would love to hear from other organisations that have seen success in sending these emails.

Are you doing something cool and funky with your emails? Something a bit outside the square? What has worked super effectively for you? What hasn't?

Any and all ideas are very much appreciated!

BV

Parents
  • You all are super great. I'm finally making some headway and the pieces are falling into place. Next stop - testing the scheduled job.


    -----Original Message-----
    From: Tessitura Ticketing Forum [mailto:forums-ticketing@tessituranetwork.com] On Behalf Of Michele Keutsch
    Sent: Thursday, December 03, 2015 5:24 PM
    To: Dot Krebs
    Subject: RE: [Tessitura Ticketing Forum] performance reminder email success stories

    If it's a pre/post performance reminder, then it would be the perf date.
    ________________________________
    From: Dot Krebs
    Sent: ‎12/‎3/‎2015 4:40 PM
    To: Michele Keutsch
    Subject: Re: [Tessitura Ticketing Forum] performance reminder email success stories


    Ok.... That's part of where I'm tripping over myself.

    Based on what you see, should I use the perf_dt for the custom_date or should custom_date be blank?
    From: Michele Keutsch
    Sent: 12/3/2015 4:09:31 PM

    The view is also required to contain a column named: custom_date This date is the date that is used by the Tessitura Date Section window in the scheduled job. For example, if you wanted to create a Membership reminder, the custom_date column would contain the date on which the membership expires. For an abandon cart reminder, the column would contain the date on which the cart was abandon. The field name must be lower case and data format should be YYYY-MM-DD.



    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Ticketing Forum. You may reply to this message to post to the Ticketing forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!


    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Ticketing Forum. You may reply to this message to post to the Ticketing forum or visit the site to search, read and post to the forums.

    In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
Reply
  • You all are super great. I'm finally making some headway and the pieces are falling into place. Next stop - testing the scheduled job.


    -----Original Message-----
    From: Tessitura Ticketing Forum [mailto:forums-ticketing@tessituranetwork.com] On Behalf Of Michele Keutsch
    Sent: Thursday, December 03, 2015 5:24 PM
    To: Dot Krebs
    Subject: RE: [Tessitura Ticketing Forum] performance reminder email success stories

    If it's a pre/post performance reminder, then it would be the perf date.
    ________________________________
    From: Dot Krebs
    Sent: ‎12/‎3/‎2015 4:40 PM
    To: Michele Keutsch
    Subject: Re: [Tessitura Ticketing Forum] performance reminder email success stories


    Ok.... That's part of where I'm tripping over myself.

    Based on what you see, should I use the perf_dt for the custom_date or should custom_date be blank?
    From: Michele Keutsch
    Sent: 12/3/2015 4:09:31 PM

    The view is also required to contain a column named: custom_date This date is the date that is used by the Tessitura Date Section window in the scheduled job. For example, if you wanted to create a Membership reminder, the custom_date column would contain the date on which the membership expires. For an abandon cart reminder, the column would contain the date on which the cart was abandon. The field name must be lower case and data format should be YYYY-MM-DD.



    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Ticketing Forum. You may reply to this message to post to the Ticketing forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!


    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Ticketing Forum. You may reply to this message to post to the Ticketing forum or visit the site to search, read and post to the forums.

    In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
Children
No Data