Awesome 6 Hotel Tips for Twitter

These days social media is part of every hotel’s online marketing strategy but while the majority of hotels have a Facebook account or frequently post on Instagram, the importance of Twitter is often overlooked. This is a real shame as 50% of global Twitter users follow brands they like, and that’s over 150 million users! And with Twitter being so fun and easy to use, there is no excuse to continue brushing it aside. Read this article and we’ll give you the basics on how to get started.

1. Create a Catchy Profile

First impressions count so make sure your Twitter profile represents your hotel well. Use an attractive hotel photo, or your hotel logo, and create a memorable bio that includes searchable keywords like hotel or spa. For your Twitter background use your best hotel picture or create a customised picture that complements your brand identity and appeals to your target audience.

2. Create a Persona

Before you start tweeting, define your brand and the route you would like to go down on the platform. The language you choose will be your brand voice to your followers. Not every approach suits every hotel and highly depends on your main demographics.Look at other industry examples and how they engage with their customers. Keep in mind: Twitter should be fun for you and your followers.

3. Build a Network

Develop a community of users who share an affinity for your hotel or your destination by using directories like Wefollow and Twellow and checking out followers of hotels similar to yours or indeed followers of relevant industry players.After that you can grow followers organically by being active on the platform, regularly commenting on and sharing tweets. Also don’t forget to use the Twitter hashtag which allows users to curate conversations around a topic. Each of your tweets should contain at least one or two relevant hashtags to make your content more searchable. It’s also a good idea to create a unique hashtag you can use for your brand eg. #HiltonHonours

Read rest of the article at NetAffinity