AI Report Library

GPT-6 Luna OpenAI · high · Work

PromptJapan izakaya customer complaints and operator struggles

ROLE

You are a qualitative market researcher who reads Japanese fluently. You analyze user-generated content (UGC) about restaurants in Japan.

OBJECTIVE

Find out what customers in Japan complain about when they visit izakaya, using ONLY user-generated content. Then work out what operational struggles those complaints reveal on the izakaya side. The end use is finding products or services that could be sold to izakaya operators to fix those struggles.

PARAMETERS

  • Time window: {{2024-10-01}} to {{2026-10-04}}
  • Geography: Japan (all regions; note region when the source states it)
  • Report language: {{English}}. Keep every quote in its original language and add a translation.

SOURCE RULES (strict)

ALLOWED, posts written by individual customers only:

  • Review sites: 食べログ, Google Maps reviews, Retty, ホットペッパーグルメ口コミ, 一休, TripAdvisor
  • Social media and forums: X (Twitter), Instagram comments, Threads, YouTube comments, Yahoo!知恵袋, 発言小町, ガールズちゃんねる, 5ch, Reddit (r/japanlife, r/japan, r/JapanTravel), note (personal posts only) EXCLUDED (do not use as evidence, even if they quote reviews):
  • News articles, industry reports, surveys, statistics, consultancy or vendor blogs, PR, restaurant-owned accounts, listicles ("居酒屋の嫌なところ10選" summaries), and any AI-generated summary (including review-site AI summaries) If you cannot open a source and read the original post yourself, do not cite it. If you have no browsing access, say "NO BROWSING" at the top and stop. Do not answer from memory.

SEARCH GUIDANCE

Search mainly in Japanese. Treat these as starting points, not limits: 居酒屋 最悪 / 居酒屋 二度と行かない / お通し 不満 / 席料 チャージ 知らなかった / 飲み放題 ラストオーダー 早い / 料理 出てこない 居酒屋 / 店員 態度 居酒屋 / モバイルオーダー 居酒屋 不便 / タッチパネル 注文 / 居酒屋 うるさい 狭い / 居酒屋 タバコ 臭い / 予約 取れない 居酒屋 / 会計 間違い 居酒屋 / 2時間制 追い出された Also search in English for complaints from foreign visitors. Cover chain izakaya and independent izakaya, and say which one each piece of evidence concerns.

METHOD

  1. Collect complaint posts. Aim for 40 or more distinct posts from at least 4 different platforms. Do NOT pad. If you find fewer, report the real number.
  2. Group the complaints into themes. Map every theme to exactly ONE of these fixed domains so the results can be compared: D1 Food quality/portion | D2 Drinks/飲み放題 rules | D3 Staff attitude/service D4 Speed/wait times | D5 Ordering system (tablet/QR/mobile order) | D6 Price/billing/お通し/charges | D7 Seating/space/noise | D8 Smoking/smell | D9 Cleanliness/hygiene | D10 Reservations/time limits | D11 Payment methods | D12 Foreign-visitor/language | D13 Other (explain)
  3. For each theme, separate three layers and never mix them:
    • OBSERVED: what the users actually said (backed by quotes)
    • INFERRED: the operator-side struggle that likely causes it (for example, a labor shortage that causes slow service). Label it as inference.
    • OPPORTUNITY: what kind of product or service could address it. Label it as speculation.

OUTPUT FORMAT (follow exactly)

0. Run metadata

Model name, browsing/research mode, date run, number of posts reviewed, platforms used.

1. Evidence table

One row per post: | ID | Platform | URL | Post date | Venue type (chain/independent/unknown) | Region | Domain | Original quote (verbatim, max 2 sentences) | Translation | IDs: E01, E02, ... Copy quotes exactly. Do not paraphrase inside the quote column. If the post date or region is not shown, write "unknown". Do not guess.

2. Complaint themes (ranked by number of supporting posts in YOUR sample)

For each theme:

  • Theme name / Domain code
  • Supporting evidence IDs (e.g. E03, E11, E27) and the count
  • OBSERVED: 2-3 sentence summary
  • Severity signal: does it cause "never coming back", lower star ratings, or only mild annoyance? Cite IDs.
  • INFERRED operator struggle: [inference] ...
  • Confidence: High / Medium / Low, with a one-line reason Do not state percentages or claim anything about the whole population. Counts describe your sample only.

