Customisation
Bespoke Solutions
If our service doesn't already meet your requirements directly, we are happy to tailor it to suit your needs. Often we can do this at no extra charge, across both pre-pay and monthly invoiced accounts.
Some examples of what we've done for customers already:
- Timestamps as the Sender ID, for a company that sends server alerts.
- New API parameters, for automatic routing of replies and delivery receipts.
- 'Associate' accounts, so that individual youth clubs can buy credits at the group rate for all the clubs combined.
- Company name as Sender ID, so the customer's brand is shown in all text messages.
Customisations in practice
We provide server-alerting notifications for many customers. A common issue is that when an engineer starts a new shift, there may be some server alerts that have already been dealt with by his colleagues. To help the engineers work more efficiently, we added a feature to set the Sender ID of each text message to be the time the alert was triggered. Now whenever engineers receive server alerts, they can see precisely when they were sent, and consequently what action is necessary. This feature was developed at no charge to the customer.
Send Using Your Own Mobile Number
We offer the facility for you to set the Sender ID of each message to be your own mobile number. This can be convenient when you want replies to be sent directly to your handset, rather than by email or online.
Payment models
By default, our normal service means that you buy message credits and these are debited each time you send a text.
However, sometimes you may want to allow people without an account with us to contact you - for example, you may want emails to be forwarded to you when you're out of the office.
This is our "recipient pays" model, where all texts sent to your mobile are debited from your account, and the sender does not need to be registered with us.


Spring Digital