Getting our container delivered, and getting paid fairly for the trouble
PODS lost our fully loaded container and pushed delivery from July 10 to July 24, then labelled the change as if we asked for it. We didn't. This is the plan: get the container fast, and extract fair compensation, calmly and on paper, hitting several channels the same night.
The situation, in plain English
We paid PODS $3,051.15 to move our container from Brooklyn to Cleveland, delivery confirmed for July 10. On July 8 a rep (Ian) told us by phone the container was lost (contents said undamaged, unverified), that delivery would slip, and offered $100, refusing to put anything in writing. He mentioned July 13 verbally; the account still says July 24, and that verbal date is nowhere in the system.
Then the front line stonewalled us: the same day, chat agent Jeanrenaud B said he was "unable to assist," gave no reference number, pushed us to a billing phone line, and ended the chat. Ian's promised callback never came.
Two things make our position strong: PODS admitted the loss (their fault, not weather), and their own paperwork contradicts their excuse. The change notice says "as you requested," but we never asked to move the delivery later. The only date request we ever made was for an earlier delivery, and their own driver note records exactly that.
The deadline (who is home, when)
This is the clock everything runs on. The demand to PODS always says July 14. Internally we have a little more room through Haseeb, but we never tell PODS that: to them, July 24 is simply unacceptable because nobody is home.
| Window | Who is home in Cleveland | Can receive? |
|---|---|---|
| On or before July 14 | You + Haseeb | Yes, the ideal, and the date we demand |
| July 15 to 20 | Haseeb only (you are in California) | Yes, via Haseeb (internal backstop) |
| ~July 21 | Haseeb packing (flies July 22) | Marginal, treat July 20 as the hard limit |
| July 22 to 28 | Nobody (both away) | No. The July 24 date fails completely |
So: July 14 ideal, ~July 20 the absolute backstop via Haseeb, July 24 dead. That backstop is real negotiating room for us, but it stays private; revealing it just tells PODS its cheapest exit is a later date.
The strategy in one breath
Tonight we hit PODS on several channels in the same hour: log the formal demand, file a Better Business Bureau complaint, email the executives directly, and message the social-media team, all carrying the same short evidence packet. Make PODS quietly choose between fixing this now or having a documented, self-contradicted failure sitting in front of a regulator and a reporter. Calm, factual, relentless. Never angry, never threatening a lawsuit.
Why this works
- We don't fight where the contract is strong. The fine print says delivery dates aren't guaranteed and blocks knock-on costs (hotels, stress). So a big lawsuit threat is empty. We never go there.
- We fight where they're weak. They lost the container, their own file proves we asked for it earlier, and their front line refused to engage. That is exactly the documented, self-inflicted failure a company settles rather than let a reporter or regulator air.
- Speed comes from the channels that actually answer. The front line is a dead end (proven). The fast doors are the executive inbox, the social-media team (answering same-day this week), and, on the record, the BBB. We use all three at once.
- One evidence packet powers everything. A single page putting the "as you requested" email next to their own "you asked for earlier" driver note turns "they were slow" into "their own documents contradict each other." Every channel inherits it.
One extra lever: the timing (phrase it as a question, never a claim)
PODS's own July 8 emails contradict each other: the same day a rep said the container was lost, PODS emailed to confirm July 10 and pre-authorise a card hold. So we ask (never assert): when was it lost, and when did PODS know? If their scan logs show they knew while still confirming July 10, this stops being "a late delivery" and becomes a knowing deceptive act, which raises the pressure at the complaint stage. Until their logs answer it, it stays a question.
What to ask for, and what's realistic
The package (ask for all of it together, as one indivisible request)
- Delivery on or before July 14, confirmed in the MyPODS system and by email (a verbal date is not a commitment).
- Refund of the transport charge: $1,670.11 (the $1,601.26 long-distance transit plus the $68.85 fuel surcharge). This is the anchor: PODS was paid a specific amount to move a container it admits it lost.
- Displacement credit of $75/day from July 10 until actual delivery, on PODS's own goodwill practice: $300 by July 14, $1,050 at the current July 24. This is the line that makes every day of delay cost them more.
- Waive the fees: the $234.45 redelivery charge, the $75 fee, no July 9 card hold, and no promo/storage/rent recalculation (about $620 of exposure).
- Written correction of the record: a statement that the delay was PODS-caused and that we asked for earlier delivery.
Anchor: the full package (about $2,290 in cash/waivers at a July 14 delivery). Target: if they deliver by July 14, realistically $500 to $1,000 credit + all waivers + the correction; if it slips past July 14 it becomes a two-week lost-container case, and we hold firm on the full $1,670.11 + per-diem. Walk-away floor: $500 + all waivers + the written correction + a firm written date.
The money and Haseeb's Clinic reimbursement (how we keep the most)
Haseeb can claim up to $5,000 of moving costs from Cleveland Clinic on receipts, so the transport cost can be recovered once. The smartest, cleanest structure (the one we're using):
- Squeeze the biggest refund out of PODS first, then claim only the remainder from the Clinic. A PODS refund is tax-free; a Clinic reimbursement is taxed as salary (2026 rule), so a PODS dollar is worth roughly 35 to 40% more in your pocket. This "hybrid" has the upside of a full PODS refund and the safety net of the Clinic: if PODS pays nothing, you simply claim it all from the Clinic. Zero risk either way.
- The per-diem credit, fee waivers, and any out-of-pocket essentials stack on top, clean. They compensate a different loss (the disruption), not the transport charge, so keeping them alongside a Clinic claim is completely proper.
Two hard lines. (1) Never claim from the Clinic a transport cost PODS refunded, that is a false expense claim, and for a physician on an H-1B visa the downside (job, then visa) dwarfs the money. Claim only what PODS did not refund. (2) Never mention the Clinic, the reimbursement, or any of this netting to PODS. To PODS, the transport charge is simply money paid for a service they did not perform. The order is always: settle PODS first, file the Clinic claim after (Haseeb starts around Aug 30; relocation claims process at or after start anyway).
The order of play
Today is Wednesday, July 8. Do the TONIGHT block first, in order. Each later tier fires only if the one before it didn't resolve things.
| When | Step | Channel | What it does |
|---|---|---|---|
| DONE | Evidence preserved + Message 1 (written record) logged; Jeanrenaud B brush-off screenshotted | MyPODS chat | The paper trail starts clean |
| TONIGHT 1 | Log Message 2 (formal demand, refund now included) | MyPODS chat | Notice then demand then escalation, in that order, before any third party looks |
| TONIGHT 2 | File the BBB complaint (refund included, brush-off added) | bbb.org | The fastest reliable route into PODS's resolution team; get the case number |
| TONIGHT 3 | File the FMCSA complaint (record/pressure) | nccdb.fmcsa.dot.gov | Adds a federal-record line the exec email can cite (see caveat below) |
| TONIGHT 4 | Send the executive email (cite the BBB + FMCSA numbers) | Email (Schutte, Schwartz + cc) | People who can actually re-route a truck; a new CEO who cares how this looks |
| TONIGHT 5 | Fire the social-team pincer: public tweet + DM + email, same hour | X (@PODS) + socialmedia@pods.com | The channel answering same-day this week; three doors to one team |
| TONIGHT 6 | Reply to the "ACTION REQUIRED" email (2 lines) | Email/portal | Records you stood ready and disputes the $75-fee predicate |
| TONIGHT 7 | Submit the Elliott Advocacy form | elliott.org/help | Free mediation by the org whose contacts page PODS execs know they are on |
| JUL 9 AM | One scoped billing call, charges only | 855-304-9887 | Kill the card hold, the $75 fee, the $234.45; get a reference number |
| JUL 9 AM | Certified mail Messages 1 + 2 | USPS to Clearwater HQ | Perfects the contract's 60-day notice (deadline Sept 6); about $10 |
| JUL 9 NOON | Only if no firm written date + named human: TV troubleshooter tips + LinkedIn DM to the CEO | News 5 / Fox 8 / LinkedIn | Proven to move PODS within 24h once a reporter bites |
| JUL 10 | Call the main line, ask for "Customer Advocacy" by name, BBB case number in hand | (855) 706-4758 | The call that reaches the team the front line refused to connect |
| IF JUL 14 SLIPS | Ohio AG + NY AG complaints; then the louder public wave (Reddit, reviews, second media) | ohioprotects.org + more | Compensation + pattern pressure; will not save the date, so it is post-deadline |
| AFTER DELIVERY | Visa card dispute, only on the fee class and any un-refunded amounts | Haseeb to his Visa issuer | Held until after delivery: a chargeback now risks a lien on the goods |
FMCSA caveat: because PODS is a "you-pack" container service, the federal moving-carrier rules don't strictly govern our dispute. The FMCSA complaint is a record and pressure lever (it adds a federal line to the exec email), not our main legal hook. Our real hooks are the contract, the card-dispute right, and state consumer-protection law.
Who to contact (the whole list, in one place)
- MyPODS chat (main written channel): log in as Munim on Haseeb's account, open the message box on the order page, paste. Do NOT reply to their system emails (no-reply).
- Executives (verified): pschutte@pods.com (Phil Schutte, Director of Operations), rschwartz@pods.com (Rich Schwartz, SVP Corporate Operations).
- Executives (best-effort, may bounce, harmless if so): jgimeson@pods.com (Jim Gimeson, CEO since Jan 2026), ssalazar@pods.com (Salvador Salazar, SVP Sales & Service). These are pattern-guessed, not confirmed; if they bounce, the verified two carry the thread.
- Social team: @PODS on X (public tweet + DM) and socialmedia@pods.com (their own funnel).
- Billing (charges only): 855-304-9887. Main line / Customer Advocacy: (855) 706-4758 or 877-770-7637. Text: 697637.
- BBB: bbb.org, file against PODS Enterprises, LLC (Clearwater FL profile).
- FMCSA: nccdb.fmcsa.dot.gov (or 1-888-368-7238), against PODS ENTERPRISES LLC, USDOT 1397252.
- Elliott Advocacy: elliott.org/help (free mediation form).
- Media (hold until Jul 9 noon): News 5 Cleveland InvestigatorTips@wews.com (Jonathan Walsh, Troubleshooter); Fox 8 I-Team tip form.
- Regulators (hold for a Jul 14 miss): Ohio AG ohioprotects.org; NY AG (origin was Brooklyn).
- Certified mail: PODS Enterprises, LLC, 5585 Rio Vista Drive, Clearwater, FL 33760.
The contradiction packet (build this first, it powers everything)
The single most powerful thing you can attach anywhere is a one-page PDF that puts, side by side:
- The July 8 "as you requested" change-notice email, and
- The July 8 "ACTION REQUIRED: confirm July 10" email (with the $75 fee and card hold), and
- PODS's own driver note from the revised order: "cx request an early delivery if possible."
Three timestamps, one page. It converts "the customer says we were slow" into "our own documents contradict each other in writing," which is the exact shape of evidence an executive cannot leave sitting in a reporter's or regulator's hands. Attach it to the executive email, the social DM, and (later) any reporter.
I can build this packet for you from the emails and the change-order PDF already in the case file; just say the word and I'll produce the one-page PDF ready to attach.
The messages (copy and paste)
Each message has a Copy button and a clear "Send to". Tap Copy, paste into the channel named on that message. Nothing sends by itself. The Send tonight ones are the priority block.
Hi, I am Munim Moiz, the authorized contact on order #600687425 (account holder: Haseeb Moiz). I am confirming in writing my phone call today, July 8, 2026 at 2:21 PM, with your representative Ian, because I was told these details could not be provided in writing. On that call, PODS stated the following: - Container 18884VX had been lost. I was verbally assured the contents are not damaged; no inspection was described, I cannot verify that statement, and all rights regarding the condition of the contents are reserved until delivery and inspection. - The container may now arrive around July 13, with delivery around July 14. My online account still shows July 24, 2026. - PODS offered $100, and said anything further requires escalation to Customer Advisory. For accuracy of the record: 1. Neither I nor the account holder requested any change to the delivery date. The email titled "As you requested" is incorrect. Our delivery was confirmed for July 10, 2026, and PODS's own revised order confirmation (Quote 405866574) records in the driver notes that we asked for an earlier delivery. Please correct your records to reflect that this change was carrier-initiated. 2. We do not accept July 24 as a delivery date. Both account users are out of state July 15 through July 27; a delivery attempted in that window cannot be received, and any fee or storage charge arising from it would result from the carrier-initiated delay. 3. Please confirm in writing that: (a) the pending $234.45 redelivery charge, now showing a July 23 date, will not be charged; (b) the $75 service fee in the "ACTION REQUIRED" email will not be applied and no card hold will be placed on July 9; and (c) no promotional-rate recalculation, additional rental month, or storage fee will be charged as a result of this delay. 4. Regarding the $100: we decline it as a final resolution. If PODS applies it as an unconditional goodwill credit, we accept it only on the express understanding that it does not settle, release, or waive any claim relating to this order. 5. Please state in writing the reason for the delay, the container's current location and last scan date, and preserve all records relating to this order, including call recordings, case notes, container scan history, and dispatch records. This message is written notice of claim under the rental agreement. Nothing in it accepts the revised delivery date, waives any right or claim, or settles any dispute; all rights and remedies under the rental agreement and applicable law are expressly reserved. If any part of this summary is inaccurate, please correct it in writing within 48 hours; otherwise we will rely on it. Munim Moiz, authorized contact for Haseeb Moiz (account holder)
This is our formal demand and notice of claim regarding order #600687425, customer #203973434, container 18884VX, under the Services Agreement accepted June 25, 2026. I am Munim Moiz, the authorized contact, writing on behalf of the account holder, my brother Haseeb Moiz. The facts, per your own documents. PODS collected our fully loaded container in Brooklyn on June 27 and committed in writing to deliver it to our Cleveland residence on July 10 (original Order Confirmation; re-confirmed by your July 8 "ACTION REQUIRED: Confirm your delivery" email, which we confirmed). On a 2:21 PM call on July 8, your representative Ian told us the container had been LOST, estimated delivery around July 14, offered $100, and declined to put any of this in writing. Your portal now shows July 24. When I then asked your chat agent only to log my written claim and give me a reference number, the agent replied he was "unable to assist," provided no reference number, and ended the chat. Your written record is false and requires correction. Your July 8 change notice states the order was updated "As you requested." We never requested a change to a later date. The only delivery-date request we ever made was for an EARLIER delivery, which is exactly what your own driver note records: "cx request an early delivery if possible." PODS moved the delivery roughly two weeks later, after losing the container, and then attributed that change to us. Misplacing a container within PODS's own network is not a circumstance beyond PODS's reasonable control. What we require, as a single package, in writing, by end of day Thursday, July 10: 1. Delivery on or before July 14, 2026, confirmed in the MyPODS system and by email. A verbal date is not a commitment. A delivery attempted after July 14 cannot be received, and any resulting fee will be disputed. 2. Refund of the transportation charge of $1,670.11 (long-distance transit $1,601.26 plus the $68.85 fuel surcharge). PODS was paid this amount to transport a container it admits it lost; the transportation service was not performed as agreed. 3. Displacement compensation of $75 per day, from July 10 until actual delivery, consistent with PODS's own goodwill practice: $300 if you deliver July 14; $1,050 at your currently scheduled July 24. This compensates the service failure and displacement itself and is separate from, and additional to, the transportation refund above. 4. Waiver of the $234.45 redelivery fee scheduled for July 23, and of any missed-delivery fee or card hold prior to actual delivery. Any such fee charged will be disputed with the card issuer under 12 CFR 1026.13 as a charge for services not rendered. 5. Written confirmation that no promotion reversal, additional rent, or storage charge will be assessed as a result of this PODS-caused delay. 6. Written correction of the July 8 "as you requested" notice, confirming the change was initiated by PODS for operational reasons and that the customer had requested earlier delivery. 7. So we can understand what happened, please also provide in writing: (a) the date, time, and facility of container 18884VX's last physical scan before July 8; (b) the date PODS first determined the container was misrouted or could not be located; and (c) whether that determination predates the July 8 "ACTION REQUIRED" email that still confirmed July 10 and referenced a $75 fee and a card hold. Please treat the container scan history and the send logs for both July 8 emails as within the records-preservation request above. The $100 offered by phone is not a resolution of this matter. I accept it only as an unconditional partial goodwill credit that settles or waives nothing. All rights are reserved under the Services Agreement, the Florida Deceptive and Unfair Trade Practices Act, and the Ohio Consumer Sales Practices Act. Absent a written response meeting the above by end of day Thursday, July 10, we will proceed with complaints to the Better Business Bureau and the appropriate state authorities. Munim Moiz, authorized contact, for Haseeb Moiz (account holder)
PODS solicited my confirmation of, and pre-authorized charges for, a delivery it already knew it could not perform, then told me in writing that the resulting two-week change was "as you requested."
We moved our household from Brooklyn to Cleveland (Order #600687425; the account is in my brother Haseeb Moiz's name and I am the authorized contact). PODS picked up our loaded container on June 27 and committed in writing to deliver it on July 10. Its own July 8 email still confirmed July 10, and we confirmed.
That same day a PODS representative told us by phone that the container had been LOST. He offered $100, refused to provide anything in writing, and refused to document the reason for the delay. The portal now shows July 24. PODS then sent a written change notice stating the order was updated "As you requested." That is false. We never asked to move the delivery later; the only delivery-date request we ever made was for an EARLIER delivery, which PODS's own driver note records ("cx request an early delivery if possible"). PODS moved the date roughly two weeks later after losing our container, then papered its file to make the change look customer-requested.
When I asked the live-chat agent only to (1) confirm my written claim was logged on the order and (2) escalate it with a reference number, the agent replied that he was "unable to assist you with this matter," referred me to a billing phone number, and ended the chat. A supervisor callback promised earlier the same day never occurred. PODS has provided no reference number, no written reason for the delay, and no written response of any kind.
Everything we own is in that container. We are camping in an empty apartment on an air mattress and have kept interim costs to a minimum. Nobody can receive after mid-July, so the July 24 date will fail. Despite this, PODS still intends to charge a $234.45 redelivery fee for the delivery it failed to make.
Desired resolution: (1) delivery on or before July 14, confirmed in writing; (2) refund of the $1,670.11 transportation charge for a transport that was not performed as agreed; (3) waiver of the $234.45 redelivery fee and any missed-delivery fee or card hold before actual delivery; (4) written confirmation that no promotion reversal, added rent, or storage charge will result from PODS's delay; (5) written correction of the false "as you requested" notice; (6) displacement compensation of $75 per day from July 10 until actual delivery.
Subject: Order 600687425: PODS admits container lost, July 10 commitment now July 24, receiving window closes July 14 Dear Mr. Schutte and Mr. Schwartz, I am asking for executive help because your front line has failed at every step. The facts, all documented: 1. Order 600687425, container 18884VX, Brooklyn NY to Cleveland OH. $3,051.15 paid, of which $1,670.11 is the transportation charge. 2. On July 8 your representative Ian told us by phone that PODS has lost the loaded container. Delivery was committed for July 10. Your system now shows July 24. Ian mentioned roughly July 13 but nothing is in writing and his promised callback never came. 3. On July 8 PODS emailed us a date-change notice described "as you requested." We never requested a later date. The only delivery-date request we ever made was for an EARLIER delivery, which your own driver note records. That contradiction is in writing on your side. 4. The same day, your chat agent refused to log or escalate a written claim, gave no reference number, and ended the chat. Your "ACTION REQUIRED" email still shows July 10, a $75 fee, and a card hold. 5. Hard constraint: someone can be home to receive only through July 14. After that nobody can receive, and the July 24 date fails completely. What I am asking for: (1) delivery on or before July 14, confirmed in writing today with a named owner; (2) removal of the $75 fee and the card hold; (3) refund of the $1,670.11 transportation charge for a transportation service that was not performed as agreed; (4) a Customer Advocacy case number. A formal written demand and a BBB complaint have been filed, and an FMCSA household-goods complaint has been filed against USDOT 1397252. I would much rather this be solved by your team than by regulators or reporters. One call or email with a firm pre-July-14 date resolves it. Munim Moiz (authorized contact on the account) [your phone number]
@PODS lost my family's loaded container (order 600687425, Brooklyn to Cleveland). Your own rep admitted it by phone on July 8. Delivery was promised July 10, now shows July 24 in your system. Then you emailed me an "as you requested" date change I never requested, plus a $75 fee. Please fix this.
Order 600687425, container 18884VX. The facts: your rep Ian admitted on July 8 the loaded container is lost. Delivery was committed for July 10; your system now says July 24. Your own driver note says we asked for an EARLIER delivery, yet your email calls the delay "as you requested." Someone must be home to receive, and that window closes July 14. I need: (1) a delivery date on or before July 14, in writing, today; (2) the $75 fee and card hold removed; (3) refund of the $1,670.11 transportation charge; (4) a named senior associate and a Customer Advocacy case number. A written demand, a BBB complaint, and an FMCSA complaint (USDOT 1397252) have all been filed today.
For the record: I was ready to receive on the committed July 10 date and remain ready through July 14. I do not accept the July 24 date, and I dispute in advance the $75 fee and any card hold, as both arise from a delay PODS caused by losing the container. Please confirm a delivery date on or before July 14 in writing.
Subject: PODS admits it lost a family's entire household mid-move to Cleveland, then billed them a $75 fee Hi Jonathan, My brother and I just moved to Cleveland. PODS picked up our loaded container in Brooklyn and committed delivery for July 10. On July 8 a PODS rep admitted on the phone that the company has lost the container, everything we own. Their system then quietly moved delivery to July 24. It gets stranger: PODS emailed us a date-change notice saying the delay was "as you requested." Their own driver note, which we have, says we asked for an EARLIER delivery. The same day their chat agent refused to log a complaint, and their billing system added a $75 fee and a hold on our card, for the delivery they lost. We paid $3,051.15. Nobody can be home to receive after mid-July, so their new date fails entirely. I have every email, the invoice, and a timeline ready to send. In 2022 your 6abc colleagues in Philadelphia ran the same story and PODS fixed it within 24 hours. Happy to talk today. Munim Moiz, Cleveland (University Circle area), [your phone number]
PODS accepted payment under a $3,051.15 moving order, promised and re-confirmed in writing a July 10 delivery of our household goods, then admitted by phone on July 8 that it had lost our loaded container, moved delivery to July 24 without our consent, and refused to document any of it. I believe this violates the Ohio Consumer Sales Practices Act (R.C. 1345.02). Three practices: (1) A false written record: PODS's July 8 notice says the order was updated "As you requested," when we never requested a later date and PODS's own driver note records that our only date request was for an EARLIER delivery. (2) Promising delivery without reasonable measures to perform it: PODS confirmed July 10 as late as July 8 while, by its own admission, it could not locate the container (OAC 109:4-3-09(A)(1)). (3) Charging for the failed service: a $234.45 redelivery fee for a delivery it failed to make, plus warned further charges from its own delay. The delay has left our household without mattresses, bedding, clothing, or cookware; we are sleeping on an air mattress. PODS's only offer is $100, verbal, with a refusal to put anything in writing. Resolution sought: delivery by July 14 confirmed in writing; refund of the $1,670.11 transportation charge for a transport not performed as agreed; waiver of the $234.45 redelivery fee and related fees; written assurance of no promotion reversal or added storage charges; written correction of the false record; and displacement compensation of $75 per day from July 10 until actual delivery.
On the phone
Announce recording: "Just so you know, I'm recording this call for my records." (Safe everywhere when announced.)
Tomorrow's billing call (855-304-9887), charges only. Open with: "I'm only calling about pending charges on order 600687425, nothing else." Get the July 9 card hold, the $75 fee, and the queued $234.45 redelivery each waived or annotated, get a reference number, hang up. Do NOT negotiate compensation here (that belongs in writing with Customer Advocacy). If billing says they can't touch them, that refusal is useful evidence too.
Always get a name and a case number. On every call and chat, say: "Please open or reference a Customer Advocacy case and give me the case number." Write down the person's name and direct line, and go back to that same person on every follow-up. Front-line agents will not volunteer the advocacy team; you have to ask by name.
Decline the $100 without waiving anything: "I appreciate the gesture, but $100 against a lost container on a $3,000 move isn't a resolution. Please escalate to Customer Advocacy. I'm not rejecting compensation, I'm declining this amount as final. If you apply the $100 in the meantime, I accept it only as a partial goodwill credit, not settlement."
Timing questions: ask at most one, lightly ("just so I understand, when was it actually lost, and when did you find out?"). Save the full set for the written demand.
Do and Don't
Do
- Keep everything in writing and screenshot after each send.
- Stay calm and factual. You are the reasonable, documented party.
- Hit the fast channels tonight: exec email + social team, not just the front line.
- Get a name and a case number on every call; keep going back to that person.
- Pin the July 14 date in writing; line up Haseeb as backup receiver (to ~July 20).
- Settle PODS first, then file the Clinic claim for the remainder only.
Don't
- Accept $100 or the words "full and final."
- Ask a front-line agent to fix or decide anything, they can't.
- File a card dispute before delivery (it can trigger a lien on your goods).
- Threaten to sue (the contract forces a Florida court; the threat is empty).
- Ever mention the Clinic or the reimbursement to PODS.
- Sign any NDA / "goodwill for silence" before delivery and inspection.
What could go wrong (and the counter)
- They slow-walk to July 24 anyway
- Most likely. Do NOT cancel the July 24 slot until a July 14 date is confirmed in the system (never trade a bad date for no date). Haseeb is the backup receiver to ~July 20. If it still slips, the media + regulator tier fires.
- They say "it was the third-party carrier, beyond our control"
- Expected. The counter: a subcontractor misplacing a container in the ordinary course of the service PODS sold is within PODS's control; their own rep called it "lost," not stolen or weather. Keep framing it as loss + false record + improper fees, never as "you were late."
- A small credit appears and the file is marked "resolved"
- Their known playbook. Reply the same day: "The $X credit is noted; it is not accepted as resolution of any part of this matter." Scan every offer for "full/final/release/settlement."
- Over-escalation flips them to legal-defense mode
- Only happens if we threaten suit or flame publicly. We don't. Everything stays factual; statutes appear only in the regulator complaints, never in the PODS-facing messages. Louder public posts stay holstered while the BBB round is live.
- They offer money for silence (an NDA) before delivery
- Decline the condition. Delivery first, compensation second, confidentiality never before the container is delivered and inspected.
- The container arrives damaged
- Photograph everything at unload before signing anything. The $10,000 contents protection (XN Financial, cert 4-150-1-1293577) is the channel, and it has a short post-delivery claim deadline, so act on delivery day.
Plain-English glossary
- Restitution vs consequential damages
- Restitution is getting back money you paid for a service not performed (the $1,670.11 transport refund), the contract does not block this. Consequential damages are knock-on costs (hotels, stress), which the contract does block, so we never ask for those.
- Route C / netting (the reimbursement rule)
- Get the most you can back from PODS (tax-free), then claim only the un-refunded remainder from the Clinic. Recovers the cost once, keeps the most after tax, and carries zero risk.
- Customer Advocacy
- PODS's internal escalation team with authority to actually resolve. Front-line agents will not connect you unless you ask by name and, ideally, have a BBB case number in hand.
- BBB (Better Business Bureau)
- A private complaints body PODS responds to (and has issued full transport refunds through, on lost-container cases). Reliable, but responses take days, so it is our record + compensation lever, not the thing that saves the date.
- Card dispute (chargeback)
- Asking the card's bank to reverse a charge. Only Haseeb (the cardholder) can file it, and only after delivery: doing it while PODS holds the goods can trigger a lien.
- Lien
- A right the contract gives PODS to hold your goods until amounts it claims are paid. This is why we never file a chargeback before the container is in the apartment.
- FMCSA / NCCDB
- The federal transport regulator and its complaint database. For a "you-pack" service its rules don't strictly govern us, so we file it as a record + pressure lever, not as our main legal hook.
- Notice of claim / reservation of rights
- A written heads-up (required within 60 days) that you have a complaint, plus a line saying "nothing here gives up any of my rights," so replying or taking a partial credit doesn't accidentally settle everything.