Skip to content
Voice carriers

Autocloz + DIDLogic

DIDLogic connects to Autocloz as a SIP carrier for reps who dial from the browser. You paste a DIDLogic personal access token into Settings → Integrations and, for in-tab audio, a Voice SDK token that DIDLogic support issues on request. Reps then click to call from a lead or work a preview or power queue in the dialer. DIDLogic is a common choice for international numbers; Autocloz lists it with a Europe region tag.

Autocloz and DIDLogic integration
Bring your own accountWorkspace-scoped, no cross-org leakFree-forever CRM core
Start freeSee pricing

What you can do with DIDLogic

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

Click-to-call in the tab

With a Voice SDK token set, the DIDLogic SDK opens its own per-call SIP session in the browser, so reps do not need MicroSIP or another softphone.

SIP softphone fallback

Leave the SDK token blank and Autocloz hands the call to an external SIP softphone using the SIP username and password on the card instead.

Call records by webhook

DIDLogic call events post to a signed webhook and become call records on the lead, with a recording link when DIDLogic includes one.

How to connect DIDLogic

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

  1. 1

    Create a personal access token

    In the DIDLogic portal open API → Personal access tokens, create one, and paste it into API key on the DIDLogic card in Settings → Integrations.

  2. 2

    Ask DIDLogic for a Voice SDK token

    Request an SdkApiToken from DIDLogic support and paste it into Voice SDK API token. This is what makes calls ring and talk inside the browser.

  3. 3

    Add your numbers

    Add your DIDLogic numbers under Voice → Numbers and pick a default inbound receiver so calls to an unassigned number still ring someone.

  4. 4

    Place a test call

    Save the card, call a mobile you own from the dialer, and confirm you hear ringback and two-way audio before giving the queue to reps.

Who DIDLogic suits in Autocloz

DIDLogic fits teams whose reps dial by hand from the browser and who want numbers in several countries from one supplier. It does not fit a call centre that needs a supervisor to push leads to many reps at once with parallel lines, because that needs server-side dialing. In that case pair DIDLogic numbers for inbound with Telnyx for campaign dialing, or use Telnyx for both.

How DIDLogic calls are placed and logged

DIDLogic is marked rep-console-only in Autocloz's carrier capability list. The rep's browser places each call, so preview and power dialing work from the rep's queue, but a supervisor cannot originate calls server-side and parallel dialing is refused with a reason on screen. There is no programmable answer webhook, so outbound IVR trees do not run on DIDLogic either.

Call events come back to /api/voice/webhooks/didlogic. Autocloz checks an HMAC signature against the webhook secret configured by your super-admin, rejects unsigned events, and writes the call record, duration and outcome to the lead history.

Which DIDLogic fields you actually need

For in-browser calling you need the API key and the Voice SDK token. The SIP username and password only matter for the older external-softphone path. The account email field is your DIDLogic login email. The Voice SDK endpoint URL should stay blank unless a call fails with an "SDK endpoint doesn't exist" 404, in which case DIDLogic support can give you the account-specific command URL.

  • API key: personal access token from the DIDLogic portal.
  • Voice SDK API token: issued by DIDLogic support, separate from the API key.
  • Default inbound receiver: the user who gets calls to numbers with no assignee.

What DIDLogic does not do in Autocloz

  • No parallel dialing and no server-side campaign dispatch. Calls start from a rep's browser.
  • Recording links are stored when DIDLogic sends them, but Autocloz cannot re-request an expired DIDLogic recording link.
  • No SMS or WhatsApp through DIDLogic. Use a provider from the SMS channel list for texts.

Troubleshooting DIDLogic

Clicking call opens an external softphone instead of ringing in the tab.
The Voice SDK token is empty. Ask DIDLogic support for an SdkApiToken and paste it on the card.
A call fails with "SDK endpoint … doesn't exist" (404).
Your account uses a different SDK command URL. Get it from DIDLogic support and put it in Voice SDK endpoint URL.
Calls happen but never appear on the lead.
Webhook events are failing signature checks. Ask your super-admin to confirm the DIDLogic webhook secret matches what DIDLogic sends.

Part of the Call stack

DIDLogic 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

Voice carriers
Telnyx

Call Control v2 + WebRTC softphone, signed-URL recordings, Ed25519 webhook verification.

View integration
Voice carriers
FreJun

India-native voice with per-agent OAuth, presence sync + recording import.

View integration
Voice carriers
Twilio

Programmable Voice — bring your own account for outbound calls.

View integration
See all integrations →

Frequently asked

Is the Voice SDK token the same as the API key?

No. The API key is a personal access token you create yourself. The Voice SDK token is issued by DIDLogic support and is only used for in-browser calling.

Can I run a parallel dialer on DIDLogic?

No. Parallel dialing needs server-side bridging and answering-machine detection. Autocloz blocks the mode on DIDLogic and shows why.

Do I need MicroSIP?

Only if you leave the Voice SDK token blank. With the token set, calls ring and talk inside the browser.

Run DIDLogic inside Autocloz

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

Start freeBook a demo
See all integrations →