|
| Messaging
parameters supported |
| |
- Account - Your text message
account
- Password - Password for access to
your account
- Message - Message to be sent to
destination number - maximum 160 characters
- Destination Number - Destination
mobile device number
- Text ID - A text identifying the
sender (optional)
- Reference - Message prefix
(optional)
|
| |
| Licencing Terms |
The number of licences a
company must purchase depends on the number of geographical locations and not
the number of development platforms.
| e.g. |
1 Company 2
Locations 20 Developers = 2 Licences |
|
1 Company 1 Location
500 Developers = 1 Licence |
|
| |
| Payment of messages |
| Each message delivered
must be paid for in advance. We have built our systems so that either the end
user of the application pays for the messages or the development company. This
will be dependant on the application being developed and the nature of the
users who will use it. |
| |
| Text Message
Account |
BuzzSMS uses servers
provided by BuzzSoft to deliver the messages. An internet connection is
required by your application. BuzzSMS submits information to our servers which
in turn forward the information to the appropriate Mobile network provider
globally.
Each message sent must be
paid for by the user or developer of the application.
We have created a system which enables the creation of
an account and password. The account code is an email address which we can use
to communicate with the account holder. Messages are bought and credited to the
account. BuzzSMS passes the account and password to our servers which verify
that they are correct and that there are sufficient credits in the account. The
account and password must be embedded in your application. Each user can have
their own account which they maintain and/or you the developer can have one
account which you control.
Click here for details on pricing for the messages
and how to buy them. |
| |
