STRAX Reach · SMS, email and voice
Two-way SMS through BulkSMS.com
BulkSMS.com has served South African senders for many years. Reach sends through its JSON API from a repliable number and files each reply on the right client record.
- BulkSMS JSON API
- Repliable senders
- Token in the webhook address
Repliable messages that come back to the right client
BulkSMS only routes replies when a message leaves from a repliable number. Reach sends that way by default, sets a short reference of its own on each message and records the BulkSMS id against the Reach message.
Received messages arrive through a BulkSMS webhook as a batch. Reach checks the secret in the webhook address, picks the received message from the batch, strips the number to digits and lands the text in the client's conversation.
When a webhook is saved, BulkSMS sends an empty batch to test it. Reach acknowledges that call and moves on, so the setup succeeds on the first try.
Where it helps
Account arrears reminders
Remind clients of an overdue account and let them reply with a promise-to-pay date that the collections team can see.
Service interruption notices
Warn prepaid meter clients about planned maintenance and gather their questions in one place.
Agent network check-ins
Send field agents a daily check-in message and handle their replies from the Reach console.
What you need
-
A BulkSMS account
With credits and repliable sending enabled for the countries you serve.
-
An API token
Its id and secret, stored in the STRAX credential vault.
-
A public address
For the received-message webhook, with the secret token appended.
-
Reach Core
The records, conversations and console for the SMS threads.
Good to know
A named sender id cannot receive replies. Keep the sender setting on repliable for two-way conversations and use a named sender only for one-way notices.
Questions
Can we test without a client handset?
Yes, BulkSMS provides a test number that fails delivery but still fires the webhooks, so the whole path can be exercised.
What if several replies arrive in one call?
Reach lands the first received message and logs the rest. Set the webhook to send one message per call if your replies tend to arrive in bursts.
Which routing group should we choose?
Standard suits most notices. Premium routes are worth testing for time-critical messages such as payment confirmations.
Is the webhook signed?
BulkSMS cannot sign webhooks, so the address carries a long secret token that Reach checks in fixed time and removes from the run history.
Read more
-
The whole Reach family →
Reach Core and every channel package, with what each one needs.
Add BulkSMS to Reach
Tell us which channels your clients use and we will plan the rollout with your team.
Premium Requires STRAX Reach - Core, which is licensed.
About this listing
| Version | 1.0.0 |
| Author | STRAX |
| Category | Communication |
| Published | 2026-09-24 |
What's inside
| Credential | 2 |
| Global variable | 2 |
| Workflow | 2 |
What happens on install
After the import, and only with your consent, the installer runs:
- Reach - Register Channel : Registers the BulkSMS channel with Reach Core, disabled until its credentials are entered
Free listing
Install it from Feature Marketplace inside STRAX
It builds on STRAX Reach - Core, a premium package. Ask us for a quote to license it first.
Open Feature Marketplace
In your STRAX installation, open Feature Marketplace from the navigation.
Find "STRAX Reach - BulkSMS"
Search or browse to this listing and review the contents disclosure; every package shows what it contains before anything runs.
Install
Choose Install, or "Customise with AI" to adapt the package to your environment first. No licence is needed for free listings.
BulkSMS is a trademark of its owner, named here only to identify the service this package connects to.
See it on your own systems.
A demo takes an hour, on your data landscape rather than ours.