API and integrations
SMS inside the software you build
Evaluate Intellipush for SaaS, booking systems and other software integrations. Resolve events, account ownership, cost and operations before the first send.
Turn a system event into a useful message
A booking confirmation, return reminder or agreed operational alert starts in your system. Your integration decides who receives it, when it is relevant and whether the event is still valid. Intellipush handles the SMS request and available delivery information.
These are proposed implementation patterns, rather than ready-made integrations for every system. Start with one workflow and clear ownership of wording, recipients and failures.
- Booking: send after confirmation; stop scheduled reminders when the booking is cancelled.
- Rental: link a return reminder to the current rental agreement and deadline.
- Operations: limit repeated alerts and define when a person should follow up.
Choose the account model before building
Decide whether each customer owns an account and credits, or whether you need an agreed setup for several businesses. Subaccounts and parent-account funding depend on enablement and account configuration. Do not assume these features are automatically available.
Describe expected volume by destination, sender identity, who owns recipient data and who pays. Query /capabilities from your server during implementation and use its response to check available features.
A documented integration: Sharefox
Sharefox describes SMS through its Notifications module for automated messages to customers or managers, using the Intellipush gateway. This is a publicly documented software integration.
Sharefox explains that its activity panel shows that sending was triggered and forwarded to the operator; it does not confirm delivery to the handset. The source documents the workflow, rather than measured outcomes or a general delivery guarantee.
A concrete evaluation before production
Create a free account, confirm sender identity and destination countries, then follow the developer guide from your server environment. New customers receive 10 free credits; the SMS count varies with destination and segments. Creation requests send real messages.
Check successful creation, invalid input, an expired token and an interrupted response. Persist a key per logical send before attempting it and verify that retries cannot create duplicates. Finish the internal evaluation with a documented status and understood cost.
Bring this to a technical discussion
Describe your software, one specific messaging workflow, destination countries, approximate monthly volumes and preferred account model. We can then clarify setup, available features and possible invoicing by agreement. Do not include API secrets or recipient lists in the enquiry.
Reviewed 30 October 2026. The API reference and current portal pricing govern implementation and purchasing.