The 10 DLC Form (US Partners)
Regardless of the method of SMS selected, the 10 DLC form still needs to be filled out and processed by the US Registry. All US number SMS traffic, even if the traffic is inbound only, must be associated with a campaign.
SMS Options Available
We have three key paths for SMS, depending on your provider as not all of these are supported by all messaging providers. These can be mixed and matched, with one number going to one and another number going to another option.
- 1stream Integrated SMS, which supports advanced notifications and creating tickets with compatible PSA platforms.
- SMS to Chat which has a convenient mobile app
- Textable which has Blasts, Drip Campaigns, and Reminders for marketing needs.
For our US-based partners, we also have SMS to Email which can send to anywhere you can receive an email, however all numbers on the account must go that route.
Group Limitations Note
While each of the options above provides the ability to send and receive SMS and MMS, they are 1:1 conversations.
We do not support Group messages at this time, so while any messages sent to a group would be received, responses would be sent back to the single number that sent the message initially.
Simple Flowchart
Follow the simple decision tree below to determine which method for SMS is the best option for your messaging needs given what your provider supports.
Who is your SMS/Phone provider?
Inbound/Outbound means you MUST complete the 10DLC regulatory process.
Are you looking to send and receive SMS, or just receive?
Are you looking for these conversations to occur in a web app, the mobile app, in an email, or a 3rd party chat software?
What is the primary purpose for this number?
As long as you have a 1stream compatible PSA/CRM/ERP, you'll want to use the 1stream Integrated SMS option available in 1stream, which can create a ticket when a new message is received.
For marketing purposes, we recommend our partner Textable, as they provide options like Drip Campaigns, Blasts, and Reminders which are not features we support on any other option currently.
This is a separate cost outside of the bvoip ecosystem, but they support your current SIPTrunk.com provider, so numbers don't have to be moved!
In this case, it's simplest to configure the SMS to Chat option, which will send messages to both the webclient and the mobile app.
In this case, it's simplest to configure the SMS to Chat option, which also enables these messages to be shown in the mobile app in addition to the web client.
In order for users to converse inside the Teams app itself, you must setup the 1stream Application for Teams, and then users can utilize the 1stream Integrated SMS option available in 1stream, which can be used with or without a ticketing system.
You can also use Textable with their MS Teams integration option, allowing you to send new message notifications into Teams, however responses can only be done within the Textable web app.
You can both send and receive using the Email SMS, it just requires specifically crafted addresses for it to work properly.
See the SMS to Email article for more details about this option.
You can use Textable with their Slack integration option, allowing you to send new message notifications into Slack, however responses can only be done within the Textable web app.
You can use Textable with their Google Chat integration option, allowing you to send new message notifications into Google Chat, however responses can only be done within the Textable web app.
Are you looking for these messages to arrive in a web app, the mobile app, in an email, or a 3rd party chat software?
In this case, it's simplest to configure the SMS to Chat option, which also enables these messages to be shown in the mobile app.
This does have some caveats, like “Taking Ownership” of a conversation locks that number to a user so no one else can see it, and only that user can undo that. To work around those, we recommend the more intelligent 1stream Integrated SMS which can be used without a ticket system connected. It just isn't available in the mobile app.
As long as you have a 1stream compatible PSA/CRM/ERP, you'll want to use the 1stream Integrated SMS option available in 1stream, which can create a ticket when a new message is received.
If your PSA/CRM/ERP isn't supported currently, you can leverage SIPTrunk.com's SMS to Email service instead and direct the messages to your primary support email.
SIPTrunk.com's SMS to Email service is what you'll want to pick for this number. You can then use Microsoft's article Send an email to a channel in Microsoft Teams to send the message into a Teams channel of your choice.
You can also use Textable with their MS Teams integration option, allowing you to send new message notifications into Teams.
SIPTrunk.com's SMS to Email service is what you'll want to pick for this number.
You can use Textable with their Slack integration option, allowing you to send new message notifications into Slack.
You can use Textable with their Google Chat integration option, allowing you to send new message notifications into Google Chat.
Are you looking for these conversations to occur in a web app, the mobile app, in Microsoft Teams, or in an email?
What is the primary purpose for this number?
As long as you have a 1stream compatible PSA/CRM/ERP, you'll want to use the 1stream Integrated SMS option available in 1stream, which can create a ticket when a new message is received.
For marketing purposes, we recommend our partner Textable, as they provide options like Drip Campaigns, Blasts, and Reminders which are not features we support on any other option currently.
This is a separate cost outside of the bvoip ecosystem, but they support your current Ixica provider, so numbers don't have to be moved!
In this case, it's simplest to configure the SMS to Chat option, which will send messages to both the webclient and the mobile app.
In this case, it's simplest to configure the SMS to Chat option, which also enables these messages to be shown in the mobile app in addition to the web client.
In order for users to converse inside the Teams app itself, you must setup the 1stream Application for Teams, and then users can utilize the 1stream Integrated SMS option available in 1stream, which can be used with or without a ticketing system.
You can also use Textable with their MS Teams integration option, allowing you to send new message notifications into Teams, however responses can only be done within the Textable web app.
Unfortunately, Ixica does not support SMS to Email at this time.
The SMS to Email service is what you'll want to pick for this number, and we can assist in moving the required number(s) to our SIPTrunk.com partner that is supported.
Alternatively, we can help in configuring a connection between Telnyx and a software like Zapier to handle this behavior manually, however support there is limited.
You can use Textable with their Slack integration option, allowing you to send new message notifications into Slack, however responses can only be done within the Textable web app.
You can use Textable with their Google Chat integration option, allowing you to send new message notifications into Google Chat, however responses can only be done within the Textable web app.
Are you looking for these conversations to occur in a web app, the mobile app, in Microsoft Teams, or in an email?
What is the primary purpose for this number?
As long as you have a 1stream compatible PSA/CRM/ERP, you'll want to use the 1stream Integrated SMS option available in 1stream, which can create a ticket when a new message is received.
For marketing purposes, we recommend our partner Textable, as they provide options like Drip Campaigns, Blasts, and Reminders which are not features we support on any other option currently.
This is a separate cost outside of the bvoip ecosystem, but they support your current Telnyx provider, so numbers don't have to be moved!
In this case, it's simplest to configure the SMS to Chat option, which will send messages to both the webclient and the mobile app.
In this case, it's simplest to configure the SMS to Chat option, which also enables these messages to be shown in the mobile app in addition to the web client.
In order for users to converse inside the Teams app itself, you must setup the 1stream Application for Teams, and then users can utilize the 1stream Integrated SMS option available in 1stream, which can be used with or without a ticketing system.
You can also use Textable with their MS Teams integration option, allowing you to send new message notifications into Teams, however responses can only be done within the Textable web app.
Unfortunately, Telnyx does not support SMS to Email at this time.
We can help in configuring a connection between Telnyx and a software like Zapier to handle this behavior manually, however support there is limited.
You can use Textable with their Slack integration option, allowing you to send new message notifications into Slack, however responses can only be done within the Textable web app.
You can use Textable with their Google Chat integration option, allowing you to send new message notifications into Google Chat, however responses can only be done within the Textable web app.
Check the selection below to determine if your provider is supported.
If you don't see your provider listed here, you can reach out to your sales manager, onboarding/implementation specialist, or support@bvoip.com to confirm what methods are supported for your generic trunk provider.
This is a non-exhaustive list, MANY more providers are supported than shown.
- Bandwidth.com
- Flowroute.com
- NexVortex
- SIPTrunk.com
- Twilio
- Thinq
- Telnyx
- VoxTelesys
- Wavix
If you don't see your provider listed here, you can reach out to your sales manager, onboarding/implementation specialist, or support@bvoip.com to confirm what methods are supported for your generic trunk provider.
- Flowroute
- Telnyx
- Thinq
- Twilio
- SIPTrunk.com
If you don't see your provider listed here, you can reach out to your sales manager, onboarding/implementation specialist, or support@bvoip.com to confirm what methods are supported for your generic trunk provider.
- Avaya OneCloud
- Bandwidth.com
- BCMOne
- BulkVS
- DIDWW
- Esendex
- Flowroute
- Intelepeer
- Inteliquent
- Ixica
- Jivetel
- Signalmash
- SignalWire
- SIPTrunk.com
- SIP.us
- SkyeTel
- Teli
- Telnyx
- TextBetter
- Thinq
- Twilio
- Tychron
- VoIP Innovations
- VoIP.ms
- VoxTelesys