Several years ago, in 2011, I was searching for a simple solution that would let me send and receive text messages from Salesforce. Our company, The Flywheel Group, had some clients that I thought could really benefit from communicating via SMS with their contacts. When I couldn’t find an existing product that really fit the bill I set out to design and build our own solution. There were three core tenets that I felt like we needed to uphold when building this solution, as follows:
- It needed to be simple. This meant that it needed to be simple to install and configure. It needed to be intuitive to use. It needed to be simple in its functionality, singularly-focused if you will.
- It needed to be reliable. Reliability is tantamount to trust. Customers needed to know that their text messages would be delivered accurately and on-time. With the myriad of carrier networks and complexity in delivering SMS messages we needed a gateway that worked. Period.
- It needed to be affordable. We wanted the solution to be priced in a way that made it accessible to even the smallest of organizations.
I felt that if we could deliver a product that was simple, reliable, and affordable that it would create high value for our customers. In mid-2012, after months of designing, building, and testing, we published Simple SMS to the Salesforce AppExchange. Simple SMS was well received on the AppExchange and our customer base began to grow. We focused on providing a high-level of support to our customers. We built relationships, we got to know our customers and their use cases. We pushed out minor updates, improvements, and bug fixes. All was going well.
We learned a lot over the next few years. We were constantly intrigued and excited about the new customers and their use cases. However, as the customer base grew so did the requests for additional features and functionality. At this point, honestly, I was against adding a host of new functionality that might convolute the application and cause us to lose sight of the simplicity that we desired from the outset. But in this same time period we witnessed a rapid growth in the acceptance of SMS as a medium for business communication, where it had traditionally been reserved for personal communication.
I reached a turning point in my thought process sometime in late 2014, and I realized that there was indeed a path forward. We would need to re-architect the application but it would put us in a position to add many of the most highly requested features while maintaining the simplicity, reliability, and affordability that we sought. We decided to invest heavily back into the product and after many months of designing, building, and testing, we have arrived on the other side. The result of this process was much more than just another iteration on an already existing application, it was really a transformation, a major evolutionary step in the product’s life cycle. While I believe the product is still simple in its intuitiveness it’s no longer simple in its singular-focus on sending and receiving individual messages, there are now a host of additional features. It’s not just SMS anymore, either. Image messaging (MMS) is also supported. Because of this it was decided that a re-branding was in order.
Thus, Textey was born.