Knowledge · Business Operations

    Voice Capture Versus Stored Note Content

    Speaking a note and storing a note are two different things. What happens to the audio, what becomes the record, and why the difference matters.

    Does voice-to-text keep a recording of what I said?

    Not in URBLD. Speaking is an input method: the browser turns speech into text as you talk, and the text is what gets stored. There is no saved audio file, no recording to play back, and no transcript archive — the note in the record is the only artefact that exists.

    Key takeaways

    • Raw audio, transcribed text, edited text and the saved note are four separate things.
    • URBLD stores the saved note only — there is no audio file to retrieve.
    • A dictation feature is not a recording feature, and should never be sold as one.
    • If you need a recording as evidence, a dictated note is not it.
    • Because only text survives, what you review before saving is the whole record.

    Four artefacts people collapse into one

    • Raw audio: the sound in the air, handled by the device as you speak.
    • Transcription: the text the recogniser produced from that sound.
    • Edited text: what the person changed, fixed or deleted before saving.
    • Saved note: the record that exists in the system afterwards.

    Why 'we don't keep the audio' is a feature, not a gap

    Stored audio is a liability with a storage bill attached. It contains background conversation, other customers, family members, and everything said before someone remembered the microphone was on. It has to be retained, secured, searched and eventually deleted under whatever policy you write.

    A dictated note has none of that surface. The person speaks, reads what appeared, fixes it, and saves a sentence. What ends up in the record is what they chose to put there — which is also what makes them accountable for it.

    When you actually need a recording instead

    There are cases where the sound itself is the point: a verbal authorisation you expect to be disputed, a compliance requirement, an incident. A dictation tool does not serve those cases and should not be stretched to cover them.

    For those, the usual answer is a written confirmation the customer acknowledges — an approval in the portal, a signed change order, an email trail — because that is evidence a reader can evaluate without pressing play.

    What this means for how you speak a note

    • Say the numbers out loud — nobody can go back to the audio to check them.
    • Speak in short, complete statements rather than trailing thoughts.
    • Name the customer's words as theirs: 'customer said', not 'they want'.
    • Read the text before you save it. The text is the record, permanently.

    Where URBLD fits

    URBLD's microphone button uses the browser's own speech recognition. The device turns speech into text while the person is talking, the text lands in the field they were already editing, and only the submitted text is stored. There is no audio upload, no stored recording and no playback.

    Principles reinforced

    This page rests on the following foundational ideas.

    FAQ

    Frequently Asked Questions

    Straight answers about how URBLD runs the business end-to-end.

    More in Business Operations

    The daily mechanics: workflows, checklists, scheduling and handoffs.

    Browse Business Operations
    Share this page