My Sender ID works in Sinch MessageMedia but is not displayed when I send SMS from Wisenet. What should I do?
If your approved Sender ID appears correctly when sending SMS directly from Sinch MessageMedia but messages sent from Wisenet display a mobile number instead, check that your Sender ID has been configured as the default sender for API traffic on your Sinch MessageMedia account.
When you connect your own Sinch MessageMedia account to Wisenet, Wisenet sends SMS using the API credentials configured for your account. Wisenet does not explicitly pass your Sender ID with each SMS. Instead, Sinch MessageMedia applies the default sender configured for API traffic associated with those credentials.
This means that having a Sender ID registered, approved and set as the default within the Sinch MessageMedia portal may not be sufficient. In some cases, Sinch MessageMedia may also need to configure the Sender ID as the default sender specifically for API-generated messages.
If you experience this issue:
- Confirm that SMS sent directly from Sinch MessageMedia displays your approved Sender ID correctly.
- Contact Sinch MessageMedia Support and ask them to confirm that your approved Sender ID is configured as the default sender/source for API traffic using your account’s API credentials.
- Make it clear that Wisenet is using your organisation’s Sinch MessageMedia account and API credentials, rather than Wisenet’s own MessageMedia account.
- Once Sinch confirms the API sender configuration, send another test SMS from Wisenet.
If Sinch MessageMedia confirms that your Sender ID is correctly configured for API traffic and messages sent from Wisenet still do not display it, contact Wisenet Support so we can investigate further.
Does Wisenet support two-way SMS communication?
Wisenet does not currently support two-way SMS communication within the platform.
Learners can reply to SMS messages where supported by your MessageMedia setup. However, replies will be received in your MessageMedia account and must be accessed and managed directly through MessageMedia.
Can I schedule SMS messages in Wisenet?
Wisenet supports automated SMS messaging through Learncycles, where messages can be triggered based on specific events. See How to Add and Edit Learncycles
However, scheduling individual SMS messages to be sent at a specific future date or time is not currently supported directly within Wisenet.
How do I choose the right MessageMedia pricing plan?
MessageMedia pricing plans are based on your organisation’s expected SMS volume rather than the number of staff members sending messages through Wisenet.
We recommend selecting a plan that aligns with your anticipated SMS usage and confirming any applicable charges directly with MessageMedia.
Does each Wisenet user need a separate MessageMedia licence?
No. Once your MessageMedia account is connected to Wisenet, all staff members with the appropriate permissions can continue sending SMS messages directly through Wisenet. See User Access Roles
You do not need a separate MessageMedia user licence for each staff member sending SMS messages through Wisenet.
How am I charged for sending SMS messages through Wisenet?
SMS charges depend on the sending option configured in Wisenet.
- Option 1: Send via Wisenet (Australia only) – Wisenet charges $0.10 per SMS, billed quarterly in arrears.
- Option 2: Send via my MessageMedia account (Australia and New Zealand) – Wisenet does not charge for SMS messages sent through this integration. Your SMS usage and any applicable fees are billed directly by MessageMedia based on your selected plan.
Important for New Zealand customers: Due to New Zealand SMS requirements, sending SMS messages to New Zealand mobile numbers through Wisenet’s shared SMS service will no longer be supported once the restrictions take effect.
For more information about billing and managing SMS costs, refer to the Usage Charges.