3. Operator struggle map

| Struggle (inferred) | Themes it explains | Evidence IDs | Confidence |

4. Sales opportunity hypotheses

| Struggle | Solution category | Why the complaints suggest the izakaya would pay for it | Counter-evidence or risk | Label every row [speculation]. Do not name vendors unless asked.

5. Self-audit

  • Claims you are least sure about
  • Platforms you could not access or search well
  • Possible biases in the sample (for example, angry reviewers are over-represented, or tourist-area venues dominate)
  • Anything you EXCLUDED because it was not genuine UGC

6. Machine-readable summary

A JSON block in this shape: {"model":"","run_date":"","posts_reviewed":0, "themes":[{"name":"","domain":"D1","evidence_ids":[],"count":0,"confidence":"High"}], "struggles":[{"name":"","theme_names":[],"confidence":"Medium"}]}

ACCURACY RULES

  • Every factual statement in sections 2 and 3 must cite evidence IDs.
  • Never invent a URL, quote, date, or reviewer. If you are unsure that a quote is exact, leave it out.
  • Prefer fewer, verified items over many unverified ones.
Model
GPT-6 Luna
Effort
high
Operator
OpenAI
Mode
Work
Search type
Web Search
Run date
Oct 5, 2026
Pack
None
Content language
English
Length
2671 words
Links
13
Domains
5
Tables
3

as of

Output

0. Run metadata

Model name: GPT-6 Pro (model label available in this run)
Browsing/research mode: Web search; original customer posts opened and checked
Date run: 2026-10-04
Posts reviewed: 14 qualifying posts retained
Platforms used: Hot Pepper Gourmet, Tabelog, Tripadvisor, Yahoo! Chiebukuro, Reddit

The search target was 40 posts, but I retained 14 that I could verify against an opened post within the time window. The sample includes chain and independent venues, though many posts did not make venue ownership clear. Counts below describe this sample only.

1. Evidence table

