Messaging integration
Netgsm
What it does
- Sends one-time passwords, order updates, and shipping tracking links by SMS through Netgsm's REST and XML APIs.
- Lists your approved sender headers from Netgsm and lets you pick which one each message type uses.
- Acts as an IYS partner, so consent records can be reported to IYS through Netgsm instead of a direct IYS connection.
Provider based in Turkey
Netgsm is Kambloo's primary SMS provider. It handles the messages a store cannot do without: one-time passwords for login and checkout, order updates, and shipping tracking links. It also serves as an IYS partner, so consent reporting can go through Netgsm. The adapter is an Internal Module with no fee from Kambloo.
How it works with Kambloo
The adapter implements the SmsProvider interface: send, delivery status, header list, and credit balance. Message content comes from the platform's template catalog and the channel per event is a store setting. OTP messages are dispatched on the critical queue with a target of under 10 seconds. Shipping notifications go through the notifications queue with a short template and a tracking link.
Sender headers are yours. Netgsm approves alphanumeric headers through its own application process, and Kambloo reads the approved list from the API so you can assign a header per message type. A store without its own header can use the shared KAMBLOO header, but only for OTP and shipping messages. Marketing SMS never goes out under the shared header.
Failover is automatic. Netgsm is first in the chain by default. If it times out or errors, the message dispatcher's circuit breaker hands the message to the next SMS provider you have installed, such as İleti Merkezi, using the same interface. The failover order is a module setting.
Consent is enforced in code. Every send job starts with a consent check. Transactional messages are exempt; marketing messages are sent only when the recipient has a valid IYS consent on record. Because Netgsm is an IYS partner, consent changes can be reported to IYS through Netgsm's intermediary mode.
Costs are visible. Messages are billed by segment, and the template editor shows the segment count as you type. The message log records segments and cost per message, and the balance is the one in your own Netgsm account, so the store owner sees the same figure on both sides.
Requirements
- A Netgsm account with API credentials.
- An approved sender header for anything beyond OTP and shipping messages.
- IYS consent records for marketing recipients.
Setup steps
The short version. The screens in your store admin follow the same order.
- Install the Netgsm module from the Market. It is free.
- Enter your Netgsm API credentials under Settings > Messaging > Netgsm. They are stored encrypted.
- Apply for an alphanumeric sender header in Netgsm's panel; Kambloo lists it once approved.
- Choose which events send SMS: OTP, order confirmation, shipping tracking.
- Send a test message and check delivery status in the message log.
Questions about Netgsm
Can I send marketing SMS without my own header?
No. The shared KAMBLOO header is available only for OTP and shipping messages. Marketing SMS requires your own approved header and IYS consent for each recipient.
How fast is an OTP?
OTP messages run on the critical queue with a target of under 10 seconds end to end. If Netgsm times out, the dispatcher fails over to the next configured SMS provider.
How is SMS cost controlled?
The template editor shows a live segment count, so you see whether a message is one segment or several. Each sent message records its segments and cost in the log.