View Storefront →

Refund Update

ashbash.sc@gmail.com · landed in info@forknfilm.com

2 messages
State:
Assigned:
  • ashbash.sc@gmail.comto "info@forknfilm.com" <info@forknfilm.com>Inbound
    9/28/2026, 7:58:25 AM

    Refund Update

    Hello, it has been another month and I have yet to receive any update in regards to my refund request. 
  • info@forknfilm.comto Ashley Chavez <ashbash.sc@gmail.com>Reply (operator)
    9/28/2026, 6:20:57 PM

    Re: Refund Update

    Hello Ashley,

    Thank you for checking in regarding your refund.

    First, we sincerely apologize for the delay in responding to your previous messages. We recently experienced an issue with our communication channels that prevented us from seeing some incoming emails, including your earlier attempts to reach us. We’re very sorry that you had to reach out multiple times before receiving a response, and we truly appreciate your patience.

    We understand how important receiving your refund is. Our team is actively working through refund requests and processing them as quickly as possible.

    We know some guests have been waiting longer than expected. While we’re unable to provide a specific timeline at this time, we also want to be transparent and avoid giving you a timeframe that we cannot confidently guarantee. Your refund is still being processed, and we’ll be in touch as soon as it has been finalized.

    Your refund remains on our radar, and you will receive a confirmation for your records once it has been completed.

    We sincerely appreciate your patience and understanding while we work to get this completed for you, and again, we apologize for the delay in communication.

    Warmest regards,
    The Fork n’ Film Team

    On Mon, Sep 28, 2026 at 12:58 AM Ashley Chavez <ashbash.sc@gmail.com> wrote:
    Hello, it has been another month and I have yet to receive any update in regards to my refund request. 
    DeliveredOpenedClicked

Reply

Draft with AI: pick an outcome

Reply sends natively via Gmail (clean threading). AI draft uses thread + order context + FAQs; always editable before send.