IDPlatformURLPost dateVenue type (chain/independent/unknown)RegionDomainOriginal quote (verbatim, max 2 sentences)Translation
E01Hot Pepper GourmetPost ホットペッパーグルメ2026-03-30Chain (新時代)Tokoname, AichiD3「そのほかの理由か分かりませんが店員さんの愛想が悪かったり、(お会計してくれた女性は良かったです) お席まで案内してくれなかったり」“I don’t know if there was another reason, but some staff were unfriendly … and they didn’t show us to our seats.”
E02Hot Pepper GourmetPost ホットペッパーグルメ2026-07-29Chain (新時代)Ueda, Nagoya, AichiD6「ちょっと席料が高いかな?」“Maybe the seating charge is a little high?”
E03Hot Pepper GourmetPost ホットペッパーグルメ2026-07-04UnknownAgeo, SaitamaD4「料理の提供が非常に遅い。ステーキを注文したが噛み切りづらく美味しくなかった。」“The food took extremely long to arrive. I ordered steak, but it was hard to chew and didn’t taste good.”
E04Hot Pepper GourmetPost ホットペッパーグルメ2025-03-29UnknownUnknownD4「土曜で混んでたので料理提供が少し遅いなと思いました。」“It was crowded on Saturday, so I thought the food was a little slow to arrive.”
E05Hot Pepper GourmetPost ホットペッパーグルメ2026-08-04Chain (炭火酒蔵 炎)Shin-Sapporo, HokkaidoD3「ただ1人店員さんで残念な方がいた。いちいち聴いたことに対して、は?って態度」“There was one disappointing staff member. Whenever I asked something, they reacted as if to say, ‘Huh?’”
E06TripadvisorPost トリップアドバイザー2025-05-09UnknownShinjuku, TokyoD5「QRコードを読み込んでの ネット注文なのは 今時なので 仕方ないのですが、ネット注文を 導入するなら 店で Wi-Fiを 用意しておくのは 必修だと思います。」“I understand QR-code ordering is common now, but if a restaurant uses online ordering, I think it should provide Wi-Fi.”
E07TripadvisorPost トリップアドバイザー2025-10-09UnknownShinjuku, TokyoD10「個室で予約しても、全く個室じゃないばかりか、他店に案内され、そこの内装はカーブとは全く似つかないただの居酒屋。しかもそこでさえ個室ではない。」“Even though I reserved a private room, it wasn’t private at all; we were sent to another restaurant whose interior looked nothing like The Cave, just an ordinary izakaya. And even there, it wasn’t a private room.”
E08TripadvisorPost トリップアドバイザー2025-08-14UnknownNamba, OsakaD4「最後の釜飯がなかなか来なくて一度店員さんに聞くと「お作りします」。忘れてるかな?と言うくらい時間が経ったのでもう一度聞くと『今、調理中です』」“The final kamameshi took a long time, so I asked a staff member, who said, ‘We’ll make it.’ So much time passed that I wondered if they had forgotten it; when I asked again, they said, ‘It’s cooking now.’”
E09Yahoo! ChiebukuroPost Yahoo!知恵袋2025-12-01Independent (described by poster)UnknownD6「頼んでいないもののオーダーが含まれていたようで、店員を呼び、かなり強めな口調で問いただし始めました。ちなみにその店はQRコードでのオーダースタイルです。」“It seemed the bill included items they hadn’t ordered, so they called a staff member and began questioning them rather forcefully. Incidentally, that restaurant used QR-code ordering.”
E10Reddit, r/JapanTravelTipsPost reddit.com2024-11-23Unknown (multiple venues)Tokyo, Osaka, Takayama, Niigata mentionedD10“all reserved seats are taken”「予約席はすべて埋まっています」
E11TabelogPost 赤池/居酒屋 [食べログ]2026-08 (day unknown)UnknownAichi (venue in Aichi)D4「予約時に、混雑が予想されるので事前に注文予約した方が良いと言われて、電話でコースを予約していたが、結局1時間以上提供されず、せっかくの会が台無しでした」“When I booked, I was told to pre-order because it was expected to be busy. I booked a course by phone, but it still wasn’t served for over an hour, ruining the gathering.”
E12Hot Pepper GourmetPost ホットペッパーグルメ2026-08-08Chain (それゆけ!鶏ヤロー!)Mizonokuchi, KanagawaD10「ラストオーダー30分前は理解できますが、2時間40分くらいで退席させられた。ラストオーダーで頼んだお酒か来たばかりで残っていたのにも関わらず…」“I understand last orders being 30 minutes before the end, but we were made to leave after about two hours and 40 minutes, even though the drink I ordered at last call had only just arrived and was still there…”
E13Hot Pepper GourmetPost ホットペッパーグルメ2026-08-13Chain (とりいちず)Miyazaki City, MiyazakiD10「コース(2時間)に飲み放題延長(合計3時間)を付けて、ホットペッパーで予約。当日、伺うと飲み放題延長が適用されておらず最初に付けてもらう。」“I booked a two-hour course with an extension to three hours of all-you-can-drink through Hot Pepper. When we arrived, the extension hadn’t been applied, so we had to get it added first.”
E14Hot Pepper GourmetPost ホットペッパーグルメ2026-08-31UnknownMizonokuchi, KanagawaD6「家に帰ってレシートを見たら、出されても居ないお通し代がレシートに載っててビックリしました。お料理もそこそこ美味しくコスパも良かったと思っていましたが、出されても居ないお通し代を請求されてたのを知って評価はダダ下がりしました。」“When I got home and checked the receipt, I was surprised to see a charge for an otoshi that hadn’t been served. I thought the food was decent and good value, but learning I’d been charged for an otoshi I never received made my rating plummet.”

2. Complaint themes (ranked by number of supporting posts in YOUR sample)

Slow or missing food service / Domain D4

  • Supporting evidence IDs: E03, E04, E08, E11; count 4. ホットペッパーグルメ
  • OBSERVED: Customers described food arriving slowly, including a Saturday visit, a long wait for a final dish, and a booked course that reportedly took over an hour to arrive. One reviewer also criticized the steak’s texture and taste. (E03, E04, E08, E11)
  • Severity signal: Mixed. E03 gave a one-star rating; E11 said the delay ruined a planned gathering. E04 rated the visit five stars despite noting a slight delay. (E03, E04, E11)
  • INFERRED operator struggle: [inference] The kitchen or service team may have trouble sequencing orders and tracking delayed dishes during busy periods. The posts do not establish the cause. (E03, E04, E08, E11)
  • Confidence: Medium; four firsthand reviews report delays, but the sample is small and conditions vary.

