Emergency SMS Messages for Vehicle Accidents: A Fastsms API Case Study
About a year ago we were approached by a young man looking to use an SMS service in his university project. At the time, Thomas West was a student at the University of West England studying Computer Systems Integration.
When it came time to work on his project, he used Google to find a SMS provider and discovered fastsms. After more researching, he chose fastsms because the price was very competitive and the SMS API documentation seemed easy to use.
He’s now received a first class degree and found the time to answer some questions for us about how he used the fastsms SMS API in his successful project.
FS: What was your project about?
TW: My project was based around introducing new safety and security measures in vehicles, potentially as a standard, with the aim of introducing a non-biased insurance rating system by measuring the driving performance of a vehicle.
A tracker like device was placed in the vehicle that would use 3G technology to communicate performance information to a server. This server would then analyse this data and if it believes an accident has occurred, the fastsms service was used to communicate this to a next of kin and could be extended to the emergency services and CCTV centres.
FS: What specific challenges were you trying to demonstrate in your project?
TW: I had to alert a next of kin or “emergency” contact with information regarding where an accident may have occurred. This included a link to point to a dynamically created web page.
FS: How did you implement the fastsms API to meet these challenges?
TW: I thought it would be quite easy. I implemented the SMS API by building a custom framework for building and making requests wrapped with error checking. It is constructed in C# and was used in an ASP.Net MVC application.
Everything was quite self-explanatory, so it was easy to follow and implement. As the way the requests are built are completely uniform and there is an easy to follow structure for checking the result of a request.
FS: Were your expectations of fastsms met or exceeded during your project?
TW: The messages were received much quicker than I had anticipated and were almost instant. If there was a problem with the request, one of a large number of error codes was provided to make it easy to identify the problem.
The free credits they donated allowed me to build my framework cost-free. Being a student, fastsms were able to offer me a cut-price VMN to aid in my project. Sadly, I was unable to include this due to time constraints with the rest of the project. The fastsms service met all of the needs for this project.
FS: Beyond the API and message delivery, is there anything you want to mention about fastsms?
TW: I did have one issue for which I required support and fastsms were able to rectify this, literally immediately. I have already suggested a friend of mine use them for sending SMS alerts to clients and wouldn’t even look elsewhere if I needed this functionality again.
FS: Thank you!
We want to thank Thomas for taking the time to share his experiences with our service and congratulate him on his first class degree. If you’re interested in learning more about his project you can find him on LinkedIn. To see more detail of the API used for the project click here.
Is SMS messaging a good investment of your business’ time and money? A report from Mobile Ecosystem Forum shares some data on how SMS is being used, who is using it, and provides some evidence showing the answer to that question is most likely “Yes”!
This SMS messaging case study explains how a student at the University of West England used the fastsms API in an experimental project aiming to improve vehicle safety. The post is Q&A session between Thomas West, the student, and fastsms, relating how the project unfolded.
So you've got a great new mobile app, or an existing one without many downloads. With well over a million apps in both the Apple store and the Google Marketplace, it's no wonder you have trouble getting people to download it. How do you let people know about it, and make it easy for them to download?
A2P SMS, or Application to Person SMS, messaging is when an application sends a person a text message just like you’d send a text to your mates. P2A SMS, or Person to Application SMS, messaging is when a person send texts to an application.
The benefit of using SMS messaging for authentication is that people have their mobiles with them all the time. It’s convenient for them to receive the passcodes quickly so they can get logged in and do their business, whatever that may be. At its simplest, the procedure goes something like this...
A few weeks ago I wrote a blog post about using SMS messaging to contact your list after some sort of trigger - they made a purchase, had a birthday, or some other event or date. I’m going to build on that concept a little bit more in this post and share how you can really offer just-in-time SMS messages by integrating with your existing systems.
Have you ever been inside a Walmart or ASDA Supercentre? If you have, you’ll appreciate the possibility of what I’ll share in a moment. If you haven’t, try imagining walking into a store so big you can barely see one end from the other, where the shelves are packed with everything you might ever need, and staff who are often less than helpful (not everywhere mind you, but often). The point is you can get lost or frustrated if you’re trying to find a certain item that you need, or is on sale. Finding the right section is sometimes challenging, and even if you think you’re in the right spot you might not be.
You’re all excited about the number of new members you have in your health club thanks to your latest member drive. And you want to do everything you can to help them reach their goals and stay a member for a long time. Here's a quick few steps to get you up and running as quickly as possible.