Enabling message parts allows you to send messages that are longer than the maximum number of characters normally allowed per SMS. Messages are split into smaller parts and recombined at the receiving end to appear as one SMS to the recipient.

Note that you will be charged for each message part.

When you set up a new SMS integration from the user portal, use the toggle under 'SMS Channel Settings' on the API setup details page to enable message parts (disabled by default). Then set the maximum number of message parts allowed.

You can enable/disable message parts and edit the number of message parts allowed by navigating to My Workspace --> SMS and selecting the integration from the table.

If you are currently using the old user portal:

You can set the maximum number of message parts allowed during your integration set-up (from your dashboard), under Settings. The default setting will accept messages that are no larger than three message parts but you can increase this value according to your needs.

If you have questions about switching to the new portal, see here or contact our support team.

If your message status is 'delivered to gateway', it means that the SMS has left the Clickatell SMS Platform and was successfully accepted by the gateway for final processing, awaiting delivery to a user's handset.

Your routing profile determines the way messages are delivered to handsets once they leave the Clickatell SMS Gateway. It's something you can configure when you create your message integration.

• Priority SMS delivery - The fastest and most direct line of delivery for your SMS messages. Intended only for important messages, such as one-time PINs (OTPs), transactional messages, and time-critical alerts. Not to be used for marketing or promotional notifications.

• Standard SMS delivery - High quality, reliable SMS delivery at cost-effective rates. Intended for non-critical messages that aren’t time-sensitive such as promotions, brand announcements, or CRM messages.

The standard length of a text message is 160 characters. However, when you use special characters (i.e. Arabic, Greek, Russian), the number of characters per SMS decreases. Remember that if you want to send SMS in special characters, you need to use Unicode. In some countries, mandatory text or numbers take up extra characters, therefore the amount of characters that you can actually use is less. Check out the specific country restrictions.

If you need to send a longer SMS, you can activate the 'Enable message parts' / 'Enable concatenated SMS' setting when you create or edit an SMS integration.

We've been in the mobile messaging gateway business for over 17 years and we've built up excellent relationships with 1000+ mobile network carriers across the world. Use our Pricing Calculator where you can find more info about the specific carriers that we support in the countries you'd like to send messages to.

You need to have added and successfully verified test phone numbers in your account before you will be able to receive test SMS messages. Submitting test messages to a destination other than the test phone numbers registered will return a simulated response which emulates what the response will look like in your system.

You can add a maximum of three test phones to your account. To add a test phone, navigate to My Workspace --> SMS and select 'Manage Test Phones'. Test phones can also be set up as part of the new integration wizard.

If you have added at least one test phone to your account, a Test Phones card is added to the My Workspace tab. Select this card to add, view, update or remove test phones in your account. Note that if your test phone has an ‘Unverified’ status (i.e. has not been verified successfully), you will not be able to send messages to this phone number and have to remove it before trying to add it again.

If you are currently using the old user portal:

Once you've configured an integration for testing in our sandbox environment, you need to ensure that your test number is linked to the integration before messages will be delivered to your test phone number. Submitting test messages to a destination other than the test phone numbers registered will return a simulated response which emulates what the response will look like in your system.

To double-check that your sandbox integration is linked to your test number, open your integration from the SMS integrations page, and select the ‘Phone numbers’ tab at the top of the page. Your test numbers will be listed here. Numbers with a green tick box are linked to your integration. Click on the tick box to link or unlink your test number to this integration. Test messages will only be delivered to a test phone if your number is linked here.

If you have questions about switching to the new portal, see here or contact our support team.

Visit your Analytics and Reports section which lists all the results of your message sending.

For a breakdown of message statuses and error codes, see our Developers Documentation website.

If you are currently using the old user portal:

Visit your Reporting section which lists all the results of your message sending as well as a breakdown of the error codes you've received.

If you have questions about switching to the new portal, see here or contact our support team.

Delayed SMS delivery generally occurs when the handset does not have a connection to the network. Once a connection is re-established, the message will be delivered.

Special character sets use more data, and thus they may take up more than one space in an SMS. For example, sending messages in Unicode or special characters may reduce your SMS length to 70 (or less) characters.

Click here to find out more about our supported character sets.