Reservation and time-limit failures / Domain D10

  • Supporting evidence IDs: E07, E10, E12, E13; count 4. トリップアドバイザー
  • OBSERVED: One customer said a reserved private room was not provided, one Reddit poster described repeatedly encountering “all reserved seats are taken” responses across cities, and two customers said booked or expected time arrangements were not honored as they understood them. (E07, E10, E12, E13)
  • Severity signal: E12 and E13 were rated one star. The Reddit post describes friction finding available venues, but does not state whether the poster avoided or revisited any venue. (E07, E10, E12, E13)
  • INFERRED operator struggle: [inference] Some venues may have gaps between booking information, floor assignment, and staff awareness of extensions or table turnover rules. The Reddit example could also reflect genuinely full venues rather than a process failure. (E07, E10, E12, E13)
  • Confidence: Medium; the posts describe concrete expectation mismatches, but not enough operational detail to identify a shared cause.

Billing and charge disputes / Domain D6

  • Supporting evidence IDs: E02, E09, E14; count 3. ホットペッパーグルメ
  • OBSERVED: Customers questioned the price of a seating charge, reported an apparent unrequested item on a bill, and reported being charged for an otoshi they said was never served. (E02, E09, E14)
  • Severity signal: E14 said the experience sharply lowered their rating. E02’s wording signals mild dissatisfaction. E09 is a witness account of another party’s dispute, so it is weaker evidence of the poster’s own customer outcome. (E02, E09, E14)
  • INFERRED operator struggle: [inference] Charge disclosure, order-to-bill reconciliation, or delivery confirmation may be inconsistent in these cases. The posts do not prove intentional overcharging. (E02, E09, E14)
  • Confidence: Medium; three posts describe charge concerns, but one is a bystander’s account and the situations differ.

Staff attitude and interaction / Domain D3

  • Supporting evidence IDs: E01, E05; count 2. ホットペッパーグルメ
  • OBSERVED: One customer reported unfriendly staff and no guidance to the table; another described a staff member responding dismissively to questions. (E01, E05)
  • Severity signal: E05 said the interaction spoiled the mood of the gathering and rated the visit three stars. E01 also mentioned some helpfulness from the employee handling payment, so the account was not uniformly negative about all staff. (E01, E05)
  • INFERRED operator struggle: [inference] Staff may be inconsistent in service behavior, guest handoffs, or handling questions. These posts do not show whether training, workload, or individual conduct was the cause. (E01, E05)
  • Confidence: Low; two posts describe staff interactions at different venues.

QR ordering friction / Domain D5

  • Supporting evidence IDs: E06; count 1. トリップアドバイザー
  • OBSERVED: A customer criticized a venue that used QR-code ordering without providing Wi-Fi and said the network connection created ordering stress. (E06)
  • Severity signal: The reviewer called the setup and service disappointing, but this post alone does not establish a return decision or rating impact. (E06)
  • INFERRED operator struggle: [inference] The ordering workflow may depend on guests having mobile data or successfully connecting to a network. (E06)
  • Confidence: Low; this is one customer’s report at one venue.

3. Operator struggle map

Struggle (inferred)Themes it explainsEvidence IDsConfidence
Tracking and sequencing kitchen tickets, especially for course meals and delayed dishesSlow or missing food service (D4)E03, E04, E08, E11Medium
Keeping reservation details, room assignments, extensions, and time-limit rules aligned across booking channels and floor staffReservation and time-limit failures (D10)E07, E10, E12, E13Medium
Making charges and served items match the receipt, with clear customer-facing disclosureBilling and charge disputes (D6)E02, E09, E14Medium
Maintaining consistent staff conduct and handoffs during guest interactionsStaff attitude and interaction (D3)E01, E05Low
Ensuring the QR-ordering path works for guests with limited or unreliable connectivityQR ordering friction (D5)E06Low

4. Sales opportunity hypotheses

