Reply-behavior benchmark — Asian restaurants, Amsterdam

Competitive intel on how Michiu's peer set replies to public reviews. Source-of-truth bias: Google Maps was inaccessible behind the EU consent gate during research; Tripadvisor (which exposes owner-reply text in HTML) was used as a proxy for reply behaviour. Where we could cross-check via aggregators (RestaurantGuru, which mirrors Google reviews) we did, and that's noted. The Tripadvisor signal is directionally accurate for who replies and how — operators who reply on Tripadvisor reply on Google; operators who don't, don't.

Date of crawl: 2 May 2026.

1. The benchmark table

Median reply rate across the 10 peers: ~0% on the typical listing. Two outliers (the Okura pair) have near-universal reply coverage. One (Taiko) replies selectively. Everyone else is silent.

2. Three reply examples per peer (verbatim)

Yamazato — replies-strong tier

(a) 5★ — sammie V, March 2026 — "The food was refined, beautifully presented and full of pure flavours… Chitomi brought the dishes and explained everything calmly and clearly."

Reply: "We are delighted to hear that you enjoyed the refined flavors, presentation, and overall dining experience at Yamazato restaurant. It is especially gratifying to know that Chihomi and Yathin were able to make your evening even more memorable through their attentive service and passionate explanations." — The Yamazato Restaurant Team

(b) 3★ Thomas S, August 2025 — "The food, course for course, was underwhelming and the ingredients and inspiration were lacking. Not one plate was memorable or noteworthy."

Reply: "We are truly sorry to hear that your anniversary experience did not meet your expectations… Your comments have been shared with our team and are regarded as valuable feedback as we continue to improve."

(c) 1–2★ — none in the visible window; the Thomas S 2-star above is the lowest. Pattern: still answered, still warm, no defensiveness.

Sazanka — replies-strong tier

(a) 5★ — Charles K, Jan 2026 — "Our chef, Rena Rebel, was magnificent both in her cooking, but also her interaction with us…"

Reply: "Dear 319charlesk, Thank you very much for your wonderful review. We are delighted to hear that you had such a memorable evening with us… We will gladly share your kind words with Chef Rena and the entire team. Your recognition of their dedication is truly appreciated and serves as great motivation for all of us. We very much look forward to welcoming you back to Sazanka restaurant for another exceptional dining experience. Yours sincerely, The Sazanka Restaurant Team"

(b) 3★ — Ibbee, Oct 2025 (food/service 5, atmosphere 3, lengthy walk to restroom).

Reply: layout feedback acknowledged constructively — "we will certainly take it into consideration."

(c) 2★ — Louise O, Sep 2023 — "Sazanka now paled in comparison to the fantastic experience we had as regular guests in the 90's and 2000's. The cook was very mediocre… the rice dish was tasteless."

Reply: "Dear B4796AOlouiseo, Thank you for your review and for sharing your feedback with the Tripadvisor community. First of all, I would like to start by apologizing for the food being below our standard… The level of service and experience you receive is of great importance to us at Teppanyaki Restaurant Sazanka. We truly value your feedback and take your experience very seriously. We appreciate the time you took to share your feedback and it is our hope that you will give us the opportunity to serve you again in the future. Yours sincerely, The Teppanyaki Sazanka Restaurant team"

Taiko — replies-medium, real-name signature

(a) 5★ — Lex, Jan 2026 (also flagged unreasonable wine pricing).

Reply (signed Susanne Hatje, General Manager): "Thank you for sharing your thoughts… Your comments about the wine pricing and selection are noted…"

(b) 3★ — Dng, Sep 2025 — "most of the savoury 8-course meal was very salty" (€370 for two).

No reply. The clearest example of Taiko's selectivity — they answer the win, ignore the constructive critique.

(c) 2★ — Raquel E, April 2024 — "Bad and very boring food, please stick to your own kitchen…" (Szechuan event night).

Reply (signed Roy Tomassen, Sept 2024 — five months later, in Dutch): "We betreuren het ten zeerste dat uw bezoek aan Taiko niet aan uw verwachtingen heeft voldaan… Dit is absoluut niet de ervaring die we onze gasten willen bieden…" — apologises, acknowledges service-recovery failure, invites direct contact.

Hosokawa — replies-only-to-praise

(a) 5★ — Happy Penguin, Aug 2015 — "My new favourite Japanese Restaurant…" → owner replied warmly. (b) 3★ — Lotte O, July 2024 — disappointing atmosphere/service. No reply. (c) 1★ — Nicholas W, Aug 2024 — "Waiting is a profession… a disaster". No reply. Same pattern for naki81 and Elif E.

Nanbu, Oceania, Sapporo, Sichuan Food — silent across the board

For each: (a) 5★ = no reply, (b) 3★ = no reply, (c) 1–2★ = no reply.

Sample 1★ that sits unanswered:

• Nanbu — Milena, March 2025: "Reserved this restaurant for my birthday dinner — online — and received a confirmation… they said they are kept for other guests."
• Sichuan Food — Red S, Jan 2026: "Terrible food and extremely pushy service… they kept asking every few seconds if I wanted this or that… Don't go to This restaurant they rip u off."
• Oceania — Brittney, June 2016: "Each bottle of water is €9!… this is unreasonable, unacceptable and frankly a rip off."
• Sapporo — Emil M, March 2023: 1★ booking-confirmation dispute.

These are reputation grenades that were never defused.

Oshima — listing unclaimed

Tripadvisor listing shows "unclaimed" status, so the owner literally cannot reply even if they wanted to. 7 reviews, all 4–5★, no engagement on either side.

Hatsune — too new

Opened 2024 (chef Narita, ex-Michelin). No Tripadvisor listing surfaced. Active on Instagram (@hatsune.nl). Reservation-only kaiseki — they may not chase digital reviews at all by design.

