THE SMS PLATFORM # Business SMS. A clear path to every message. Send appointment reminders, run opted-in campaigns or handle customer replies. Choose the SMS workflow that fits your business, then set up its sender and destinations. [Start now](/dashboard/signup?returnTo=%2Fdashboard%2Fw%2Fsms%2Fonboarding) [Talk to sales](/demo?product=sms&source_page=%2Fsms) CHOOSE THE CUSTOMER JOB ## One channel. Three different workflows. The same SMS API can serve different messages. Start with the job, then check eligibility and local sender rules before an integration choice. [Today · 9:41 Your studio visit is tomorrow at 14:00. Booking FN–1042. Illustrative service update · delivery is observed separately.](/sms-api#showcase) 01 ### [Notifications ↗](/sms-api#showcase) Send a timely booking, account or service update from your application. Consent and message category still matter. [Today · 9:41 Fieldnotes studio: The autumn workshops are open. See available dates in your account. Illustrative opted-in campaign · sender and consent checked before sending.](/products/sms/marketing) 02 ### [Campaign messages ↗](/products/sms/marketing) Plan a permissioned audience, suppress withdrawals and review segments and timing before a supported send. [Today · 9:41 Can we move booking FN–1042 to Friday? We’ll check with the studio and reply here.](/products/sms/two-way) 03 ### [Two-way conversations ↗](/products/sms/two-way) Receive a reply on a supported number, verify the event and let your application confirm the customer task. Need a one-time code? [Verify](/verification-api) owns code creation, attempts, expiry and checks. Need number evidence? [Lookup](/lookup) can return signals, but it does not establish ownership or consent. [Open the SMS API example ↗](/sms-api#implementation) BIRD / SMS Illustrative experience Bird / SMS FROM YOUR APPLICATION ### A thoughtful reminder. Your message Short reminder Add an emoji Enter a nonblank message estimated at 12 segments or fewer. To Alex · +1 555 000 0142 Sender Your supported number Preview delivery ↗ Text Message • SMS Yesterday 3:18 PM You’re booked, Alex. Your studio visit is confirmed for Friday at 14:00. FN–1042. Lovely. Looking forward to it! Today 10:42 AM Follow the message Example · no request is made 01 / Acceptance 02 / Carrier handoff 03 / Receipt or incoming evidence Local illustration. No request is made. Inspect the message outcome ↗ Text Message • SMS Yesterday 3:18 PM You’re booked, Alex. Your studio visit is confirmed for Friday at 14:00. FN–1042. Lovely. Looking forward to it! Today 10:42 AM Your application SAME CUSTOMER / NEXT MOMENT Customer Alex Lee Booking FN–1042 · Tomorrow, 14:00 Event Text Message • SMS Yesterday 3:18 PM You’re booked, Alex. Your studio visit is confirmed for Friday at 14:00. FN–1042. Lovely. Looking forward to it! Today 10:42 AM Thank you. See you there! Write the message Follow delivery Continue the conversation Replay ↺ Example content and data. Explore the workflow below; nothing is sent or changed in a live account. Companies that trust Bird across their communications. - [Airwallex](/customers/airwallex) - Uber - [Zillow](/customers/zillow) - [Glovo](/customers/glovo) - PayPal - Adobe [Read Bird customer stories](/customers) BEFORE YOUR FIRST SEND ## Resolve the destination, then the sender. 01 / DESTINATION ### Check the country you will reach. Enable each destination in your workspace allowlist. Sender types, registration, message categories and reply support vary by country. The [current destination details](/products/sms/destinations) is the authority; [Netherlands](/products/sms/destinations/netherlands) and [United States](/products/sms/destinations/united-states) are examples to inspect there, not a substitute for current approval or account access. [Explore three country examples ↗](/products/sms/destinations) 02 / SENDER & REPLY ### Choose an eligible sending identity. Read the [sender guide](/docs/guides/sms/senders) for number or sender ID selection and registration. A displayed name cannot receive replies; a two-way workflow needs a supported receiving number and an application path for inbound messages. [Read sender setup ↗](/docs/guides/sms/senders) ### The details behind your setup #### Consent and category Separate service updates from opted-in campaigns. Keep permission, preference and opt-out decisions in your application. #### Integration mode The [SMS API example](/sms-api#implementation) shows the request path; the [local outcome example](/sms-api#experience) distinguishes acceptance, a final receipt, no receipt and a reply. #### Delivery and cost Encoding can turn a draft into several billable segments. Estimate in the [SMS composer](/sms-api#showcase) , then read [character limits](/docs/guides/sms/character-limits) and [current destination rates and fees](/pricing/sms) . A COMPLETE STARTING PATH ## From a useful message to a supported rollout. [Start now](/dashboard/signup?returnTo=%2Fdashboard%2Fw%2Fsms%2Fonboarding) [Talk to sales](/demo?product=sms&source_page=%2Fsms) 01 [Choose your destinations ↗ Review three dated country examples, then confirm allowlist, category, sender and reply support in current details.](/products/sms/destinations) 02 [Estimate and build ↗ Try the local segment estimator, then open the SMS API implementation and maintained sending guide.](/sms-api#showcase) 03 [Follow the result ↗ Keep the message ID and observe later carrier outcomes. A receipt is not proof of reading or booking success.](/docs/guides/sms/events) LEARN / BUILD / OPERATE ## The next answer, within reach. [SMS RESOURCE LIBRARY Find a task you can finish. Start, build, diagnose, migrate or evaluate with current guides, references and tools. Explore SMS resources →](/sms/resources) [01 Run your first SMS Prepare your sender, run a complete Node.js example and read the outcome. ↗](/docs/get-started/send-your-first-sms) [02 Send and follow an SMS Use the maintained sending contract and follow its result. ↗](/docs/guides/sms/sending-sms) [03 Use the SMS segment calculator Check a standalone message draft, character map and smart encoding before reviewing rates. ↗](/tools/sms-segment-calculator) [04 Try the API message composer Preview a message and segment estimate in the local SMS API story. ↗](/sms-api#showcase) DESTINATION / SEGMENT / SENDER ## A clear plan for each market. SMS is charged per segment, with rates and fees depending on destination and sender. The composer estimates encoding and segment count; it is not a worldwide quote. Confirm registration, coverage or volume with our team. [Start now](/dashboard/signup?returnTo=%2Fdashboard%2Fw%2Fsms%2Fonboarding) [Talk to sales](/demo?product=sms&source_page=%2Fsms) [Check current SMS rates ↗](/pricing/sms) YOUR SMS SETUP Destination first Decide the use case, then check the maintained rules for every market. Send Country allowlist, eligible sender and message category. Reply Supported two-way number and inbound application handling. Cost Encoding, billable segments, destination rates and applicable fees. [Current destination requirements ↗](/products/sms/destinations) A FEW USEFUL ANSWERS ## Business SMS, answered. ### Can every sender receive replies? No. Reply support depends on destination and sender type. Use a supported two-way number and route incoming messages into your application. [Read sender setup.](/docs/guides/sms/senders) ### Should I use SMS API for login codes? [Verify](/verification-api) owns the separate verification lifecycle: code creation, attempts, expiry and checking. A normal SMS send does not supply those controls. ### Does one SMS mean one billable segment? No. GSM-7 extension characters and Unicode can change encoding and length; multipart messages reserve header space. [Estimate segments](/sms-api#showcase), then check [current rates](/pricing/sms). YOUR NEXT CONNECTION ## Make the next message fit the moment. [Start now](/dashboard/signup?returnTo=%2Fdashboard%2Fw%2Fsms%2Fonboarding) [Talk to sales](/demo?product=sms&source_page=%2Fsms) [Explore the SMS resource library ↗](/sms/resources)