Frequently asked questions

Yes. Intellipush considers partnerships with organisations that want to integrate SMS into their own products or provide services to shared customers. Send us information about the product, audience, technical model and expected scope.

Any partnership, responsibilities, customer ownership and commercial terms are agreed separately.

Yes. Export the contacts in a supported spreadsheet format, clean the phone numbers and retain only the fields you need. Check country codes, duplicates and the lawful basis for each recipient before importing.

Run a small test import first if the list is large or contains custom fields.

Available delivery status is shown in the portal and can be handled through the API where supported by the workflow. The status describes the technical delivery reported through the chain.

A delivery status is not evidence that the recipient has read or understood the message.

Yes. Use the REST API with OAuth 2.0 from a secure server-side component. Keep the client ID and secret out of browser or application code distributed to users.

Follow the API documentation for current requests and responses, and implement validation, limited logging and safe error handling.

Yes. If your system can send HTTPS requests and handle OAuth 2.0, the REST API can be used to add SMS to the workflow.

Decide which events should trigger messages, which data is necessary, and how errors and delivery status should be handled. Use the API documentation during implementation.

The API provides technical responses to requests, and available delivery status can be used in the subsequent workflow. Follow the API documentation for current status fields and their meaning.

Distinguish between the request being accepted, the message being passed onward and a final delivery status being reported. Allow for some status updates to be delayed or unavailable.

Yes. Every Intellipush account includes access to the REST API and open developer documentation. The API uses OAuth 2.0 and suits applications, backends and other established workflows.

Use the developer guide for an introduction and the API documentation for current endpoints, fields and responses.

Availability and conditions for short numbers depend on the use case, country and operator requirements. Contact us with a short description of your needs so that we can assess the appropriate receiving setup.

Do not publish a number or keyword until the setup has been confirmed and tested.

Payment methods depend on the account type and agreement. The standard account uses prepaid SMS credits, while invoicing may be agreed for certain customer relationships.

Contact us with your organisation number, expected volume and preferred payment method so that we can confirm what is available.

Yes. The portal supports scheduled campaigns. Prepare the recipients and content, choose the intended time, and review the settings before confirming.

Consider the recipient’s time zone, expectations and local rules, particularly for international campaigns.

A standard SMS contains text rather than a file attachment. You can instead link to a file or page made available in an appropriate and secure way.

Consider access control, expiry and privacy before sending links to documents or personal data.

Yes, if the form service or backend can call the REST API after a valid submission. Implement the integration server-side and use the submitted data only for the agreed purpose.

Validate the phone number, avoid sensitive data in the message, and handle repeated submissions so the same recipient does not receive unintended duplicates.

This depends on the sender setup. An alphanumeric sender name generally cannot receive replies, while a configured receiving number can support two-way communication.

Contact us before sending if replies form part of the workflow so that the number, routing and follow-up can be configured correctly.

No. Intellipush has no lock-in or requirement to use the service for 12 or 24 months. You are free to leave whenever you choose.

You buy prepaid SMS credits when you need them, without committing to future usage.

Use a clear link to the relevant landing page and enable link tracking where you have a valid lawful basis. Available click data can then help you assess the content and follow-up.

Do not reuse click data for a new purpose without informing the recipient and checking the lawful basis. Marketing must still meet the requirements for consent, relevance and opt-out.

You need a configured receiving number and, where relevant, a keyword or routing for the workflow. Incoming messages can then be handled through available portal or integration features.

Contact us with the country, use case and expected traffic so that we can confirm availability and setup.

Use “Forgot password” in the sign-in form if you cannot access the account. Instructions will be sent to the email address associated with the user.

If you are already signed in, available security and account settings can be managed in the portal. Contact us if you no longer have access to the registered email address.

A keyword and receiving number must be configured for the account before they can be used. Contact Intellipush with the intended use, market and expected traffic so that we can confirm availability and the appropriate setup.

Once the setup is active, you will receive information about the number, keyword, response format and handling of incoming messages.

Create a list in the contacts area of the portal, give it a clear name and description, and then add or import the contacts relevant to that purpose.

Use separate lists or segments where recipients have different expectations or lawful bases.

Open the account registration page, enter your company name and email address, and follow the confirmation you receive. There is no charge for creating the account.

Once the account is active, you can sign in to the portal, review the account settings and buy SMS credits when you are ready to send.

You can add an individual contact in the portal or import several contacts from a file. Normalise the phone number with the correct country code and record only the information needed for the purpose.

Check the lawful basis before including the contact in a campaign.

Prepare the file with one contact per row and clear columns for the phone number and any necessary fields. Use .xls or .xlsx, check country codes, and remove empty rows and duplicates before importing.

You can import into a new or existing list. Check a sample of the contacts afterwards before sending.

Choose a recipient or contact list in the portal, write the message, and check the sender, links, character use and scheduled time. Confirm the campaign only after reviewing the recipient basis and content.

Consider sending a test to your own number before a larger campaign.

Add the destination address to the link tool while preparing the message, then check that the shortened link opens the correct and secure page. Link activity should only be processed where the recipient has been informed and you have a valid lawful basis.

Use UTM parameters if the traffic should also be identified in website analytics, but do not place personal data in the URL.

A keyword is an agreed word that the recipient sends to a specified number. The combination of number and keyword can be used for activities such as joining a list, opting out or receiving a defined automated response.

Setup, pricing and availability vary. Describe the intended workflow before promoting the keyword so that receiving, responses and privacy are handled correctly.

Marketing messages must give the recipient an easy, free way to stop further marketing. This may use an agreed keyword, an opt-out link or another clear method appropriate to the setup.

The opt-out must be acted upon without undue delay and respected during later imports and campaigns.

The customer will normally be the controller for recipient data and determine the purpose and lawful basis. Intellipush will normally act as processor when the platform processes data on the customer’s documented instructions.

The Data Processing Addendum applies automatically as Schedule 1 to the service terms and covers matters including security, assistance, erasure and subprocessors. The customer therefore does not need to order or sign a separate standard agreement. See provider categories and data processing, the Trust Centre and Terms+DPA. Verified customers and prospects may request the confidential, versioned subprocessor schedule from Intellipush.

There is no monthly platform fee. You create an account for free and buy prepaid SMS credits when you are ready to send. Credits are valid for 24 months.

The final cost depends on the length and content of the message, and the country it is sent to. One text can consist of several SMS segments. Portal prices are shown excluding VAT. Optional services such as keywords and short numbers may carry a recurring rental charge.