Book Business Magazine recently asked me if I would provide them with a few Twitter tips for book publishers. I was flattered, of course, and happily obliged. I put together the first five tips in the following list for them--which they've published here along with other great tips from other Twitter mavens. But I realized after sending off the list, that I had a few more I wish I had included. So I've put together this new list of Twitter tips for book publishers, made each tip tweetable, and posted here for all the (publishing) world to enjoy and discuss. Please let me know if you have other Twitter tips for bookish types.
(Some of the tips have been edited down in their Tweet version to fit the character limit.)
1. [Tweet this tip!] Sign up for Twitter then cruise through WeFollow.com, TwitDir.com and the new Twitter Lists to find and follow folks in your niche.
2. [Tweet this tip!] Create several Twitter accounts based on the niches in which you publish.
3. [Tweet this tip!] Avoid the temptation to automate. It is important that you are on Twitter to respond to the community.
4. [Tweet this tip!] Sell books by adding substantive information from your books and authors to the conversation. No hard sales pitches, please.
5. [Tweet this tip!] Have fun. Invent new ... ways to engage your Twitter community--contests, polls, jokes, raffles, giveaways, etc.
6. [Tweet this tip!] Twitter accounts dedicated to a single book are hard to build and sustain. Stick with the larger niche.
7. [Tweet this tip!] If you are one of a few people running a single Twitter account, be open about it by signing your name ala: -Jesse
8. [Tweet this tip!] Create and use hashtags to start and follow conversations in your niche.
9. [Tweet this tip!] Join appropriate Twitter groups (twittgroups.com) and have honest interactions with the folks there.
10. [Tweet this tip!] Use tools to track your Twitter success: ChartBeat, HootSuite, Google Analytics.
Read more great tips for book publishers in Book Business Magazine's latest Twitter article.
This post was originally published on Jesse's blog.