Answers for sending SMS, running campaigns, and registering numbers.

按照发送指南，使用区域 API 密钥、已启用的美国目的地和合适的美国发送方。向文档中的沙箱接收号码 +15005550006 发送消息，以触发送达事件而不联系真实收件人。向你自己的手机发送消息属于真实发送。

发送消息、接收回复、管理发送方和目的地，以及查看送达结果。产品中心连接号码类型、注册、活动、分析和相应的设置指南。

使用目的地目录检查当前覆盖范围、发送方类型和注册要求。发送前在工作区中启用目的地；仅有覆盖范围不等于完成发送方设置。

从美国本地十位号码发送应用到个人的消息需要 10DLC 品牌和活动注册。免费号码和短码项目有各自的要求。先选择发送方类型，然后按照其注册指南操作。

营销活动描述的是营销任务：受众、内容、时间安排和效果衡量。群发是管理一次受众发送的发送资源。控制面板和 Broadcast API 是操作该工作流的方式。

对应用触发的通知使用单条 SMS 发送。对需要共享内容、排期和进度跟踪的协调受众发送使用营销活动。一批独立的 SMS 请求是另一种操作。

可以。一个联系人可以同时拥有电话和邮箱标识以及共享属性。渠道资格、许可和抑制规则仍决定该联系人能接收哪些消息。

不会。标准 SMS 不报告打开事件。送达回执、回复、已配置的链接点击和关联的转化事件回答的是不同问题，应分别报告。

使用智能体通过 Bird 支持的工具和工作区权限来准备和执行工作流。审核收件人和消息内容，并在流程中授权发送操作。

批量发送包含最多 100 条独立的 SMS 消息。群发针对一个受众发送共享内容，并管理准备、排期、进度和收件人结果。

成员资格在定时发送启动时确定。在此之前添加或移除的人会改变该次发送的受众。调查营销活动时，可查看生成的收件人快照。

取消会停止尚未提交的工作。已移交给运营商的消息无法撤回，因此请在取消完成后检查收件人结果。

从送达数量和失败数量入手。使用单独配置的回复、点击和转化信号来衡量营销活动预期产生的行动。标准 SMS 不会产生打开事件。

You pay per message segment based on the destination country and the sender type you use, so sending from a US 10DLC number has a different rate than sending from a UK alphanumeric sender ID. You can look up published rates by country and sender type on the SMS pricing page.

Carriers meter and bill SMS by the segment. A single segment holds up to 160 standard GSM-7 characters, or 70 characters if an emoji or non-Latin symbol switches the message to Unicode. Messages that exceed those limits split into multiple billable segments and reassemble as one text on the recipient's phone, so trimming a few characters or swapping out an emoji can cut a campaign's cost in half.

Mobile networks in some countries add a per-segment carrier surcharge that varies by operator. In the US, 10DLC sending also includes one-time brand vetting and recurring campaign registration pass-through fees. You can check the full schedule by country on the SMS carrier fees page.

Open the SMS message log to inspect the exact segment count and billed cost for any individual message, or use the analytics dashboard to track total accepted volume, segment usage, and spend across a date range.

A standard GSM-7 message fits 160 characters in a single segment, or 153 characters per segment when split across a longer multipart message. Adding an emoji or non-Latin character switches the message to Unicode encoding, which fits 70 characters in a single segment or 67 per multipart segment. Because emojis and certain symbols take up multiple encoding units, check the segment counter before launching a campaign.

You can send messages up to 12 segments long in a single SMS request, which works out to 1,836 standard GSM-7 characters or 804 Unicode characters. Messages exceeding 12 segments are rejected at submission, so preview your template with live merge fields to confirm the encoded segment count stays within bounds.

A single batch API call can send up to 100 individual messages, each with its own recipient and custom text. For larger marketing sends to thousands of subscribers, launch a campaign broadcast so Bird handles audience segmentation, pacing, and opt-out filtering automatically.

Single-message sends and batch sends have separate API rate limits determined by your SMS plan tier. Upgrading your plan increases both limits, and each API response includes rate-limit headers showing your remaining capacity so your application can pace requests smoothly. API request limits govern how fast you submit to Bird, while carrier throughput governs how fast mobile networks accept messages from your sender number.

Outbound delivery speed depends on your sender type, destination country, and registration status. For example, dedicated short codes and high-trust 10DLC campaigns deliver large broadcasts faster than standard local numbers. Bird queues your accepted messages and paces delivery to match the throughput allowed for your registered sender.

Match your number type to your destination market and messaging volume. Local 10DLC numbers and toll-free numbers support two-way messaging in North America, alphanumeric sender IDs provide recognizable brand names for one-way alerts in supported international markets, and short codes handle high-volume bursts. When browsing inventory, check each number's supported capabilities to confirm it carries SMS, voice, or both.

