SMART SAFETY CONNECTION

One press.
Connected support
when it matters.

Press TagBell to send a BLE signal to your connected smartphone. The app then sends a help request to your preselected contacts over the network.

Your phone must be within BLE range, with the app and internet connection available. Contacts receive alerts over the network.

Download reports · Korean / English PDFExplore the app · seven interactive screens ↓New scenarios · School check-ins & bullying alerts ↓
Designated contacts
App · network
BLE · your phone
SMART
TAGBELL
Caregiver
Responder
Partner
●

App pushFCM · APNs

No response
•••

MessengerBackup alert

No response
◎

EscalationPreselected contacts

BLETagBell ↔ your phone
NetworkApp → designated contacts
Android · iOSMobile platform support

SMART TAGBELL · APP EXPERIENCE

From one small button
to connected safety

Check connections, route alerts and follow the response. Select a screen below to explore the proposed app.

Development proposalInteractive screens · sample data
Smart TagBellSample screen
Your connections today

Safety starts with connection

◉
Ready to connect

External button → your phone → contacts

Registered buttonTagBell-001
Sample battery85% ▰▰▰▱
Bluetooth LEConnected
Recipient groupFamily · 3
Design demo · no real alerts or location collection

TECHNICAL DESIGN

Clear roles from device to response

  1. 01

    Devices

    BLE · ID · Battery

    Button registration, user association and connection/battery monitoring. Keyring, pendant and helmet-mounted form factors.

  2. 02

    Mobile app

    Android · iOS

    Receive button events, manage consent and permissions, location, recording, cancellation and confirmation. Validate background operation per OS.

  3. 03

    Alert processing

    Push · Routing · Events

    Groups, sequential/simultaneous routing, unanswered policies, deduplication and response state. Distinguish dispatch from acknowledgment.

  4. 04

    Operations

    Dashboard · Audit · Report

    Role-based access, responder assignment, timelines, reports and fleet operations, with organization-specific policies and retention.

Extensions to validate

Wearable fall/inactivity detection / indoor BLE positioning / consent-based continuous location / AI-assisted false-alarm review / charging docks and maintenance

Phase 01

Connection and guardian alerts

Pairing, battery, groups, routing and basic incident reports

Phase 02

Everyday safety and sensors

Safe zones, location history, wearable confirmation and AI validation

Phase 03

Organization-wide operations

School, care and workplace dashboards, access roles, analytics and maintenance

The sequence is proposed. Timing, device support, detection performance and indoor accuracy require validation and integration review.

Everyday Smart TagBell · School journeys for children in Korea

“Mom, I got to school safely!”
A child’s day,
shared with one press

From school to an after-school academy, then home.
In this service scenario, a child presses the button and says a few words. Their voice is automatically recorded and sent to a parent together with their current location.

School→Academy→Home

Children share an update without making a call.
Parents receive their child’s voice and location together.

From a child’s point of view

A call can feel like a chore.
A press and a few words feel easy.

“Call me when you arrive.” A child may mean to, but put it off because calling feels inconvenient—or forget while busy with something else.

Smart TagBell combines the fun of pressing a button with the convenience of a short voice message. A casual “Mom, I’m here!” is designed to make staying in touch feel easy and help build a natural check-in habit.

How an update reaches home

Press. Speak. Keep a parent informed.

  1. 01

    The child presses the button

    They press Smart TagBell when arriving or starting the next part of their journey.

  2. 02

    Record voice and capture location

    The app on the child’s connected smartphone collects a short recording and the current location.

  3. 03

    Send automatically to a parent

    The registered guardian receives the voice message, location and transmission time together.

A daily journey

Five reassuring updates,
from school to home

Each example shows what the child says and what a parent receives.

  1. 01

    Arriving at school

    “Mom, I got to school safely!”

    At the school entrance, the child presses the button and shares a quick update.

    What a parent receivesSchool arrival confirmed

    Voice recording · School arrival location · Transmission time

  2. 02

    Leaving school for the academy

    “Mom, I’m on my way to the academy.”

    After school, the child sends an update before heading to their after-school academy.

    What a parent receivesOn the way to the academy

    Voice recording · Location when leaving for the academy · Transmission time

  3. 03

    Arriving at the academy

    “Mom, I’m at the academy!”

    The child presses the button on entering the academy to let a parent know they have arrived.

    What a parent receivesAcademy arrival confirmed

    Voice recording · Academy arrival location · Transmission time

  4. 04

    Heading home

    “Mom, I’m on my way home now.”

    When lessons finish, the child sends a quick message before heading home.

    What a parent receivesHeading home

    Voice recording · Location at the start of the trip home · Transmission time

  5. 05

    Arriving home

    “Mom, I’m home safely!”

    Once home, the child leaves one last reassuring update.

    What a parent receivesHome arrival confirmed

    Voice recording · Home arrival location · Transmission time