StruggleSolution categoryWhy the complaints suggest the izakaya would pay for itCounter-evidence or risk
[speculation] Delayed and untracked dishesKitchen order queue visibility, delay alerts, and course-service checklists[speculation] Several posts describe long waits, including a course meal delay that the customer said ruined the gathering. Reducing missed or late dishes could protect repeat visits and group-booking satisfaction. (E03, E04, E08, E11)[speculation] These posts do not establish how often delays occur or whether a software tool would help; staffing, kitchen layout, or menu complexity may be the actual constraint.
[speculation] Reservation and time-limit mismatchesReservation synchronization, table/room assignment checks, and clear time-limit prompts[speculation] Customers reported a room mismatch and confusion around extended booking time. A tool that surfaces the reservation terms at check-in could reduce disputes. (E07, E12, E13)[speculation] The Reddit example may simply reflect high demand, and venues may already have effective booking systems. (E10)
[speculation] Charge disputes and unserved otoshi chargesReceipt-to-order reconciliation and served-item confirmation[speculation] Reports of unexplained charges can directly harm trust and ratings; an auditable order and delivery record may help staff resolve discrepancies. (E02, E09, E14)[speculation] The sample does not show whether these were system errors, staff mistakes, customer misunderstandings, or isolated incidents. The posts do not reveal willingness to pay.
[speculation] Uneven staff interactionsShort service scripts, onboarding materials, and shift-level coaching[speculation] Customers explicitly noticed dismissive interactions and lack of basic guidance. (E01, E05)[speculation] Only two posts support this theme, and training materials cannot by themselves solve workload or management issues.
[speculation] QR ordering depends on guest connectivityGuest Wi-Fi setup and a fallback ordering path[speculation] One customer described the QR-order flow as stressful without reliable Wi-Fi. (E06)[speculation] This is a single report; providing Wi-Fi may add setup and support work, and other guests may have had no difficulty.

5. Self-audit

  • Claims I am least sure about: The operational causes are inferences from customer descriptions, not confirmed root causes. The Reddit post records repeated reservation difficulty across several cities, but it does not identify particular venues or prove those venues mishandled reservations. (E10)
  • Platforms I could not access or search well: I did not obtain original posts that met the verification standard from Google Maps, X, Instagram comments, Threads, YouTube comments, Retty, or the other listed forums. I found and opened posts from five platforms in total.
  • Possible sample biases: Critical customers are more likely to write detailed reviews than satisfied customers. Hot Pepper Gourmet contributes the largest share of this sample. The evidence also skews toward urban or destination areas where review posts were discoverable.
  • Anything excluded because it was not genuine UGC: I excluded review summaries, restaurant-owned material, review-analysis blogs, out-of-window posts, and pages where the underlying individual post could not be checked. I also excluded older Tripadvisor reviews visible on pages that contained eligible newer posts.
  • Method note: The sample contains 14 distinct posts, not 14 independent venues; the two Tripadvisor complaints about The Cave are separate posts about the same venue. Evidence is not a measure of complaint prevalence across Japan.

6. Machine-readable summary

{
  "model": "GPT-6 Pro",
  "run_date": "2026-10-04",
  "posts_reviewed": 14,
  "themes": [
    {
      "name": "Slow or missing food service",
      "domain": "D4",
      "evidence_ids": ["E03", "E04", "E08", "E11"],
      "count": 4,
      "confidence": "Medium"
    },
    {
      "name": "Reservation and time-limit failures",
      "domain": "D10",
      "evidence_ids": ["E07", "E10", "E12", "E13"],
      "count": 4,
      "confidence": "Medium"
    },
    {
      "name": "Billing and charge disputes",
      "domain": "D6",
      "evidence_ids": ["E02", "E09", "E14"],
      "count": 3,
      "confidence": "Medium"
    },
    {
      "name": "Staff attitude and interaction",
      "domain": "D3",
      "evidence_ids": ["E01", "E05"],
      "count": 2,
      "confidence": "Low"
    },
    {
      "name": "QR ordering friction",
      "domain": "D5",
      "evidence_ids": ["E06"],
      "count": 1,
      "confidence": "Low"
    }
  ],
  "struggles": [
    {
      "name": "Tracking and sequencing kitchen tickets",
      "theme_names": ["Slow or missing food service"],
      "confidence": "Medium"
    },
    {
      "name": "Aligning reservation details, room assignments, extensions, and time-limit rules",
      "theme_names": ["Reservation and time-limit failures"],
      "confidence": "Medium"
    },
    {
      "name": "Reconciling charges and served items with receipts",
      "theme_names": ["Billing and charge disputes"],
      "confidence": "Medium"
    },
    {
      "name": "Maintaining consistent staff conduct and handoffs",
      "theme_names": ["Staff attitude and interaction"],
      "confidence": "Low"
    },
    {
      "name": "Providing a reliable QR-ordering path despite connectivity limits",
      "theme_names": ["QR ordering friction"],
      "confidence": "Low"
    }
  ]
}