support review boundary for license-related refund question

A practical copy pattern for support review boundary. Adapt it to your actual Refund Policy, product page, and support route.

View product preview Back to hub Refund Policy

Use case

A customer misunderstood commercial use, sharing, resale, transfer, or license limits and asks for a refund.

Writing rule

Keep the first line empathetic and specific. Do not provide legal advice or create new rights. Link to published license and refund policy.

Compliance note

This is a self-serve copy resource, not legal advice, payment support, checkout, waitlist, hands-on service, or refund-processing service.

Draft copy

Hi [name], Thanks for reaching out. I understand this refund question is about license-related refund question. The published Refund Policy and product page are the source of truth for what support can review. If we need to locate an existing order, please send only the order number or purchase email through the official support route. Please do not send passwords, full card numbers, bank access, one-time codes, account access, IDs, API keys, mailbox access, or remote access. This message does not promise refund approval, denial, exception handling, credit, replacement access, payment-provider timing, or bank posting dates. Thanks, [store name]

Customize safely

Replace the issue with the exact customer claim, then link to the relevant Refund Policy, product page, and Delivery & Support page.

Useful support route

Use Refund Policy, Terms, Delivery & Support, product status, product preview, or Contact.

Do not overclaim

Do not promise refund outcomes, exceptions, payment timelines, legal conclusions, or payment-provider decisions.

Checklist

Does the reply show empathy?
Does it cite the published policy?
Does it avoid refund outcome promises?
Does it avoid sensitive data requests?
Does it avoid checkout or custom-service language?