Agency owners or admins connecting their RingCentral phone system to PolicyTek for click-to-dial, call logging, and presence syncing. You’ll need admin access on the RingCentral account (so you can create a developer app) and on the PolicyTek account (so you can reach Agency Settings › Integration › RingCentral). Plan on 10–15 minutes the first time through.
What you’ll be doing
PolicyTek uses RingCentral’s JWT authentication flow. That means three values from the RingCentral side — Client ID, Client Secret, and a JWT credential — get pasted into PolicyTek. You create those values yourself in the RingCentral Developer Console, then paste them into PolicyTek and check the Active Ring Central box. RingCentral keeps the JWT alive indefinitely (it doesn’t expire like an OAuth token), so once you finish you don’t have to come back unless someone leaves the company or you rotate credentials.
1. Open the RingCentral Developer Console
Sign in at developers.ringcentral.com
Go to developers.ringcentral.com/login.html and sign in with the same credentials you use for your normal RingCentral account. The Developer Console uses the same login — there’s nothing separate to sign up for.
If you see a “Sign up” prompt instead, double-check you’re entering your existing RingCentral email. Service accounts may need to log in through your company’s SSO portal first.
2. Create a JWT-auth app
Click Apps in the sidebar, then Create App
In the left-hand nav, click Apps, then the Create App button in the top-right of the listing page.
Choose "REST API App" and click Next
RingCentral will ask what kind of app you’re building. Pick REST API App — that’s the option that lets PolicyTek call RingCentral on your behalf. Click Next.
Fill in the app details
Use whatever name helps you find it later:
- App Name: something like
PolicyTek Integration - Organization name: your agency name
- Description: “Connects RingCentral to the PolicyTek CRM”
These are internal — they only appear inside your RingCentral account.
Under "Auth", select "JWT auth flow"
This is the most important step on this page. RingCentral defaults to OAuth — switch it to JWT auth flow so PolicyTek can authenticate without bouncing your users through a browser login every time.
Select the permissions PolicyTek needs
Scroll to the App permissions (sometimes labeled Scopes) section and check the boxes below. These are the minimum needed for click-to-dial, call logging, and presence:
ReadAccounts— read basic info about your RingCentral account and usersReadCallLog— pull call history into PolicyTekReadPresence— see which agents are on a call vs availableRingOut— place outbound calls from PolicyTek’s click-to-dialSubscriptionWebhook— receive real-time call events (incoming call, call ended)ReadMessages— only if you want SMS or voicemail to sync into PolicyTek
If you’re not sure, err on the side of selecting all six. You can’t do harm — permissions you don’t use just sit there unused.
Save the app
Click Create (or Save, depending on which screen you’re on) at the bottom of the form. RingCentral will drop you onto the app’s overview page.
3. Grab the Client ID and Client Secret
Open the "Credentials" tab on your app page
On the app’s overview page, look for a tab or sub-section labeled Credentials — depending on the console version it may also be called Keys or sit under App Settings.
Copy the Client ID
The Client ID is a string roughly 22 characters long. Click the copy icon next to it and paste it directly into the Client ID field on PolicyTek (you’ll do that in section 5).
Reveal and copy the Client Secret
The Client Secret is hidden behind a Show button (or an eye icon). Click it, then copy the value. Treat this like a password — don’t paste it into chat, email, or anywhere outside the PolicyTek form.
If you ever expose this, click Reset Client Secret on the same screen and re-paste the new value into PolicyTek.
4. Create a JWT credential
Open Credentials from the user menu (top-right)
In the upper-right corner of the Developer Console, click your name or avatar. A dropdown appears — select Credentials.
Direct link: developers.ringcentral.com/my-credentials.html
Click "Create JWT"
Top of the Credentials page. The button opens a form.
Fill in the JWT form
- Label: something like
PolicyTek — Productionso you can identify it later - Environment: Production (the default; Sandbox is only for testing)
- App access: select “Only specific apps of my choice”, then paste the Client ID from step 9 and click Add app. The app you created in section 2 should appear in the table below.
Locking the JWT to a specific app is best practice — even if the JWT ever leaks, it’s useless without your Client Secret.
Click Create — then copy the JWT immediately
RingCentral displays the JWT string once. There’s a Copy button (and usually a Download option). Click Copy.
If you close the dialog without copying it, you’ll need to delete the credential and create a new one — RingCentral cannot show you the same JWT again.
5. Paste into PolicyTek
Open the RingCentral settings in PolicyTek
In a new tab, sign in to your PolicyTek admin account and go to:
Admin Dashboard › Agency Settings › Integration › RingCentral
Paste in the three values
- Client ID — from step 9
- Client Secret — from step 10
- JWT — from step 14
All three fields are required. Don’t add any extra spaces or quotes — paste the raw values exactly as RingCentral gave them.
Tick "Active Ring Central?" and click Save
The checkbox tells PolicyTek to actually use the credentials. If you save without checking it, the values are stored but the integration stays off.
After saving you should see a confirmation. From here, click-to-dial, call logs, and presence will start flowing within a minute or two.
6. Verify it’s working
Pick any lead in your CRM and click their phone number. Your RingCentral desk phone or app should ring — pick it up to call the lead. After the call ends, the entry should appear in the lead’s activity log within ~30 seconds.
If nothing happens, jump to section 8 below.
7. Permissions cheat-sheet
A quick reference for what each scope unlocks. If something in PolicyTek says “permission denied”, edit your app in the RingCentral console, add the missing scope, and save.
| Scope | Required? | What it unlocks in PolicyTek |
|---|---|---|
ReadAccounts | Required | Reads your RingCentral users so PolicyTek can map them to PolicyTek agents. |
RingOut | Required | Click-to-dial. Without this, the phone-number links in PolicyTek do nothing. |
ReadCallLog | Recommended | Pulls call history into each lead’s activity timeline. |
SubscriptionWebhook | Recommended | Real-time call events — PolicyTek pops the lead screen the moment a call connects. |
ReadPresence | Recommended | Shows which agents are on a call vs available on the agency dashboard. |
ReadMessages | Optional | Syncs inbound SMS and voicemail into the lead timeline. |
8. Troubleshooting
“Invalid client credentials” / “invalid_client”
The Client ID or Client Secret is wrong, has a trailing space, or was for a different app. Re-copy both from the RingCentral console and paste them in again. Make sure you copied the values out of the Production environment, not Sandbox.
“Invalid JWT” / “Unauthorized”
Either the JWT was truncated when copying (these strings are long — 400+ characters), or the JWT was created for a different Client ID than the one you pasted in. Delete the credential in the RingCentral console, create a fresh one bound to the right Client ID, and re-paste.
“Permission denied” on a specific feature
You’re missing a scope on the RingCentral app. Open Apps › your app › App permissions, add the scope from section 7 above, and save. PolicyTek picks up new permissions on the next event — no need to re-paste anything.
Click-to-dial does nothing
Confirm the Active Ring Central? box is checked on PolicyTek (section 5, step 17), and that RingOut is included in your app permissions. If both are correct, sign out and back into your RingCentral phone or desktop app to refresh the session.
Calls log on the wrong agent
PolicyTek matches RingCentral users to PolicyTek agents by email address. Make sure each agent’s PolicyTek email matches their RingCentral email exactly — an extra dot or alias breaks the match.
9. Need help?
Email contact@policytek.com with your agency name and a screenshot of where you’re stuck (never include the Client Secret or JWT in the email — if you need to share them, do it through the PolicyTek admin form). We’ll usually have you running same day.
For deeper detail straight from RingCentral, see the official JWT Authentication guide.