Hello blogosphere! Today, I decided to take a departure from the video blog of “The Q” and just type. Maybe it was lots of the talking I did this weekend (my mother graduated with her Master of Theology and I had to be “on” at her party and commencement reception so she could show off her baby boy) or maybe I am worried I will enter a diatribe about “LOST”… So I think this is easier to edit rather than reshooting a video.
I have had the tremendous opportunity to meet face to face with a couple ministries in the last week and a major topic we have been talking about was Twitter. One of my parent’s friends also asked me Friday at my mom’s graduation party “why on earth would any company or ministry Twitter? No one cares what other people had for breakfast”.
While I agree with my parent’s friend Bob, this question still perplexes ministries and businesses alike. I believe this question came up no less than a half dozen times in our office last week. So, allow me to give some practical ideas for your ministry.
- -Tweet events- When you’re doing something special, let people know about it via Twitter.
- -Offer something special- Give your congregation a reason to follow you on Twitter. Make it special for them. Give them something that you can only get via Twitter. Maybe it’s a special time to meet and have coffee with the pastor, and hey, if your budget allows, let the church buy! Or maybe a special preview for next week. Get creative!
- -Be consistent- I follow a few churches who send one tweet every month. That’s a little on the light side I would say. But don’t go too far the other direction and send out 10 tweets per day. Can you say Twoverload? I don’t think I can, but I wanted to type it anyway.
Need help with your Twitter strategy? What does your church tweet about? Do you tweet? What does your Twitter account say about what’s important at your church?
pic by respres







This website uses IntenseDebate comments, but they are not currently loaded because either your browser doesn't support JavaScript, or they didn't load fast enough.