Nothing quite like the sound of wheels on asphalt, and money being made. It’s a winning combination, and sounds better with the windows down! It’s been said there’s a season for everything, and this one has been full tilt. Sometimes it’s impossible to get to everything and everywhere. With that in mind, here’s one that might be hard to handle, if so – drop it like it’s not!
Snazzy titles aside, this one does have some key points of interest. It isn’t about music, and cool songs. This is more about deliveries gone bad, or recognizing when one has gone bad, and what to do about it.
If you haven’t encountered a bad one yet, kudos, you’re doing something right, and fair warning your first will occur. The biggest challenge at times, is to avoid things and situations, that can create the bad delivery scenario. Some of that only comes with experience, ain’t no cheat sheet for that. Even though the work can be routine, no two deliveries are ever the same.
There are helpful tools that are available in every delivery app that can quickly get a driver out of a sticky situation. For example, accepting a run, arriving to pick up cargo, and it was dispatched to another driver an hour ago. Clearing the system of the run is the next step in a situation like this. But, it’s important to note that not every app does this the same way.
Clear the system. Depending on the app being used there are different ways to release a run. Lets start with Doordash, simple and intuitive, it’s relatively easy to drop it like it’s not. However if the run is simply released without alerting HQ that it’s a bad run, it will count against overall completion ratings. When completion ratings fall below a certain threshold, getting banned from the app is possible.
Alerting HQ means contacting support to have the run cleared from the que and canceled. When the agents at support clear the run, it will also clear in the app, and leave the completion ratings untouched. If completion ratings aren’t going to be impacted severely, sometimes it’s a time saver to drop the run, and take the hit in the metrics. Simply provide a reason from the drop down list, when prompted, and voila all done.
Ubereats varies, mostly because the app doesn’t track metrics in a visible way. In other words, the stats aren’t going to be used to influence the quality of the runs that are offered. When or if it becomes necessary to drop a run, click the red alert button, and select a reason for dropping the run, click apply, and once again, all done.
The mechanics for dropping or releasing a run or delivery, are close to the same across apps. There are however, a few scenarios that should be avoided, if at all possible.
Avoid dropping the run after pickup. There are times when emergencies occur, but releasing a run after pickup can lead to difficulties that can cause significant delays with more offers.
In for a penny, in for a pound. Deciding to drop the run because there was a better chance to review the details, after accepting, should also be avoided. Follow through, and make sure to study the details carefully on the next offer.
Don’t quit now. That’s right, standing in the actual drop off location is not a good time to release that run. If the client doesn’t answer or didn’t provide additional details, use the app’s process to get verified evidence of arrival and attempts at contact. Complete the run, or return the run to the original merchant. Best practice is to try and contact the client, try once more, this could be the one!
Getting every run complete with no snafus is a great goal. It also helps with the bottom line at the end of the night. It’s also been said practice makes perfect, time to go out and get some practice, stay safe out there. Zoom Zoom.
Speedy Delivery on all orders!
