The sometimes overlooked action of a simple reminder to device users who should be returning a device significantly improve the remote device return rates for our enterprise customers. The reason some organizations may not be sending reminder notifications isn't due to them not realizing it could improve return rates. Traditionally, its simply a hard practice to implement. But don't worry, Evercycle literally automates every single piece of this for you - at any scale - for any various asset recovery workflows.
.png)
We have seen the sometimes overlooked action of a simple reminder to device users who should be returning a device significantly improve the remote device return rates for our enterprise customers. The reason some organizations may not be sending reminder notifications isn't due to them not realizing it could improve return rates. Traditionally, its simply a hard practice to implement and manage appropriately, especially at scale - even more so for ongoing, as-needed device return programs.
To work, a few things need to be true...
It must be known which users have been flagged as needing to return a company owned device and that they have what they need to in order to return the device including knowing that they need to, the material such as a return label and return kit delivered to their location, as well as whether or not the user has shipped the return yet. Also, these things must be known as instantly as they happen and at all times before you can even facilitate a reminder email and sms notification.
Lets say you have the above in place. Then there is the actual work and time that goes into writing and sending emails and sms messages to each individual, and at some frequency up to some determined maximum sends. As part of the reminder emails, you would need to also include the ability for them to handle the return and most likely confirm in response to you that the device has been shipped or returned so that you then know to stop sending reminders to them.
Then consider that there could be various reasons that devices may need to be returned and therefore the message may need to be different for each potential return scenario.
You will also need to stay consistent in the message and include the device details of the device that they need to return. You should also keep a log of the communication history as a part of this practice.
If this sounds like something you wish you could do.. probably even should be doing already, but at the same time impossible to orchestrate these pieces, don't worry!
Evercycle literally automates every single piece of this for you - at any scale - for any various asset recovery workflows.
With Evercycle you can automate device return escalation when you:
Check out this quick video walkthrough to see how you could provide self-managed service order features within your automated workflows and automate your end-user email and sms notifications.
.webp)
