AIプロンプト: 顧客フィードバック

アンケート、NPSプログラム、レビュー管理、フィードバックから製品への連携パイプラインで、顧客フィードバックを収集・分析・活用しましょう。

アンケートデザイナー

正直で実用的な回答が得られるアンケートを作成する

I need a customer feedback survey for [product/service/experience].

Goal of the survey: [what you want to learn]
Audience: [who will fill it out]
Survey length target: [number of questions]
Distribution method: [email, in-app, post-purchase, etc.]
Last survey sent: [when, or never]

Design the survey:
1. 8-12 questions in optimal order (easy to hard, closed to open)
2. A mix of rating scales, multiple choice, and open-ended questions
3. The one question that reveals the most actionable insight
4. NPS question placement and follow-up question for detractors
5. An incentive strategy that increases completion without biasing results
6. A pre-survey message that explains why their feedback matters (under 50 words)

プロのコツ

最も重要な質問は3番目に配置しましょう。最初の2問は回答者をウォームアップしコミットメントを構築します。3問目までに十分投資され、想い的に流さず熟考した回答をしてくれます。

テスト済み Mar 15, 2026

フィードバックアナライザー

非構造化の顧客フィードバックからパターンを見つける

Analyze this customer feedback and tell me what to prioritize:

[Paste 20-50 pieces of customer feedback: reviews, survey responses, support tickets, social comments]

