Your call.
A clear picture.

Your RingCentral connection

Each person signs in and authorizes their own RingCentral account. The service stores encrypted access and refresh tokens linked to their workspace identity, so they can reconnect without signing in for every call. RingCentral handles the phone service.

Audio and menu text

While automatic navigation is listening, audio from the other side of the call is sent to Deepgram for transcription. Call Navigator uses that text to select an announced keypad option. The main Deepgram API key stays on the server.

Take over stops automatic listening and keypad entry. The phone call can continue through RingCentral. If you resume the navigator, audio processing starts again for a fresh menu.

What this app stores

Call Navigator does not save raw call audio or menu transcripts to its database. The activity feed is kept in the page during the current session and clears when the page reloads. The server stores the encrypted connection, temporary authorization state, and request-limit counters.

This describes Call Navigator’s own storage. RingCentral and Deepgram have their own processing and retention policies. The transcription connection requests Deepgram’s model-improvement opt-out; that does not mean all provider logs are disabled.

Disconnecting your line

Open Connection setup in the workspace and choose Disconnect RingCentral. The app removes its stored connection and requests token revocation from RingCentral. You can also manage app authorization directly in RingCentral.

Using the pilot with other people

Only approved workspace users can access this private pilot. The current RingCentral app supports the configured organization. Before using customer call audio, your organization should confirm its intended use and give callers any required notices. Broader availability is pending live testing and additional service controls.