[VoiceOps] Carriers / TCR requiring NetNumber ID for SMS, even P2P
Matthew Crocker
matthew at corp.crocker.com
Wed May 4 19:13:29 EDT 2022
Well, this is all new to me so I apologize for misleading or incorrect information. I’m going through the CSP process now and it has been pretty quick/easy. I’ve registered one brand ($4) and one campaign ($2/month).
I’m using Inteliquent as my interconnect, they charge fees per SMS/MMS. I don’t believe I will be receiving invoices from individual carriers (ala CABS)
From: Peter Beckman <beckman at angryox.com>
Date: Wednesday, May 4, 2022 at 7:08 PM
To: Matthew Crocker <matthew at corp.crocker.com>
Cc: VoiceOps <voiceops at voiceops.org>
Subject: Re: [VoiceOps] Carriers / TCR requiring NetNumber ID for SMS, even P2P
CAUTION: This email originated from outside of Crocker. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Your statement is misleading, borderline wrong.
It's $200 just to sign up with TCR.
Then it is a variable fee based on how many DIDs you are attempting to
register.
Low Volume: $2 per MONTH per DID (non-time-sensitive)
Undisclosed how much it costs if NOT Low Volume.
Then carriers can add on their own per-DID and per-campaign fees.
And this is ONLY for 10DLC A2P SMS -- BUSINESS or BULK SMS, not P2P,
person-to-person SMS.
Look at the pricing Commio is putting out regarding T-Mobile:
https://www.thinq.com/blog/t-mobile-10dlc-text-messaging-fee-changes/
- $50 Campaign Service Activation Fee
- $50 Campaign Migration Fee
- $2,000 one-time NNID Registration
- $10,000 pass-through fee if T-Mobile doesn't like your SMS
- $1,000 pass-through fee if they think you're evading the rules
Bandwidth increasing per-SMS fees too:
https://support.bandwidth.com/hc/en-us/articles/1500002422242-10DLC-Overview
Can you imagine your cost basis as a small carrier, to increase your direct
costs of a DID by 10x or more, just to allow your customer to send and
receive SMS messages?
Please note:
I am discussing P2P -- PERSON-TO-PERSON -- NOT A2P, BUSINESS-TO-PERSON
See the CTIA Best Practices for the difference between the content of the
two.
Beckman
On Wed, 4 May 2022, Matthew Crocker wrote:
>
> www.campaignregistry.com<http://www.campaignregistry.com><http://www.campaignregistry.com%3chttp:/www.campaignregistry.com%3e> The process is quick,painless and a campaign costs a small one time fee ($4 I think)
>
>
> From: VoiceOps <voiceops-bounces at voiceops.org> on behalf of Peter Beckman <beckman at angryox.com>
> Date: Wednesday, May 4, 2022 at 5:09 PM
> To: VoiceOps <voiceops at voiceops.org>
> Subject: [VoiceOps] Carriers / TCR requiring NetNumber ID for SMS, even P2P
> CAUTION: This email originated from outside of Crocker. Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
>
> I'm hearing from one of my carriers that in order to continue sending P2P
> (NOT A2P) SMS from our DIDs, my $dayjob needs to purchase and maintain a
> NetNumber ID to use as the SPID for SMS.
>
> I'm also hearing that ALT-SPIDs are being discontinued.
>
> Does anyone else know about this change, who is driving it, and why? Anyone
> want to share costs involved in getting and maintaining an NNID for this
> purpose?
>
> This feels more like pay-to-play than a solution to reduce unwanted SMS.
>
> Beckman
> ---------------------------------------------------------------------------
> Peter Beckman Internet Guy
> beckman at angryox.com https://www.angryox.com/
> ---------------------------------------------------------------------------
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
---------------------------------------------------------------------------
Peter Beckman Internet Guy
beckman at angryox.com https://www.angryox.com/
---------------------------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20220504/df256de3/attachment-0001.htm>
More information about the VoiceOps
mailing list