Instill Lens

Let’s get you back in focus.

Start with the checks below. For account, privacy, or processing issues, include a request ID—but never send a password, access token, or raw recording by email.

Quick checks

Sign-in does not complete

  • Allow cookies for lens.instill.ai and auth.lens.instill.ai.
  • Return to the dashboard and start Managed Login again.
  • Confirm your Cognito account email is verified.

An upload is rejected

  • Use M4A/MP4, MP3, WAV, or WebM audio.
  • Request a fresh upload link; presigned links expire.
  • Keep the upload key returned by the API unchanged.

Analysis is delayed or failed

  • Keep the app online long enough to finish the direct upload.
  • Check the meeting again after processing has had time to complete.
  • Use Retry once for a failed meeting; repeated retries will not improve a bad or silent recording.

Contact support

Email help@instill.ai with:

  • the account email address (not authentication credentials);
  • the approximate date/time and affected meeting ID;
  • the request ID from the API response or x-request-id header; and
  • a short description of what you expected and what happened.

Do not attach meeting audio, voiceprints, transcripts, access tokens, or passwords. Support will request a secure transfer only if necessary.

Privacy and deletion

Delete individual meetings in the app. For account deletion or a data rights request, visit Privacy choices or contact help@instill.ai. Account deletion safely queues removal from Cognito, S3, and the application database.

Service health

Automated systems can verify the public API health endpoint. A healthy web response does not guarantee that a third-party transcription or model provider is available.