**Prerequisites**

- A **Left Main System Administrator** with the **role** of "**Super Admin**" in their **RingCentral** account must complete the following steps prior to having standard users or users with limited permissions complete SMS Provider Configuration.
- Additional users do not require the Super Admin role, but they will need to complete the following steps while logged into their own Left Main and RingCentral accounts.

Access the "SMS Provider Configuration" Page

Type and select **SMS Provider Configuration**

Enter the **username** associated with your **RingCentral account**.

credential

Enter your **password**, and select **Sign In**.

- Enter a name in the **Label** field, such as your company name.
- Select the ***Only specific apps of my choice*** checkbox
- Continue to the next step to capture the required **Client ID** value.

To capture the **Client ID**, right-click on **Console**, and select **Open in a New Tab**.

Select this icon to copy the **Client ID**.

1. Return to the RingCentral **Credentials** page.
2. Paste the **Client ID** into the box outlined below.
3. Click **Add App**.

1. Return to the **SMS Provider Configuration** page in your Left Main org, and paste the **JWT token** in the text field.
2. Click **Submit**

Congratulations! SMS Provider Configuration is complete. \
\
**Attention Left Main/RingCentral admin users**: if configuring the integration for the first time, we recommend following this [Create an Error SMS Report ](https://docs.leftmainrei.co/docs/create-an-error-sms-report)guide to create a report and ensure SMS Cadences for incoming users are working as expected. Otherwise, continue to [Cadences Configuration for RingCentral](https://docs.leftmainrei.co/docs/cadences-configuration-for-ringcentral).\
\
If **new users forget to complete the SMS Provider Configuration**, it could appear as if SMS is being sent when they're not actually getting through.

The *SMS Provider Configuration* page is visible to users with the *Left Main User* permission set.

When Does a RingCentral JWT Token Need to Be Regenerated for a User?

A **RingCentral JWT token** does **not** typically need to be regenerated if a user switches phone numbers as long *as* the following conditions are met:

**The JWT Token is App-Specific, Not User-Specific**

-  *JWT tokens are usually tied to the* \*application credentials\*\* (Client ID/Secret) and **account scope** — not an individual user's phone number.
- If the phone number change is made within the same user profile on RingCentral, the JWT token remains valid.

**When Regeneration *Might* Be Required**

A new JWT token may be necessary **if any of the following occur**:

- The user's RingCentral account is deleted and recreated (creating a new user ID).
- The JWT token was originally scoped to a specific user extension that is now reassigned.
- The token is explicitly configured to reference a phone number or extension that no longer exists.
- The integration logic hardcodes the previous number for routing/mapping.

**Best Practice**

When a user switches numbers:

1. **Check** if their RingCentral user ID and extension remain the same.
2. **Validate** the token by attempting a simple authenticated API call (e.g. get profile or get device).
3. **Update** any internal Salesforce mappings or fields (e.g. CTI softphone configuration) to reflect the new number.

Would you like a short checklist or Salesforce flow recommendations for handling RingCentral number changes?

Salesforce

Ringcentral

Revised May 2, 2025

The steps below apply only to Left Main customers using RingCentral as their preferred phone integration system.

Complete SMS Provider Configuration