Everyday reassurance for children and parents

An update can arrive,
even when a call cannot fit.

Fun and easy for children

No contact search or phone conversation. Just press and say a few words—an experience designed to make checking in feel effortless.

A voice and location for parents

When parents cannot answer a call, they can listen to the delivered recording and see where the child sent it.

Key moments in one timeline

Review school arrival, the trip to the academy, academy arrival and the journey home in time order to understand the day’s movements.

School bullying or violence

A way to ask for help,
when speaking up is difficult

A child is forced into a secluded part of the school and cannot openly call or ask for help. In this scenario, they discreetly press Smart TagBell to alert a teacher or parent registered in advance.

  1. 01 · The child signals danger

    Press discreetly

    The child requests help without taking out a phone or making a call in front of the other person. Quiet operation and accidental-activation prevention must be validated in the actual device and app design.

  2. 02 · A teacher or parent is alerted

    Review audio and location

    The connected smartphone app sends captured on-site audio, location and the alert time to registered recipients. They review the information and arrange help to get the child to safety.

  3. 03 · Review what happened afterward

    Use the records to explain the incident

    Audio, location and time records may help explain a school bullying or violence incident and support a later review of the facts. The service design should preserve original records together with their timestamps.

The priority is the child’s safety and prompt assistance. Actual capture and delivery depend on smartphone connectivity and permissions. Records alone do not guarantee proof of school violence or acceptance as evidence.

One alert.
The right response for the situation.

Explore the roles of a traveler, security officer, field technician and responder. No real recording, notification, emergency report or location transmission occurs.

The rental company clips TagBell onto the edge of the driver’s Sunshade while it stays folded up against the ceiling with a PRESS IN EMERGENCY notice. After an accident, the driver presses the button from inside the car and describes the situation and help needed. Explore sharing the accident location and recorded request with the company’s designated response contact. Changing the scenario resets the experience.

An East Asian man in his forties requesting help by pressing a clip-on TagBell attached to the closed, stowed Sunshade in a stopped rental car after a minor accident near an overseas airport
Overseas travel · rental car accidentAI-generated illustration. Device appearance is illustrative.
Who receives it

Rental company’s preselected accident response contact, then the next designated contact if unanswered

What is shared

Accident alert · accident location · driver’s recorded request

If nobody responds

Pass the request to the next preselected contact

Ready to explorePress TagBell below to begin

Rental car driver

Overseas road · example accident location

Start an alert when you need assistance.

Designated response contact

Your choice determines the next step.

Respond here when a request arrives.

Activity log

Start a request to see the steps you choose.

The demo advances only when you press a button. All locations and messages are examples. A real service needs device and app integration, pre-registered contacts, recording and location permissions, sharing consent and local response arrangements. This page does not request microphone or location access, record, transmit or translate.

Beyond an alert.
A pathway to response.

Signal that you need help without taking out your phone.

In a threatening situation, using a phone may expose it to being taken or damaged. Smart TagBell is designed around a simple idea: press a button to alert people selected in advance, without searching for a contact or navigating a screen.

If the first recipient does not respond, the request can move through backup channels and a registered network. Actual transmission depends on the device’s communication design and connection status.

Different ways to wear it.
One way to call for help.

Three design concepts: a badge, a phone ring and a pendant.

TagBell badge, phone ring and pendant concepts with wearing examples
Click to enlarge. AI-generated appearance concepts, not final product specifications. Any labels within the original illustration are retained.
01 · BADGE

Attach to clothing

A chest-mounted button designed for easy access on clothing or uniforms, including security and field-service roles.

02 · PHONE RING

Attach to your phone

A folding finger ring combined with an alert button. It can be used while holding a phone, but may become inaccessible if the phone is taken.

03 · PENDANT

Wear around your neck

A pendant-style button for travel and everyday use. A breakaway strap and wearing safety need validation during product development.

The form factor does not determine independent connectivity. Dimensions, attachment, battery, communications and activation conditions remain subject to product design and validation.

From pressing the button
to someone taking action.

A service concept connecting a designated recipient with location information and an on-site audio recording.

