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/
n5http://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:-9yhcK_tdcNRGFfkkq0rqA
rdf:type
rev:Review
schema:dateCreated
2015-12-02T00:00:00
schema:itemReviewed
n5:7xbNWqzjUPF32NV7VkSntA
n6:funnyReviews
1
rev:rating
1
n6:usefulReviews
2
rev:text
I called prior to placing an order to make sure I could have them in a few days. The guy on the phone said ABOLUTELY, so I went online to place the order. I roughly placed the logo on the shirt with a note for them to adjust it so it's centered properly. When I was about finished it said the turn-around time would be a week. So I called back to verify again they could do it in my time frame and that they would just note the order. The guy said it would be faster if he just took the order over the phone, I wasn't sure how, but why not. After going over everything he said I could either submit the payment on the phone to him or on their website. So I told him I'd just finish the online order and verified the purchase would be based on our conversation, I also emailed him a copy of the logo since we weren't basing it on the online order. When I sent someone to pick up the shirts, they weren't ready on time. They were available that afternoon instead of morning. Not a huge deal. But, having our company logo on the wrong side of the shirt was the issue. I contact the company and they couldn't care less they made my shirts wrong. So instead of me placing another order, this time much larger, I am certainly going with someone else. What a waste of time and money!
n6:coolReviews
0
rev:reviewer
n7:biwNJEk-AHVSyRkrQK8c9w