Who can use this
- Desktop users preparing for important calls.
- Admins and operators setting rollout expectations.
Before you start
- Confirm Desktop access, sign-in, permissions, and network connectivity.
- Use a supported Mac device and the approved Ergo Desktop download path.
- Run a test recording on the same machine and meeting setup you plan to use.
- Close unnecessary resource-heavy apps before recording, especially during screen sharing.
- Avoid running multiple notetaker sources unless your team has tested dedupe behavior.
Requirements and limits
- Desktop download access is feature-gated.
- Desktop recordings require a successful upload session and backend processing.
- The backend rate-limits successful desktop upload creation to protect the service.
- Live transcript depends on temporary transcription credentials, audio capture, and network availability.
- Very short or incomplete recordings may be skipped instead of becoming normal processed meetings.
What to expect
- Local recording can be more private than a cloud bot because no bot joins the call, but it depends more heavily on the user’s machine, permissions, and network.
- Processing state can move through recording, uploading, processing, completed, failed, or skipped.
- Failed desktop recordings may be retryable only when the required upload and recording identifiers are present.
Common issues
- CPU, memory, screen-sharing, audio-device, or network pressure affects capture quality.
- Upload succeeds but processing later fails.
- The recording is too short to produce useful transcript or meeting output.
- Another notetaker source produced a duplicate meeting.