Skip to content
Integration · Voice · JustCall

JustCall calls. Recorded and threaded onto the case.

Connect the JustCall account your practice already runs on and place outbound VOIP calls straight from a client card. Recordings, duration and outcome land on the case timeline as soon as the call ends. Billing stays with JustCall so you keep your existing plan and never pay a markup.

Client · Daniel Nguyen
JustCall connected
Outbound · 07:12Recording ready

Walked through 190 nomination timeline for NSW. Client agreed to lodge Friday.

Play in-line
Missed callVoicemail linked

Voicemail attached to the case with the audio URL. Auto-transcribed if JustCall transcription is enabled on the account.

Beta integration

Live and hardening. Every capability on this page ships today and we are actively improving edge cases based on early customer feedback. Errors are welcome. Email support@immiiq.com and we will turn it around fast.

What the JustCall integration actually does.

Every capability listed below is live in production today. Nothing here is a roadmap promise or a marketing stub.

Click-to-call from a case

Click the client's phone number on the case and JustCall places the outbound call through your connected account. Direction, duration and agent are captured automatically.

Recordings on the timeline

When JustCall's webhook confirms a recording exists, ImmiIQ links the URL onto the case timeline so agents can play it back inline without leaving the client card.

Voicemail and missed calls

Voicemails and missed calls surface on the client timeline the moment JustCall fires the webhook. Auto-transcription flows through when it is enabled on your JustCall account.

Case-timeline threading

Every call, missed call and voicemail threads onto the same client timeline as email so the full history is one scroll. Agents, timestamps and outcomes are captured for compliance.

How it works.

Three stages. Connect, configure and then everything else runs itself. Most firms are calling clients from inside a case within five minutes.

01

Connect

Paste your JustCall API Key and Secret into the JustCall tile under Settings then Integrations. We verify the credentials against JustCall's API before saving and then seal them with your organisation's key.

02

Configure

Pick which JustCall number to use as the default caller ID per user. Point JustCall's webhook at ImmiIQ so recordings, missed calls and voicemails thread onto the right client.

03

Automate

Click a phone number on a client card to dial. JustCall places the call through your account. The moment the call ends the webhook fires and the recording, duration and outcome land on the case timeline.

In the app

One connection. Every case. Inline recording playback.

The JustCall tile sits in the Integrations marketplace inside the app. Once connected, the click-to-call and inline recording player appear directly on the client card.

JustCall · Bring-your-own VOIP
Beta
1
2
3
4
5
6
7
8
9
*
0
#
Priya Kapoor
+61 412 987 654
REC
02:14 · recording to client 20 timeline
Click-to-call from any phone. Recording auto-attaches to the case.

Security posture

Your JustCall account. Your API Secret. Our sealed vault.

JustCall credentials are sealed with AES-256-GCM using a per-organisation key derived from AUTH_SECRET via HKDF. Plaintext API Keys and Secrets never touch the database or logs. Inbound webhooks from JustCall are validated against the shared secret so nothing else can spoof a call onto a case. Tenant isolation is enforced at the row level: JustCall credentials for one organisation cannot be queried, indexed or read from another organisation under any code path. Every connect, disconnect and outbound call is written to the tenant audit log with the actor, timestamp and result. Revoking the connection deletes the sealed row immediately and stops all outbound routing through that account within seconds. Call recordings live inside JustCall; ImmiIQ links to them so the audio itself is never copied off JustCall infrastructure.

AES-256-GCM sealed credentials
Per-org tenant isolation
Audit-logged connect + disconnect

Frequently asked.

Whose JustCall account gets billed for calls?

Yours. This is a bring-your-own-JustCall integration. You provide the JustCall API Key and Secret and every call is placed through your account, so JustCall invoices you directly at your existing plan and per-minute rate. ImmiIQ never sits in the payment path.

Are call recordings copied into ImmiIQ storage?

No. Recordings stay on JustCall under your account. When the JustCall webhook confirms a recording exists, ImmiIQ stores the recording URL against the client timeline entry so an agent can play it back inline. Deleting the recording in JustCall removes the playback link on the next verification.

Does click-to-call work from a client card?

Yes. Click the client's phone number and JustCall places the outbound call through your connected account. Duration, direction, outcome and the recording link land on the client timeline the moment JustCall's webhook fires.

Is this generally available or still in beta?

The JustCall integration is currently in beta. It is live in production and being hardened based on early customer feedback. Errors are welcome. Email support@immiiq.com if you see anything unexpected and we will turn it around fast.

How are JustCall credentials stored and what happens on disconnect?

The JustCall API Key and Secret are sealed with AES-256-GCM using a per-organisation key derived from AUTH_SECRET via HKDF. Plaintext credentials never touch the database or logs. Disconnecting the integration deletes the sealed row immediately and stops all outbound routing through that JustCall account. Every connect and disconnect is written to the tenant audit log.

Related integrations.

Bring your JustCall account across in one minute.

Start a trial and paste your API Key and Secret. The click-to-call button plus inline recording player light up on every client card immediately.

JustCall integration for migration CRM | ImmiIQ | ImmiIQ