Skip to content
Voice carriers

Autocloz + Voximplant

Voximplant connects to Autocloz as a programmable voice and SMS carrier. You paste your Voximplant account ID, API key and the ID of the routing rule that owns your VoxEngine scenario into Settings → Integrations. A call step then asks Voximplant to start that scenario for the lead's number, passing the step's text and the lead's number as custom data. What the call does is whatever your scenario does, so Voximplant suits teams who already script calls in VoxEngine. Autocloz does not provide a scenario.

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

What you can do with Voximplant

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

Your scenario runs the call

Autocloz calls StartScenarios with your rule ID. Your VoxEngine code decides whether to play audio, connect a rep or record.

Script and number passed in

The step body and the lead's number go to the scenario as script_custom_data, so one scenario can serve many campaigns.

SMS from the same account

The Voximplant SMS adapter uses the same account ID and API key, so one card covers both channels.

How to connect Voximplant

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

  1. 1

    Write and deploy a scenario

    In Voximplant, create an application, write a VoxEngine scenario that places the outbound call, and attach it to a routing rule.

  2. 2

    Copy the IDs

    Note your account ID, an API key, the application ID and the routing rule ID.

  3. 3

    Fill in the Voximplant card

    Open Settings → Integrations, Voice tab, Voximplant, and paste the four values. The rule ID is required for calls.

  4. 4

    Run a single-lead test

    Enroll one test lead with your own number in a sequence with a call step and check that the scenario runs.

A minimal scenario, in outline

Your VoxEngine scenario receives custom data containing to, from and body. A simple scenario reads those, calls the lead's number from your Voximplant caller ID, plays the body with text-to-speech or connects a rep, and hangs up. If you want the result in Autocloz, have the scenario, or a small service it calls, post the outcome to Autocloz's outcomes endpoint with the shared signature. Voximplant's own documentation covers the scenario API; Autocloz only starts it.

  • Card fields: account ID, API key, application ID, scenario rule ID.
  • Required for calls: account ID, API key, rule ID.
  • Also used for SMS: account ID and API key.

What Autocloz sends to Voximplant

Each call step sends one StartScenarios request with the account ID, API key and rule ID, plus custom data holding the lead's number and the step text. Voximplant returns a result, and Autocloz records the call touch as sent or failed on the lead. It does not receive per-call status from Voximplant by itself; call outcomes reach Autocloz only if your scenario or a relay reports them to the outcomes endpoint.

Our 2026-09-28 check confirmed the Settings card values reach the adapter and it makes the request. We did not place a live Voximplant call.

Where Voximplant fits next to the dialer

Voximplant is used by the sequence call step, not by the in-browser dialer, which runs on Telnyx, DIDLogic and FreJun. If you want reps on live calls with click-to-call and recordings on the timeline, one of those carriers is the better fit. If you want scripted calls that your own VoxEngine logic controls, Voximplant is. Every call step still passes the compliance gate.

What Voximplant does not do in Autocloz

  • No built-in scenario. Without your VoxEngine code the call does nothing useful.
  • No inbound call webhook, recording import or browser softphone for Voximplant. The voice platform page lists which carriers have them.
  • No per-call status unless your scenario reports it back.

Troubleshooting Voximplant

Calls fail with "extras.rule_id required".
Fill in Scenario rule ID on the Voximplant card.
The request succeeds but nothing rings.
Check your scenario's logs in Voximplant. The scenario must read the number from custom data and place the call.

Part of the Call stack

Voximplant 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

Do I have to write code?

Yes. Voximplant calls in Autocloz run your VoxEngine scenario.

Can reps take Voximplant calls in the browser?

Not through Autocloz. Use Telnyx, DIDLogic or FreJun for that.

Is Voximplant good for a rep-driven call team?

Not in Autocloz. Voximplant calls here start your scenario from a sequence step. Rep click-to-call with audio in the browser runs on Telnyx, DIDLogic or FreJun.

Run Voximplant inside Autocloz

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