In regulated markets, you need to complete sender registration before live traffic can go out on a newly purchased number. For instance, US 10DLC numbers require brand and campaign approval, and US or Canadian toll-free numbers require verification. You can buy the number and build your integration right away, then start live sending as soon as registration clears.

Short codes are provisioned through our telecom specialists because mobile carriers review each application, message flow, and opt-in process individually. Contact our team with your target country, expected volume, and sample messages, and we will guide your application through carrier approval.

Yes, many local and toll-free numbers support both SMS and voice calls on the same line. Filter the number catalog for both capabilities when purchasing so customers can text or call back the same number.

在 SMS 发送方字段中显示的简短品牌字符串，用于替代电话号码。它是你声明并在需要时注册的身份标识，而不是可接收回复的号码。

不能。当流程需要接收回复时，请使用具有 SMS 功能的号码。为活动和目的地准备适当的退订机制。

仅当目的地允许该发送方且不再有未完成的必要注册时才可以。启用目的地并在上线前检查发送方的国家/地区要求。

免费号码消息使用单独的验证流程。选择具有 SMS 功能的号码，并为预期用例完成免费号码验证。

不保证。审批只是确立了参与该计划的资格。消息内容、接收方可用性、抑制规则和运营商条件仍会影响送达。

具有 SMS 功能的免费号码在目的地和运营商允许的情况下可以支持回复。请订阅入站事件并查看相关的关键词处理规则。

10DLC 是一种十位长码，用于在美国以注册品牌和活动身份发送应用到个人的消息。长码编号和注册方式在其他国家/地区有所不同。

不一定。请检查特定号码的功能。部分本地号码仅支持语音而不支持 SMS，因此请按你的应用所需功能筛选号码库存。

吞吐量取决于目的地、运营商和注册计划。请查看美国 10DLC 流量的已批准品牌和活动限额。

短号码是四到六位数字的国内消息号码，用于经过审核的大批量消息计划，不提供语音服务。

联系 SMS 专家审核目的地、使用场景和计划需求。Bird 分配短号码；自助号码订购 API 不出售短号码。

短号码是国内号码。请查看每个市场的本地计划，而不是将一个号码当作全球发送方。

对于自由文本发送，请提供你的工作区可在该目的地使用的发送方以及相应的消息类别。系统模板发送会根据模板自动确定类别和发送方。

提供一个幂等键，并在重试同一请求时复用它。没有该键的发送可能被视为新消息。

不是。202 响应表示 API 已接受该请求。通过消息记录和签名事件跟踪运营商报告的结果。投递回执并不能证明收件人已阅读短信。

一个批量包含最多 100 条独立消息，每条有自己的收件人和正文。群发是面向受众的营销活动，共享内容并具有托管的发送生命周期。请选择与你的需求匹配的工作流。

When a customer texts your two-way Bird number, Bird sends a signed inbound message webhook to your server with the customer's phone number, the receiving Bird number, and the message body. Verify the webhook signature in your handler, then route the reply into your support inbox, application workflow, or AI agent.

Send your outbound response from the same Bird phone number the customer texted, addressed to their mobile number. Because mobile phones group SMS threads by the sender and recipient number pair, keeping the same two-way number preserves a single continuous conversation on the customer's handset.

In countries with built-in keyword handling, texting STOP automatically adds the recipient to your suppression list for that sender number and sends a compliant confirmation reply. Future sends from that number to that recipient are blocked automatically. In markets where network-level keyword handling does not apply, handle inbound opt-out replies through your webhook integration.

A keyword STOP reply blocks messages between that specific recipient and the sender number they texted. That lets a customer opt out of a promotional number while still receiving transactional alerts from a separate number. If you want a single opt-out to block messages across your entire workspace, update the contact's workspace-wide subscription preference.

No. Alphanumeric sender IDs support outbound one-way messages such as alerts and verification codes, and recipients cannot reply directly to a brand name on their handset. If your workflow needs customer replies, send from a two-way local 10DLC number, toll-free number, or short code, or include a reply link or support number in the message text.

打开目的地目录，查看每个市场的发送方类型和注册要求。你的工作区还必须启用该目的地，发送请求才会被接受。

它报告来自运营商的投递结果。回执可能在请求被接受后才到达，消息记录可能仍处于待处理状态。投递成功并不代表收件人已阅读或响应了短信。

从消息状态和失败原因入手。按运营商、国家或发送方对比报告，然后检查注册和目的地配置。仅凭汇总失败率无法定位原因。

如果你的应用在发送前需要电话号码情报，请使用 Lookup。查看该查询可用的信号和覆盖范围，而不是将 SMS 投递报告当作完整的号码检查。

