Repair/Complete website that uses challonge api to send sms texts -- 2
Budget: $30 – $250 USD
BUDGET IS $100.
Challonge SMS Website:
Budget is $100.
Site was built but previous programmer could not complete correctly. We need his errors repaired and the site working correctly. I can not allow access to the live files until you start the project. But if you know a file you would like to see I can share it. The file list is below in images.
Website link: https://bisque-grasshopper-934419.hostingersite.com/settings
Password: (contact for password)
Site requirements:
1: Must send only 1 SMS per player per each open match. Players will only have 1 match open at a time.
2: It must send SMS messages throughout the tournament and in all stages(single and 2 stage) tournaments except ladders.
3: It must be able to send a SMS to players individually
4: It must be able to send SMS to all players in the tournament.
Current issues:
1: Sends SMS to players 1 time, than no longer sends messages automatically. It will send sms using the manual sms button throughout the tournament.
2. Will not send an sms to an indvidual player or to all players in the tournament.
3. Will not work on 2 stage tournaments.
Flow: We upload a Csv File to the program you build. We pick the tournament it should apply to from a drop down list based on our user account data stored in the menu. We upload the csv to the program you built. This program than uploads the player data to challonge and provides the sms to the players via Twillo.
Admin side(password protected):
This menu allows user to add the challonge api, challonge account, challonge community account, twillo information. There is a button that allows us to delete all player data stored in the data base.
Upload Security: Depending on how we upload or how the program is set up we may want a password only for upload to keep others from accessing the service.
Player data needed to upload: Player Name 1(required), Player 2(Not Required), Phone Number 1(required) Phone number 2(Not Required).
Notes: Automatically add the +1 country code to the phone number. The player only enters xxx-xxx-xxxx vs +1-xxx-xxx-xxxx. We use google sheets to export data and the +1 in the field is an issue. We also only want to text US Numbers.
Example User Interface: https://tally.so/r/w4d1bO
Example Admin Interface: https://tally.so/r/3EYB2o
SMS Flow: Once SMS data is uploaded to challonge your program will use api from challonge to send sms messages to players based on their current status in the event. I believe we used the [state] as the way to send texts to players that had a tournament match up. We also sent a link to the tournament in the sms text that the players received. I would like to send the station number but if I remember that is not available in the API.
[id] => 370367809
[tournament_id] => 14647124
[state] => open
[player1_id] => 233179844
[player2_id] => 233179864
5:05 PM
We also need a on/off or timed switch if we use A chrons job or a program that pulls data every minute so we do not get blocked by the server.
This project was built before on cpanel by another freelancer. The server went down and we lost all data.
Challonge SMS Website:
Budget is $100.
Site was built but previous programmer could not complete correctly. We need his errors repaired and the site working correctly. I can not allow access to the live files until you start the project. But if you know a file you would like to see I can share it. The file list is below in images.
Website link: https://bisque-grasshopper-934419.hostingersite.com/settings
Password: (contact for password)
Site requirements:
1: Must send only 1 SMS per player per each open match. Players will only have 1 match open at a time.
2: It must send SMS messages throughout the tournament and in all stages(single and 2 stage) tournaments except ladders.
3: It must be able to send a SMS to players individually
4: It must be able to send SMS to all players in the tournament.
Current issues:
1: Sends SMS to players 1 time, than no longer sends messages automatically. It will send sms using the manual sms button throughout the tournament.
2. Will not send an sms to an indvidual player or to all players in the tournament.
3. Will not work on 2 stage tournaments.
Flow: We upload a Csv File to the program you build. We pick the tournament it should apply to from a drop down list based on our user account data stored in the menu. We upload the csv to the program you built. This program than uploads the player data to challonge and provides the sms to the players via Twillo.
Admin side(password protected):
This menu allows user to add the challonge api, challonge account, challonge community account, twillo information. There is a button that allows us to delete all player data stored in the data base.
Upload Security: Depending on how we upload or how the program is set up we may want a password only for upload to keep others from accessing the service.
Player data needed to upload: Player Name 1(required), Player 2(Not Required), Phone Number 1(required) Phone number 2(Not Required).
Notes: Automatically add the +1 country code to the phone number. The player only enters xxx-xxx-xxxx vs +1-xxx-xxx-xxxx. We use google sheets to export data and the +1 in the field is an issue. We also only want to text US Numbers.
Example User Interface: https://tally.so/r/w4d1bO
Example Admin Interface: https://tally.so/r/3EYB2o
SMS Flow: Once SMS data is uploaded to challonge your program will use api from challonge to send sms messages to players based on their current status in the event. I believe we used the [state] as the way to send texts to players that had a tournament match up. We also sent a link to the tournament in the sms text that the players received. I would like to send the station number but if I remember that is not available in the API.
[id] => 370367809
[tournament_id] => 14647124
[state] => open
[player1_id] => 233179844
[player2_id] => 233179864
5:05 PM
We also need a on/off or timed switch if we use A chrons job or a program that pulls data every minute so we do not get blocked by the server.
This project was built before on cpanel by another freelancer. The server went down and we lost all data.