Tickets
AuraScore 83/100

Premium VOD Purchase Dispute Ticket Remediation Script

Create an escalated support script for transactional video-on-demand billing disputes, accidental rentals, and payment errors.

Use this template when media consumers submit tickets regarding unexpected pay-per-view charges, duplicate rentals, or failed playback refunds. It standardizes resolution dialogue across billing gateways.

Template

Role: Tier-3 Billing and Entitlement Support Lead for premier VOD and theatrical streaming services.

Context

  • Transaction Category: {{transaction_type}}
  • Disputed Transaction Amount: {{disputed_amount}}
  • Billing Gateway: {{payment_gateway_vendor}}
  • Title in Dispute: {{content_title}}
  • Policy Grace Window: {{grace_period_days}}
  • Customer Tenure: {{subscriber_loyalty_years}}

Task

Develop an escalation support ticket response script for resolving disputed transactional rentals and purchases for {{content_title}}, balancing consumer retention with fraud prevention policies.

Method

  1. Review the dispute details regarding {{transaction_type}} and cross-reference with {{payment_gateway_vendor}} refund capabilities.
  2. Evaluate customer history based on {{subscriber_loyalty_years}} against the standard {{grace_period_days}} return policy.
  3. Write an opening acknowledgment confirming receipt of the ticket regarding {{disputed_amount}} for {{content_title}}.
  4. Design a decision-tree response script based on viewing telemetry (e.g., 0% watched vs. >50% watched).
  5. Detail the approved remediation path (immediate gateway refund, store wallet credit, or entitlement re-issue).
  6. Embed clear account-security guidance to prevent future unauthorized household purchases (PIN setup, biometric auth).
  7. Draft closing reassurance message setting expectations on banking processing cycles for {{payment_gateway_vendor}}.

Constraints

  • MUST follow payment network compliance and anti-fraud guidelines.
  • MUST NOT promise cash refunds if consumption logs exceed the threshold defined by {{grace_period_days}} without manager override.
  • Tone MUST balance financial firmness with customer retention empathy.
  • The script MUST provide both an approved refund branch and a compliant denial/partial credit branch.

Output format

  • Part 1: Ticket Intake & Verification Script (Written customer reply, max 100 words).
  • Part 2: Decision Tree Response Scripts (Two branches: Approved Refund vs. Alternative Wallet Credit/Policy Denial; max 150 words each).
  • Part 3: Account Hardening & Upsell Advisory Script (Parental control instructions and retention note; under 80 words).

Self-review

  • Does the script account for the specific limitations of {{payment_gateway_vendor}}?
  • Is the loyalty factor ({{subscriber_loyalty_years}}) utilized to determine concession elasticity?
  • Are both approval and denial scenarios clearly scripted?
AuraScore breakdown
83/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 specification6/14 · Thin

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 efficiency7/10 · Adequate

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

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-tickets
media-entertainment
billing
vod
disputes