Skip to content
Voice carriers

Autocloz + Bandwidth

Bandwidth is listed as a North American voice carrier in Settings → Integrations, where you can save a Bandwidth account ID, API username, API password and application IDs. Today those saved settings are not enough to place a call: the Bandwidth call adapter also needs a Voice application ID under a different field name and a public answer URL that the card does not collect, so calls fail with a visible error. If you need calling now, use Telnyx, which runs every dialer mode.

Status: limited today. Measured on 2026-09-28: with only the Settings → Integrations card filled in, a Bandwidth call or SMS fails before it reaches Bandwidth, with an error naming the missing fields. Nothing is sent and nothing is reported as sent.

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

What you can do with Bandwidth

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

Credentials stored encrypted

The account ID, API username, API password and application IDs you save are encrypted at rest and scoped to your workspace.

Fails loudly, never silently

When the adapter is missing a value it returns a failure with the exact field names, so a campaign never shows phantom calls.

Voice API adapter exists

Autocloz has a Bandwidth Voice adapter that posts to Bandwidth's v2 calls endpoint with basic auth once its inputs are complete.

How to connect Bandwidth

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

  1. 1

    Collect your Bandwidth IDs

    From the Bandwidth dashboard note the account ID, an API user's username and password, and the Voice and Messaging application IDs.

  2. 2

    Save them on the Bandwidth card

    Open Settings → Integrations, Voice tab, Bandwidth, and paste the values. Saving is allowed and stored per workspace.

  3. 3

    Understand the current gap

    The call adapter reads the application ID and an answer URL from fields the card does not fill, so sends stop with a clear error for now.

  4. 4

    Use a working carrier meanwhile

    Connect Telnyx, Twilio, Voximplant or MSG91 for live calling, and keep the Bandwidth settings saved for when the mapping is fixed.

Checking a Bandwidth sender yourself

Open the campaign's activity or the lead timeline after a test send. A Bandwidth call touch will show as failed with the text naming application_id and answer_url. That text is the adapter's own check and appears before any network call, so no Bandwidth charge is incurred. If you see a different error, such as a 401 from Bandwidth, tell support, because that would mean the request did reach Bandwidth.

What the Bandwidth adapter expects

Bandwidth's Voice API needs four things for an outbound call: the account ID in the URL, an API user for basic auth, a Voice application ID, and an answer URL that Bandwidth fetches when the call connects. The Autocloz adapter checks all four before it makes a request. The Settings card stores the application IDs as voice_app_id and messaging_app_id, while the adapter looks for application_id and answer_url, so the check fails.

This is a field-mapping gap, not a Bandwidth outage. It is reported here because a carrier page that says "connect and call" when the call cannot go out would waste your setup time. The same gap affects the Bandwidth SMS adapter.

What Bandwidth would add once it works

Bandwidth runs its own network in the US, which is why teams use it for high-volume North American calling and toll-free or 10DLC messaging. In Autocloz it would sit behind the same call step in sequences and the same compliance gate (quiet hours, DNC, consent) as every other carrier. It has no in-browser softphone path in Autocloz, so it would be used for API-placed calls rather than a rep's click-to-call.

What Bandwidth does not do in Autocloz

  • Calls and texts do not go out with only the Settings card filled in (see the notice above).
  • No in-browser softphone, no inbound call webhook and no recording import for Bandwidth.
  • No number purchase or porting inside Autocloz.

Troubleshooting Bandwidth

Call touches fail with "extras.application_id + extras.answer_url required".
That is the mapping gap described above. Use another carrier for the call step until it is fixed.
The sender stays pending.
Senders need resolvable credentials and a Verify click. With Bandwidth the verify step cannot complete a real send yet.

Part of the Call stack

Bandwidth 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

Is Bandwidth usable for calls in Autocloz today?

Not through the Settings card alone. The adapter needs an application ID and answer URL under field names the card does not collect, so calls fail with a clear error.

Will my saved Bandwidth settings be lost?

No. They stay stored and encrypted in your workspace.

Run Bandwidth inside Autocloz

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