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
n4http://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:stBzcNZdkH_XhKoln4LwhQ
rdf:type
rev:Review
schema:dateCreated
2011-11-23T00:00:00
schema:itemReviewed
n7:q5SoWYsF-u7zrlYWGnkdjw
n4:funnyReviews
0
rev:rating
1
n4:usefulReviews
1
rev:text
Having worked in customer service and as an Administrative Professional for 15 years, I have never run across such complications booking travel! My December wedding requires lots of flights from the Midwest so I've been trying to use Frontier. The flights keep changing ... direct flights be come crack of dawn connection flights (not good considering my little sister and dad have not ever flown before!), and each time I try to call and clarify things I get nothing but more confusion and smack talk. Then I attempted to add my cousin's flight to the mix - big mistake! The online portal is an ABSOLUTE MESS just like the customer service line I've had to call four times now. I didn't write down my cousin's locator because I made the mistake of thinking they would actually get the emailed confirm sent! When I called back they couldn't even find her by name ... I had to pull up my credit card statement to prove they charged me for it and in the mean time got nothing but smack talk from the Rep. Not cool, not cool at all. I have many, many years more travel coordination to do, it definitely will not involve Frontier.
n4:coolReviews
0
rev:reviewer
n5:tQ3b1LHwOQr9H9Vsh5k_iw