Skip to content
Help Center
Submit a request Sign in

Enable RingCentral for agents

Make RingCentral available to the support team, then have each agent authorize their own extension. Account activation and individual connection are separate steps. Use a pilot agent to verify customer context and the intended call workflow before depending on the integration across a B2B service desk.

Applies to: Supportbench Core. Location: Settings → Integrations → RingCentral. Requires Administer all integrations.

Before you begin

  • Identify the RingCentral administrator, the intended individual extensions and the support agents who need the integration. Do not share one person’s provider credentials to bypass individual authorization.
  • Review current Status, Enabled agents and Connected agents, plus Created and Created by. A count difference can identify incomplete agent setup; it is not a reason to disable the whole integration.
  • Plan an approved test call and a customer/case context you may use safely. Provider permissions, sign-in and the agent’s Supportbench record access remain relevant.
  • If removing the integration, coordinate the account-wide interruption first. Active off is a removal operation, not a temporary pause.

Configure and verify

  1. Open Settings → Integrations → RingCentral and review the current account status and agent counts.
  2. To make the integration available, enable Active and choose Save Changes. Reopen the page and confirm the saved account state.
  3. Have the pilot agent open their own profile, then Connect → Connected accounts → RingCentral.
  4. The agent enables Enable for me, chooses Connect RingCentral and authorizes the intended individual extension. Profile connection changes save immediately; there is no shared account Connect button on this settings page.
  5. Choose Check status in the agent’s connection area. Use Open phone when available and complete any RingCentral sign-in requested by that window.
  6. Make the approved test call. Check the intended caller matching and accessible customer/case context, and inspect any expected call association or activity. Do not infer a recording exists merely because a call occurred.
  7. Repeat individual setup for each intended agent. Recheck Enabled agents and Connected agents and resolve incomplete authorizations without repeatedly toggling account availability.

Settings reference

Connection and operating controls

SettingWhat it controlsHow to choose
ActiveEnables the account integration. Turning it off removes the account connection and disables RingCentral for all agents.Review the account-wide impact before switching it off.
Enabled / Connected agentsCounts showing agent setup progress.Use them to identify incomplete individual setup.
Setup guidance and auditExplains agent authorization and shows configuration metadata.Have each intended agent complete their own profile setup.

Behavior to know

  • Turning Active off and saving is removal, not a pause. Confirming Disable RingCentral attempts provider-subscription cleanup for configured agents, then removes this account’s RingCentral agent connections and account settings.
  • Provider cleanup is best-effort. Successful removal from Supportbench does not prove every provider subscription was deleted; coordinate provider-side confirmation when retiring the connection.
  • Re-enabling availability does not restore the removed agent authorizations automatically. Agents must complete their individual setup again.
  • Supported calling, SMS/voicemail events, caller matching and case activities depend on the enabled capabilities and access. Do not promise every call has a recording.

Recommended use

  • Pilot one extension before enabling the team’s operating routine. Check a known caller, an unrecognized caller and the expected accessible case context using approved test data.
  • Keep account administration and individual provider authorization separate. This makes ownership clear when one agent is disconnected while others still work.
  • Before retirement, record the affected agents and coordinate an alternative calling process. After removal, verify both Supportbench state and any relevant provider subscriptions.

Worked example

  1. A service desk starts with one pilot agent’s extension and an approved test caller. The administrator activates the account integration, then the agent authorizes their own extension.
  2. The agent checks status, opens the phone and verifies the intended customer matching and case association. The team records the observed behavior and any capability limits.
  3. The remaining agents connect individually. An agent who is enabled but not connected completes authorization; the administrator does not toggle Active to repair that one profile.
  4. When the team later retires the integration, it coordinates the loss of dialers, confirms Disable RingCentral and verifies the resulting account/profile state and provider cleanup.

Troubleshooting

ProblemWhat to check
Active is on but one agent is not connectedComplete the agent’s own Enable for me and Connect RingCentral flow, then Check status. Account activation does not authorize every extension.
The phone requests sign-inComplete the intended agent’s RingCentral sign-in. Do not replace the account configuration merely because a provider session expired.
A settings-changed message appearsReload the latest account state before making the deliberate change again. Avoid overwriting another administrator’s change.
A save or removal result is unclearInspect account and agent-profile state before repeating it. Provider cleanup or local removal may already have occurred.
Re-enabling did not restore agentsRemoval deletes the stored agent connections. Reauthorize each intended agent; availability alone does not recreate them.
Caller or case context is missingCheck the caller identity, customer association and agent’s record access. An enabled integration does not grant access to otherwise restricted customer data.
  • Integrations → Use the data synchronization log
  • Organization → Configure agent roles and division access

Was this article helpful?