Your delivery rate divides carrier-confirmed deliveries by the total messages Bird accepted during your selected time range. Because mobile carriers return delivery receipts asynchronously, recently sent messages may stay pending for a short window until the handset responds.

The failure rate combines messages that bounced as undelivered, failed at the carrier, or expired before reaching the handset. Messages rejected before carrier handoff, such as sends to opted-out numbers, are tracked in a separate rejected metric so carrier delivery performance stays distinct from list hygiene.

Yes. You can group delivery metrics by mobile carrier, destination country, or sender number in the dashboard and analytics API to spot network-specific drops. Each breakdown aggregates one dimension at a time, so inspect individual message logs when you need to cross-reference a specific carrier inside a single country.

Standard SMS carrier receipts confirm that a message reached the recipient's phone, whereas handset read status stays private to the device. To measure engagement and conversions after delivery, include tracked links with UTM parameters in your message body and record visits in your web or app analytics.

Yes. Open any message in the SMS log to view its full delivery timeline, from API acceptance and carrier handoff to the final delivery receipt or error code. You can also stream real-time status updates to your own application using delivery webhooks.

Yes. When a recipient texts a supported opt-in keyword such as START to your number, Bird clears the keyword suppression for that sender and recipient pair so messages can flow again. If the contact was suppressed manually or opted out through workspace-wide preference settings, update those records directly in the dashboard or API before resuming sends.

You can check whether a phone number is opted out for a specific sender in the dashboard or through the suppressions API while building your audience list. Bird also checks active suppressions and workspace consent preferences automatically when you submit a message, blocking sends to opted-out recipients before they reach the carrier.

美国长码使用 10DLC 进行应用到个人的消息发送。免费号码消息有单独的验证流程。其他国家/地区的注册取决于发送方和目的地。请阅读你计划使用的发送方的相关要求。

不能。发送方注册、客户许可和当前退订状态是三项独立的检查。准备好已批准的发送方并不意味着有权向每个联系人发送消息。

查看其国家/地区要求、注册状态以及目的地是否已启用。在发送流量之前，完成 Bird 报告的后续操作。

不是。声明是在工作区中创建品牌身份。国家注册则确定该发送方是否被批准用于有此要求的目的地。

查看是否需要注册、注册状态、目的地是否已启用以及后续操作。发送方已获批并不会自动启用已禁用的目的地。

查看该国家发布的预估时间（如有）。外部审核和要求的更正可能影响时间；请以状态为准，而非假定的上线日期。

品牌标识企业身份。活动在该品牌下声明一个用例。在将发送号码用于美国应用到个人 (A2P) 流量之前，需将其关联到已批准的活动。

已注册的用例无法更改。当用例发生变化时，请创建新活动，并在提交前审核相关要求和费用。

不是。还需完成活动审批、关联号码并启用目的地。上市公司品牌在注册活动前还需满足 Auth+ 要求。

免费号码消息有自己的验证流程。10DLC 适用于美国长号码的应用到个人消息。

API requests between your application and Bird are encrypted in transit over HTTPS, and webhook deliveries to your server use HTTPS as well. Once a message reaches the mobile network, standard SMS travels over carrier protocols without end-to-end encryption and remains readable to the telecom operator and on the recipient's lock screen. Avoid placing full passwords, payment details, or sensitive health data directly in an SMS body; send a short-lived verification code or a secure portal link instead.

Bird signs webhook requests with an HMAC signature tied to your endpoint's signing secret. Verify that signature on your server before processing an inbound reply or delivery receipt, and rotate the signing secret from the dashboard whenever your security policy requires it.

Your message logs and account data stay in the US or EU hosting region you selected when creating your organization. Because your API key encodes your workspace region automatically, the Bird SDKs and CLI route requests to the matching regional endpoint without manual URL configuration.

Each API key is restricted to the specific products and permission levels you assign when creating it. You can scope a key strictly to sending SMS so a compromised service cannot read billing records, modify account settings, or access other channels.

Yes to both. You can attach an IP allowlist using CIDR ranges to any API key so Bird blocks requests from unrecognized networks. When rotating a key, you can keep the previous key active for a configurable grace period (24 hours by default, or zero for immediate revocation) so you can update production services without dropping traffic.

Yes. The workspace audit log records configuration and security events, showing which team member or API key made the change, what resource was updated, and when it happened. For individual message delivery history, inspect the SMS message logs.

Download compliance certifications and security reports from the Bird Trust Center at trust.bird.com, and review our data processing agreement, privacy statement, and acceptable use policy at bird.com/legal. If your procurement team needs a custom security questionnaire completed, contact your Bird account team.