Question

Topic: Taglines/Names

Need Title/tagline For Customer Support Newsletter

Posted by tina.yarovsky on 250 Points
I work in the Customer Support department of a software company in the financial trading space. We send customers various email "advisories" pertaining to software issues, new product features, 3rd party Exchange news, etc. We have started to aggregate these point-in-time advisories into a "weekly e-bulletin." We need to brand this communique with a fitting title and tag line to relay the fact that this publication (a) is targeted to a customer support audience; (b)contains news that impacts our software and the customers' trading environments; and (c) includes news that customers may (or may not) need to act upon to keep their trading environments running. We've been brainstorming titles and taglines and have not come up with anything particularly effective (or catchy!). Weekly Bulletin? Weekly Digest? Support News? Help!
To continue reading this question and the solution, sign up ... it's free!

RESPONSES

  • Posted on Accepted
    I'd look for a word like "Action" (as in "Action Digest") or "Impact" (as in "Trading Impact") -- something with some life to it, and that will motivate recipients to read it rather than ignore it. Also, if there's a way to include some reference to the company name in the newsletter name, that would probably be good.
  • Posted by Jay Hamilton-Roth on Accepted
    Up With Trading!
    Trading 24/7/365
  • Posted by SteveByrneMarketing on Accepted
    Trading Software Advisory (April)
    Trading Software Advisory (April 15th)
    Trading Software Advisory (biweekly)
  • Posted by SteveByrneMarketing on Member
    also ...

    Trading Software Advisory (Monday)

    April (usually 4 issues per month)
    April 15th ( Monday's date in April ... or other day of week)
    biweekly (consider twice a month, get feedback from readers to learn if they would prefer biweekly)
  • Posted by Moriarty on Accepted
    Financial Update (to coin the software term). Relevant actionable advice for your portfolio.
  • Posted by tina.yarovsky on Author
    These are all great ideas...thanks! I like the "trading" theme but want to make we also pay homage to the "technology" aspect. Oh, and I didn't mention, our marketing team is going to launch its own eNewsletter, so we need to make sure we differentiate our "Support" publication from theirs. Too many nuances! I'm going to keep chewing on this...and re-review all of the posts. Thanks so much! If you have any other thoughts/suggestions, please continue to share! I appreciate your insight.
  • Posted on Moderator
    Be careful about having too much communication from the company. Maybe you can combine the newsletters? Your customers may not be as eager to hear from you as you'd like them to be, and the result will be a lot of "unsubscribes" or spam filtering that works against you.
  • Posted by tina.yarovsky on Author
    @mgoodman, that's a very good point; we do have a targeted recipient list of support professionals...and marketing has a different list with minimal overlap, so that should (hopefully!) prevent us from spamming our users! i think their newsletter frequency will be monthly -- and ours will be the weekly, practical, "gotta make these changes in your environment to keep your traders functioning" bulletin!
  • Posted by Moriarty on Member
    "and marketing has a different list with minimal overlap"

    Does this not mean that you do not need to differentiate the newsletters so much? After all, the headlines used (email headlines, that is) would tell the recipient if it were the financial or the marketing newsletter.

    So:

    Financial Update - technology newsletter affecting your portfolio

    Oh, and since there are two newsletters, the occasional subscribe link to the other one may pay good dividends.
  • Posted by tina.yarovsky on Author
    Thanks, Carrie. Apologies for not getting back to this. Was out of the office...but wanted to say a huge "thank you" to everyone for the brainstorming. It helped tremendously.

Post a Comment