A child presses her necklace-style Smart TagBell as a suspicious person follows; a designated recipient checks her location and on-site audio; guardians assist the child at the scene
AI-generated scenario illustration. It does not demonstrate or guarantee real transmission, recording or response.
  1. 01

    Child presses the pendant

    When a suspicious person follows her, the child presses the Smart TagBell pendant around her neck to request help from a designated contact.

  2. 02

    Recipient checks location

    The alerted recipient checks where the child is on their smartphone.

  3. 03

    Review the recording

    The recipient listens to shared on-site audio to understand the situation.

  4. 04

    Respond at the scene

    A guardian or designated contact goes to the child or arranges on-site assistance and checks that she is safe.

A real service requires device and app connectivity, registered recipients, location and recording permissions, and sharing consent. This page illustrates the flow and does not record audio or send emergency messages.

A four-step response flow

Conditions and coverage can be configured for each operating environment.

01

Instant alert

Pressing TagBell sends a BLE signal to your connected smartphone. Its app sends a notification to preselected contacts over the network.

02

Backup channel

If no one responds, a messenger backup channel helps reduce the risk of a missed notification.

03

Next designated contact

If unanswered, the app follows the configured order of preselected contacts.

04

Connected response

Recipients review the location and situation, then choose an available response path.

Devices, apps, messaging and monitoring—connected.

The concept combines standard mobile push infrastructure with messenger channels and notification delivery to designated contacts. Control centers, caregiver apps and operating policies can be integrated to suit each partner.

Smart TagBellBLE signal
→
Your phoneApp · network connection
→
Designated contactsHelp request notification

Patented technologies for connected safety

Two Korean patents registered to PASSnet Co., Ltd.

KOREAN PATENT · 10-2491615

Emergency rescue management system for smartphone users

Describes a request device linked to a smartphone that shares emergency signals, location and on-site audio with a control center, supporting CCTV coordination and notifications to responders and guardians.

Emergency requestLocation & audioControl center integration
Application no.
10-2022-0113915
Filed
2022.09.08
Registered
2023.01.18
Patentee
PASSnet Co., Ltd.

KOREAN PATENT · 10-2959613

Smart tag device and intelligent integrated safety management system using the same

Describes trigger-based, time-limited audio collection, inaudible acoustic data transmission as a backup, event-synchronized CCTV clip extraction, and pedestrian–vehicle safety integration.

Time-limited audioBackup communicationCCTV & traffic safety
Application no.
10-2025-0212373
Filed
2025.12.29
Registered
2026.04.27
Patentee
PASSnet Co., Ltd.

Summarized from the supplied patent certificates and specifications. The technologies described are distinct from the demonstrations on this site; product implementation and external integrations require separate development and validation.

On the move. On the job.
Keep the right people informed.

These are service scenarios. Actual recording, location sharing and local response require integration and field validation.

In-car rental vehicle alerts scenario illustration01

In-car rental vehicle alerts

The rental company clips TagBell onto the edge of the driver’s Sunshade while it stays folded up against the ceiling. After an accident, the driver presses it and describes what happened. The accident location and recorded request are shared with the company’s designated response contact.

Retail security teamwork scenario illustration02

Retail security teamwork

Connect a store with its control center and nearby registered security personnel for coordinated support.

Field service & telecom installation scenario illustration03

Field service & telecom installation

Share an emergency at a customer site with a manager and designated colleagues.

Older adults & vulnerable people scenario illustration04

Older adults & vulnerable people

When sudden chest discomfort makes calling difficult, an older adult presses TagBell. The phone lies right beside their hand, but they lack the strength to operate it. A maintained connection and successful audio capture can relay a spoken request for help and location to a preselected hospital or responder. This service concept requires app connectivity, recording permission and prior recipient integration.

Industrial & workplace safety scenario illustration05

Industrial & workplace safety

During an emergency while painting a high-rise exterior, a rope-access worker hangs from secured ropes and a safety harness, gripping a rope to steady themselves. They cannot free their hands to hold and operate a smartphone. They press the TagBell button attached to the side of their helmet to request rescue from the site manager and safety personnel.

Travel & outdoor activities scenario illustration06

Travel & outdoor activities

A hiker slips down a steep slope, drops their phone and falls roughly 10 meters below the trail. They press the TagBell pendant to request rescue. If the BLE connection remains active, the phone left above receives the signal and relays an emergency alert to a designated contact. Terrain, obstacles and device status affect connectivity; any shared position is the phone’s location.

Facilities & local communities scenario illustration07

Facilities & local communities

