Skip to content
Hypamoon

For teams that run on Sendcloud

Sendcloud claim: keep each deadline in view

In Sendcloud the time to file a claim depends on the carrier and the type of claim, from a few days for damage to several weeks for a lost parcel, and each type asks for its own papers. With your own carrier contract the claim goes to the carrier directly.

How it goes today

  1. Notice a parcel is lost or damaged when the customer gets in touch.
  2. Look up the claim deadline for that carrier and type in the help center.
  3. Ask the customer for photos, a signed statement or the packaging.
  4. Fill in the claim form per parcel and track its progress in a spreadsheet.

How it can go

Know which parcels need a claim, by when, and which papers you still need.

Parcels without a new scan for longer than you set, or reported as damaged or returned, go on a claim list with the carrier, the type of claim and the date it has to be in, based on the deadlines in the Sendcloud help center for your carriers. Your customer gets a short form for the photos or statement that type needs. When a file is complete you get a reminder to submit it in Sendcloud, and the list keeps the outcome.

Say this in ChatGPT, Claude or Copilot

Your chat gets connected to Hypamoon first, with this request filled in. You paste your Sendcloud key in the portal, never in the chat.

Your request

With Hypamoon, keep a claim list for our Sendcloud parcels. Add parcels that have had no new scan for five working days, or that the carrier reports as damaged. Show the carrier, the type of claim and the last day to file it, using the deadlines from the Sendcloud help center for our carriers. Send the customer a short form for the photos or statement we need, remind me when a file is complete or a deadline is three days away, and note the outcome.

You create the Sendcloud key yourself under Settings, Integrations, Sendcloud API. It stays yours.