# IntelliSend
> Business SMS for Australian teams. Send with IntelliSend, manage campaigns and two-way replies, and connect your applications through SMS APIs and OTP.
Official public information about IntelliSend. Consult the linked pricing and product pages for current plans, availability and limits. API documentation is hosted separately at docs.intellisend.io.
## Platform
- [Business SMS Provider Australia | IntelliSend](): Send business SMS across Australia with IntelliSend. Run campaigns, reply to customers and connect your applications with SMS APIs, OTP and webhooks.
- [About IntelliSend | SMS for Australian Businesses](): Meet IntelliSend Technologies Pty Ltd, an Australian company bringing SMS sending, campaigns, conversations and developer tools into one workspace.
- [Book an Australian Business SMS Demo | IntelliSend](): Explore IntelliSend SMS for your Australian business, with campaigns, Inbox, developer tools and team workflows in a personalised product demo.
- [Careers – IntelliSend](): Learn how IntelliSend approaches dependable messaging work and check whether any roles are currently open.
- [Contact IntelliSend | Australian Business SMS](): Contact IntelliSend about product questions, demos, account support, billing, integrations, or security.
- [Australian Business SMS Workflows | IntelliSend](): Explore SMS workflows for Australian businesses, from café offers and appointment reminders to customer service, order updates and verification.
- [Frequently Asked Questions – IntelliSend](): Find answers about IntelliSend setup, SMS sending, provider routing, workspace controls, pricing and support.
- [SMS Features for Australian Businesses | IntelliSend](): Explore business SMS for Australian teams: campaigns, two-way Inbox, SMS API, OTP, MCP, provider routing, reporting and branded workspaces.
- [SMS Provider Integrations Australia | IntelliSend](): Send with IntelliSend or connect supported SMS and email provider accounts. Explore provider capabilities, senders, delivery receipts and routing options.
- [SMS Pricing Australia: Free, Business & Enterprise | IntelliSend](): Compare SMS plans for Australian teams. Business: AUD 39/month or AUD 390/year, 500 SMS credits each month. Try Business for 30 days.
- [Privacy Policy – IntelliSend](): How we collect, use, and protect your data at IntelliSend. We take your privacy and data security seriously.
- [IntelliSend Blog](): Practical articles on business SMS, campaign operations, provider routing, contact hygiene, opt-outs and delivery reporting.
- [IntelliSend Guides](): Explore IntelliSend setup guides for SMS sending, campaigns, provider connections and imports, plus developer API, OTP and MCP resources.
- [Feature Requests – IntelliSend](): Explore published customer ideas for IntelliSend business messaging. Share product feedback and feature requests from your workspace.
- [Workspace Security – IntelliSend](): Review tenant isolation, role-based access, OTP, rate limiting, protected provider credentials, verified callbacks, opt-outs, and auditability.
- [Developers](): SMS API, OTP, signed webhooks and MCP overview.
- [Sender ID registration](): Business-name Sender ID setup and registration guidance.
- [Our team](): The team behind IntelliSend.
## Products
- [SMS API](): Send SMS from your backend with scoped keys, safe retries and delivery events. Accepted or queued does not mean delivered. Delivery receipts depend on the provider. Production API access is subject to your plan and permissions.
- [Two-way SMS Inbox](): Read and reply to customer messages using an eligible reply-capable number. Business-name Sender IDs cannot receive replies. A shared number can match a recipient’s reply to the latest outbound message across workspaces; use an assigned dedicated number when direct routing is required.
- [OTP verification](): Create reusable SMS verification services and check one-time codes through the API. OTP uses one provider and sender per service, with no automatic failover. Codes expire and verification attempts are limited. Provider acceptance does not confirm handset delivery.
- [MCP & AI](): Access SMS reports and optional messaging tools from an authorised AI client. MCP must be enabled for your installation. Reporting is the default; messaging needs additional consent and can spend credits. Confirm recipients and message details in your client before sending. MCP cannot send or verify OTPs or change workspace settings.
- [Teams & workspaces](): Organise contacts, messaging and team access within each business workspace. Member, team, provider and domain limits vary by plan. Roles apply only within their own business workspace. Scheduled messages use the workspace’s saved timezone.
- [Custom domains](): Give your workspace a branded address with DNS and SSL verification. Custom domains require an eligible plan; Business currently includes one. This connects an existing domain to your workspace—it does not register, sell or park domains.
## Industry use cases
- [Industries](): SMS workflows for Australian businesses.
- [Retail & ecommerce](): Give shoppers useful updates before, during and after a purchase. Bring opted-in campaigns, collection messages and customer replies into your team's working day. Order-triggered messages need an integration from your store to the SMS API. You can also send individual updates or prepare campaigns directly in IntelliSend.
- [Cafés & hospitality](): Keep regulars close with timely offers, booking updates and clear answers. Make every message feel like it came from the people behind the counter. Start with your existing opted-in contacts and reusable templates. Booking or ordering software can trigger messages through an integration with the SMS API.
- [Health & wellness](): Help people remember the next visit and give your team a clear place to handle replies. Use practical appointment details that customers can act on. Appointment-based triggers need a booking-system integration. Replies arrive in IntelliSend; your team or integration remains responsible for updating the booking record. Keep sensitive details in your established secure channels.
- [Software & platforms](): Connect SMS updates and one-time verification codes to the actions in your application. Give your backend a clear path from request to message status. Keep API keys on your server and use the permissions your integration needs. An accepted send is not a delivery confirmation. OTP code length, expiry, provider and sender are configured per service.
- [Trades & services](): Keep customers informed while your team is on the tools. Share visit details, service changes and collection updates without losing track of the conversation. Use Quick SMS for day-to-day changes. Job-management software can trigger updates through the SMS API when an integration is configured; IntelliSend does not track staff or vehicle locations.
- [Logistics & delivery](): Give recipients the information they need for a handover. Send delivery windows, collection instructions and changes from your operational workflow. Delivery times, tracking links and order status must come from your logistics system. Connect those events through the SMS API, then use supported delivery receipts to follow the SMS itself.
- [Real estate & property](): Help people keep track of inspections, access arrangements and maintenance visits. Give your property team one place to follow up on customer messages. Use SMS for practical reminders alongside your existing property workflow. Property records, formal notices and access decisions remain in your established systems.
- [Education & training](): Make course reminders, room changes and enrolment follow-up easy to act on. Share practical information without asking people to search through a long email thread. Keep enrolment and learning records in your existing system. Pass session events through an integration, or send reminders from contact groups in IntelliSend.
## Blog
- [How Multi-Provider SMS Failover Prevents Delivery Outages](): A practical look at reducing provider dependency with ordered routes, observable failures, and tested backup connections.
- [Single, Round-Robin, and Failover SMS Routing Explained](): Choose a routing model based on campaign intent instead of applying one provider strategy to every message.
- [SMS Campaign Analytics That Improve Delivery Decisions](): Turn campaign status, provider distribution, delivery events, usage, and cost into operational improvements.
- [Contact Hygiene, Opt-Outs, and Responsible SMS Operations](): Build safer audiences with validated imports, explicit marketing status, and provider-aware opt-out handling.
- [Designing a Reliable SMS Campaign Lifecycle](): A practical campaign workflow from draft and audience selection through scheduling, sending, and post-send review.
- [Provider Health, Balance, and Routing Readiness](): What to inspect before a provider becomes the primary route for an important SMS campaign.
- [When to Use SMS Templates, Quick Send, or a Campaign](): Choose the smallest sending workflow that preserves the review, reuse, and reporting your message needs.
- [A Safer CSV Contact Import Workflow for SMS Teams](): Map, validate, preview, and correct audience data before it reaches a campaign.
- [SMS Delivery Receipts, Webhooks, and Message Logs](): Understand how provider callbacks and status polling become traceable delivery state inside IntelliSend.
- [Designing Secure Multi-Tenant SMS Workspaces](): How workspace isolation, permissions, server-side provider clients, and audit trails reduce operational risk.
## Guides
- [Connect an SMS Provider and Send a Quick Message](): Set up a supported provider connection, validate it, and complete a controlled first send.
- [Build and Schedule an SMS Campaign](): Prepare an audience, select a template and route, schedule the send, and review its lifecycle.
- [Configure and Test a Failover Route](): Create an ordered provider recovery path and prove that each connection can send before production use.
- [Import Contacts and Manage Opt-Outs](): Create a contact group, map a CSV safely, resolve invalid rows, and preserve recipient status.
## Developer documentation
- [API documentation](): Official API setup, authentication, message sending and delivery events.
## Optional
- [Sitemap](): Index of public canonical pages and articles.