Fall Alerts and Manual SOS: A Practical Guide for Personal Alarm Projects

Practical guide · Amulink

Automatic fall alerts and a manual SOS button serve different purposes. For a telecare project, explaining both clearly is as important as demonstrating the device. This guide helps service teams introduce the Amulink WPD-01 without creating unrealistic expectations about detection or response.

Amulink WPD-01 care application scenario
Clear training and an agreed response process support the use of a personal alarm.

Keep prevention and alerting separate

The World Health Organization’s falls fact sheet describes prevention as a broader task involving education, safer environments and appropriate interventions. An alarm has a different role: supporting a process for asking for help or notifying agreed contacts.

A fall alert should not be presented as preventing a fall or replacing an individual assessment by a qualified professional. Product evaluation and the person’s wider support plan need to address different questions.

Explain what each feature is for

WPD-01 supports fall alerts and manual SOS. Automatic alerting is intended to flag a potential event; manual SOS gives the wearer a way to request help deliberately. Neither feature establishes the severity of an injury or guarantees that assistance has arrived.

During onboarding, explain that automatic detection is not a guarantee that every fall will be identified. Keep the agreed manual SOS procedure central to training, including situations where help is needed for a reason other than a fall. Refer to the How It Works page and product resources for the supplied operating information.

Confirm the configured response workflow

Before handover, establish who receives each type of alert and what they do next. WPD-01 includes two-way calling, but the actual call routing, contact availability and escalation arrangement must be confirmed for the project.

  • Who reviews an automatic fall alert?
  • How does the receiving team try to contact the wearer?
  • What is the agreed process if the wearer cannot be reached?
  • Who records the outcome and any follow-up action?

Do not assume an alert automatically contacts emergency services. Make the project’s actual arrangement clear to the wearer and their support network.

Evaluate safely and document the limits

Ask the supplier for the approved evaluation method and relevant instructions. Never ask a wearer to fall deliberately, and do not improvise unsafe demonstrations or drop the device to manufacture a result.

Use arranged manual SOS calls to verify the receiving workflow. Any separate evaluation of the fall-alert function should follow the approved procedure and be conducted by an appropriate team. A staged demonstration cannot prove performance across all real-world events.

Record the device configuration, test method, receiving contact and observed outcome. Keep automatic-alert observations separate from manual SOS results so the project record does not imply that one test validates every feature.

Plan for unexpected alerts and missed events

Explain how the service handles an alert when no assistance is required, using the project’s confirmed procedure. Review repeated unexpected alerts with the supplier or service team rather than making undocumented changes.

If someone reports an event without an alert, record the circumstances and arrange a review of the device, setup and service process. Avoid turning a small pilot’s results into an unsupported accuracy percentage.

Use a clear handover message

A useful explanation is: the device offers a manual way to request help and a fall-alert feature, while the service team follows an agreed response plan. Ask the wearer to explain the manual SOS process in their own words and make the support contact easy to find.

Our support plan guide covers charging, contacts and regular reviews. For voice evaluation, see the indoor two-way calling guide.

Discuss a WPD-01 evaluation

Explore Amulink application scenarios or request a sample for your project. Share your intended users and receiving workflow so the evaluation can address the service you plan to provide.

Source and editorial note

World Health Organization: Falls (April 26, 2021; checked October 13, 2026) provides the general prevention context. This is an original practical guide, not a new research report. The onboarding and evaluation recommendations are Amulink editorial guidance, not a medical assessment or a statement of product detection accuracy. WHO does not endorse the product.

Chat on WhatsApp