SSL Wireless SMS gateway with SORS ERP
SSL Wireless is configured as an SMS gateway, commonly used for transactional messages across all operators.
SSL Wireless is an aggregator rather than an operator, which means one account reaches subscribers on every network instead of requiring a relationship with each.
For most businesses that is the simpler arrangement, particularly where the customer base is spread across operators and the volume does not justify negotiating separately.
What is actually built
Stated plainly, including the parts that are not finished.
SSL Wireless is configured as an SMS gateway in SORS ERP, sending templated messages on event triggers, with Bangla Unicode encoding and delivery logs.
How to set it up
In order. Each step assumes the one before it.
-
Arrange an SSL Wireless account
Get API credentials and register your sender ID or masking.
-
Configure the gateway
Enter the credentials in SMS gateway settings.
-
Set templates and triggers
Map the events you want messaged to the templates that carry them.
-
Test and monitor
Send a test message and keep an eye on the delivery log for the first few days.
Questions
Answered plainly, including where the answer is no.
What is the advantage of an aggregator?
One account reaches every network, so you are not managing separate relationships and credentials per operator. The trade is usually a slightly higher per message cost at volume.
Can the sender name be my business?
That depends on the sender ID or masking your gateway account has registered, which is arranged with the provider rather than in the ERP.
See SORS ERP running on your own numbers
A 30-minute demo in Bangla or English, with your products, your VAT setup and your questions.