Membership Renewal Process

Former Member
Former Member $organization

Hey Dev people!

I'm more an IT guy at the Fairfield Theatre Company, but i'm looking to find the best way to implement a workflow for membership renewals.  Call it solicitation, call it sales, up-selling, recruitment, whatever.  Basically, i'm lost in a circle of CSIs, Solicitations, tasks/ticklers, Procedures, and form vs function.

Our current plan is pretty simple on paper, its just properly executing it:

2 weeks prior to expiration, we send a reminder email
day of expiration, we send an email (naturally)

These steps are currently automated with Wordfly....

Then comes the rub;

1:  If they don't renew after 2 weeks, I want to call them....
2:  If they don't renew with the call, log it and set possible action (call back, try on the weekend, etc.)
3:  Months later, if they still haven't renewed, send a letter.

So my real question is:  From your experience, what is the best way of accomplishing the above?

Any input is greatly appreciated.

Parents
  • Hi James,

     

    The easiest way I can think of to manage this work flow is with promotions. As long as you’re careful to make a promotion every time you send an email, make a phone call, or send a letter, you should be able to keep track of who has received each contact and who has yet to renew.

     

    The downside to using only promotions, though, is that it’s not as easy to track responses on a donor by donor basis. We manage our renewals through a similar combination of email, mail, and phone calls, and we track this process in Tessitura through both promotions and solicitations. We promote all emails and mailings, and we create a solicitation (in addition to a promotion) for any phone calls we make. If a donor gives a specific reason for why they’re not renewing, we’re able to capture that within their solicitation.

     

    I hope that helps. If you’re interested, I’ll be happy to pass along the structure we use for solicitation types and statuses.

     

    All the best,

    Alex

     

    Alex Harris | Patron Development Manager | 206.443.2210 x1018 | Fax: 206.443.2379
    SEATTLE REPERTORY THEATRE | www.seattlerep.org | In Lower Queen Anne at Seattle Center

    ON SALE NOW | The K of D, an urban legend Jan. 14-Feb. 20, 2011 | The Brothers Size Feb. 4-27, 2011

     

    From: Tessitura Development Forum [mailto:forums-development@tessituranetwork.com] On Behalf Of James Boncek
    Sent: Thursday, February 24, 2011 8:02 AM
    To: Alex Harris
    Subject: [Tessitura Development Forum] Membership Renewal Process

     

    Hey Dev people!

    I'm more an IT guy at the Fairfield Theatre Company, but i'm looking to find the best way to implement a workflow for membership renewals.  Call it solicitation, call it sales, up-selling, recruitment, whatever.  Basically, i'm lost in a circle of CSIs, Solicitations, tasks/ticklers, Procedures, and form vs function.

    Our current plan is pretty simple on paper, its just properly executing it:

    2 weeks prior to expiration, we send a reminder email
    day of expiration, we send an email (naturally)

    These steps are currently automated with Wordfly....

    Then comes the rub;

    1:  If they don't renew after 2 weeks, I want to call them....
    2:  If they don't renew with the call, log it and set possible action (call back, try on the weekend, etc.)
    3:  Months later, if they still haven't renewed, send a letter.

    So my real question is:  From your experience, what is the best way of accomplishing the above?

    Any input is greatly appreciated.




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Development Forum. You may reply to this message to post to the Development 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!

  • Former Member
    Former Member $organization in reply to Alex Harris

    Thanks for your input, Alex!

    I think i see where you're going with that, but i'm not quite sold on the solution.  Perhaps i don't have a great enough understanding of your exact workflow, or how promotions integrate with everything else, but from a functional standpoint, i really like how Ticklers work/Can work.

    Designating a list of tasks for a user to complete and note an outcome is great.

    But maybe i'm missing some of the benefits of a promotion and how you manage them.  reporting on successful sales of a promotion/appeal must be nice, and better than notes in a tickler.

    I dunno.  Anyone else care to share?

Reply
  • Former Member
    Former Member $organization in reply to Alex Harris

    Thanks for your input, Alex!

    I think i see where you're going with that, but i'm not quite sold on the solution.  Perhaps i don't have a great enough understanding of your exact workflow, or how promotions integrate with everything else, but from a functional standpoint, i really like how Ticklers work/Can work.

    Designating a list of tasks for a user to complete and note an outcome is great.

    But maybe i'm missing some of the benefits of a promotion and how you manage them.  reporting on successful sales of a promotion/appeal must be nice, and better than notes in a tickler.

    I dunno.  Anyone else care to share?

Children
  • Former Member
    Former Member $organization in reply to Former Member

    Hi James!

    I think the solution depends in part on volume. With promotions, you can do more updates en masse and then suppress certain constituents from future lists, extractions, etc. This is very helpful in a high volume operation where touching each constituent record isn't feasible.

    If you're in a situation where you have the time to track each constituent individually, you might want to look into solicitations or CSI/ticklers.

    Let me know if you'd like to chat further.

    Best,

    Mara

  • Former Member
    Former Member $organization in reply to Former Member

    Thanks Mara!

    I've taken a step forward in the process and wrote a nightly procedure to add a tickler assigned to the Box Office Group>bo tickler user, for any constituent who hasn't renewed after 2 weeks of expiration.  The BO Staff of they day makes calls to these people and logs notes of the results.

    The trick now is how to properly process them if they still haven't renewed in x time...But at least we're making that next step for now.