Service updates
Let customers know about an order, a service change or the next step in their enquiry.
SMS Messaging
A short message.
A useful update.
Keep customers informed with outbound SMS. Send from the portal or connect your application to the API, then follow each message’s delivery status.
Make the message
worth opening.
Use SMS for clear, relevant information your customers expect to receive.
Reminders
Send a reminder about an upcoming appointment or an agreed follow-up.
Application notifications
Connect your own business events to SMS through the API, including sending to multiple recipients.
Two ways to send
From your account.
Or your application.
Choose a hands-on workflow in the portal or build SMS into the software you already use.
Know what happened
after you sent it.
Review status in your message history or use the status endpoint and webhooks to update your application.
Accepted for sending
The request has queued the accepted recipients. This confirms acceptance, not delivery to the handset.
Keep the returned message IDs to track the outcome.
Explore delivery webhooksBefore sending
Get the details
right at the start.
A recognizable sender
Request approval for your custom sender ID before using it. The documented API accepts names of 1–11 letters; numeric phone numbers are not accepted as sender IDs.
The complete recipient number
Use international numbers with the country code. Formatting is normalized and invalid destinations are rejected before queuing.
Text, encoding and cost
Message length and encoding affect segment counts. Unicode support varies by destination. Review the text and quote before sending.
Keep your systems
in the conversation.
Use an idempotency key when retrying the same send request, store the returned message IDs and subscribe to delivery events. Your application can follow the result without repeatedly sending the message.
Read SMS API documentationBefore your
first message.
Ask our teamCan I send to multiple recipients?+
Yes. The API accepts an array of recipient numbers for one message. The response separates accepted recipients, rejected numbers and normalized duplicates. A successful request can still contain rejected recipients, so check each result.
Can I use my company name as the sender?+
Custom sender IDs require approval and confirmation that they are available for SMS delivery. The documented API format is 1–11 letters (A–Z). Use the approved sender options in your account.
Does delivered mean the message was read?+
No. Delivery status is not an SMS read receipt. Use it to follow the delivery outcome, not to infer that the recipient opened or acted on the message.
Can I send Unicode characters or emoji?+
Encoding support depends on the destination. The service checks GSM-7 or Unicode before quoting and queuing; unsupported encoding can be rejected. Where character conversion is offered, review the converted text before sending.
Does buying a phone number include SMS sending?+
The outbound SMS service uses its own sender-ID workflow. Do not assume a purchased phone number can be used as the sender or receive replies. Confirm number-specific messaging capabilities with our team.
How much will my messages cost?+
Check current destination rates and the sending quote. Charges depend on the recipients and message segments. For API batches, the returned total_cost covers queued recipients; rejected recipients are listed separately.
Keep customers
in the loop.
Prepare your next message in the portal, or start with the API reference.