View Storefront →

Refund

nicolasgdiez@gmail.com · landed in info@forknfilm.com

2 messages
State:
Assigned:
  • nicolasgdiez@gmail.comto info@forknfilm.comInbound
    5/22/2026, 3:04:10 AM

    Refund

    To whom it may concern,

    I sent an email last night regarding a refund for two cancelled bookings. My name is Nicolas Diez and I had purchased 4 tickets to see Cloudy with a Chance of Meatballs on Saturday May 9th at 6:30pm at the Cambira Hotel in Detroit Michigan. I had just received a second cancellation for 3 tickets purchased to see Lilo & Stitch at 6:30pm at the Cambira Hotel in Detroit Michigan. 

    The tickets for Cloudy with a Chance of Meatballs were purchased on February 21st this year, as well as the tickets for Lilo & Stitch. I do not want a credit to reschedule. I would like a full refund to the original form of payment.

    I look forward to hearing from you,

    Nicolas Diez
  • nicolasgdiez@gmail.comto info@forknfilm.comInbound
    5/27/2026, 7:50:01 AM

    Fwd: Refund


    ---------- Forwarded message ---------
    From: Nicolas Diez <nicolasgdiez@gmail.com>
    Date: Thu, May 21, 2026 at 11:04 PM
    Subject: Refund
    To: <info@forknfilm.com>


    To whom it may concern,

    I sent an email last night regarding a refund for two cancelled bookings. My name is Nicolas Diez and I had purchased 4 tickets to see Cloudy with a Chance of Meatballs on Saturday May 9th at 6:30pm at the Cambira Hotel in Detroit Michigan. I had just received a second cancellation for 3 tickets purchased to see Lilo & Stitch at 6:30pm at the Cambira Hotel in Detroit Michigan. 

    The tickets for Cloudy with a Chance of Meatballs were purchased on February 21st this year, as well as the tickets for Lilo & Stitch were purchased February 20th of this year. I do not want a credit to reschedule. I would like a full refund to the original form of payment.

    I look forward to hearing from you,

    Nicolas Diez

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.