What you see when a phone goes dark
The member's pin stays exactly where it was last confirmed, grayed slightly, with two crucial facts attached: the timestamp of the last fix and a status badge — 'Offline', 'Phone off' or 'Sharing paused'. 'Maya — last seen Westfield Mall, 4:40 PM, phone likely dead' is a completely different emotional experience from a vanished dot.
In practice, the last known location plus a recent timestamp resolves the overwhelming majority of 'where are they?!' moments. The phone died at the mall; she's at the mall.
How the app tells the difference
FamilyTracking distinguishes the ways a phone can go quiet. A graceful shutdown (low battery, powered off) lets the app send a final 'going dark' beacon with the closing position. A sudden loss of signal — tunnels, basements, dead zones — shows as 'No signal' once the connection times out. A member pausing their own sharing shows honestly as 'Sharing paused'.
Those labels matter: 'phone off since 4:40' suggests a dead battery; 'no signal for 5 minutes' suggests a parking garage. The app gives you the evidence instead of one ambiguous gray dot.
Back-fill: the timeline catches up
Phones out of coverage but still powered keep recording locally. The moment connectivity returns, those queued points upload and the timeline back-fills — so a hike through a no-signal valley appears in location history as a complete route, just delivered late.
Live viewers see the jump too: the pin snaps from last-known to current, the freshness stamp resets, and an optional 'back online' notification tells subscribed members the gap has closed.
Pairing with battery alerts
The best way to handle dead phones is to prevent the mystery before it starts. Battery alerts warn the Circle when a member's phone drops below a threshold, so 'phone died at the mall' arrives as a forecast — 'Maya's phone is at 15%' — rather than a surprise. Together, the two features mean a flat battery is an errand, not an incident.
When last-known saves the day
- The concert dead-zone. Stadium networks collapse; the pin holding at the venue with a 9:55 PM stamp is all the reassurance needed.
- The subway commute. Underground means offline; the entry station and timestamp tell you which train they're on.
- The teenage battery. Phones die daily at 15. Last-known plus the battery alert that preceded it keeps everyone calm.
- The hiking trail. Out of coverage all afternoon, the full route appears in history the moment they crest the ridge.
- Genuine emergencies. If something is truly wrong, the last confirmed point and time is exactly what responders ask for first.
Stronger together: pairings worth enabling
No FamilyTracking feature lives alone — this one gets noticeably better next to the right neighbors:
- Battery monitoring. The 15% warning an hour before the phone died turns a frozen pin from a mystery into a footnote — enable both and the panic never starts.
- Location history. Back-filled points from offline stretches complete the day's timeline automatically once the phone reconnects.
- Check-in requests. When a pin has been offline a while, a queued check-in request greets the phone the moment it wakes — the gentlest possible 'you OK?'.
The bottom line
This is the feature you never configure and one day deeply appreciate. Its entire job is honesty under failure: when the network, the battery or a teenager's charging discipline gives out, the map degrades gracefully into 'here's what I knew and when I knew it' instead of a blank that breeds panic. There's nothing to buy and nothing to enable — just check, the first time a pin grays out, that you read the timestamp before the worry starts. Paired with battery alerts, it converts the single most common family-tracking scare into a non-event.