Before using Skedulo, we were on a mission to build the bridge between the office and the field teams, and ensure that operationally we were being as efficient as possible. Managing manual scheduling processes for our engineers meant that we couldn't offer the best customer experience. That's something that we are very precious about as a company. Making the move to Skedulo meant we could bridge that gap between the office and the field teams.
Before working with Skedulo, we used manual and Field Service Salesforce scheduling procedures, which did not fit with our growth as a company—we moved from a very stressful and unreliable manual system. Being able to have our own bespoke software that is made for our company's needs has been a massive help for us operationally.
Our systems in place for our engineering function weren't suitable for the scale and the growth that we were experiencing. The system we used couldn't perform handover notes as we can on Skedulo, and we couldn’t leave any pictures with the jobs. Previously, when that job was complete, we had to wait for the engineer to come back to the office and inform us of what had actually happened on that site—whereas we can see it in real-time on Skedulo and act accordingly.
Personally, I have worked on both systems and was a huge part of the transition. The old system was impractical, we couldn't go home at night and be comfortable and confident with our jobs for the next day. It was a constant checking process: making sure everything was as it should be, and whether jobs were dispatched properly. Whereas with Skedulo, it’s automated—we can rest easy knowing that.