Subject: Returns process notes - for the new system integration project
From: project mailbox note, undated (found in shared drive, author unclear)

Here's roughly how our returns process works, as far as I remember from
sitting in on a few cases last year. Writing this from memory for the
integration project since nobody could find an up-to-date writeup.

A customer sends in a refund request, usually by email. Someone on the
Returns team looks at it and decides whether to approve it. If it's
approved, we send the customer a form and ask them to send the item back.

Once the item arrives, the warehouse checks it's actually the right item
and in acceptable condition, and then Finance processes the refund
straight back to the customer's original payment method. That's
basically the end of it - I don't think there's a formal "close the
case" step, it just kind of ends when the money's been sent.

A few things I'm not sure about / don't think happen:

- I don't remember us tracking inventory specifically as part of this
  process - that's probably a separate warehouse system thing, not
  something the Returns process itself does.
- I don't recall there being an escalation step if something's wrong
  with the request itself (missing info, customer doesn't respond,
  whatever). I think we just reject it and move on - no supervisor gets
  involved as far as I've seen.
- Replacements - I think we only ever issue refunds, not replacement
  items, but I could be wrong about that.

One thing I do remember clearly: we always call it a "Refund Request"
internally, not a "Return Request" - the two terms get used
interchangeably by customers but "Refund Request" is what's on all our
internal tickets and in the old training material.

Hope this is useful as a starting point - happy to be corrected on any
of it, it's been a while since I was closely involved.
