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:ZF3wYPBeVdl4M7jhU11zfw
rdf:type
rev:Review
schema:dateCreated
2016-11-05T00:00:00
schema:itemReviewed
n7:bBYL8rhb5Z0y8y0JIefACw
n3:funnyReviews
0
rev:rating
1
n3:usefulReviews
1
rev:text
I bought a Groupon for a massage so I could give this salon a try. Because it's higher end prices, I thought it would be nice to get a discounted service on one thing to check it out before I booked anything else. Bought the Groupon in early August. When I called they said they'd be booked until October, which is patently ridiculous if you are a business offering massage services. I called back end of Sept. when my schedule was more clear. I have called this business FOUR times and each time I get promised a call back and do NOT get one. On a separate, fifth incident, the actual masseuse called me to schedule. We went back and forth on half a dozen times, and in the end, she couldn't guarantee my preferred date because she had to find out if she had child care. Ok, I get that... however she promised to call me back and confirm my appointment and she did not. So I call again today in the first week of Nov. and the receptionist says I can have this Sunday or wait until January, which the Groupon expires in December. They are obviously super unorganized and do not staff their business to meet the needs of customers. I'm going to try and get a refund from Groupon and I wouldn't pay full price for any service here since it comes with so much hassle.
n3:coolReviews
0
rev:reviewer
n6:y90YmjtKAKQMv93MmCfBXQ