Skip to main content
Open RingCentral in Settings → Integrations and select Connect RingCentral. Presolve checks business-phone and contact-center access after sign-in. If both are available, choose Contact center · RingCX. You can also select it from the RingCentral service setting. This requires a RingCX contact-center subscription. Coordinate configuration with the person who manages your firm’s call system and intake routing.
Have RingEX only? Use the RingCentral RingEX integration. RingEX business phone accounts cannot complete RingCX authorization.
Old RingCX setup links open the shared sign-in screen for a new connection. Existing connections and account-selection steps open directly. Access checks use the signed-in user’s permissions; an authorization failure does not establish which products the firm owns. Changing the service setting opens that service’s setup without migrating or disconnecting an existing connection.

Connect your workspace

  1. Use Connect RingCentral for automatic discovery. For explicit contact-center setup, select Contact center · RingCX in RingCentral service, then choose RingCentral OAuth or Continue with JWT. For JWT, enter the application’s client ID, client secret, and the integration user’s JWT credential, then choose Find RingCX accounts. You do not need to enter a sub-account ID.
  2. Choose your RingCX account from the discovered list. If only one is available, it is already selected.
  3. Review the account’s queues, campaigns, and phone numbers. Shared accounts require at least one queue or campaign belonging to this workspace. Assign phone numbers when you also need to identify calls without a queue or campaign.
  4. Choose Activate workspace connection. Call imports and webhook setup begin after this confirmation. Review webhook status and make a test call before relying on the connection.
Complete setup before the time shown on screen. If it expires, choose Start sign-in again. Changing accounts clears your selections. A permission problem with phone inventory does not prevent you from assigning queues or campaigns you can access. If OAuth is marked not configured, the platform administrator must enable the deployment’s OAuth application. You can use JWT when it is available. This is separate from RingCX permissions: a successful sign-in does not automatically grant access to webhook setup, reports, or recordings.

Review the configuration

Connection methods can vary by environment. If OAuth is unavailable, review the authentication method offered on your setup screen with the integration owner.

See the account’s phone numbers

After connecting, RingCX phone numbers loads the sub-account’s number inventory. Use Refresh numbers to check again. Shared workspaces see only explicitly assigned numbers and numbers routed directly to their assigned queues. Connection owners can select Manage an owned connection to view that sub-account’s full inventory. Saved workspace number assignments remain visible when RingCX cannot return live inventory. They are configuration, not proof of a current provider assignment. This list does not establish which caller IDs an individual agent may use; those permissions remain in RingCX.

Resolve webhook setup permissions

If Set up / retry webhooks reports a permission denial, ask the RingCX administrator for the integration’s connected identity to update its permissions in Users & Permissions. Creating the webhook service group requires CREATE on Account. Setup also needs access to manage the HTTP services and update the selected queues or campaigns. A successful OAuth or JWT sign-in does not establish this access. For managed connections, contact the HQ or firm that owns the connection. Paralegals’ individual agent logins do not need these setup permissions. Retry after access changes, then complete a test call through an assigned queue or campaign to verify delivery. A previous received event does not prove that the current setup works. See RingCX’s service permission guide. Phone inventory has separate read permissions; its error message identifies those when access is denied.

Share a RingCX account across firm workspaces

After signing in, an integration manager can use Share this account across workspaces when assigning each firm’s resources. Assign each workspace its own campaigns, queues, and phone numbers. The same queue, campaign, or number cannot belong to two active workspace integrations. Shared setup requires at least one campaign or queue. Existing connections remain exclusive. To convert one, disconnect it and reconnect with shared mode and explicit assignments before connecting another firm. Disconnect and reconnect to change shared assignments later. Each workspace retains its own resource assignments and case permissions. Sharing a sub-account does not grant access to another workspace’s cases. Select workspace phone numbers in international format, such as +12125551234, from the discovered inventory. Managed connection owners enter permitted numbers when granting resources. They help identify manual calls without queue or campaign information. Configure the agent’s permitted caller IDs in RingCX as well; entering a number here does not grant permission to use it.

Use an HQ-managed or firm-managed connection

When Managed RingCX connections is available, the account owner signs in with OAuth or a dedicated integration user’s JWT, chooses a discovered account, and confirms Save connection. The owner selects each firm’s queues, campaigns, numbers, and agents and grants them to that firm’s workspace ID. A manager in the receiving workspace chooses Use in this workspace to accept the grant. For a firm-owned account, add the connection in the firm’s workspace and choose Assign to this workspace. The owner retains control of authorization and can rotate it or revoke a workspace’s access. Disconnecting one workspace does not disconnect other firms. Use Check connection capabilities to see which operations are accessible. Authentication, report access, webhook delivery, and recordings are separate checks. A successful sign-in does not mean every operation is ready. Open Workspace readiness and paralegal setup, load the assignments, and map each active member to their own permitted RingCX agent. The same paralegal may have a separate mapping in each firm they work for. Agents never receive the background integration credential.

Paralegal sign-in

After a manager connects the workspace, open the calling panel and choose Sign in to RingCX. Use your individual agent login. For managed connections, sign in as the assigned agent ID displayed in the calling panel; ask an integration manager to add a missing mapping. Daily agent sign-in does not require completing the organization’s administrative connection flow. Check the workspace name and choose its assigned caller ID in the RingCX dialer. Finish an active call and save notes before switching workspaces. RingCX manages your agent permissions and phone controls; Presolve verifies provider call information before attaching activity. If a call belongs to another workspace, it cannot be attached to the case currently open here. For managed connections, Waiting for RingCX to verify this call means the provider’s call record has not arrived yet. Keep the panel open: Presolve retains the call activity and notes and checks automatically for up to two minutes. If checks pause, use Check verification now after call sync, or ask your integration manager to check imports. You can save notes separately when a call entry is already present. Closing the panel’s calling session stops verification retries; workspace switching stays blocked while verification is pending. Each call has its own notes draft and case selection, including calls waiting for verification. You can type notes while waiting; Save call notes becomes available when that call has a record. Use New call to choose the case, contact, and number for your next outbound call. Use Notes for call to return to an earlier draft; reviewing or editing that draft does not change the new-call form. A verification retry will not replace the draft you are viewing. Save all drafts before switching workspaces; closing the calling session discards unsaved drafts only after confirmation. Shared-account recording import remains disabled until provider verification is complete. It requires report segments with verified queue or campaign information; the standard v1 report cannot supply that ownership evidence, and shared inbound v2 reports are also excluded until a verified queue source is available. Full-call recordings are excluded because a transferred call may include another firm. Calls whose workspace cannot be established are not imported into a firm’s review queue. Give the integration manager the call time and queue/number details to investigate missing activity.

Distinguish saving from sending a lead

Case intake can offer Save and Save & Send to RingCentral. A matter can also expose Send to RingCentral. Review the intended destination and automatic-sending configuration before using a send action. Saving an intake, routing a lead, and importing a later call are separate results. Check the relevant case and provider activity when verifying each step.

Review imported activity

Open Records → Calls on the intended matter. Check the call participants, time, and available recording details. If an expected call is missing, inspect filters and give the integration owner a specific example, including campaign or queue context when known. Managers can review the latest imported, skipped, and failed counts in settings. Recover missed reports can replay up to seven days within the workspace’s current resource assignment, without duplicating existing calls. Unknown ownership remains excluded. After configuration, verify the intended lead-routing and call-import results separately. A setup change alone does not confirm either outcome.
RingCX account and import controls, including automatic lead sending and recording options.

RingCX account and import controls, including automatic lead sending and recording options.

Related: Integration overview.