Connecting RingCentral to PolicyTek
Connect your RingCentral phone system to PolicyTek for click-to-dial, automatic call logging, and live agent presence — set up in 10 to 15 minutes.
- What this gets you
- What you''ll need
- The three steps
- –1. Create a JWT-auth app in the RingCentral Developer Console
- –2. Create a JWT credential
- –3. Paste into PolicyTek
- Common gotchas
- –"invalid_client" error
- –"invalid JWT" error
- –Click-to-dial does nothing
- –Calls log on the wrong agent
- Full step-by-step walkthrough
- Need help?
What this gets you
Connecting RingCentral to PolicyTek unlocks three things across the CRM:
- Click-to-dial — every phone number in PolicyTek becomes a one-click outbound call.
- Automatic call logging — inbound and outbound calls land in the lead''s activity timeline within ~30 seconds of ending.
- Live presence — agency dashboards show which agents are on a call vs available, pulled straight from RingCentral.
What you''ll need
- Admin access on the RingCentral account (you need permission to create developer apps).
- Admin access on the PolicyTek account so you can reach Agency Settings → Integration → RingCentral.
- About 10 to 15 minutes the first time through. You won''t need to come back — RingCentral JWTs don''t expire.
The three steps
1. Create a JWT-auth app in the RingCentral Developer Console
Go to developers.ringcentral.com and sign in with your normal RingCentral credentials. Click Apps → Create App, choose REST API App, and on the Auth section switch from the default OAuth to JWT auth flow. This is the single most important setting on the page — without it the rest won''t work.
Select these permissions on the app:
ReadAccountsandRingOut— required.ReadCallLog,SubscriptionWebhook,ReadPresence— strongly recommended.ReadMessages— only if you want SMS or voicemail to sync.
Save. RingCentral drops you on the app''s overview page, where the Credentials tab holds the Client ID (about 22 characters) and Client Secret (behind a Show button — treat it like a password).
2. Create a JWT credential
JWTs live separately from apps in RingCentral. In the top-right of the Developer Console, click your name and choose Credentials → Create JWT. Label it something like PolicyTek — Production, select Production for the environment, and under App access choose "Only specific apps of my choice" — then paste the Client ID from step 1 to bind the JWT to that one app.
Click Create. The JWT string is shown once, and it''s long (400+ characters). Click Copy immediately — if you close the dialog without copying you''ll have to delete the credential and start over.
3. Paste into PolicyTek
Go to Admin Dashboard → Agency Settings → Integration → RingCentral and paste in:
- Client ID from step 1
- Client Secret from step 1
- JWT from step 2
Tick the Active Ring Central? checkbox and click Save. Within a minute or two the integration is live. Click any phone number in PolicyTek to test — your RingCentral desk phone or app should ring.
Common gotchas
"invalid_client" error
Client ID or Client Secret has a trailing space, or you copied from the Sandbox environment instead of Production. Re-copy both and re-paste.
"invalid JWT" error
Either the JWT got truncated when copying (these are very long strings), or the JWT was bound to a different Client ID than the one in PolicyTek. Delete the credential and create a fresh one bound to the right Client ID.
Click-to-dial does nothing
Make sure Active Ring Central? is checked and that RingOut is in your RingCentral app permissions.
Calls log on the wrong agent
PolicyTek matches RingCentral users to PolicyTek agents by email address. Make sure each agent''s PolicyTek email exactly matches their RingCentral email — an alias or extra dot breaks the match.
Full step-by-step walkthrough
For the screenshot-level detail (every menu, every button, every form field), see the standalone setup page at /ringcentral-setup. That''s the link to send to anyone setting this up for the first time.
Need help?
Email contact@policytek.com with your agency name and a screenshot of where you''re stuck. Don''t include the Client Secret or JWT in the email — those go directly into the PolicyTek form.