Open Relay

Support

Recover safely and keep moving.

Start with the recovery path for the affected part of Relay. Keep the request ID visible, and never share credentials or private call evidence through an unverified channel.

Guidance updated July 19, 2026

01

Sign-in or account problem

Return to Sign in and complete any pending Google or email verification in the same browser. Once signed in, use Account security to manage email addresses, connected accounts, passwords, and sessions. Your Relay display name and work preferences are managed separately in Profile.

02

Request is missing or cannot open

Open the Dashboard and choose the request shown there instead of reusing an old demo bookmark. If the request still fails, keep its current request ID and the approximate time of the error. Do not create repeated calling runs while the original status is uncertain.

03

Voice interview or provider error

Confirm that microphone access is allowed for Relay, then retry once from the current brief. If a live business-calling run has already started, pause or cancel it from the request workspace before troubleshooting. This prevents duplicate outbound calls.

04

Profile, notifications, or privacy

Update Relay-specific information in Profile. Sign-in identity is managed in Account security. Evidence retention, exports, and communication choices are in Settings. Read the privacy notice before sharing any personal information for troubleshooting.

05

What a safe issue report includes

  • The Relay request ID, such as the value shown in the page title.
  • The approximate time and the page where the problem occurred.
  • A screenshot with addresses, phone numbers, and quotes obscured.
  • The recovery step you already tried and what happened next.
Never include secrets.

Do not share your password, one-time code, session cookie, API key, database URL, webhook secret, full transcript, or recording.

Security or privacy concern

Stop active calls, preserve the request ID and time, sign out other sessions from Account security if needed, and notify the verified deployment owner. Do not delete local evidence that may be needed to understand the event.