Qliq University: Broadcast Best Practices


May 30, 2019

I’ve driven my car for about two years with no accidents, no malfunctions. It got me from point A to point B and I would have told you I know that car pretty well. I was a successful driver, it would seem. But on a long road trip last Sunday my husband made that car come alive. He flipped it into “Sport” mode and took off, bending curves like I have never attempted. I didn’t even know the car had a sport mode! Can you imagine, owning your car for two years and never realizing the power, or even the existence of such a key feature? No, you’re far too smart I’m sure. However, in preparation for Qliq University session two “Broadcast Best Practices” - I learned many customers experience this same “ah-ha” moment when they’re taught just what broadcast messaging is and how it can help their organization. A key feature, a simple, no-nonsense, function - was hiding right there in plain sight. This session focused on using broadcast messaging in the most efficient and effective way possible, and was as one attendee put it - “An eye opener.” If you missed the session please take 30 minutes to check it out and I’ll be re-capping some highlights below.

What is Broadcast Messaging?

As reviewed in class, the most significant difference between broadcast messages and all other messaging types we offer is: When you send a broadcast message all replies are directed back to the original sender only.

When you’re involved in a Group or Multi-party message, all participants are exposed to the replies. This is really nice when you’re seeking collaboration, but sometimes you need to send out information where replies being seen by all could overwhelm or waste time.

Broadcast messages are ideal for sending out information to multiple users where the responses only need to be seen by the sender, for example - alerts, codes, informational communication. We covered several examples in our class but the best ones always provide clear, concise, actionable information. These messages engage users with a call to action. For example, you could send out a broadcast message to alert licensed staff that they are in need of additional continuing education credits (to maintain their license) and provide them with a link to enroll in an upcoming skills lab to satisfy the requirement. This may have traditionally been handled by emails or flyers but our customers report much greater results by sending the message as a broadcast. Why? Because you’re putting the information in a place that they look anyway, you’re giving them the link to enroll, you can track (in message details) that they received/read the announcement, and if they do happen to have more questions they can reply without everyone seeing their reply.


During our class we reviewed several use cases from actual customers, some where they send out their code pages via Qliq broadcast, some who find their missing IV pumps by issuing alerts via Qliq broadcast, and even examples where natural disasters impacting roads and patients were communicated via broadcast with actionable recommended steps.

Whether there is a baby missing from the NICU, a road blocking home health aides, missing TB tests delaying new hire start dates, or upcoming community health events - a broadcast message can quickly get the word out in a secure manner and allow for real-time, private, responses.

What else did this session cover?

Students were guided through definitions, terms, security settings, use cases, and best practice tips. What makes one broadcast message more successful than others? We covered that. What fascinating use cases are out there among Qliq customers today? We covered that. How can I engage my user base and keep them coming back to the app for useful information? Covered. So now you have to ask yourself, what was missing from this session? If the answer is YOU then take a moment today to watch the session and enroll in our upcoming June 28th session - “User Upgrade”.

The Author

Related Content

Customer Success Story:

No items found.
Related Story:


Want our blogs in your inbox?
Subscribe for more!

Thank you!
Oops! Something went wrong while submitting the form.