Paging: Beep prior to each page

  • 0
  • 2
  • Idea
  • Updated 4 years ago
Archived and Closed

This conversation is no longer open for comments or replies and is no longer visible to community members. The community moderator provided the following reason for archiving: We have archived this topic as it has either reached a resolution has become inactive, or information contained in this thread is no longer accurate. If you have a related question on this subject, please post a new topic.

We are a medical office.  We have several physicians, a lab and an IV infusion area who all see patients.  The physicians see patients every 20 minutes.  We page the patients arrival for the staff so they know when to come out and get the patient from the waiting room.  There is a loud beep that precedes the page.  I understand this is a precursor for in settings that are noisy so others can listen for the page instructions, however, hearing a beep a hundred times a day in a medical office is untenable. We are requesting a feature be added to allow us to turn off the beep prior to paging or at least turn it down to a very minimal level without affecting the volume of anything else.
Photo of Zina McKenzie

Zina McKenzie

  • 80 Points 75 badge 2x thumb

Posted 4 years ago

  • 0
  • 2
Photo of Danno

Danno, Champion

  • 28,852 Points 20k badge 2x thumb
When you say "page" is that through an over-head speaker or via the phone sets?
Photo of Dan Hannula

Dan Hannula

  • 60 Points
Good Morning, Per Zina McKenzie above, we have a manufacturing plant.  We use the page feature to make announcements on the floor.  But, the 'beep' the precedes the announcement is way too loud.  Everyone on the production floor jumps when it goes off.  The volume of the announcement itself, is controllable via an external amplifier and external speakers.  So, we can control the announcement volume but not the beep.  I agree with Zina that we should have the option to turn the 'beep' off and/or control the 'beeps' volume.  Thank you, Dan Hannula/June 16. 2016.

This conversation is no longer open for comments or replies.