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/
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:fIH5VjwGWen_F4jousqu6Q
rdf:type
rev:Review
schema:dateCreated
2017-10-08T00:00:00
schema:itemReviewed
n6:kgLTL1qgIKPpEwsEx3lSRA
n4:funnyReviews
0
rev:rating
3
n4:usefulReviews
1
rev:text
This is a mixed review, but it's important to be critical with this particular type of service. After all, if you're unlucky you'll only have to bury a loved one, once. If you're really unlucky, you'll have maybe a couple of experiences with it, like I have. Sandy was awesome, in really being genuinely understanding and thoughtful and efficient. The part that I think needs to improve for the business as a whole, is communication with related cemeteries that their customers may use, and feedback to their customers with the progress of things. Where they can shine is making sure once a customer agrees to and pays for a service, that the customer doesn't have to chase down and figure out, amidst his or her grief, where the body is, and why isn't it where it's expected to be. Now there may be legitimate reasons for the unexpected, but whatever the reasons, it should be quickly determined, communicated, and resolved "for" the customer where appropriate. In fairness, this is also on the cemeteries too, to make sure things go as smoothly a possible. I'd use Angels Cremation and Burials again though, and Sandy is the reason.
n4:coolReviews
0
rev:reviewer
n7:K4p7RB4BSvr_-9iDuVgouQ