Schneider chat room - Closed see new thread linked in the last post

Wow. NaviGo wants you to go through the heart of San Francisco?

Um....




In your dreams, NaviGo.

 

Lol, exactly what I was thinking. As if the multiple signs saying "tractor trailers over 30' from king pin to rear axle not recommended" isn't enough.

Finally finished with this darn load. Now I'm sitting in a Walmart parking lot waiting for my next load. 3.5 hours left on my 14 and ticking down, and I was told freight is slow up here today and it can take a while for a load. I'm supposed to be back up in Portland on Monday for some time off......... Measly 180 miles today.

 

Wow there is a cascada burnt up here at Charlotte oc.

Sent from my Galaxy Nexus using Xparent Cyan Tapatalk

 

you're here too? I'll be going to take pics of that in the morning before I pull out. Hope the guy made it out ok. That cab is toasted and roasted!!

 

Workflow updates, rants maybe a fix or 2 for guys still having issues.

Unless they push a new update onto us, we will need to call in to have ETD changed. ETD is set by the "average" time at customer. And can not be altered by the driver.

This forces you into a locked "earliest" NAT.

As an extreme example: Customer typically takes 5 hours to live unload. We have new contract which allows us to drop loads. Your appointment is 1400. This means the ETD will reflect 1900. Which in turn means the earliest you can set your NAT is 1901.

Once empty. Your ETD and NAT will not auto correct if you finish early. It remains locked to the driver. And you'll need to contact your DBL to do it for you.

Trailer updates continue to be a royal pain in the ###.

Average QC delays are 10-20 minutes. Sometimes more.

 

My etd are always set to the day after my drops even if I drop the day before and could have 10hrs left on my 11 and 11 left on my 14hr clock :thumbdown: that part of wf sucks I've wasted a couple of days sitting because of that part

See, my damie, Pootie Tang don't wa-da-tah to the shama cow... 'cause thats a cama cama leepa-chaiii, dig?"

 

Yup. That's why I bring it up.

The ETD is pissing a lot of drivers off. In your case, I suspect you're dropping with a 24 hour window for delivery.

You can change the ETA. But you need to follow it up after you get the "eta has been updated" return message. Then do it a second time, this has proven to update the ETD for some people. Which in turn allows you to send a better NAT.

Our biggest problem right now. Wasted man hours on the phone. Correcting what some MIT drop out screwed up. Actually, I think upper management made the call on the design issue. And now we're paying the price for their arrogance.

I only caught this issue because I was at the OC. And refused to move until we could get it to reflect corrections at my end. Speaking directly to DBL and looking over her shoulder allowed me a bit of insight into the issue. That, and realizing the #### ETD is "hard coded" based on your ETA.

Another issue I've noticed "late delivery" notifications. These SOB's are driving me crazy. I really don't care what time I was supposed to get there based on the computer model. Especially since I updated my ETA prior to accepting the load and prior to making it active.

I got a notification earlier this week. 1800 minutes late - select a reason. I still haven't found "because you're a #######" in the drop down list.

 

I just left charlotte oc. Take some pics and post them. I applaud sni they are making inroads into phone delays. Even gives a rough update on hold times.

Sent from my Galaxy Nexus using Xparent Cyan Tapatalk

 

Yeah. Yesterday I called my DBL directly (not the 800 #). First it told me 5 minute wait time, then 3, then 5 again, then 10, 10, and 10. Finally said screw it and call the ops manager directly. Got right through.

 

We all know it's because you failed to wear the required uniform. Just admit it already.