SMS web application
a. User registers via Web with 0 credits (Login name, Name, Company (optional), E-mail, Cel number,Address (optional), City (optional), Country (optional), NUIT (9 digit numeric field) (optional)., date/time, user type (smsuser/admin).
b. User specifies usage report periodicity
c. System generates password and sends it to the given cellphone number as SMS.
a. User has to login (login name/pw). Then user chooses to buy credit through Paypal (credits will be increased in back-office) or off-line (we will get in touch). We will receive e-mail in either case.
3. SMS Send:
a. User sign-in (login name/pw) –and can send SMS to one or several recipients.
b. User can build/edit its own address book and group them in lists of recipients. Address book includes Name, cell number, comment.
c. Depending on operator prefix, credit is deducted depending on destination and number of messages.
d. Screen shows form with sms entry field (counting characters) up to 160, destination (either numbers or list), send and clear button, credit available, date/time to send (credits will be deducted on request, not on sending).
e. If credit not enough, doesn’t send and alerts the user.
4. User edit/PW recovery:
a. User can recover pw using login name – sent to cellphone as SMS.
b. User can edit cell number, e-mail, pw (one at a time) and the other contact (e-mail or pw) is informed of this activity.
a. On screen - User can view message history with delivery report.
b. On screen - User can view scheduled messages (not yet sent) and request their cancellation (recovering corresponding credits if it is possible to cancel – they have not been sent to gateway yet).
c. E-mail - Usage report will be sent by e-mail according to chosen periodicity (daily, weekly, monthly) with info about usage after date of last report
(Date/time, recipient number or list name, Status, Credits taken, Message content shown on reports)
6. Back Office (only admins):
a. Enables us to manage users, namely credits (increase/decrease) and turn them inactive/active (even if they have credits)
b. Enables to manage parameters (operators prefix and credits/msg)
c. Enables to list and search users with criterias (# credits available, # messages sent, #credits used, alphabetically, etc.)
d. History of credit increase/decrease kept (smsuser affected, value, date/time).
§ System works by placing outgoing messages (message and recipient) in an SQL Server database table and reading its status from another table (this will be further detailed)
§ It will not be possible to send messages to other operators than the available from a list/table.
§ This list must include operator prefix and number of credits to be deducted per operator (maybe less than 1 – field format 9.9).
§ Project requires back-end development with functional front-end. We will integrate into our own design.