Skip to content
Voice carriers

Autocloz + FreJun

FreJun is an India and APAC voice provider that Autocloz connects over OAuth. Each rep can link their own FreJun identity, or an admin can connect FreJun once for the whole team. After that, reps dial leads from the browser using the FreJun softphone SDK, and call events and recordings come back to the lead timeline. It suits teams calling Indian numbers who already use FreJun; see India-first features for the rest of that stack.

Autocloz and FreJun integration
Bring your own accountWorkspace-scoped, no cross-org leakFree-forever CRM core

What you can do with FreJun

FreJun plugs into the Call stack — bring your own carrier account, scoped to your workspace.

OAuth instead of pasted keys

Reps sign in to FreJun in a popup and Autocloz stores the OAuth tokens, refreshing them as they expire. No API secret sits in a form field.

Connect once for the team

An owner or admin can connect FreJun for the whole workspace. Reps without their own link then dial through the admin's FreJun identity.

Recording import

Recording links arrive on FreJun's webhook. When an event arrives without one, Autocloz queues a follow-up fetch so the recording still lands on the call.

How to connect FreJun

Bring your own carrier account — you keep control of the account, the spend and the data boundary.

  1. 1

    Make sure the FreJun app is configured

    The FreJun OAuth client ID and secret are set once by a super-admin for the whole platform. If Connect FreJun is greyed out, that is the missing piece.

  2. 2

    Connect FreJun

    Open Settings → Integrations → Voice → FreJun and click connect. Sign in to FreJun in the popup. Admins can instead connect once for everyone.

  3. 3

    Confirm the account email

    The browser SDK needs the email registered on your FreJun account. It is captured from the OAuth callback when FreJun supplies it; otherwise type it on the card.

  4. 4

    Dial a test call

    Call a number you own from the dialer. If the call dials out with no ring, the account email is usually the cause.

Inbound calls and number assignment

FreJun numbers are added in Voice → Numbers like any other carrier's. A number can be assigned to a rep, and the FreJun card has a default inbound receiver for numbers with no assignee, so an inbound call rings someone instead of going unanswered. Missed-call text-back from the AI receptionist needs an SMS provider as well, since FreJun has no SMS in Autocloz.

Per-rep links versus one team connection

With per-rep OAuth, each rep's calls go out under their own FreJun identity, which keeps FreJun's own reports split by person. With a team connection, every call uses the admin's FreJun identity, so FreJun sees one caller. Autocloz still records which rep placed each call on its side, so the lead timeline and voice reports stay per-rep either way.

An admin can revoke the team connection, and each rep can revoke their own, from the same card.

What FreJun can and cannot do in the dialer

FreJun is marked rep-console-only in Autocloz's carrier list. Preview and power queues work from the rep's browser. Parallel dialing and server-side campaign dispatch are not available, and outbound IVR trees do not run on FreJun because its IVR builder is inbound-only and lives in the FreJun dashboard. Default country is IN, so ten-digit Indian numbers are dialled correctly without a +91 prefix.

Call events post to /api/voice/webhooks/frejun and are checked against an HMAC secret before they are accepted. If you call Indian consumers, read the TCPA and DNC basics Autocloz applies alongside India's own DND rules.

What FreJun does not do in Autocloz

  • No SMS or WhatsApp through FreJun. It is voice only in Autocloz.
  • No parallel dialing and no outbound IVR.
  • A team connection collapses per-rep attribution on FreJun's side, though not in Autocloz.

Troubleshooting FreJun

Calls dial out but never ring.
Type the email registered on your FreJun account into the FreJun account email field and save.
Placing a call returns FREJUN_API_ERROR with status 404.
FreJun's dial endpoint differs by API version. Set Dial endpoint path to the path your FreJun account documents.
The OAuth popup fails on return.
The redirect URI registered in the FreJun console must exactly match the one on the card.

Part of the Call stack

FreJun is one of several carriers you can run behind the Call channel. They share the same dialer, CDR logging, recordings UI and compliance gates.

Explore the Call feature

Related integrations

Frequently asked

Does every rep need a FreJun login?

No. An admin can connect FreJun once for the workspace, and reps without their own link dial through that connection.

Are FreJun calls recorded?

When FreJun records the call, the recording link is stored on the call record. If the first event lacks it, Autocloz fetches it again shortly after.

Run FreJun inside Autocloz

Bring your own account, plug it into the Call channel, and keep a free-forever CRM for 3 users.