video LUTs first access reply

A practical support pattern for first access reply related to video LUTs. Adapt it to the exact files, instructions, license, and support policy published with your product.

View product preview Back to hub Delivery & Support

Use case

A customer buys LUT files and asks how to download, import, locate, or use them in editing software.

Writing rule

Keep the first sentence calm and product-specific. Do not promise editing-app compatibility, color results, device support, or creative outcome.

Compliance note

This is a self-serve copy resource, not a custom setup service, software support desk, compatibility guarantee, or purchase flow.

Draft reply

Subject: About your video LUTs access Hi [name], Thanks for reaching out. I understand the issue is [specific video LUTs issue]. I can help explain the product instructions and delivery details we publish for this digital item. Please send only your order number or purchase email if needed. Please do not send passwords, one-time codes, full card numbers, private account links, private files, API keys, mailbox access, or remote access. The next step is to check the delivery email, product instructions, file format notes, and support policy that apply to this product. Some install, import, print, edit, or open steps may vary by device, browser, app, or third-party software, so this reply does not guarantee those external outcomes. Thanks, [store name]

Customize safely

Replace [specific video LUTs issue] with a neutral phrase such as missing file, wrong format, import trouble, mobile access, license question, or bundle navigation.

Support boundary

Support can clarify the order and published instructions, but should not ask for account access or promise third-party software behavior.

Useful CTA

Link to Delivery & Support, Terms, product preview, product status, or the relevant product instructions.

Checklist

Does the reply identify the product type clearly?
Does it avoid asking for sensitive information?
Does it separate delivery from installation, import, printing, or app behavior?
Does it avoid official third-party support claims?
Does it avoid checkout, waitlist, or custom-service purchase language?