View Storefront →

Refund

mike.wilder.12@gmail.com · landed in losangeles@forknfilm.com

2 messages
State:
Assigned:
  • mike.wilder.12@gmail.comto losangeles@forknfilm.comInbound
    5/24/2026, 9:16:59 PM

    Refund

    Hi,
    Our Fork and Film was cancelled for show on May 16th. We were told to go reschedule but unfortunately there are no shows available. I’ve checked quite a few times. So at this point, I think it’s best if I get a refund instead. 
    
    Thanks. 
    
    Michael Wilder 
    Sent from my iPhone
  • losangeles@forknfilm.comto Michael Wilder <mike.wilder.12@gmail.com>Reply (operator)
    5/25/2026, 1:17:36 AM

    Re: Refund

    Dear Michael,

    I sincerely apologize for the last-minute cancellation. We know how much anticipation and planning go into a special night out, and we’re truly sorry for the disruption this caused.

    Please know we made this decision only after considering every possible option. We completely understand your decision not to reschedule and are happy to accommodate your refund request. Refunds may take longer than usual as we’re currently managing high volume, but we’ll keep you updated.

    If you change your mind and would like to reschedule your tickets for another event, we’d be happy to offer a complimentary VIP upgrade as a gesture of appreciation.

    If you have any questions in the meantime, please don’t hesitate to reach out. We’re happy to help. We hope to have the pleasure of hosting you at Fork n’ Film in the future.

    Warm regards,

    Alex


    On Sun, May 24, 2026 at 2:17 PM Michael Wilder <mike.wilder.12@gmail.com> wrote:
    Hi,
    Our Fork and Film was cancelled for show on May 16th. We were told to go reschedule but unfortunately there are no shows available. I’ve checked quite a few times. So at this point, I think it’s best if I get a refund instead.

    Thanks.

    Michael Wilder
    Sent from my iPhone
    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.