> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stackshift.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# Send files and voice notes

> Share useful files and audio while checking that they are safe and ready.

<Note>
  This guide includes features awaiting release. If an option is not available in your workspace, contact StackShift Support.
</Note>

## What you can do

Share useful files and audio while checking that they are safe and ready. Where to find it: The conversation or ticket attachment picker; Voice notes for audio management.

## Before you start

* Access to the conversation or ticket.
* For recording, HTTPS and browser microphone permission.

## Steps

<Steps>
  <Step>
    Choose a file or start a recording from a supported composer. Keep the file relevant to the customer’s request.
  </Step>

  <Step>
    Wait for upload, security scanning and any conversion to finish. Ready means it can be attached; uploaded alone does not.
  </Step>

  <Step>
    Review the selected files and message audience, then send. A reply can contain only attachments where supported.
  </Step>

  <Step>
    For audio, review the recording before sending. After an upload error, retry or explicitly discard it instead of recording another copy immediately.
  </Step>

  <Step>
    In Voice notes, find an authorized recording and inspect its processing or transcription result. Check names, numbers and other important facts before using a transcript.
  </Step>
</Steps>

## Example

Ask for a screenshot of an error, then reply with a short voice note explaining the next step.

## Things to know

* Up to five attachments are allowed per message. Ordinary files and video are limited to 10 MiB; supported audio is limited to 20 MiB and five minutes. Individual messaging providers can impose smaller limits.
* Automatic transcription needs workspace opt-in, a provider and an available transcription allowance. Recording a voice note does not automatically enable transcription.
* Customer portal microphone recording is unavailable. Audio already uploaded through supported flows can still be subject to its access rules.

## What happens next

<Check>
  The customer receives a usable attachment and your team can track any processing failure.
</Check>

## If something goes wrong

<Warning>
  * Microphone blocked: allow microphone access for the site and check that the embedding site permits the messenger to use it.
  * Processing failed: inspect the file error, correct its format or size and retry. Making a file public does not bypass scanning.
  * Transcript missing: check transcription settings and allowance; do not assume silence means no speech.
</Warning>

## Related guides

<CardGroup cols={2}>
  <Card title="Reply, add private notes and work together" href="/stackshift-support/reply-and-collaborate">
    Keep customer replies separate from internal discussion.
  </Card>

  <Card title="Support channels and message recovery" href="/stackshift-support/channel-reliability">
    Connect supported inboxes, preserve message history, and recover interrupted delivery safely.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.