Reference · built on requestOperator by FibricSafety, security & compliance

Lone Worker

Tracks scheduled check-ins for people working alone and proposes an escalation call or a dispatch when a check-in is missed.

Request accessPricing ↗

About

Lone Worker is an operator job for the person on site with no one nearby to help. It reads which shifts are lone work from Deputy, When I Work, or Connecteam, and the check-in interval you set for each. It counts a check-in when the worker replies to a Twilio text, posts in a Teams or Slack thread, or badges at a reader in Kisi or Brivo. It reads the last badge read and door, so a missed check-in comes with a last known location.

When a check-in is missed, it proposes an escalation call to the worker through Amazon Connect or Twilio, then a call to the supervisor, then a dispatch notice to the guard or nearest colleague. Each step waits for a person to approve it, and every step is timed on the record.

This is a reference listing. It documents what Fibric would read from Lone Worker and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Shifts flagged as lone work: Deputy rosters, When I Work shifts, or Connecteam shifts with a custom field, with start, end, and the worker's phone
  • Check-in replies: inbound SMS through Twilio, replies in a Microsoft Teams or Slack thread, or clock_in and time activity events from Connecteam
  • Badge reads and door names from Kisi or Brivo during the shift, as a last known location
  • Call outcomes from Amazon Connect contact records or Twilio call status: answered, no answer, busy, or failed
  • Who supervises the shift and who is on the guard roster, from the scheduling connector or the operator's configuration

Proposed actions

  • Target capability: propose the check-in prompt to the worker by SMS through Twilio at each interval, with a one-word reply to confirm
  • Target capability: propose an escalation call to the worker through Amazon Connect StartOutboundVoiceContact or a Twilio call, when a check-in is missed
  • Target capability: propose a call or message to the supervisor if the worker does not answer, with the last badge read and door
  • Target capability: propose a dispatch notice to the guard or nearest colleague in Microsoft Teams or Slack, naming the location to check
  • Target capability: propose the incident record for a missed check-in that ended in a dispatch, with every step and time

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Text check-ins for a night engineer

    A Deputy shift marked lone work gets a Twilio text every interval. A missed reply proposes an Amazon Connect call to the engineer, then to the supervisor, with the last Kisi read attached.

    With Deputy, Twilio, Amazon Connect, Kisi

  • Check in from Slack

    A When I Work shift in a remote store uses a Slack thread for check-ins. A missed post proposes a Twilio call and, if unanswered, a dispatch notice to the district manager.

    With When I Work, Slack, Twilio

  • Use Connecteam clock events as presence

    Connecteam clock_in and time activities count as check-ins for field crews. A gap longer than the interval proposes a Teams message to the crew lead and an Amazon Connect call to the worker.

    With Connecteam, Microsoft Teams, Amazon Connect

Requirements

  • One scheduling connector that marks lone-work shifts: Deputy, When I Work, or Connecteam
  • One voice connector for escalation calls: Amazon Connect, with a flow for the outbound call, or Twilio
  • One messaging connector for check-ins and dispatch: Twilio for SMS, and Microsoft Teams or Slack
  • Optional: Kisi or Brivo, so a missed check-in carries a last badge read
Authentication
Reads shifts and badge reads through the scheduling and access connectors, and places calls and messages through the voice and messaging connectors' own credentials; it holds none itself.

Limits

  • It is not a personal alarm or a fall detector. It knows a check-in was missed, not that the worker is hurt
  • It has no location beyond the last badge read. Outdoors, in a vehicle, or on a site without readers, location is what the worker said
  • It does not call emergency services. The supervisor or guard decides that, and the operator records the time they did
  • Escalation timing follows your configuration. A worker whose phone has no signal is escalated whether or not they are fine

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Lone Worker ↗

Questions and answers

What does a supervisor approve during an escalation?
Each escalation step: the call to the worker, the call to the supervisor, and the dispatch. The approver sees the shift, the missed time, the last badge read, and who is next. Check-in prompts themselves run on the schedule you approve once.
What is on the shift timeline?
A timeline per shift: every prompt, every reply, every missed interval, each call with its outcome, who approved each step, and the dispatch. It becomes the incident record if one is needed.
What if the worker cannot reply?
A missed reply is treated as a missed check-in and the escalation runs. A worker who knows they will lose signal can post an expected gap in the thread, which the operator shows to the approver beside the missed interval.
Ask about Lone Worker

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy