Back to Details

sms-10dlc-registration

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
<!-- Verified against Sent sources: - https://docs.sent.dm/troubleshooting/compliance - https://docs.sent.dm/start/quickstart/channel-setup - https://docs.sent.dm/start/quickstart/dashboard-walkthrough - Sent v3 OpenAPI: /v3/brands, /v3/brands/{brandId}, /v3/brands/{brandId}/campaigns, /v3/brands/{brandId}/campaigns/{campaignId}, /v3/profiles/{profileId}/complete Review notes: - Sent docs verify that US SMS A2P messaging requires 10DLC registration and that Sent handles TCR registration as part of the compliance process. - Sent docs list required compliance-form inputs: legal business name, business address, EIN/tax ID, live website, privacy policy, opt-in mechanism URL, use-case description, sample messages, and opt-out instructions. - Treat exact carrier throughput, vetting-score impact, and TCR taxonomy details as external/compliance reference material unless Sent compliance data confirms them for the account. -->
<!-- 已对照Sent来源验证： - https://docs.sent.dm/troubleshooting/compliance - https://docs.sent.dm/start/quickstart/channel-setup - https://docs.sent.dm/start/quickstart/dashboard-walkthrough - Sent v3 OpenAPI: /v3/brands, /v3/brands/{brandId}, /v3/brands/{brandId}/campaigns, /v3/brands/{brandId}/campaigns/{campaignId}, /v3/profiles/{profileId}/complete 审核说明： - Sent文档确认，美国SMS A2P消息发送需完成10DLC注册，且Sent会在合规流程中处理TCR注册。 - Sent文档列出了合规表单的必填项：合法企业名称、企业地址、EIN/税号、有效网站、隐私政策、用户授权机制URL、使用场景说明、示例消息及退订说明。 - 除非Sent合规数据针对该账户确认了具体的运营商吞吐量、审核分数影响及TCR分类细节，否则将这些内容视为外部/合规参考资料。 -->

SMS 10DLC registration

SMS 10DLC注册

Overview

概述

Use this skill to prepare US A2P SMS compliance for Sent. Sent’s compliance documentation states that compliance is a prerequisite for sending messages and that 10DLC registration is mandatory for A2P messaging to US numbers. Sent handles TCR registration as part of the compliance process, while the customer must provide accurate business identity, consent, use-case, sample-message, and opt-out evidence.
The Sent v3 API exposes Sent-facing brand and campaign resources through 
/v3/brands
and 
/v3/brands/{brandId}/campaigns
. Profile completion through 
/v3/profiles/{profileId}/complete
validates profile, brand, and campaign prerequisites before the profile is ready.
使用本技能可为Sent平台准备美国A2P SMS合规材料。Sent的合规文档指出，合规是发送消息的前提条件，向美国号码发送A2P消息必须完成10DLC注册。Sent会在合规流程中处理TCR注册，而客户需提供准确的企业身份信息、用户授权证明、使用场景说明、示例消息及退订相关证明。
Sent v3 API通过
/v3/brands
和
/v3/brands/{brandId}/campaigns
接口对外暴露品牌和活动资源。通过
/v3/profiles/{profileId}/complete
完成资料提交，会在资料就绪前验证资料、品牌及活动的前置条件。

When to use

使用场景

Use this skill when the request mentions 10DLC, A2P, TCR, brand registration, campaign registration, SMS compliance, US long code, EIN, opt-in proof, sample messages, opt-out, HELP/STOP language, vetting, rejected campaign, or carrier filtering caused by compliance. Use it before enabling US SMS sending or SMS fallback for RCS.
Do not use this skill for non-US country compliance unless the user supplies a Sent compliance source for that country. Do not use it to analyze live delivery failures except to identify whether compliance status is the likely next check.
当请求中提及10DLC、A2P、TCR、品牌注册、活动注册、SMS合规、美国长码、EIN、授权证明、示例消息、退订、HELP/STOP话术、审核、活动被驳回或因合规导致的运营商过滤时，可使用本技能。在启用美国SMS发送功能或RCS的SMS fallback功能前使用。
除非用户提供Sent针对其他国家的合规来源，否则不要将本技能用于非美国地区的合规处理。除了判断合规状态是否为下一步排查的重点外，不要用本技能分析实时投递失败问题。

Required evidence

所需证明材料

Collect evidence before creating or updating Sent brand/campaign resources. Bad evidence creates review loops and downstream filtering risk.
EvidenceWhat to captureSent-grounded reason
Legal business identityLegal business name, address, EIN/tax ID, entity typeSent’s compliance guide lists these as required inputs.
Public web presenceLive website URL and privacy policy URLSent requires a live website and privacy policy for compliance review.
Opt-in mechanismURL, screenshot, form text, checkbox language, or checkout flowSent requires an opt-in mechanism URL.
Use-case descriptionClear description of what messages are sent and whySent requires use-case description.
Sample messagesRealistic messages matching the declared use caseSent requires sample messages.
Opt-out instructionsSTOP/HELP or equivalent instructions where applicableSent requires opt-out instructions.
Sender ProfileSent profile ID or dashboard profile being completedProfile completion validates compliance prerequisites.
在创建或更新Sent品牌/活动资源前，需收集相关证明材料。不合格的材料会导致审核循环，增加后续被过滤的风险。
证明材料需收集的内容基于Sent要求的原因
合法企业身份合法企业名称、地址、EIN/税号、实体类型Sent合规指南将这些列为必填项。
公开网络存在有效网站URL及隐私政策URLSent合规审核要求提供有效网站和隐私政策。
用户授权机制URL、截图、表单文本、勾选框话术或结账流程Sent要求提供用户授权机制的URL。
使用场景说明清晰描述发送的消息内容及原因Sent要求提供使用场景说明。
示例消息与申报使用场景相符的真实消息Sent要求提供示例消息。
退订说明适用情况下的STOP/HELP或等效话术Sent要求提供退订说明。
发送方资料Sent资料ID或正在完善的控制台资料资料提交会验证合规前置条件。

Process

流程

1. Decide whether this is US A2P SMS

1. 判断是否为美国A2P SMS

Confirm destination country, traffic type, and sender type. This skill applies to US A2P SMS over 10DLC. If the user is sending only WhatsApp, RCS without SMS fallback, short code, toll-free, or non-US traffic, document the difference and route to the appropriate compliance workflow.
Example. “We send appointment reminders from a SaaS platform to US patients using local long-code numbers” is US A2P SMS and needs 10DLC. “We send only WhatsApp utility templates” is not a 10DLC workflow, though WhatsApp has its own template and business requirements.
确认目标国家、流量类型及发送方类型。本技能适用于基于10DLC的美国A2P SMS。如果用户仅发送WhatsApp消息、无SMS fallback的RCS消息、短码消息、免费电话消息，或非美国地区流量，需记录差异并引导至相应的合规流程。
示例：“我们通过SaaS平台使用本地长码向美国患者发送预约提醒”属于美国A2P SMS，需要完成10DLC注册。“我们仅发送WhatsApp实用模板消息”不属于10DLC流程，不过WhatsApp有其自身的模板和企业要求。

2. Normalize the business identity

2. 规范企业身份信息

Use the exact legal business name and tax ID records. Do not “clean up” the name to a marketing brand if the tax record uses another legal entity. Mismatches between legal identity, website, and opt-in flow are common rejection causes.
If the customer is an ISV registering many customers, decide whether each customer needs its own profile/brand/campaign boundary with 
sender-profile-architect
. Do not put unrelated customers under one brand because it is faster.
使用准确的合法企业名称和税号记录。如果税号记录使用的是其他法律实体名称，不要将名称“修正”为营销品牌名。合法身份、网站及授权流程之间的不一致是常见的驳回原因。
如果客户是为众多客户注册的ISV，需通过
sender-profile-architect
技能决定每个客户是否需要独立的资料/品牌/活动边界。不要为了图快将无关客户归到同一个品牌下。

3. Classify the campaign by use case

3. 根据使用场景分类活动

Pick the narrowest truthful campaign use case. Mixed-use campaigns can be valid, but they invite broader review and more filtering risk if the sample messages do not match the declared intent.
Declared intentBetter sampleBad sample
Account notification“Acme: Your password was changed. If this was not you, visit https://acme.example/security. Reply STOP to opt out.”“Huge sale today. Click now.”
Delivery notification“Acme: Order 1234 is out for delivery today. Track: https://acme.example/t/1234. Reply STOP to opt out.”“Your package is coming. Also buy these add-ons.”
Customer care“Acme Support: We received your request and will respond shortly. Reply STOP to opt out.”“Thanks for contacting us. Get 20% off now.”
Marketing“Acme: Spring sale starts today. Use code SPRING. Reply STOP to opt out.”Transactional description with promotional samples.
Keep detailed TCR taxonomy and carrier-specific advice in a reference file. In the skill body, use only enough taxonomy to keep the submission honest.
选择最精准且真实的活动使用场景。混合使用场景可能有效，但如果示例消息与申报意图不符，会引发更严格的审核并增加被过滤的风险。
申报意图合适的示例不合适的示例
账户通知“Acme：您的密码已修改。若非本人操作，请访问https://acme.example/security。回复STOP退订。”“今日大促销，点击查看。”
配送通知“Acme：订单1234今日已发货。追踪链接：https://acme.example/t/1234。回复STOP退订。”“您的包裹即将送达。另外购买这些附加商品吧。”
客户服务“Acme支持：我们已收到您的请求，将尽快回复。回复STOP退订。”“感谢您联系我们。立即享受20%折扣。”
营销推广“Acme：春季促销今日开启。使用优惠码SPRING。回复STOP退订。”事务性描述搭配推广类示例。
将详细的TCR分类体系及运营商特定建议存入参考文件。在技能主体中，仅使用足够的分类信息确保提交内容真实准确。

4. Create or update Sent brand resources

4. 创建或更新Sent品牌资源

Use Sent’s brand endpoints when API work is in scope. The verified v3 API includes:
OperationEndpointNotes
Create brand
POST /v3/brands
Creates a new brand and associated information.
List brands
GET /v3/brands
Retrieves brands for the authenticated customer, including inherited brands where applicable.
Update brand
PUT /v3/brands/{brandId}
Cannot update brands already submitted to TCR or inherited brands.
Delete brand
DELETE /v3/brands/{brandId}
Deletes a brand that belongs to the authenticated customer.
Use optional 
Idempotency-Key
headers on create/update calls when retrying. Store the Sent brand ID returned by the API. Store any returned TCR identifiers separately only if the API response exposes them.
当涉及API操作时，使用Sent的品牌端点。已验证的v3 API包括：
操作端点说明
创建品牌
POST /v3/brands
创建新品牌及相关信息。
列出品牌
GET /v3/brands
获取已认证客户的品牌列表，包括可继承的品牌（如适用）。
更新品牌
PUT /v3/brands/{brandId}
无法更新已提交至TCR的品牌或可继承品牌。
删除品牌
DELETE /v3/brands/{brandId}
删除属于已认证客户的品牌。
重试创建/更新调用时，可使用可选的
Idempotency-Key
请求头。保存API返回的Sent品牌ID。仅当API响应中包含TCR标识符时，才单独保存这些标识符。

5. Create or update Sent campaign resources

5. 创建或更新Sent活动资源

Create campaigns under the relevant Sent brand. The verified v3 API says each campaign must include at least one use case with sample messages.
OperationEndpointNotes
Create campaign
POST /v3/brands/{brandId}/campaigns
Links the campaign to the brand and requires use-case/sample-message data.
List campaigns
GET /v3/brands/{brandId}/campaigns
Retrieves campaigns and their use cases/sample messages.
Update campaign
PUT /v3/brands/{brandId}/campaigns/{campaignId}
Cannot update campaigns already submitted to TCR.
Delete campaign
DELETE /v3/brands/{brandId}/campaigns/{campaignId}
Deletes a campaign within the brand.
Do not claim a public 
tcr_campaign_id
field unless the actual response includes it. Refer to the Sent campaign ID for Sent API operations.
在对应的Sent品牌下创建活动。已验证的v3 API规定，每个活动必须包含至少一个带示例消息的使用场景。
操作端点说明
创建活动
POST /v3/brands/{brandId}/campaigns
将活动与品牌关联，需提供使用场景/示例消息数据。
列出活动
GET /v3/brands/{brandId}/campaigns
获取活动及其使用场景/示例消息。
更新活动
PUT /v3/brands/{brandId}/campaigns/{campaignId}
无法更新已提交至TCR的活动。
删除活动
DELETE /v3/brands/{brandId}/campaigns/{campaignId}
删除品牌下的活动。
除非实际响应中包含公共
tcr_campaign_id
字段，否则不要提及该字段。Sent API操作请使用Sent活动ID。

6. Complete the Sender Profile setup

6. 完成发送方资料设置

After profile data, brand, and campaign prerequisites are ready, call or trigger profile completion through 
POST /v3/profiles/{profileId}/complete
. The OpenAPI describes this as the final step in the profile compliance workflow, validating prerequisites and connecting profile configuration in the background.
If completion fails, fix the missing prerequisite rather than creating duplicate brands or campaigns. Duplicate compliance objects increase confusion and can lead to sending from the wrong profile.
在资料、品牌及活动前置条件就绪后，通过
POST /v3/profiles/{profileId}/complete
调用或触发资料提交。OpenAPI将此描述为资料合规流程的最后一步，会验证前置条件并在后台关联资料配置。
如果提交失败，需修复缺失的前置条件，而非创建重复的品牌或活动。重复的合规对象会增加混淆，可能导致从错误的资料发送消息。

7. Prepare the review-ready submission summary

7. 准备可供审核的提交摘要

End the workflow with a compact summary the user can paste into Sent support, a dashboard form, or an internal ticket. Include legal identity, website, privacy policy, opt-in URL/evidence, use-case description, sample messages, opt-out instructions, Sent profile ID, Sent brand ID, Sent campaign ID, and any unresolved questions.
Example summary.
“Acme Logistics LLC, EIN ending 1234, sends US SMS delivery notifications to customers who opt in at checkout. Website and privacy policy are live. Opt-in screenshot and URL are attached. Campaign use case is delivery notification. Sample messages match shipment status only and include opt-out instructions. Sent profile 
...
, Sent brand 
...
, Sent campaign 
...
are ready for completion.”
流程结束时，生成一份简洁的摘要，用户可将其粘贴到Sent支持工单、控制台表单或内部工单中。摘要需包含合法身份信息、网站、隐私政策、授权URL/证明、使用场景说明、示例消息、退订说明、Sent资料ID、Sent品牌ID、Sent活动ID及任何未解决的问题。
示例摘要：
“Acme Logistics LLC，税号末尾为1234，向在结账时授权的客户发送美国SMS配送通知。网站及隐私政策均有效。已附上授权截图及URL。活动使用场景为配送通知。示例消息仅包含发货状态信息，并附有退订说明。Sent资料
...
、Sent品牌
...
、Sent活动
...
已准备就绪，可提交审核。”

Common rationalizations to avoid

需避免的常见错误理由

Do not register a marketing campaign as a utility or account-notification campaign because it may be cheaper or easier. The samples, opt-in flow, and actual traffic must match.
Do not submit placeholder websites, private staging URLs, or missing privacy policies. Sent’s compliance guide calls for live URLs.
Do not reuse one brand/campaign for unrelated customers. Compliance belongs to the sender and use case, not just the platform sending the API call.
Do not edit a submitted brand or campaign in place if the API says submitted objects cannot be updated. Create the right correction path with Sent.
Do not promise exact approval times beyond Sent’s guidance. Sent says TCR registration typically completes within 3 to 7 business days after the Sent compliance form is approved, with additional propagation time possible.
不要将营销活动注册为实用型或账户通知型活动，即便这样可能更便宜或更容易。示例消息、授权流程及实际流量必须保持一致。
不要提交占位网站、私有预发布URL或缺失的隐私政策。Sent合规指南要求提供有效URL。
不要为无关客户重复使用同一品牌/活动。合规属于发送方及使用场景，而非仅属于发送API请求的平台。
如果API说明已提交的对象无法更新，不要直接编辑已提交的品牌或活动。需与Sent确认正确的修正路径。
不要做出超出Sent指导范围的审批时间承诺。Sent表示，在Sent合规表单获批后，TCR注册通常需要3至7个工作日完成，可能还需要额外的传播时间。

Verification checklist

验证清单

  • The traffic is confirmed as US A2P SMS over a long-code route.
  • Legal business identity matches tax and website evidence.
  • Website and privacy policy URLs are live.
  • Opt-in evidence is concrete and matches the declared use case.
  • Sample messages are realistic and match the use case.
  • Opt-out instructions are included where applicable and consistent with the user experience.
  • Sent brand and campaign IDs are stored separately from any provider/TCR identifiers.
  • Profile completion is run only after profile, brand, and campaign prerequisites are ready.
  • Unverified throughput, carrier, or pricing claims are not presented as Sent facts.
  • 已确认流量为通过长码路由的美国A2P SMS。
  • 合法企业身份与税号及网站证明一致。
  • 网站及隐私政策URL均有效。
  • 授权证明具体明确，与申报使用场景相符。
  • 示例消息真实可信，与使用场景相符。
  • 适用情况下已包含退订说明，且与用户体验一致。
  • Sent品牌及活动ID已与任何供应商/TCR标识符分开存储。
  • 仅在资料、品牌及活动前置条件就绪后才执行资料提交。
  • 未将未经验证的吞吐量、运营商或定价声明作为Sent的事实呈现。

Related skills

相关技能

Use 
sender-profile-architect
when deciding whether brands, tenants, departments, or use cases need separate Sender Profiles.
Use 
rcs-agent-onboarding
when 10DLC work is needed for SMS fallback from RCS.
Use 
messaging-performance-analyzer
when registered traffic still shows delivery failures or filtering symptoms.
Use 
template-builder-ui
when the customer needs reusable SMS template copy that matches the registered use case.
Use the 
sent
skill for shared Sent terminology and routing.
当决定品牌、租户、部门或使用场景是否需要独立的发送方资料时，使用
sender-profile-architect
技能。
当RCS的SMS fallback需要完成10DLC工作时，使用
rcs-agent-onboarding
技能。
当已注册流量仍出现投递失败或过滤症状时，使用
messaging-performance-analyzer
技能。
当客户需要与注册使用场景匹配的可复用SMS模板内容时，使用
template-builder-ui
技能。
如需共享Sent术语及路由，使用
sent
技能。

Bundled references and scripts

附带参考资料及脚本

FileTypePurpose
references/tcr-use-cases.md
Lookup tableTCR use-case taxonomy, sample-message patterns, and rejection reasons.
references/10dlc-evidence-checklist.md
Worked exampleField-by-field checklist for Sent's 10DLC compliance form.
references/10dlc-rejection-remediation.md
Decision matrixCommon TCR / carrier rejection codes mapped to fix steps and re-submission etiquette.
scripts/validate_10dlc_packet.py
Validation scriptPre-flight validator for a packet JSON. Run from the skill root: 
python scripts/validate_10dlc_packet.py packet.json
.
scripts/fixtures/good.json
FixtureComplete valid packet (passes validator).
scripts/fixtures/bad.json
FixturePacket with missing fields / invalid EIN / short sample (validator exits non-zero).
文件类型用途
references/tcr-use-cases.md
查找表TCR使用场景分类体系、示例消息模式及驳回原因。
references/10dlc-evidence-checklist.md
示例模板Sent 10DLC合规表单的逐项检查清单。
references/10dlc-rejection-remediation.md
决策矩阵常见TCR/运营商驳回代码对应的修复步骤及重新提交规范。
scripts/validate_10dlc_packet.py
验证脚本数据包JSON的预校验工具。从技能根目录运行：
python scripts/validate_10dlc_packet.py packet.json
。
scripts/fixtures/good.json
示例数据完整的有效数据包（可通过校验）。
scripts/fixtures/bad.json
示例数据包含缺失字段/无效EIN/短示例的数据包（校验会返回非零状态码）。

Unverified claims to confirm or remove

需确认或移除的未验证声明

  • Sent's 
    /v3/brands
    and 
    /v3/brands/{id}/campaigns
    endpoints exist; their internal mapping to TCR identifiers is opaque to the customer. Store the Sent brand and campaign IDs returned by the API — don't claim a public 
    tcr_brand_id
    or 
    tcr_campaign_id
    field unless an API response surfaces it.
  • Exact throughput limits, per-carrier caps, and vetting-score-to-throughput mapping are not in Sent's docs. The snapshot only confirms account-wide tier limits (Starter 60 msg/min, Growth 300 msg/min, Enterprise custom) — these are not TCR / carrier per-campaign throughput numbers.
  • Country-specific compliance, routing, and pricing claims beyond Sent's listed country-specific document requirements (AU, BE, PL, ZA, SE, TH, UK) require a current Sent source.
  • Sent的
    /v3/brands
    和
    /v3/brands/{id}/campaigns
    端点确实存在；它们与TCR标识符的内部映射对客户不透明。保存API返回的Sent品牌及活动ID——除非API响应中显示公共
    tcr_brand_id
    或
    tcr_campaign_id
    字段，否则不要提及这些字段。
  • 确切的吞吐量限制、各运营商上限及审核分数与吞吐量的映射关系未在Sent文档中提及。当前仅确认了账户级别的 tier 限制（Starter 60条/分钟，Growth 300条/分钟，Enterprise 自定义）——这些并非TCR/运营商的单活动吞吐量数值。
  • 除Sent列出的特定国家文档要求（AU、BE、PL、ZA、SE、TH、UK）外，其他国家的合规、路由及定价声明均需提供最新的Sent来源。