Omnichannel Return Policy Knowledge Base Gap Analysis
Identify discrepancies and customer friction points across retail return and exchange knowledge base articles.
Use this prompt when updating retail support content after policy shifts or channel expansions. It pinpoints knowledge gaps between digital self-service articles and physical store return workflows.
Role: Principal Omnichannel Customer Experience Architect with fifteen years of retail operations expertise.
Context
- Retail brand: {{retail_brand_name}}
- Core product categories: {{product_categories}}
- Existing policy documentation: {{current_kb_articles}}
- Recent policy and operational changes: {{return_policy_changes}}
- High-volume ticket themes: {{support_ticket_trends}}
- Applicable commerce channels: {{target_channels}}
Task
Conduct a rigorous knowledge gap and friction analysis comparing current self-service articles with updated return policies across all retail channels, delivering prioritized recommendations to reduce support contact rates.
Method
- Map {{current_kb_articles}} against {{return_policy_changes}} to isolate outdated conditions, timeline discrepancies, and contradictory rules.
- Cross-reference {{support_ticket_trends}} to identify high-friction customer queries currently unaddressed by self-service documentation.
- Evaluate channel parity across {{target_channels}}, ensuring buy-online-return-in-store (BORIS) and mail-in rules are distinct and explicit.
- Analyze readability and jargon within the content for {{product_categories}}, highlighting restrictive terms that confuse shoppers.
- Score each article across four criteria: policy accuracy, channel consistency, findability, and dispute-prevention efficacy.
- Classify discovered documentation deficiencies by customer impact, contact deflection potential, and operational risk.
- Formulate specific copy corrections, layout adjustments, and new topic requirements for each flagged knowledge asset.
Constraints
- Recommendations MUST directly cite contradictory phrasing between {{current_kb_articles}} and {{return_policy_changes}}.
- MUST NOT suggest adding unstructured policy text that exceeds an eighth-grade reading comprehension level.
- Findings must distinguish between physical retail rules and digital e-commerce workflows.
- Prioritization must reflect ticket volume severity indicated in {{support_ticket_trends}}.
Output format
Provide an analysis document with the following structure:
- Executive Summary (under 200 words)
- Policy Inconsistency Matrix (markdown table: Article Title, Current Stated Policy, Actual Policy, Severity Score 1-5)
- Channel-Specific Friction Audit (detailed findings grouped by channel in {{target_channels}})
- High-Volume Inquiry Coverage Gaps (bulleted analysis linking to {{support_ticket_trends}})
- Remediation Roadmap (table: Topic, Action Required, Expected Deflection Lift, Implementation Effort)
Self-review
- Confirm every channel in {{target_channels}} has dedicated analysis.
- Verify that all identified policy contradictions cite exact snippets from {{current_kb_articles}}.
- Check that the total remediation roadmap contains actionable, concrete article revisions.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.