代表多个业务从一个号码发送

huangapple go评论56阅读模式
英文:

Sending on behalf of multiple business from one number

问题

我的公司多年来一直在使用Twilio,我们只使用一个免费电话号码。我们的客户是其他企业,我们使用Twilio代表这些企业发送短信。我刚刚被告知,由于所有新的验证措施已经实施,这将不再是一个可行的设置。Twilio支持告诉我,现在我需要为我们代表发送短信的每个企业都拥有一个电话号码。还有其他人以类似的方式使用Twilio吗?也就是说,您是否为多个企业使用同一个号码发送短信?如果是这样,您是如何处理免费电话号码验证流程的?还是使用本地号码或短号码?

英文:

My company has been using Twilio for years and we've only used one toll free number. Our customers are other businesses and we use Twilio to send SMS texts on behalf of those other businesses. I've just been told this will not be a possible set up anymore with all of the new verification stuff put in place. Twilio Support told me I now need a phone number for each business that we send texts on behalf of. Does anyone else use Twilio in a similar manner? Meaning do you send texts for multiple businesses on the same number? If so how did you handle the Toll Free Verification process? Or are using a local number or short code?

答案1

得分: 2

免费电话号码每月1美元,如果这是最佳解决方案,为什么不添加更多呢?而且,我认为,无论是免费电话还是本地号码,要求都是相同的。短代码也有类似的要求,这些要求在这个页面上有解释:“允许最终用户选择退出多个程序的短代码活动的各个部分。”

我发现A2P 10DLC的流程很令人困惑,已经多次阅读过 - 可能是因为要求在迅速变化和实施。为了减少垃圾短信和垃圾短信,值得表扬的是任何减少垃圾短信的举措。

表格“了解您的ISV类型”对齐您对公司的看法与Twilio对您公司的看法非常有帮助。

请注意这个建议的架构:

但是,请注意,鉴于将在2023年夏季开始强制执行的A2P 10DLC注册要求,这些不同的架构并不都是同样可行的。一般来说,以下模式#3、#5和#6将不适用于A2P 10DLC注册,目前使用这些架构的客户需要迁移到模式#1、#2或#4。在这三者中,我们建议模式#1在长期内将最有用。这些要点将在下文中通过具体模式的参考来解释。

英文:

Tollfree numbers are $1 per month, if that is the best solution, why not just add a few more? And, I think, whether tollfree or local number, the requirements are the same. Short Codes also have similar requirements which are explained on this page about "Allowing end users to opt-out of individual parts of a multiple program short code campaigns."

I am finding the A2P 10DLC process to be confusing and have read through it multiple times - probably because the requirements are changing and being implemented fast. Bravo for anything to reduce spam and junk SMS.

The table "Understanding your ISV type" is helpful to align your view of your company with how Twilio views your company.

Note this suggested architecture:

> Please note, however, that these different architectures are NOT all
> equally viable going forward, given the requirements for A2P 10DLC
> registration that will enforced as of the Summer of 2023. In general,
> patterns #3, #5 and #6 below will not be viable for A2P 10DLC
> registration, and any clients using these architectures currently will
> need to migrate to patterns #1, #2 or #4. Of these latter three, we
> suggest that pattern #1 will prove the most useful in the longer term.
> These points will be explained below with reference to specific
> patterns.

huangapple
  • 本文由 发表于 2023年7月20日 20:57:01
  • 转载请务必保留本文链接:https://go.coder-hub.com/76730144.html
匿名

发表评论

匿名网友

:?: :razz: :sad: :evil: :!: :smile: :oops: :grin: :eek: :shock: :???: :cool: :lol: :mad: :twisted: :roll: :wink: :idea: :arrow: :neutral: :cry: :mrgreen:

确定