View Storefront →

Re: Fork n' Film: Event Canceled

feliciajohnson9315@yahoo.com · landed in sanfrancisco@forknfilm.com

1 message
State:
Assigned:
  • feliciajohnson9315@yahoo.comto "Fork n' Film San Francisco" <sanfrancisco@forknfilm.com>Inbound
    6/6/2026, 12:31:49 AM

    Re: Fork n' Film: Event Canceled

    Hello,

    I have to be honest—this email is extremely frustrating and disappointing to receive. This is now the third time my Fork n' Film reservation has been canceled.

    What I don't understand is how payments were able to be collected on time, yet refunds are now delayed due to operational changes and restructuring. As a customer, I upheld my end of the transaction, and I expect the same level of urgency when it comes to returning my money.

    It's also confusing to see Fork n' Film continuing to promote and host events on social media while my reservation has been canceled for the third time. From a customer's perspective, that simply doesn't make sense.

    At this point, I would appreciate a clear timeline for when I can expect my full refund to be processed. After multiple cancellations and ongoing delays, my confidence in the company has been significantly impacted.

    I look forward to your prompt response and a concrete update regarding my refund.

    Thank you,

    Felicia Johnson 

    Sent from my iPhone

    On May 28, 2026, at 12:46 PM, Fork n' Film San Francisco <sanfrancisco@forknfilm.com> wrote:

    
    Dear Fork n' Film Guests, We regret to inform you that the Fork n’ Film shows scheduled for May & June have been canceled. We want to be honest and transparent: the company is currently undergoing major operational changes, and at this time we are not in a position to execute this event su‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ 
    Can't see this message? View in browser
    This email was sent from this site.
    If you no longer wish to receive this email, change your email preferences here.

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.