How can we help you?

IntelliSend is a multi-provider SMS operations platform built around the working SMSHub application. It brings provider connections, campaigns, contacts, templates, routing, delivery reporting, and team administration into one organization workspace.

It is designed for teams that send operational, transactional, or campaign SMS and need clearer provider control, delivery visibility, and a safer alternative to relying on one provider connection.

You can send directly with IntelliSend SMS or connect TouchSMS, ClickSend and SMSGlobal. Available sender IDs, delivery reports and routing controls depend on the provider connection and your plan.

Yes. A workspace can connect multiple provider accounts and use them in single-provider, round-robin, or failover campaign routes.

Yes. Quick SMS provides a shorter send flow for individual messages while campaigns handle reusable audiences, templates, scheduling, and reporting.

Yes. Team members with the required permission can create and manage SMS templates, then select them during campaign or quick-send workflows.

Contacts can be organized in groups and imported from CSV. The import workflow supports field mapping, preview, validation status, and follow-up corrections before a group is used for sending.

Yes. The campaign builder includes scheduling, and scheduled sends are visible alongside other workspace activity in the campaign and calendar views.

Campaigns can use a single provider, distribute work using round-robin routing, or use an ordered failover route with primary and backup providers.

A failover route stores an ordered set of connected providers. When the active provider cannot complete a send, the campaign can continue through the next configured provider according to that route.

Yes. Failover routes are managed independently from campaigns so an approved provider order can be selected again when building future campaigns.

Round-robin routing is useful when you intentionally want to distribute messages across multiple available providers. Failover routing is better when providers have a primary and backup priority.

The application records campaign status, message delivery state, provider distribution, campaign logs, and delivery events received through provider webhooks or status polling.

Yes. Reporting screens cover campaign results as well as usage and cost data that is available from campaign and provider records.

ClickSend and SMSGlobal can send delivery-receipt callbacks to provider-specific webhook handlers. TouchSMS status can also be refreshed through its message-status endpoint.

No software can guarantee carrier delivery time. IntelliSend improves operational control by exposing provider state, delivery outcomes, and alternate routing, but final delivery still depends on provider and carrier networks.

The main application uses tenant-aware routing and authentication so organization data is resolved within the active workspace rather than a shared global view.

Yes. Role and permission checks protect campaign, contact, provider, report, billing, settings, and administration actions. Navigation also adapts to the permissions assigned to the signed-in user.

Provider requests are performed by server-side integration classes. Credentials are configured in the authenticated application and are not used to call provider APIs directly from the public landing site.

Yes. Registration, authentication, inquiry, and other public submission routes use throttling appropriate to their risk and expected traffic.

The onboarding flow guides an organization through workspace creation, profile and email setup, and the remaining account steps before operational screens are opened.

The application includes a company-selection flow so an authenticated user can choose the organization workspace they need to enter.

Yes. Organization settings include primary and hover colors, light and dark presentation controls, and custom-domain configuration.

Yes. Account activity and application log views provide traceability for workspace and messaging operations that are recorded by the backend.

New workspaces start with a 30-day Business trial and 15 trial SMS credits. Trial credits expire when the trial ends. The trial grant is one-time; moving to Free does not create a second introductory grant.

Without an active paid subscription, your workspace moves to Free. Existing data remains available to view, export or delete with your usual permissions. Paid-only features are restricted, and modules above Free limits become read-only. Reduce usage to the Free limits or upgrade to restore access.

Business is AUD 39 billed monthly or AUD 390 billed yearly. Yearly billing works out to AUD 32.50 per month and saves AUD 78 compared with twelve monthly payments. The full yearly amount is billed together.

No. Business includes 500 SMS credits for each monthly allowance period, on both monthly and yearly subscriptions. Yearly allowances are released monthly. Unused included credits expire at the end of their allowance period and do not roll over.

Sending through IntelliSend uses one credit per billable SMS segment. Longer messages and some character sets create multiple segments. Review the segment count and credit estimate before sending; a credit is not a guarantee of delivery.

IntelliSend sending uses your IntelliSend credits. Optional external provider connections use that provider account’s balance and rates and do not consume IntelliSend SMS credits. External provider charges are separate from your workspace subscription.

Check your workspace Billing area for available credit packs and their purchase terms. Availability depends on the published packs for your workspace. Included allowances, trial credits and purchased packs can have different expiry terms.

Enterprise is a custom agreement. Messaging credits, users, teams, provider capacity, routing and support are confirmed with sales before a contract is agreed. Contact us to discuss your requirements.

Organisation administrators and super administrators can manage subscriptions and payment details. Developer tools and sending actions require the relevant role permissions and API token scopes. Production API access requires Business access, including during the Business trial. MCP also requires enablement, authorisation and consent.

Existing subscriptions retain their agreed pricing and credit terms. Review your active subscription in Billing before changing plans or billing cycles.

Where the provider API supports it, the provider summary can retrieve current balance or credit information and related billing details.

Yes. The main application contains plan, subscription, invoice, and payment screens used by the organization billing workflow.

Not necessarily. Provider pricing and supported destinations vary. Review the connected provider account and campaign usage data before choosing a route for a cost-sensitive send.