Autocloz + Bandwidth SMS
Bandwidth SMS is listed in Autocloz for US 10DLC messaging, and the Bandwidth card in Settings → Integrations saves your account ID, API username, API password and application IDs. In the current build a Bandwidth SMS send still fails before reaching Bandwidth: the adapter expects the API username and the messaging application ID under different field names than the card uses, so it reports missing credentials. Nothing is sent and nothing is shown as sent. For working SMS today, use Twilio SMS or Telnyx SMS.
Status: limited today. Measured on 2026-09-28: a Bandwidth SMS send configured through the Settings card fails with "Bandwidth SMS requires accountId, username, password…". It never reaches Bandwidth.
What you can do with Bandwidth SMS
Bandwidth SMS plugs into the SMS stack — bring your own sms provider, scoped to your workspace.
Settings saved securely
Your Bandwidth values are stored encrypted for your workspace and kept for when the mapping is fixed.
Adapter for Bandwidth Messaging v2
The adapter posts to messaging.bandwidth.com with basic auth and your application ID once its inputs line up.
Visible failure
The failure is recorded on the touch with the missing field names, so reports stay honest.
How to connect Bandwidth SMS
Bring your own SMS provider — you keep control of the account, the spend and the data boundary.
- 1
Collect Bandwidth values
Account ID, API user credentials, and the Messaging application ID from the Bandwidth dashboard.
- 2
Save the Bandwidth card
Settings → Integrations → SMS → Bandwidth.
- 3
Expect the mapping error
A test send reports missing credentials. That is the known gap.
- 4
Send through another provider
Use Twilio, Telnyx, Sinch, Vonage or MSG91 SMS senders in the meantime.
Planning around the gap
If Bandwidth is your only US carrier, keep SMS steps paused or on another provider until the mapping is fixed. Email, LinkedIn and calls through other carriers are unaffected, so a multichannel sequence can keep running with the SMS step moved or removed.
How to confirm nothing was sent
Each Bandwidth SMS attempt creates a failed touch on the lead with the adapter's message listing the missing values. The check happens before any request, so Bandwidth sees no traffic and bills nothing. Campaign analytics count these as failed, not sent. When you move the SMS step to another provider's sender, you can retry the failed leads.
Bandwidth card fields
What the card stores today:
- Account ID
- API username
- API password
- Messaging app ID
- Voice app ID
The four Bandwidth values and where they break
Bandwidth messaging needs an account ID (in the URL), an API username and password (basic auth), and a Messaging application ID (which ties the number to 10DLC or toll-free routing). The adapter reads the username from an api_key slot and the application ID from application_id. The card stores them as api_username and messaging_app_id, and the resolver does not translate them, so the username and application ID arrive empty.
This is described here because a provider page should not promise working texts that cannot leave. See also the Bandwidth voice page, which has the same kind of gap.
Why teams pick Bandwidth anyway
Bandwidth owns its US network and is a direct carrier for 10DLC, which some teams prefer for throughput and support. If you are already a Bandwidth customer, keep your settings saved. When the mapping is fixed, the SMS step will use them without re-entry. Until then, the SMS channel works with the other listed providers.
What Bandwidth SMS does not do in Autocloz
- No working Bandwidth SMS from the Settings card today.
- No inbound Bandwidth webhook.
- No 10DLC registration inside Autocloz.
Troubleshooting Bandwidth SMS
- Touches fail with "Bandwidth SMS requires accountId (account_sid), username (api_key)…".
- Known mapping gap. Switch the step to another provider.
Part of the SMS stack
Bandwidth SMS is one of the providers behind the SMS channel. All providers share the same two-way threading, STOP-keyword DNC and quiet-hours enforcement.
Explore the SMS featureRelated integrations
Frequently asked
Is my Bandwidth password wrong?
Probably not. The adapter never receives the username, so it cannot try your password.
Which provider should I use instead?
For US 10DLC traffic, Twilio or Telnyx. Both work from their Settings cards and share the same SMS step, limits and compliance checks.
Can I paste Bandwidth credentials on the sender instead?
The sender form in the app does not collect secrets for SMS senders; credentials come from the Settings card. So no.
Will Bandwidth MMS work?
No. SMS itself does not send yet, and MMS is not part of the Autocloz SMS step.
Run Bandwidth SMS inside Autocloz
Bring your own account, plug it into the SMS channel, and keep a free-forever CRM for 3 users.