This HTML5 document contains 9 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

Namespace Prefixes

PrefixIRI
n3http://www.openvoc.eu/poi#
schemahttp://schema.org/
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
n2http://data.yelp.com/Review/id/
n7http://data.yelp.com/Business/id/
revhttp://purl.org/stuff/rev#
xsdhhttp://www.w3.org/2001/XMLSchema#
n6http://data.yelp.com/User/id/

Statements

Subject Item
n2:md4UgXP_z9NnABi1Aqls7A
rdf:type
rev:Review
schema:dateCreated
2018-05-10T00:00:00
schema:itemReviewed
n7:s1lt4bPK-wRHT9Jp2NdP9Q
n3:funnyReviews
0
rev:rating
1
n3:usefulReviews
0
rev:text
What a crappy experience this time around. Can't say if it's this location's owner/managers or a corporate issue. First off, on confirmation THE DAY before pick up, told to go down by airport to pick up truck. When we booked, requested 2 locations on West Bell as in Glendale or Peoria. Yes, pick up request may not work but UHaul states they will try to get it as close as possible. REALLY?!?!! We contact, get assurance, even a phone confirmation for Peoria pick up. So guess what? We get there (drove 4 hours to Phoenix to get our stuff out of storage) only there is NO record of our reservation at that location. UGH!! But, wait, they do have a truck available. Really?!?!! After 500 mile trip, that truck beat the hell out of me. Turns out to look good but that truck has been treated horribly. AND obviously never checked or serviced or it wouldn't be on the road!! Loose ball joints, no shocks in the front end, and steering so bad, hard to keep on the road. Accident waiting to happen people!! And shame on UHaul managers not caring about our safety. I'm going to post the plate and serial number, plus contact corporate, just in case there ever is an accident. UHaul can't blame the driver.
n3:coolReviews
0
rev:reviewer
n6:HOzcxz0JM2_eN3OaY91Wwg