Review Management for Restaurants in the Philippines

Almost every restaurant owner we talk to knows they should reply to reviews. Very few have decided who does it, by when, and what happens when that person is off. So it gets done in bursts, usually after a bad one, and then not again for a month.

Fix that first and the rest is easy. Name one person, give them a window — same day for anything under four stars, within three days for everything else — and put it on the closing checklist rather than in someone's head.

The reason speed matters is that the reply is dated on the page. A complaint answered the same day reads as a business paying attention. The identical words posted three weeks later read as damage control.

Most restaurants only reply to complaints, which is backwards. Four and five-star reviews are the bulk of your volume, they are read by everyone comparing you to the place next door, and each one is an opportunity to say something specific about your food that a search engine and a customer both understand.

Keep them to one or two sentences, and name the dish. "Salamat, Jomar — glad the sisig was right. See you soon." mentions the thing you want to be known for, which a generic "Thank you for your feedback!" does not.

Vary them. Twenty identical thank-yous down a profile look automated, because they are.

Automation is reasonable for the routine majority and dangerous for the exceptions, and the distinction is not about star rating alone.

Safe to automate: four and five-star reviews with no complaint in the text, and rating-only reviews with no words at all. These are thank-yous, they carry no risk, and they are the ones that otherwise never get answered.

Never automate, whatever the rating: anything mentioning food poisoning, illness, a foreign object, an allergic reaction, injury, hygiene, pests, harassment, discrimination, a refund demand, or a named staff member. These need a person, because an AI-written reply to a food poisoning claim is a legal and reputational problem in one sentence.

The middle band — one, two and three stars without any of the above — is best handled as a draft a human approves. You get the speed without publishing anything you have not read.

Match the language. A review written in Taglish should be answered in Taglish; replying in formal English to someone who wrote "ang sarap ng adobo, sulit!" reads as a corporate account rather than the owner.

Delivery complaints are the recurring unfairness. Riders are late, food arrives cold, and the review lands on your profile. Acknowledge the experience without blaming the customer or the platform: "Sorry it arrived cold, Ana — that is not how it leaves us, and we have changed how we pack for delivery." Readers know how it works.

Expect volume around Christmas parties, Valentine's, graduations and Holy Week. A restaurant that answers nothing through December has its worst month visible at the top of the profile in January.

The average rating is the number everyone watches and the least useful one. It moves slowly, it is dominated by history, and it tells you nothing you can act on this week.

• New reviews per week. This is the number that moves ranking and the one you control directly by asking.
• Share answered. Aim for every review, and treat anything under about 90% as a process failure rather than a wording problem.
• Median time to reply, split by rating band. If complaints are slower than compliments, the process is backwards.
• Recurring themes. Four separate reviews mentioning the wait is an operations problem showing up in marketing — that is the most valuable thing reviews give you, and it is invisible unless someone reads them together.