Product/service: [what they're giving feedback on]
Recent changes: [anything you've changed recently]
Known issues: [problems you're already aware of]

Provide:
1. Theme analysis: group feedback into 5-7 categories with frequency counts
2. Sentiment breakdown: positive, negative, neutral percentages
3. The #1 issue to fix immediately (biggest impact, most mentioned)
4. Hidden insights: feedback patterns that aren't obvious on first read
5. Exact customer quotes that best represent each theme
6. A prioritized action plan: what to fix this week, this month, this quarter

プロのコツ

タイプミスや感情を含む生のフィードバックをそのまま含めましょう。AIは整理された要約よりもフィルタリングされていない顧客の言葉からより多くのインサイトを抽出します。生のフィードバックの怒りや興奮が、本当に重要なことを明らかにします。

テスト済み Mar 15, 2026

レビューレスポンダー

オンラインレビューにプロに大規模で返信する

Help me respond to these customer reviews:

[Paste 5-10 reviews with star ratings]

Business type: [what you do]
Brand voice: [professional/friendly/empathetic/casual]
Common misconceptions: [things reviewers often get wrong]
Changes you've made: [improvements based on past feedback]

For each review, write:
1. A personalized response (not generic 'thank you for your feedback')
2. Acknowledgment of their specific experience
3. For negative reviews: what you're doing to address the issue
4. For positive reviews: a genuine reaction that encourages loyalty
5. A subtle invitation to return or try something new
6. Flag any reviews that need private follow-up (and a DM template)

プロのコツ

ネガティブレビューには4時間以内、ポジティブレビューには24時間以内に返信しましょう。ネガティブレビューへの素早い対応は気にかけていることを示します。ポジティブレビューへの返信が遅れても問題ありません――満足している顧客は不安に待っていないからです。

テスト済み Mar 15, 2026

NPSアクションプラン

NPSスコアを測定可能な改善に変える

Help me act on our NPS results.

Current NPS score: [number]
Previous NPS score: [number and when]
Promoters feedback themes: [what happy customers say]
Detractors feedback themes: [what unhappy customers say]
Passives feedback themes: [what neutral customers say]
Response rate: [percentage who responded]

Build an NPS action plan:
1. Score interpretation: what our NPS really means in context
2. Top 3 actions to convert passives to promoters
3. Top 3 actions to reduce detractor volume
4. A promoter program: how to activate happy customers as advocates
5. Detractor rescue workflow: steps to save at-risk customers
6. Quarterly NPS improvement targets with specific initiatives for each

プロのコツ

デトラクターには個人的に電話しましょう。低いスコアをつけた人への本物の人間からの電話は、30〜40%を満足した顧客に戻します。AIはスクリプトを書けますが、信頼を再構築する実際の仕事は人間の電話が行います。

テスト済み Mar 15, 2026

機能リクエスト優先順位付け

ビジネスロジックで顧客の機能リクエストに優先順位を付ける

Help me prioritize these feature requests from customers:

[List 10-15 feature requests with: who requested it, how many times it's been asked, customer tier/value]

Product roadmap capacity: [how many features you can build this quarter]
Strategic priorities: [company goals this year]
Competitor features: [what competitors have that you don't]
Technical constraints: [anything limiting what you can build]

Prioritize and provide:
1. A scoring matrix: impact (revenue, retention, acquisition) x effort
2. The top 5 features to build, in order, with business justification
3. Features to explicitly NOT build (and how to communicate that)
4. A 'quick wins' list: low-effort features that delight customers
5. A customer communication plan for each decision (yes, not yet, no)
6. A feedback loop: how to validate the priority order with customers before building

プロのコツ

顧客に「この機能を作ったら何を使わなくなりますか?」と聞きましょう。「この機能が欲しいですか?」ではなく。前者は実際の価値トレードオフを明らかにします。後者は常に「はい」という無意味な回答になります。

テスト済み Mar 15, 2026

フィードバック→プロダクトパイプライン

顧客フィードバックを製品の意思決定に直結する仕組みを作る

Help me build a system that connects customer feedback directly to product decisions.

Current state: [how feedback reaches the product team today — or doesn't]
Feedback sources: [support tickets, surveys, reviews, social, sales calls, churned customer interviews]
Product team structure: [PMs, designers, engineers — how they work]
Sprint/release cadence: [how often you ship]
Biggest gap: [the disconnect between what customers say and what gets built]

Design a feedback-to-product pipeline:
1. Collection layer: how to tag and categorize feedback at the source (support, sales, reviews) with consistent taxonomy
2. Aggregation layer: how to centralize feedback from all sources into one view with theme detection
3. Signal detection: how to distinguish noise (one loud customer) from signal (pattern across many)
4. Product integration: how to inject customer evidence into sprint planning, roadmap reviews, and design critiques
5. Closed loop: how to notify customers when their feedback becomes a shipped feature
6. Measurement: how to track whether the pipeline is actually influencing product decisions (not just existing on paper)

プロのコツ

フィードバックから製品へのパイプラインは、製品チームが要約レポートしか見ないときに失敗します。Slackチャンネル、Jiraチケット、スプリント計画に生の顧客の声を流し込むことで、どんなダッシュボードよりも共感と緊急性が生まれます。すべての意思決定ポイントに顧客の実際の声を届けましょう。

テスト済み Mar 15, 2026

フィードバックループビルダー

継続的な顧客フィードバックエコシステムを構築する

Help me build a continuous customer feedback system.

Business type: [product/service/SaaS/e-commerce]
Customer base size: [number of active customers]
Current feedback sources: [surveys, support tickets, reviews, social — or none]
Team responsible: [who handles feedback]
Biggest feedback gap: [what you don't know about your customers]

Design a feedback ecosystem:
1. Feedback collection touchpoints: when and where to ask (map to customer journey)
2. Passive feedback sources: signals you can read without asking
3. A feedback aggregation system: how to centralize data from all sources
4. A weekly feedback review ritual: agenda, attendees, and action format
5. Closed-loop process: how to tell customers their feedback led to changes
6. Quarterly 'voice of customer' report template for leadership

プロのコツ

クローズドループがすべてです。フィードバックに基づいて変更を行ったら、それをリクエストしたすべての顧客にメールしましょう。「お客様の声を受け、実現しました」は送れる最も強力なリテンションメッセージです――そしてコストはかかりません。

テスト済み Mar 15, 2026

NailedItで試す

上記のプロンプトをNailedItに貼り付けて、モデルを並べて比較しましょう。