Knowledge base
AuraScore 89/100

Omnichannel Returns Policy Knowledge Specification

Standardize complex retail returns and exchanges into structured customer-facing and agent-ready articles.

Use this template when aligning retail return policies across digital and physical store touchpoints. It creates an unambiguous article specification covering exceptions, workflows, and edge cases.

Template

Role: Senior Customer Experience Content Architect with 12 years of omnichannel retail documentation expertise.

Context

  • Brand identity and positioning: {{brand_name}}
  • Sales touchpoints and distribution channels: {{retail_channel_mix}}
  • Standard return and exchange eligibility window: {{return_window_days}}
  • Excluded inventory and hygiene-restricted items: {{non_returnable_categories}}
  • Processing and credit reconciliation turnaround: {{refund_settlement_timeline}}
  • VIP or loyalty program deviations: {{tier_level_exceptions}}

Task

Draft an exhaustive omnichannel returns knowledge base article specification that equips retail support agents and self-service shoppers with explicit, non-conflicting return instructions across digital and brick-and-mortar touchpoints.

Method

  1. Map out the standard shopper return journey for {{brand_name}} across each channel in {{retail_channel_mix}}.
  2. Formulate clear eligibility requirements anchored on {{return_window_days}} and explicitly catalog all item restrictions under {{non_returnable_categories}}.
  3. Define step-by-step instructions for initiate-by-mail versus in-store drop-off return methods.
  4. Detail the financial settlement sequence, referencing {{refund_settlement_timeline}} for payment method contingencies.
  5. Integrate loyalty program handling guidelines to address differentiated policies defined in {{tier_level_exceptions}}.
  6. Specify visual cues, callout boxes for common friction points, and inline policy verification criteria.
  7. Construct a troubleshooting matrix for edge cases such as missing receipts, gifts, and damaged in-transit deliveries.
  8. Establish agent-only internal notes and verification checklist distinct from public consumer text.

Constraints

  • MUST maintain strict distinction between customer-facing copy and tier-one internal processing notes.
  • MUST include a dedicated section addressing cross-channel purchase and return scenarios.
  • Do not use ambiguous policy language like 'at management discretion' without specific operational rules.
  • MUST NOT exceed 1,200 words in the final generated specification.

Output format

Provide the specification in four sequential sections:

  1. Metadata & Governance (Audience, Channel Scope, Review Cadence)
  2. Customer Self-Service Article Layout (Hero summary, Step-by-step procedure, Settlement timelines)
  3. Edge Case & Policy Variance Matrix (Tabular format: Scenario, Policy rule, Agent action)
  4. Internal Triage Notes (Verification fields, CRM tagging rules)

Self-review

  • Confirm every channel in {{retail_channel_mix}} has corresponding intake instructions.
  • Verify that exclusions in {{non_returnable_categories}} include clear rationale to minimize customer friction.
  • Check that payment settlement expectations in {{refund_settlement_timeline}} account for original payment methods.
AuraScore breakdown
89/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification12/14 · Strong

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness5/5 · Strong

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

support-success
support-knowledge-base
retail-consumer-goods
returns
omnichannel
customer-support