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

Follow the sending guide with a regional API key, an enabled US destination and a suitable US sender. Send to the documented sandbox recipient +15005550006 to exercise delivery events without contacting a real recipient. A message to your own phone is a real send.

Send messages, receive replies, manage senders and destinations, and inspect delivery outcomes. The product hub connects number types, registration, campaigns, analytics and the corresponding setup guides.

Use the destination catalogue to check current coverage, sender types and registration requirements. Enable the destination in your workspace before sending; coverage alone does not complete your sender setup.

US application-to-person messaging from local ten-digit numbers uses 10DLC brand and campaign registration. Toll-free and short-code programs have their own requirements. Choose the sender type first and follow its registration guide.

Campaign describes the marketing job: audience, content, timing and measurement. A broadcast is the sending resource that manages one audience send. The dashboard and Broadcast API are ways to operate that workflow.

Use individual SMS sends for application-triggered notifications. Use a campaign for a coordinated audience send with shared content, scheduling and progress. A batch of independent SMS requests is a different operation.

Yes. A contact can carry phone and email identifiers and shared properties. Channel eligibility, consent and suppressions still determine which messages that person can receive.

No. Standard SMS does not report opens. Delivery receipts, replies, configured link clicks and connected conversion events answer different questions and should be reported separately.

Use an agent to prepare and operate the workflow through Bird’s supported tools and workspace permissions. Review the recipients and message, and authorize the sending action as part of your process.

A batch contains up to 100 independent SMS messages. A broadcast targets an audience with shared content and manages preparation, scheduling, progress and recipient outcomes.

Membership is resolved when the scheduled send starts. A person added or removed before then can change that send’s audience. Inspect the resulting recipient snapshot when investigating the campaign.

Cancellation stops work that has not yet been submitted. Messages already handed to a carrier cannot be recalled, so inspect the recipient outcomes after cancellation settles.

Start with delivery counts and failures. Use separately configured reply, click and conversion signals to measure the action the campaign was intended to produce. Standard SMS does not produce an open event.

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.

A short brand string shown in the SMS sender field instead of a phone number. It is an identity you claim and register where required, rather than a reply-capable number.

No. Use a number with SMS capability when the workflow needs replies. Prepare the appropriate opt-out mechanism for the campaign and destination.

Only where the destination permits that sender and no required registration remains. Enable the destination and inspect the sender’s country requirements before launch.

Toll-free messaging uses a separate verification program. Choose a number with SMS capability and complete toll-free verification for the intended use case.

No. Approval establishes eligibility for the program. Message content, recipient availability, suppressions and carrier conditions still affect delivery.

An SMS-capable toll-free number can support replies where the destination and carrier allow them. Subscribe to inbound events and review the relevant keyword handling.

A 10DLC is a ten-digit long code used for application-to-person messaging in the US under a registered brand and campaign. Long-code numbering and registration differ in other countries.

No. Check the capabilities on the specific number. Some local numbers support voice without SMS, so filter inventory for the capabilities your application requires.

Throughput depends on the destination, carrier and registration program. Review the approved brand and campaign limits for US 10DLC traffic.

A short code is a national messaging number of four to six digits. It is used for reviewed, high-volume messaging programs and does not provide voice service.

Contact an SMS specialist to review the destination, use case and program requirements. Bird allocates short codes; the self-service numbers ordering API does not sell them.

Short codes are national. Check the local program for each market rather than treating one code as a global sender.

For a free-text send, provide a sender your workspace can use in the destination and the appropriate message category. A system-template send resolves its category and sender from the template.

Provide an idempotency key and reuse it for a retry of the same request. A send without that key can be treated as a new message.

No. A 202 response means the API accepted the request. Follow the message record and signed events for the carrier-reported outcome. A delivery receipt does not establish that the recipient read the text.

A batch contains up to 100 independent messages, each with its own recipient and body. A broadcast is an audience campaign with shared content and a managed send lifecycle. Choose the workflow that matches your job.

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.

Open the destination catalogue and review the sender types and registration requirements for each market. Your workspace must also allow the destination before a send is accepted.

It reports a delivery outcome from the carrier. Receipts can arrive after acceptance, and the message record may still be pending. Delivery does not measure whether someone read or acted on a text.

Start with the message status and failure reason. Compare reporting by carrier, country or sender, then check registration and destination configuration. An aggregate failure rate alone does not identify the cause.

Use Lookup when your application needs phone-number intelligence before sending. Review the signals and availability for that lookup rather than treating an SMS delivery report as a complete number check.

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.

A US long code uses 10DLC for application-to-person messaging. Toll-free messaging has a separate verification program. Other country registrations depend on the sender and destination. Read the requirements for the sender you plan to use.

No. Sender registration, customer permission and current opt-out status are separate checks. Preparing an approved sender does not grant permission to message every contact.

Read its country requirements, registration status and whether the destination is enabled. Complete the next actions Bird reports before launching the traffic.

No. Claiming creates the brand identity in the workspace. Country registration establishes whether that sender is approved for the destination that requires it.

Read whether registration is required, its status, whether the destination is enabled and any next actions. Having an approved sender does not turn on a disabled destination.

Review the estimate published for the country when one is available. External review and requested corrections can affect timing; use status rather than an assumed launch date.

The brand identifies the business. A campaign declares a use case under that brand. Link the sending numbers to an approved campaign before using them for US application-to-person traffic.

The registered use case cannot be changed. Prepare a new campaign when the use case changes, and review the requirements and charges before submitting.

No. Complete campaign approval, link the number and enable the destination. A public-company brand also has an Auth+ requirement before campaign registration.

Toll-free messaging follows its own verification program. 10DLC applies to US long-code application-to-person messaging.

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.