Integration with TurboSMS for a website and online store
A TurboSMS integration lets a website or online store send SMS to customers: an order confirmation, a waybill number, a phone confirmation code or an appointment reminder. Messages go to the customer's number through the service, and the balance and delivery statuses are visible in the dashboard.
- SMS about a new order and changes to its status;
- a message with the waybill number after dispatch;
- a one-time code to confirm the phone number at sign-in or checkout;
- a reminder about a visit or a booking;
- a sender signature (alpha name) with your business name, if the service approves it;
- a check of the text, the message length and the customer's consent to promotional SMS.
What a TurboSMS integration gives you
SMS arrive on any phone without apps, so this channel suits short important messages: the order is accepted, the parcel is sent, the visit is tomorrow. A TurboSMS integration passes such messages from the website to the service automatically, and the manager does not need to type them by hand.
Store owners search for SMS notifications for an online store and connecting TurboSMS to a website. TurboSMS sets the service terms, the cost of messages and the rules for the sender signature, so we check them before work begins.
What the TurboSMS integration includes
- connecting the service API to the website with a key from your dashboard;
- SMS templates for an order, a dispatch, a code and a reminder;
- sending on events: a new order, a status change, a waybill number;
- processing of delivery statuses, if the service provides them;
- recommendations on monitoring the balance in the dashboard so that messages do not stop;
- test sends to your number and on real orders.
How we connect TurboSMS
On WordPress and custom-built websites, the website calls the service API on order events. On Horoshop, which is a closed platform, we use a suitable plan option or a small intermediate service: it reads orders via the API and webhooks and sends SMS via the TurboSMS API. Webhooks arrive with a delay, so such SMS are not instant. The stages:
- a consultation and the choice of events that trigger SMS;
- from you: a TurboSMS account, an access key, an approved sender name, the message texts;
- connection, setup of templates and protection against duplicates;
- a test on real orders, then launch; the timeline depends on the platform and the number of events.
Cost and terms of the TurboSMS integration
We calculate the cost of the integration after a free consultation, once the platform and the number of events and templates are known. SMS rates and the rules for promotional messages are part of the service terms and the advertising law. If you need an online store, see store development and launch (from $500), and for more complex projects – a turnkey corporate website. Send your questions on the contacts page.
Questions and answers
Does the sender name need approval?
A sender signature instead of a number (alpha name) usually requires registration with the service. TurboSMS sets the procedure and the timeline, so we advise applying before development starts.
Why does a long message cost more?
Cyrillic takes up more space in an SMS, so a long text is split into several parts, and the service may count them as several messages. We write short templates.
Can I send promotional SMS?
Yes, with the recipient's consent and in line with the advertising law and the service rules. Service messages about orders are a separate category, and we agree on their texts with you.
What happens if the balance runs out?
Messages will stop arriving. That is why we log sending errors, and we advise you to keep an eye on the balance in the service dashboard.
