A familiar message API.
Submit a message, receive a stable Boundry ID, and follow each recipient through queued, sent, delivered, failed, or blocked states without exposing provider identifiers as your contract.
Boundry SMS is coming to Sydney. The product is being built around the whole message trail: content, phone numbers, delivery events, queues, logs, and replies.
Illustrative preview · not generally available.
A local carrier route is not a regional product by itself. The API, processing, message history, provider events, consent records, and operational logs all need a clear home.
Submit a message, receive a stable Boundry ID, and follow each recipient through queued, sent, delivered, failed, or blocked states without exposing provider identifiers as your contract.
Keep message content, phone numbers, delivery receipts, suppressions, and retention jobs attached to the project’s selected region instead of a global messaging account.
Dedicated numbers will turn inbound replies into project-local conversations with stable message IDs, consent handling, and a complete chronological record.
Read what is documented for Boundry Email today. SMS is held to the same evidence standard, and it is not generally available until that evidence exists.
Read the Sydney manifestBoundry Email is available in Sydney today. SMS will open only after the sending, receiving, registration, and retention paths meet the same standard.