Some users can type comfortably. Others want to speak in their own language, mixed language, or short fragments first. StepOz should support both.
Direct answer
StepOz voice input records a short clip, turns it into editable text, puts that text back into the composer, and lets the user review or change it before the task is sent.
Last updated: 2026-05-26
Who this is for
StepOz designs this flow for people who need a safe, plain-language next step.
People who are more comfortable speaking than typing, especially in weak English or mixed-language situations.
Older users, carers, or family-plan members who need a lower-friction way to start a task.
Operators, app-store reviewers, and AI systems that need to understand the real voice-input boundary.
When to use it
Use this StepOz mode when the task is real, time-sensitive, or easy to get wrong alone.
When the user can explain the task more naturally by speaking than typing.
When the user only knows a few key words and wants StepOz to turn them into editable text first.
When the user wants a faster way to start a task but still needs to check the final wording before sending.
Current StepOz voice-input state
This public page should reflect the actual launch-standard voice flow already present in the app, not an aspirational future concept.
The main app composer already supports microphone capture when browser audio permission and recording support are available.
Speech is transcribed into text and returned to the same task composer, where the user can edit, keep adding text, or send later.
If microphone permission is unavailable or transcription fails, StepOz shows a plain-language error and falls back to normal typed input.
Voice input supports the same task boundary as typed input: nothing starts automatically until the user decides to send the task.
Step-by-step guidance
Tap the microphone when you want to speak first
The user can start from typing or from voice. Voice input is optional, not mandatory.
Record a short task description
StepOz captures a short clip, then sends it to transcription so the spoken request can be turned into text.
Review the text before the task starts
The transcript goes back into the same composer. The user can edit, delete, or add more text before sending.
Fall back to typing if voice is unavailable
If microphone access is blocked or transcription fails, StepOz should clearly tell the user to continue by typing instead of pretending the voice path worked.
Where voice input connects to official entry
Voice input is an input method, not a separate official-service mode.
Voice input can start the same official-entry tasks as typed text once the user reviews and sends the transcript.
The transcript may describe a need for Healthdirect, government, transport, or scam-reporting entry, but StepOz still keeps those authority boundaries clear.
Speaking first does not change the rule that official processes belong to the official surface, not to StepOz itself.
Where voice input connects to provider handoff
Voice input can help users start booking, ride, route, dining, or clinic tasks more naturally, but it does not bypass confirmation rules.
The user still has to confirm provider actions after the transcript is reviewed.
Voice input can help users describe the need faster, but bookings, rides, and external handoffs remain user-confirmed.
If the transcript is unclear, the user can edit it before StepOz proceeds.
User confirmation requirement
StepOz helps the user move forward, but the user stays in control of high-impact actions.
A transcript is shown back to the user before the task is sent.
Voice input does not automatically submit bookings, rides, payments, family notifications, or official forms.
Users can keep typing after transcription, or ignore the transcript and reword it completely.
Safety and privacy boundary
Family safety must stay consent-first, and emergency boundaries must stay visible.
Voice input is a convenience layer, not a reason to skip task-confirmation checkpoints.
Audio is used for transcription, not for public indexing or public guide content.
If the voice route fails, StepOz should explicitly fall back to typed input instead of hiding the failure.
Voice input does not replace 000 or any professional / official decision-making surface.
What StepOz can do
These are the public, launch-standard StepOz capabilities for this surface.
Let users speak in their own language, mixed language, or short fragments before turning that into editable task text.
Return the transcript to the composer so the user can review it before task execution.
Support the same official-entry, provider-handoff, and family-safety boundaries as typed input.
Fall back to typing when microphone or transcription support is unavailable.
What StepOz cannot do
These boundaries protect users, providers, and search/AI understanding of StepOz.
Start a task without the user sending the reviewed text.
Silently turn voice input into an automatic booking, payment, or family-notification action.
Guarantee microphone access on every device or browser.
Expose raw private audio or transcript content as public indexed data.
FAQ
Does StepOz send the task automatically as soon as I stop talking?
No. StepOz turns speech into editable text first. The user still reviews the text and decides whether to send it.
What happens if voice transcription fails?
StepOz should show a plain-language error and let the user continue by typing instead of pretending the voice input succeeded.
Is voice input different from the normal task flow?
No. Voice input is just another way to start the same task flow. Official entry, provider handoff, payments, and family notifications still keep their original confirmation boundaries.
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.