3. Michiu's current state

• Google volume: 413 reviews, 4.3★ (RestaurantGuru mirror).
• Visible reply behaviour: zero. Across both Tripadvisor and the RestaurantGuru Google mirror, no owner replies are visible on the recent window.
• Live negative grenades right now:
  • Jose Manuel Ruiz Espadas, Google, ~Mar 2026, 1★: "Came here for a birthday but the whole experience was ruined by the long waiting times, the loud and out of place music and messy service. We paid for the best experience that they offer but noticed that was the worst choice comparing with A la carte. Wouldn't recommend for a good dining experience." (€100+ per person). Unanswered.
  • femke, Tripadvisor, Feb 2024: "8 dry pieces of sushi and a portion of Peking duck, also bone dry, for 47 euros." Unanswered.
  • Ad P, Tripadvisor, Oct 2023: "Dishes that were supposed to be hot were cold… not worth the money." Unanswered.
• Live wins also unanswered: Dik K (Apr 2025, 5★, "What a fantastic place this is"); denise Baks (Google, 5/5/5/5, ~Feb 2026); Laurberto17 (Dec 2018, 5★).

Michiu sits in the same silence bucket as Nanbu, Oceania, Sapporo and Sichuan Food — the majority bucket.

4. The competitive landscape verdict

The reply-quality field is wide open.

Eight of the ten peers either don't reply at all (six) or reply only to praise while ducking the negatives (Hosokawa, partly Taiko). Only Yamazato and Sazanka — both inside Hotel Okura, sharing one corporate hospitality apparatus — reply consistently and across the rating spectrum. Both use group-signed templates ("The Yamazato Restaurant Team") — warm and competent, but recognisably corporate. Reviewer-handle salutations like "Dear B4796AOlouiseo" read as machine-generated.

Taiko is the only operator with a named human at the keyboard — Roy Tomassen, Susanne Hatje. That earns trust the Okura template doesn't. But Taiko replies selectively and slowly (Roy's reply to Raquel E came 5 months after the review).

No peer combines all four: (1) high reply rate, (2) replies to negatives, (3) signed by a real human, (4) brand-distinct voice. Michiu can.

The bar Michiu must clear to just match the best (Sazanka) is already low — warm, long, polite, group-signed. The bar to clearly outclass the field is also low — sign with a name, reply within 48 hours, sound like a person rather than a hospitality template, and never duck a negative.

5. Recommendations for Michiu's reply strategy

Three moves, in priority order.

Move 1 — Sign every reply with a real name (Sutherland + Kahneman lens)

Reply "— Mark" or "— Sara" (already the convention in the example CSV at imports/example.csv). The Okura corporate sign-off is the ceiling for everyone else; a first name underneath is a small, legible signal that beats it. Sutherland's reframing logic: the marginal cost is one word, the perceived-value swing is large. Kahneman: a name triggers System-1 trust ("a real human reads these") that "The Michiu Restaurant Team" never will.

This is the single highest-leverage move. Taiko already does it part-time. Nobody else does. Michiu should do it 100% of the time.

Move 2 — Reply to every 1–3★ review, fast, accountable, never defensive (Guidara lens)

Six of ten peers literally do not respond to bad reviews. Hosokawa replies to praise but ghosts complaints — the worst of the three options because the asymmetry is visible to any prospective guest scrolling the listing. The Sazanka Louise O reply is the floor: "I would like to start by apologizing for the food being below our standard… we truly value your feedback." Michiu's brand-voice prompt should beat that floor by being specific to the complaint (name the dry sushi, name the cold dish, name the loud music) rather than generic. Specificity is the brand-voice tell from Review-Reply-Prompt.md already — it just needs to fire on negatives, not only positives.

Target SLA: 48 hours, not Roy Tomassen's 5 months.

Move 3 — Reply in the language the guest used (Godin + GaryVee lens)

The Roy Tomassen reply to Raquel E in Dutch is a moment most peers don't even attempt. Michiu's dual NL/EN guest base (Status Builders + Connoisseurs Dutch-leaning, RAI corporates English-leaning, expats mixed) makes language-matching a ground-level expectation, not a flourish. The 5-voice prompt system already supports this; the production rule should be: detect language → reply in that language → never code-switch within one reply unless the original review did.

Combined effect: Michiu becomes the only Asian restaurant in Amsterdam where every reviewer — 5★ or 1★, NL or EN — gets a fast, named, specific reply within two days. None of the ten peers does this. The 5-voice prompt already produces the content; these three behaviours determine whether it lands as voice or evaporates as templated noise.

Sources

• Yamazato Tripadvisor
• Sazanka Tripadvisor
• Taiko Tripadvisor
• Hosokawa Tripadvisor
• Nanbu Tripadvisor
• Sichuan Food Tripadvisor
• Oceania Tripadvisor
• Sapporo Teppanyaki Tripadvisor
• Oshima Tripadvisor
• Michiu Tripadvisor
• Michiu — RestaurantGuru (Google mirror)
• Nanbu — RestaurantGuru (Google mirror)
• Sichuan Food — RestaurantGuru (Google mirror)
• Hatsune website

Methodology caveat: Google Maps requires a JavaScript-loaded EU consent flow that the WebFetch crawler cannot complete; review-reply text is not present in the static HTML. Tripadvisor exposes owner replies in its server-rendered HTML, so it was used as the primary source. RestaurantGuru re-hosts Google reviews and was used to spot-check Google-side replies — none surfaced for any peer except Yamazato/Sazanka indirectly (via Tripadvisor cross-platform consistency). Operators who reply on Tripadvisor reply on Google; operators who don't, don't. Any peer marked as "no replies" should be re-verified once Michiu has Google Business Profile API access (per docs/finding-reviews.md).