Submit a Support Request

6. Choose a subject that identifies the action

A useful subject describes the issue you want handled, such as fit question for Metro Grid12, address correction for an order or tracking clarification. A subject containing only help gives little context. Name the product when no order exists and the order reference when one does. Do not place a full home address or payment credential in the subject. The first line of the message should say what happened and what you need next. Distinguish a request for information from a request to change an order, because the team should not infer a financial or fulfillment action from a general question.

If two unrelated issues need review, identify them as separate requests in the message rather than hiding the second action in a long story. Keep the wording factual. A clear subject helps preserve the intended scope when you reply with new information later.

7. Identify the relevant product or order

For a product question, include the exact title or SKU and the size you are considering. For an existing purchase, include the order reference and the affected design, size and quantity. A phrase such as my blue jersey can be ambiguous across the independent catalog. Do not assume that a support reader can identify an order from a cropped image of the number on a jersey. A bag screenshot does not establish that an order was completed. Explain which record you actually have, and if you have no confirmation say that directly. The team must locate the real record before describing its stage.

Use a private support message for order identifiers. You do not need to publish them in a comment. If multiple lines are affected, list the specific lines so the team can distinguish a whole-order request from a question about one jersey.

8. Describe the result you expected

State the intended result and the actual result. For a website issue, this might be the size you selected and the different bag label you see. For a received-item issue, it might be the ordered design and the item that arrived. This comparison is more useful than saying everything is wrong. Identify whether the mismatch concerns appearance, size label, quantity, destination or a financial amount. The team needs enough factual detail to choose the right investigation rather than guessing from the emotional urgency of a message. A generated mockup should not be treated as a verified measurement chart.

Keep the request precise and avoid adding unrelated assumptions about a supplier, carrier or payment processor. If a fact is uncertain, label it as uncertain. For example, say that you cannot locate a parcel rather than claiming a specific person took it without evidence.

9. State the outcome you want

An explanation, correction, cancellation, exchange and refund are different outcomes. State which one you are requesting so support can review the actual order stage and relevant policy. A tracking question alone does not authorize a refund, and an exchange request should not be silently converted into cancellation. If you are comparing options before deciding, say that you want information first. The store should explain what is confirmed and what requires review. Do not assume that a request automatically changes a record merely because the message was sent.

If your preferred outcome changes while the issue is open, state the new request near the start of the reply. Identify whether it replaces the earlier request or adds another question. This prevents the conversation from carrying conflicting instructions that appear equally current.

10. Include dates that explain the concern

Give the date or approximate time of the relevant event, such as the bag update, order attempt, dispatch notification, delivery event or refund approval. Distinguish those stages instead of using one date for all of them. A label creation date differs from carrier acceptance, and a return request date differs from refund approval. If timing matters for a personal event, name the needed date without assuming the store has guaranteed it. The team must compare actual records and any confirmed commitment rather than inventing a delivery appointment from a reference site.

You do not need to send a complete unrelated calendar or message history. Include the event that matters and any new development. When following up, state what changed since the previous message so the team can identify the new information quickly.

11. Attach relevant evidence safely

A screenshot should show the page or line needed to understand the problem. Hide unrelated addresses, balances, account numbers and other people’s private information. A product condition image should show the condition being discussed, not an identity document. If a shipment label is relevant, provide only the detail needed for the actual private investigation. Never attach passwords, authentication tokens or full payment credentials. The purpose of an attachment is to establish a specific fact, not to grant access to an account.

Explain which part of the attachment matters. A large collection of unexplained images can leave the issue less clear. For a selector problem, identify the intended size; for a partial delivery, identify the missing line. The team should request clarification connected to the issue rather than unnecessary sensitive material.

12. A fit or garment specification ticket

Name the design and proposed size, then ask for the actual fact you need: confirmed chest width, body length, material composition or care instructions. Explain the units and measuring points if you are comparing another garment. A named sizeS–5XL does not establish an exact dimension. The generated appearance gallery does not replace a care label or physical specification. If the fit question concerns room for a layer, describe that preference directly. You do not need to send a personal body photograph to ask about a garment measurement.

The store should distinguish confirmed specifications from unresolved facts. If an exact measurement is important to your purchase, wait for an actual answer rather than importing a chart from another supplier or a league shop. Keep the product reference in the conversation so the requested fact stays connected to the correct item.

13. An order-change ticket

State the order reference and exactly which old detail should become which new detail. An address correction should include the complete intended replacement privately, while a size change should identify the design, current size and proposed size. Quantity changes and cancellations need their own explicit wording. The actual fulfillment stage determines what can be reviewed; a working request window does not guarantee reversal after dispatch. Do not place another order as an assumed correction unless you intend a separate purchase.

Wait for confirmation of the reviewed action rather than treating the sent email as proof that the order changed. If a proposed change affects the amount, use the verified next step rather than sending an additional payment through an unfamiliar link. The cancellation/change-order policy explains the stage distinctions.

14. A shipment or partial-delivery ticket

Provide the order reference, any genuine tracking reference and the latest event wording and date. Distinguish label created, accepted, in transit, attempted delivery and delivered. If several jerseys were ordered, identify the lines received and unresolved. Do not assume that one parcel reference represents the entire order without confirmation. For a delivered-but-missing concern, explain the normal receiving places already checked. Support needs the actual shipment record before describing a carrier investigation or approving a replacement.

If an unexpected message requests payment or login information to activate delivery, report the request without supplying the secrets. Name the sender and reference needed to understand the concern. Keep shipment questions separate from a requested cancellation or refund so the intended action is clear.

15. A return or refund ticket

Start with the order reference, delivery date, affected design/size/quantity and whether you want an exchange or refund. The store’s60-day window and no-restocking-fee policy provide the starting terms, while authorization and return-shipping responsibilities depend on the actual case described in the linked policies. Do not send a parcel to a guessed address. An approved refund follows the7-calendar-day timeline to the original payment method; a request alone is not approval. If the concern is an incorrect or damaged item, describe the specific mismatch or condition.

Keep the approval notice when following up about refund timing. Do not provide a full card number or authentication code to investigate it. If you change from an exchange to a refund, state that explicitly rather than leaving the preferred outcome hidden inside a tracking update.

16. A rights or privacy ticket

For a rights concern, identify the exact URL and material, the right involved and whether you own the right or act for the owner. Copyright, trademark and name/likeness issues can require different facts. For a privacy question, identify the interaction or record you want explained or corrected without sending unnecessary personal documents. These requests should remain focused on the material or processing issue rather than unrelated accusations. The store does not invent a registered designated-agent status, legal jurisdiction or provider fact to answer a gap in the request.

Use the DMCA, intellectual-property and privacy pages for the relevant contact guidance. If a formal legal process applies, its actual requirements must be considered separately. Keep the private message precise and avoid publishing sensitive information while trying to ask that it be protected.

17. Follow up and close the issue clearly

Reply in the existing conversation for the same issue and add new facts near the start. State whether the requested outcome remains the same. Repeated messages through separate conversations can describe inconsistent scopes and obscure the latest instruction. When the issue is resolved, identify the result you can actually confirm, such as receipt of the missing line or confirmation of a reviewed change. Do not assume that one resolved parcel closes another unresolved item. If the issue remains open, name the specific next fact or decision you need.

The response target is a working estimate until mailbox and operational staffing are confirmed, not an invented guaranteed service commitment. For a time-sensitive concern, explain the date and relevant reference in the first message. Keep the conversation useful by separating verified facts, open questions and the actual action you request.