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
n6http://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#
n5http://data.yelp.com/User/id/

Statements

Subject Item
n2:kw9S5yzO2xUU477vIv1B7g
rdf:type
rev:Review
schema:dateCreated
2017-01-20T00:00:00
schema:itemReviewed
n7:nxCRx5_US4XLxufkF6-Tlw
n6:funnyReviews
0
rev:rating
1
n6:usefulReviews
0
rev:text
Another horrible experience with SuperShuttle today. After using other services because of previous deteriorating service from SuperShuttle, I took a chance and booked them again. Bad decision. Trip Res ##6670510. Driver arrived 40 minutes after scheduled pick up. Driver could barely speak English. Driver got lost due to inability to use his tablet GPS to find my house. Driver was erratic, at best, and seemed confused between the meaning of red lights and green lights. I had bet that someone was paying attention to the poor levels of service and working to take action to correct them. Bad bet. Having drivers who can read and speak English would seem to be a pretty basic requirement. Then, the big step of being "on-time" would seem to inject some value into your business proposition. Perhaps a few "secret shopper" rides would be helpful to those responsible for fixing the rapidly evaporating service. You guys must be becoming the "poster child" for Uber! To add insult to injury, when speaking with your customer service, their solution was "write to us on our website". Really? I get to pay for running through an airport due to your bad service and "write to us on the website" is the solution? Wow, maybe customer service started out as drivers? Same attitude prevails.
n6:coolReviews
0
rev:reviewer
n5:lOMe7L2SoL6hgLMmEq58pA