Categories
message on hold resources social media

#OnHold Fails and Wins to Brighten Your Day

Have you ever searched for #onhold on Twitter? It’s one of my favorite activities… and it’s not because I work for a company that produces on hold messages, it’s because the #onhold content is some of the funniest, silliest Twitter fodder out there. Here are some on hold fails:

#onhold Fails:

#onhold WINS! (?) 

Lessons for you, the marketer:

twitter on hold fails and wins 96227945

People are paying attention to what you say on hold.

When you say to a caller, “We’ll be with you in a moment” and a representative doesn’t answer their call for the next half hour, guess what? They are going to be MAD. And then they take to Twitter. If you repeat the same content over, and over, and over, and over, it’s really, really, really annoying. (See what I did there??) If you find that callers are complaining about repetitive music or messages, consider a longer Message On Hold program

If you try to play music your callers actually like, they just might like it!

Some of these Wins are based on the caller actually enjoying the music playing on hold. Go figure. Now, think about your buyer personas and target customers, and play the kinds of music that they want to hear while they’re waiting on hold. BAM! Instant Success.

You have an opportunity.

If there is any marketing or customer service content you want or need to reinforce (should I say “WHEN there is”?), Message On Hold is a great opportunity to share important information to a group of people who, as these tweets show, are actively listening.

Monitor Twitter

Here’s a stream to add to your social media monitoring: Your brand name or Twitter handle plus #onhold. You might be surprised to see complaints or praises about your on hold programming.

What are you playing to callers waiting on hold? Do you think your Twitter followers will like it? Let us know in the comments.

 

{{cta(‘b76d85c5-995f-4fda-b1f1-bbafeb8ce6b2’)}}

 

 

 

Leave a Reply

Your email address will not be published. Required fields are marked *