Daily check-ins help families confirm that a loved one is okay without turning every outing into constant manual follow-up.
Direct answer
StepOz daily check-ins are a consent-first reassurance flow: the user sets the check-in expectation, StepOz records the latest response, and only escalates to family or SMS fallback when the configured safety policy says it should.
Last updated: 2026-05-26
Who this is for
StepOz designs this flow for people who need a safe, plain-language next step.
Families who want a predictable check-in rhythm for parents, elderly relatives, or loved ones living in Australia.
Users who want reassurance support while still staying in control of ordinary family updates.
Carers who need a clear difference between normal check-ins, overdue follow-up, and real safety escalation.
When to use it
Use this StepOz mode when the task is real, time-sensitive, or easy to get wrong alone.
When a user goes out alone and wants one lightweight daily reassurance step instead of constant calls.
When a family account needs a clear overdue process instead of informal guessing or repeated manual chasing.
When timeout, missed check-in, or risk events should move into the configured family escalation flow.
Step-by-step guidance
Agree the check-in rule first
The user or household owner sets the daily check-in policy first, including timing, family contact coverage, and what happens when a check-in is missed.
Let the user complete the normal check-in
A normal check-in should stay simple: confirm okay, note the place if relevant, and decide whether this check-in also needs a family notification.
Use overdue follow-up only when the check-in is late or unclear
If the user is delayed, StepOz keeps the follow-up window visible and moves from standby to ask-first or family escalation only according to the configured policy.
Reserve server-side SMS fallback for real safety events
If a check-in is missed, risk escalates, or SOS logic is triggered, StepOz can route the event into the family escalation chain and server-side SMS fallback where configured.
Official entry and emergency boundary
Daily check-ins are a reassurance layer, not a replacement for official emergency response.
Call 000 in Australia for immediate danger or any life-threatening emergency.
Use official health, transport, or government services when the overdue event turns into a real emergency or authority-required action.
Use StepOz to keep the next action clear before deciding whether the event stays ordinary, moves to family escalation, or needs an official channel.
Provider handoff within check-in follow-up
When a normal reassurance flow needs a real task action, StepOz can still move into trusted provider or official surfaces after explicit user confirmation.
If the user is late because they still need transport, StepOz can prepare a ride request through mature provider integrations or approved handoff after explicit user confirmation.
If the user needs health support after the check-in, StepOz can route them to Healthdirect or a provider booking flow after explicit user confirmation.
If the user simply wants to reassure family, the default launch-standard route is still their own SMS or WhatsApp app.
User confirmation requirement
StepOz helps the user move forward, but the user stays in control of high-impact actions.
Users must agree to the daily check-in expectation and who can be notified when a check-in is missed.
High-impact actions such as bookings, transport requests, or provider handoff require explicit user confirmation.
Safety and privacy boundary
Family safety must stay consent-first, and emergency boundaries must stay visible.
Daily check-ins are not a replacement for 000 or emergency services.
Family escalation must stay consent-based and policy-based, not hidden or arbitrary.
Private check-in logs, family contacts, and SMS delivery details must not be publicly indexed or exposed.
Overdue follow-up should stay proportional: normal delay, risk review, and SOS are not the same thing.
What StepOz can do
These are the public, launch-standard StepOz capabilities for this surface.
Support a real daily check-in runtime with latest status, latest timestamp, and family escalation policy.
Show whether the current follow-up stage is standby, ask-first, notify-family-now, or SOS-priority.
Use SMS fallback for safety events where the family safety policy and channel readiness allow it.
Keep the user-initiated normal reassurance path separate from the safety-event escalation path.
What StepOz cannot do
These boundaries protect users, providers, and search/AI understanding of StepOz.
Replace emergency services or official welfare checks.
Silently notify family every time without the configured consent and policy rules.
Guarantee a third party will respond to a missed check-in.
Expose private household safety logs publicly.
FAQ
Does every daily check-in automatically message the family?
No. Ordinary daily check-ins can stay user-initiated. Family escalation is used only when the user chooses it or the configured safety policy says a missed or risky check-in should escalate.
What happens when a daily check-in is overdue?
StepOz keeps the overdue window visible, shows the current escalation stage, and can move into ask-first, notify-family-now, or SMS fallback according to the household safety policy.
Is a daily check-in the same as an emergency alert?
No. A normal check-in, an overdue follow-up, and an SOS-priority event are different safety states. StepOz keeps those states separate so families do not overreact or underreact.
Start with a real task
Use StepOz when the next real-life step matters.
Say it in your own language, or mix your own language with English. StepOz will clarify the task, guide the next step, and keep the safety boundary visible.