Phone integration guide

Connect and use RingCentral

Use your practice’s existing RingCentral account for supported calling, call records and voicemail in SoapBox.

Your practice needs the phone integration enabled and an authorized connection to its existing provider account. Connecting does not purchase phone service or change your SoapBox role. Screenshots show the actual staging app with synthetic training records; your practice, names and connection status will differ.

Download the complete phone guide (PDF)

Before you start

  • A SoapBox practice administrator must choose the intended practice and have phone integration enabled. Phone & VOIP settings and the web Call Log currently require administrator access.
  • Have an existing compatible RingCentral/RingEX account, an authorized user/extension and the required calling service and permissions. Your provider administrator may need to approve the integration.
  • Know which phone RingCentral is allowed to ring for your extension. Sign in to that phone/client and test its microphone and speaker.
  • Confirm approved patient use, communication consent and applicable agreements. Manage ringing, queues, forwarding, business hours and voicemail in RingCentral.

Add the connection

  1. Sign in to SoapBox, complete security verification and choose the practice. New users can create an account from that page and complete practice setup first.
  2. Open Phone & VOIP settings. If the link sent you to sign-in, choose your practice and open this settings link again.
  3. Choose Connect in the RingCentral card. Complete any fresh SoapBox security check, allow the authorization popup and sign in to the intended RingCentral account.
  4. Review and approve the permissions for the intended account. You do not need to create a developer application or provide a client secret or JWT.
  5. Return to the original SoapBox tab. Wait for the connection to become Ready; an in-progress setup is not a completed connection. If necessary, reload the original settings page and inspect its status before repeating authorization.
  6. Configure the supported Call routing mappings and verify incoming calls, outgoing calls and voicemail with approved test endpoints. Mapping an extension in SoapBox does not change RingCentral’s own call routing.
RingCentral provider card showing Ready and Disconnect in the actual SoapBox phone settings
Actual staging settings with a ready RingCentral connection. Your practice and account identifier will differ. The relevant controls are framed for readability; select the image for the complete original capture.

One voice provider is selected per practice. Managed RingCentral connections do not provide an embedded browser dialer. Carrier-branded services such as Office@Hand are not established as supported by this guide.

Place a patient call

  1. Open the intended patient chart, verify the saved number and choose Call.
  2. Enter Phone to ring first, including + and country code. It must be an endpoint allowed for your RingCentral extension.
  3. Choose Start call. RingCentral rings your chosen phone first; answer it to continue to the patient.
  4. Watch your phone/client for the call. “Call requested” confirms the request, not that the patient answered. If the result is uncertain, inspect RingCentral before trying again.
Patient call dialog with the Phone to ring first field and Start call button
Actual staging call dialog. Opening this example did not place a call. The relevant controls are framed for readability; select the image for the complete original capture.

Answer inbound calls using your configured RingCentral phone/client. SoapBox’s caller card helps identify and file the conversation; it does not replace your provider’s phone controls. Use the shared call and voicemail guide for parents, shared numbers and patient filing.

Troubleshoot or reconnect

  • No Ready status: inspect the exact setup error and confirm the intended account and required permissions. If cleanup needs administrator review, contact support rather than repeatedly connecting.
  • Your phone does not ring first: check the full callback number and whether RingCentral permits that endpoint for the extension.
  • Answered elsewhere: inspect the other RingCentral devices before placing another call.
  • Silent microphone: verify the operating system’s input, the selected device and microphone permission in the RingCentral client/browser, then run its microphone test.
  • No caller card or missing voicemail: verify the Ready connection, authorized extension, staff mapping and screen-pop preferences. Your provider account may not expose every user’s calls or voicemail.
  • Duration is blank: completed records can arrive later. RingCentral’s duration is its call-record duration, not guaranteed pure talk time or a sum of transfer legs; some records remain unknown.
  • Needs reconnect: use the supported Connect/reconnect action with the authorized account and verify status. Keep passwords, MFA codes and tokens out of support email.

Disconnect and remove access

  1. Choose the correct practice, open Phone & VOIP settings and choose Disconnect on RingCentral. Read and confirm the action, then verify the selected voice connection is removed.
  2. Review any displayed provider-cleanup status. Removal from SoapBox does not itself confirm that every RingCentral resource or independent login has been removed.
  3. To revoke the app’s RingCentral authorization as well, use your RingCentral account’s connected-app management or ask its account administrator to revoke SoapBox’s access. Review any separately connected services before doing so.

Previously imported SoapBox call records, transcripts and patient links are not deleted by Disconnect; existing access and retention policies still apply. Provider-held records are managed in RingCentral. Follow the Privacy Policy for SoapBox data requests. Texting uses separate connection purposes when enabled; voice Disconnect is not a blanket cancellation of every messaging authorization.