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/
n6http://data.yelp.com/Business/id/
revhttp://purl.org/stuff/rev#
xsdhhttp://www.w3.org/2001/XMLSchema#
n7http://data.yelp.com/User/id/

Statements

Subject Item
n2:-QQ7ymW4edd2dRGumUKouA
rdf:type
rev:Review
schema:dateCreated
2016-09-26T00:00:00
schema:itemReviewed
n6:IXHjZvtBKqG4qad7vzu2Ng
n3:funnyReviews
0
rev:rating
1
n3:usefulReviews
6
rev:text
We have a 2.5 year old home with Chas Roberts installed a/c equipment and ducts.. In the last 6 weeks we have had to replace the compressor 2 times. Since the first time was during extreme heat, would have had to wait 6 days for service with higher charges, so called another more responsive and as we found out reasonably priced company. Now we have scheduled another service through the builder with Chas Roberts. It has been a month trying to get a missing duct installed. First visit scheduled between 8-12 with a call ahead. No call. I finally followed up and they showed up at 6. Man confirmed we needed the duct and said they needed parts which were not ordered for the job. Second visit scheduled, no call and no show. Scheduling the third appointment, I asked for the first appointment at 8 on Monday since they had not shown up or called. I asked for confirmation call Friday afternoon. Yup, you guessed, Didn't happen. It is now 8:30 Monday and when I called they said they did not have me at 8, it was 8-12. Fortunately, I have some time flexibility. My business allows me some control over appointments, but having to reschedule is not well received by clients. Imagine if you had to loose a days pay each time Chas Roberts didn't follow through on their appointments. Beware!
n3:coolReviews
0
rev:reviewer
n7:8OqynX-K_17zXQ8CCXlQaA