When a shattered smartphone screen prevents touch operation in an apartment complex or public facility, the user presses TagBell to request help from a preselected building manager or guardian. This scenario assumes only the display or touch input is damaged: phone power, BLE, the app and network connectivity must remain available. A fully failed or disconnected phone cannot relay the alert.

Find a phone while hiking scenario illustration08

Find a phone while hiking

A phone slips away during a hike and becomes hidden among fallen leaves near a tree roughly 15 meters away. In a preconfigured phone-finding mode, pressing TagBell signals the BLE-connected phone to play a locating chime and emit light through its screen or flash. The hiker follows the sound and light, locates the phone and retrieves it. Fifteen meters is a scenario setting, not a guaranteed connection range. Phone power, a running app, BLE connectivity and supported sound/light controls are required.

Build safer services together.

01

Flexible deployment

Adapt response roles and operating rules to homes, care services, industrial sites and facilities.

02

Partner integration

Explore service models with telecom, security, monitoring, insurance and care platforms.

03

Operational insight

Use notification, response and escalation history to evaluate and improve the response process.

Plan for your environment.

Try the response flow here. Real device alerts, app notifications and messenger delivery need separate service integration.

01 · ASSESS

Who will use it, and where?

Identify user numbers, locations, connectivity and the existing monitoring setup.

02 · DESIGN

Who will respond?

Define contacts, waiting times, escalation coverage and the final unanswered-alert procedure.

03 · VALIDATE

Test in real conditions.

Verify device connections, delivery, accidental-alert cancellation and safety confirmation. Cost and timing depend on the agreed scope.

Frequently asked questions

How can it help when reaching for a phone is difficult?

The concept is to send an emergency signal to preselected contacts with one button press, reducing the need to find contacts or operate a phone screen during a threatening situation.

Will it work if my phone is taken or damaged?

TagBell relies on your connected smartphone. The phone must be powered on, within BLE range, and able to run the app and access the network. If these conditions fail, the alert may not be sent.

Does this website send a real emergency alert?

No. The interactive experience runs only on this page. It does not contact emergency services, send notifications, record audio or transmit your location.

What happens if nobody responds?

The demo shows backup messaging and escalation, followed by an unanswered state. A real service needs a separate emergency contact and response procedure. A response or rescue is not guaranteed.

What if I press the button by mistake or cannot respond?

The requester can cancel an alert. Recipients can decline to move the demo to the next stage. Accepted requests close only after arrival and a safety confirmation.

What if connectivity or location permission is unavailable?

Notification delivery and notification delivery to designated contacts may be limited. Deployment planning should include connection indicators, permission guidance, alternative contact methods and unanswered-alert procedures.

How does the rental car installation work?

The rental company clips TagBell onto the edge of the driver’s Sunshade while it stays folded up against the ceiling beside a PRESS IN EMERGENCY notice. From inside the car, the driver presses the button and describes the accident and assistance needed. The accident location and recorded request are sent to the company’s preselected response contact. Local assistance requires partner arrangements. This site does not automatically call emergency services or provide interpreting.

Can recordings and location be shared together?

Yes, in this service concept: press the in-car TagBell and describe the accident. The location and driver’s recorded request are shared together with the rental company’s designated contact. The real service requires in-car hardware, audio capture, location and communication integration, and consent. This demo displays sample text only.

Is emergency information shared with everyone nearby?

No. Travel and field-service scenarios use preselected contacts. Security collaboration uses a registered response network. Each deployment defines who receives information and how widely it is shared.

Smart Tagbell reports

Explore the technology, R&D objectives and commercialization strategy in the 18-page Korean and English reports.

한국어PDF · 18 pages · 10.9 MB

스마트 테그벨 사업·기술 보고서

AI·IoT 기반 휴대형 스마트 안전단말 및 통합관제 플랫폼 개발·사업화

Download Korean PDF
EnglishPDF · 18 pages · 10.8 MB

Smart Tagbell Business & Technology Report

AI·IoT-Based Portable Smart Safety Device and Integrated Monitoring & Control Platform Development & Commercialization

Download English PDF

Shape the next chapter
of connected safety.

Discuss product co-development, field pilots, distribution and service partnerships, or strategic investment.

Co-developmentField pilotsDistributionStrategic investmentEmail us →

boss@passnet.co.kr

Start a partnership inquiry

This form opens your email app with a message to boss@passnet.co.kr. The site does not store your entries. Send the email from your email app to complete your inquiry.

Development & deployment considerations

Location and personal data protection, consent, mobile permissions, messaging costs and fallback response arrangements require planning for the intended country and service environment.